We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Users having multiple redpanda deployments would like to differentiate between instances using a label.
rpk generate prometheus-config to have the ability to specify label for a redpanda cluster https://prometheus.io/docs/prometheus/latest/configuration/configuration/#:~:text=labels%20assigned%20to%20all%20metrics%20scraped%20from%20the%20targets.
Collision of metrics if no label is specified and hard to track in Prometheus if a customer has multiple redpanda instances.
The text was updated successfully, but these errors were encountered:
rpk generate
Successfully merging a pull request may close this issue.
Who is this for and what problem do they have today?
Users having multiple redpanda deployments would like to differentiate between instances using a label.
What are the success criteria?
rpk generate prometheus-config to have the ability to specify label for a redpanda cluster
https://prometheus.io/docs/prometheus/latest/configuration/configuration/#:~:text=labels%20assigned%20to%20all%20metrics%20scraped%20from%20the%20targets.
Why is solving this problem impactful?
Collision of metrics if no label is specified and hard to track in Prometheus if a customer has multiple redpanda instances.
The text was updated successfully, but these errors were encountered: