Fixed adding the same metric family more than once when there are many mBeans #24
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.
In current version, when there is more than one connector (e.g. AJP and HTTP connector), metrics for each connector is added as many times as number of connectors. This lead to the
/metrics
endpoint being unparsable for the Prometheus.Consider the below example of this issue:
As you can see, five metric families are added twice, each of them having two metric instances inside.
These metric families are:
tomcat_threads_total
,tomcat_threads_active_total
,tomcat_threads_max
,tomcat_connections_active_total
andtomcat_connections_active_max
.