-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Use namespace prefix on Prometheus registry #4025
Comments
This would be an improvement IMO. I also don't see any downsides of doing this. |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Still valid and help wanted :) |
While we're at it I think we should leverage different subsystems as opposed to prefixing metrics with query/rule/store/compact etc. |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Closing for now as promised, let us know if you need this to be reopened! 🤗 |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Closing for now as promised, let us know if you need this to be reopened! 🤗 |
It's a good idea.
Just wondering, would having a namespace add any help? Users can always define scrape job config with job name
We can use this to auto inject the prefix https://pkg.go.dev/github.com/prometheus/client_golang/prometheus#WrapRegistererWithPrefix Let me know, what do you think. I'd love to work on this issue : ) |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Is your proposal related to a problem?
There is a current pattern to prefix all metrics with the
thanos_
prefix. This is what the namespace feature of the Prometheus registry is intended for.Describe the solution you'd like
Remove
thanos_
prefixes from metrics, and add it to the registry as a namespace.Describe alternatives you've considered
Do nothing, and continue to enforce the prefix on pull request reviews.
Additional context
I added a histogram expecting the namespace to be provided by the registry, instead it was unexpected toil during review.
The text was updated successfully, but these errors were encountered: