Skip to content
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

Metricbeat: Ensure canonical naming for JMX beans is disabled (backport of #7047 to 6.3) #7061

Merged
merged 1 commit into from
Jun 14, 2018

Conversation

jsoriano
Copy link
Member

@jsoriano jsoriano commented May 9, 2018

Canonical naming for JMX beans in Jolokia is enabled by default, this
orders mbean fields, what breaks metricbeat internal mapping.

We were already setting these options in the url, but url parameters are
ignored in POST requests. This change adds these parameters as part of
the body.

…c#7047)

Canonical naming for JMX beans in Jolokia is enabled by default, this
orders mbean fields, what breaks metricbeat internal mapping.

We were already setting these options in the url, but url parameters are
ignored in POST requests. This change adds these parameters as part of
the body.
@jsoriano
Copy link
Member Author

jenkins, test this again, please

@ruflin
Copy link
Contributor

ruflin commented May 11, 2018

This should not be merged before 6.3 is released as I don't think this is a critical bug fix.

@ruflin ruflin merged commit 9a51f38 into elastic:6.3 Jun 14, 2018
@jsoriano jsoriano deleted the backport_7047_6.3 branch June 20, 2018 17:32
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…c#7047) (elastic#7061)

Canonical naming for JMX beans in Jolokia is enabled by default, this
orders mbean fields, what breaks metricbeat internal mapping.

We were already setting these options in the url, but url parameters are
ignored in POST requests. This change adds these parameters as part of
the body.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants