Register all available Go runtime metrics#2005
Conversation
joe-elliott
left a comment
There was a problem hiding this comment.
Thanks for the addition! I like the idea of adding these metrics, but my impression is that they are rarely used and can be high cardinality.
Can we add a flag to turn these on and have them off by default?
|
Thanks for the review! I've moved them to a feature flag now (off by default). I wasn't sure if I should name it |
joe-elliott
left a comment
There was a problem hiding this comment.
I'm good on the name in the PR. It looks like you have a conflict to resolve?
Heads up that we are going to hold on merging this til after 2.0 is cut. We will likely get an RC out this week and start aggressively working on 2.0. We will revisit merging this likely in a few weeks.
bfa22d9 to
bdfb8bb
Compare
|
I've rebased the PR and fixed the conflict. Ok, np - thanks for letting me know. Looking forward to Tempo 2.0 :) |
Signed-off-by: Andreas Gerstmayr <agerstmayr@redhat.com>
bdfb8bb to
1b443cc
Compare
joe-elliott
left a comment
There was a problem hiding this comment.
Thanks for the improvement!
|
Thanks for merging & congrats on the v2 release yesterday! 🎉 |
What this PR does:
Registers all available Go runtime metrics
Which issue(s) this PR fixes:
PR #1528 upgraded prometheus/client_golang to version v1.12.2, which contains the following change:
The removed metrics contain some interesting GC metrics (e.g.
go_gc_cycles_total_gc_cycles_total). This PR (re-)introduces these metrics:No currently existing metrics are removed.
This PR is based on grafana/loki#6962.
Alternatively we could also make this configurable if we don't want to export all metrics by default, wdyt?
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]