-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Enable checks for jolokia documented fields #10979
Conversation
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.
I might be wrong but I think that when you add a new field and you run make update
more files than the ones present here are updated. I think that docs and metricbeat.reference.yml
. Can you double check?
@sayden this is a field for output metrics seem like, not a config field 😄 that's why metricbeat.reference.yml didn't change. |
@kaiyan-sheng thanks for starting with this! |
@jsoriano Thanks for pointing this out! This will be a bigger change than just fixing the test then 😄 |
@@ -11,3 +11,31 @@ | |||
description: > | |||
jolokia contains metrics exposed via jolokia agent | |||
fields: | |||
- name: agent.version |
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.
Not directly related to this PR but I just realise now that this at one stage should become an ECS field and Metricbeat in this case is the observer. @jsoriano is this correct?
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.
Do you mean setting observer.version
to this field and observer.type
to jolokia
? I guess it could make sense, but yeah, nothing to be done on this PR about this.
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.
Yesish. This agent.version
would end up on the top level an observer.version
would be the current beat version. It's a more general issue we have but just jumped in my face here :-D
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.
This needs a changelog entry as I would consider it a bug that it was not documented.
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.
Ok to move the fields to some common place in a follow up.
And yes, testing this is a bit hard as it depends on UDP multicast, we might add some tests mocking the network.
@@ -11,3 +11,31 @@ | |||
description: > | |||
jolokia contains metrics exposed via jolokia agent | |||
fields: | |||
- name: agent.version |
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.
Do you mean setting observer.version
to this field and observer.type
to jolokia
? I guess it could make sense, but yeah, nothing to be done on this PR about this.
It seems a |
@jsoriano Yeah! I just ran make update, thanks! |
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.
@kaiyan-sheng We should also backport this?
Yes, how about 7.0? |
Fixes #10925