-
Notifications
You must be signed in to change notification settings - Fork 49
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
None of the kafka.consumer.* metrics are reported #9
Comments
Key configurations are as below: external.kafka.statsd.metrics.exclude_regex=(.ReplicaFetcherThread.)|(kafka.cluster.Partition..)|(kafka.controller..)|(kafka.network..)|(kafka.log..)|(kafka.util..*) external.kafka.statsd.dimension.enabled.count=trueexternal.kafka.statsd.dimension.enabled.meanRate=false external.kafka.statsd.dimension.enabled.rate1m=trueexternal.kafka.statsd.dimension.enabled.rate5m=false |
And I store the offsets in the topic __consumer_offsets. |
Hi @shadyxu your issue sounds similar to #8 See the details in the release notes: https://github.com/airbnb/kafka-statsd-metrics2#040 |
Thanks @alexism I am using the official statsd, but I found no documentation about how to set or test if it supports tags. Any idea? |
Tags are an extension of the statsd protocol. It was introduced by Datadog: http://docs.datadoghq.com/guides/dogstatsd/#tags If your server does not support tags, you can disable them by adding When tags are disabled, the tags values are appended to the metrics names. I'm sorry for the confusion. I created #11 to address the lack of clear documentation. |
Setting I checked the kafka documentation, there is only |
Hi @shadyxu, We went through kafka code and collected all metrics. You can find ConsumerTopicMetrics from https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/metrics/KafkaMetricsGroup.scala#L114-L117. I tested it locally using I can see Did you set any filter to exclude |
I have configured some exclude filters but not the I am writing offsets to the kafka topic |
@shadyxu
|
I am using Kafka 0.8.2.
Is this a bug of kafka-statsd-metric2 or mismatch of version?
The text was updated successfully, but these errors were encountered: