-
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
In Metricbeat Kafka modules based on Jolokia, collect OneMinuteRate instead of MeanRate #17295
Comments
Pinging @elastic/integrations (Team:Integrations) |
@jsoriano can you please comment on this? |
Hey @danielyahn, thanks for your feedback! It makes sense, it also looks to me that @ChrsMark do you see any problem with collecting If after changing these metrics, some user still finds that some metric is not being collected as they would like, they can still use the Jolokia module directly, and the Kafka metricset manifests can be used as help to create the mappings. |
No, I don't see any problem since it makes more sense. |
Pinging @elastic/integrations-services (Team:Services) |
MeanRate doesn't mean anything (it's too smoothed as time passes) and doesn't reflect Kafka's current status. |
Describe the enhancement:
Describe a specific use case for the enhancement or feature:
By default, it seems like Metricbeat Kafka Jolokia module takes MeanRate attribute of metrics. A lot of times, I would prefer using OneMinuteRate to using the MeanRate. For example,
name=BytesOutPerSec,type=BrokerTopicMetrics
. MeanRate would have mean value of the throughput from broker start time. I want Metricbeat to ingest more granular value, and do necessary aggregation using lastic.The text was updated successfully, but these errors were encountered: