-
Notifications
You must be signed in to change notification settings - Fork 870
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Attempt to align and cleanup some jmx metrics #11621
Draft
SylvainJuge
wants to merge
17
commits into
open-telemetry:main
Choose a base branch
from
SylvainJuge:jmx-metrics
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+103
−90
Draft
Changes from 16 commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
02b5448
tomcat prefix + fix busy/idle threads
SylvainJuge cf15127
tomcat align network metric/attributes
SylvainJuge d450d9a
wildfly align 'sessions' in plural form
SylvainJuge 5c7688b
wildfly align network.io with semconv attributes
SylvainJuge 4b966cc
update documentation
SylvainJuge 2349720
clarify doc
SylvainJuge cc85a16
doc again
SylvainJuge 64e9cdd
reformat example
SylvainJuge aa41343
jetty singular thread metrics
SylvainJuge 3f9b71e
tomcat move to 'request' namespace
SylvainJuge fe09251
tomcat singular session
SylvainJuge 931032b
singular units + tomcat fix
SylvainJuge 313ed49
fix tomcat request reference + clarify a bit
SylvainJuge 545a066
fix doc for tomcat.thread.*
SylvainJuge cb27853
wildfly align with upcoming semconv
SylvainJuge 286d784
wildfly transaction name fits mbean attribute
SylvainJuge fb71fa1
simplify metrics for wildfly
SylvainJuge File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unless I'm missing something, the metric will have a metric attribute which will always have the same constant value. What is really the point of having such an attribute?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are correct here, having a constant metric attribute only makes sense to provide breakdown of the same metric, occurences of
wildfly.db.client.connection.usage
should be renamed towildfly.db.client.connection.count
. I am currently trying to validate with the implementation if there is an overlap between the connection states or if it's an effective partition (in which case we can provide a breakdown).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When looking at the implementation and the wildfly test cases it seems that we have:
https://github.com/wildfly/wildfly/blob/841fea771567a71d06490a0d7e9a398dc6fdf5c0/testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/jca/statistics/DataSourcePoolClearStatisticsTestCase.java#L69
https://github.com/wildfly/wildfly/blob/841fea771567a71d06490a0d7e9a398dc6fdf5c0/testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/jca/capacitypolicies/ResourceAdapterCapacityPoliciesTestCase.java#L143
Given that both
InUseCount
andIdleCount
refer to physical connection states in documentation, they effectively form a partition and then using a common metric with a constant attribute foridle
|used
makes sense.For
WaitCount
this is about the number of logical connections that are waiting for a physical connection, so it would also make sense to use the same metric with a customwait
constant attribute.When aggregating and removing attributes this would return the total number of logical connections to the database pool, and only a subset with either
idle
orused
attribute value would be the physical connections.I have updated this PR to match this in fb71fa1