-
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
Add integration/system tests for Kafka JMX metricsets #14677
Conversation
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
44e8e2e
to
46442e0
Compare
Signed-off-by: chrismark <chrismarkou92@gmail.com>
13d018b
to
9d229cd
Compare
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
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 think we should better follow conventions for some field names.
Proposed changes in integration tests would be nice to have, but not required.
type: float | ||
- name: topic.messages_in | ||
description: The incoming message rate per topic | ||
type: float | ||
- name: net.bytes_in |
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.
Following field conventions this should probably be:
- name: net.bytes_in | |
- name: net.in.bytes_per_sec |
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.
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.
there's no strict requirement on the naming. The field names were taken from the ER attached to the original issue. Do we have the mentioned naming convention somewhere?
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.
You can find the conventions here: https://www.elastic.co/guide/en/beats/devguide/7.5/event-conventions.html
- name: net.bytes_in | ||
description: The incoming byte rate | ||
type: float | ||
- name: net.bytes_out |
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.
And:
- name: net.bytes_out | |
- name: net.out.bytes_per_sec |
- name: net.bytes_out | ||
description: The outgoing byte rate | ||
type: float | ||
- name: net.bytes_rejected |
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.
And:
- name: net.bytes_rejected | |
- name: net.rejected.bytes_per_sec |
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
(cherry picked from commit a5d86cb)
This PR adds integration and system tests for Kafka JMX metricsets as a follow-up of #14330