-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[metrics] Sanitize route label with only the path #5859
Conversation
/werft run 👍 started the job as gitpod-build-laushinka-http-metrics-5825.3 |
/werft run 👍 started the job as gitpod-build-laushinka-http-metrics-5825.5 |
10bf282
to
d84b50f
Compare
/werft run 👍 started the job as gitpod-build-laushinka-http-metrics-5825.7 |
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.
Code looks good
LGTM label has been added. Git tree hash: 3e300f791257786e862917166e459a3d4eb09e0d
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: geropl Associated issue: #5825 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Fixes #5825
Description
Our Prometheus route label was high in cardinality (e.g. /apps/bitbucket/callback?xxxxxx) and therefore needs to be sanitized for better observability.
Related Issue(s)
Fixes #5828
How to test
Will try @ArthurSens's cool monitoringSatellite.
Go to here and go through the
route
label. You can also hit some endpoints in the preview env to trigger more metrics.Release Notes
/werft run with-observability withObservabilityBranch=laushinka-http-metrics-5825