Skip to content
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

kafka_consumed_messages_total topic label #21330

Open
jpds opened this issue Sep 20, 2024 · 1 comment
Open

kafka_consumed_messages_total topic label #21330

jpds opened this issue Sep 20, 2024 · 1 comment
Labels
domain: observability Anything related to monitoring/observing Vector source: kafka Anything `kafka` source related type: feature A value-adding code addition that introduce new functionality.

Comments

@jpds
Copy link
Contributor

jpds commented Sep 20, 2024

A note for the community

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Use Cases

The vector_kafka_consumed_messages_total metric should have a topic label as there may be multiple topics configured for a source.

Attempted Solutions

No response

Proposal

No response

References

No response

Version

No response

@jpds jpds added the type: feature A value-adding code addition that introduce new functionality. label Sep 20, 2024
@jszwedko
Copy link
Member

Agreed. Would you also want this at the partition level? Or is just topic sufficient?

@jszwedko jszwedko added source: kafka Anything `kafka` source related domain: observability Anything related to monitoring/observing Vector labels Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain: observability Anything related to monitoring/observing Vector source: kafka Anything `kafka` source related type: feature A value-adding code addition that introduce new functionality.
Projects
None yet
Development

No branches or pull requests

2 participants