jmx-metrics: allow any resource path for classpath resources rules #15413
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 an oversight in #15220, which I unfortunately only discovered when plumbing this new API in jmx-scraper with open-telemetry/opentelemetry-java-contrib#2446.
This PR adds a more versatile
JmxTelemetryBuilder#addRulesas replacement, this allows to load JMX metrics rules from anyInputStream, not only the classpath resources injmx/rules.The following methods are not yet annotated with
@Deprecatedto prevent having to deal with changes when the dependency of contrib to instrumentation is updated, they should be replaced withJmxTelemetryBuilder#addRulesin the future:JmxTelemetryBuilder#addClassPathRulesJmxTelemetryBuilder#addCustomRulesThis limitation currently makes loading "legacy" metrics definitions in jmx-scraper more complicated than necessary (see open-telemetry/opentelemetry-java-contrib#2446 for details).