You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The recent change 4593 updated the consumer code of the ingester to support ingestion from multiple Kafka topics when sarama consumer is created in custom way with multiple topics. However, the metrics lack the tag with topic name.
Steps to reproduce
Ingest from multiple Kafka topics with sarama consumer created in custom way.
Check the metric with name name:sarama-consumer.messages - it does not have information about the topic.
Expected behavior
All consumer metrics should have a tag with topic name.
Relevant log output
No response
Screenshot
No response
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
No response
The text was updated successfully, but these errors were encountered:
abliqo
changed the title
[Bug]: Consumer metrics do not have a tag with topic name
[Bug]: Consumer metrics should have a tag with topic name
Sep 26, 2023
abliqo
added a commit
to abliqo/jaeger
that referenced
this issue
Sep 26, 2023
What happened?
The recent change 4593 updated the consumer code of the ingester to support ingestion from multiple Kafka topics when sarama consumer is created in custom way with multiple topics. However, the metrics lack the tag with topic name.
Steps to reproduce
name:sarama-consumer.messages
- it does not have information about the topic.Expected behavior
All consumer metrics should have a tag with topic name.
Relevant log output
No response
Screenshot
No response
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
No response
The text was updated successfully, but these errors were encountered: