-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Change pprof labels to be prometheus compatible #32865
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
Conversation
Enables scrapping pprof endpoint for continuous profiling
Is this a breaking change for those upgraded Gitea instance? |
It was marked as such in the fork. However the for it to be breaking someone would actively have to scrape the endpoint for (semi-)automated analysis, which I very much doubt anyone is doing (evidence being that no one complained about it). If you consider that a real possibility then yes, it is breaking. |
No, there are different, do not mix them at the moment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's measure if it is breaking by whether someone complains 😄
Actually it breaks nothing ..... |
Enables scrapping pprof endpoint for continuous profiling
Closes: #32854
There's probably room for improvement - for example dropping
graceful_lifecycle
completely and makingwith-hammer
intowith: hammer
key value (or something similar). But I'd wait with that for a proper spec in OTel so there there won't be a need to align to specn
times.Name is compliant with both prometheus regex and OTel recommendation (but not to their semantic conventions):