fix(common.jolokia2): Add Jolokia 2.x compatibility for proxy target tag #18195
+204
−4
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.
Summary
Jolokia 2.x changed the response format for proxy requests. The target URL is now returned under
request.options.targetinstead ofrequest.target(Jolokia 1.x format).This change adds support for both formats by checking both locations when extracting the target URL for the
jolokia_agent_urltag.Without this fix, metrics from
jolokia2_proxyplugin using Jolokia 2.x are missing thejolokia_agent_urltag, making it impossible to distinguish metrics from different proxy targets.Checklist
Related issues
resolves #18194