feat: improve configurability of prometheus metrics #450
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related issue
Proposed changes
This PR introduces a new boolean configuration parameter
collapse_request_paths
in the prometheus configuration stanza of theoathkeeper.yml
file:The parameter is optional and if not set it defaults to
true
.When set to
true
it modifies the behaviour of the metrics Middleware so that for all the request metrics that contain therequest
label (which is equal to the request context path) its value is collapsed to only the first element of the segment. Eg.will result in the following request metrics (trimmed for reading convenience):
When
collapse_request_paths
is set tofalse
the metrics will keep the path previous fine granularity:Checklist
vulnerability. If this pull request addresses a security. vulnerability, I
confirm that I got green light (please contact
[email protected]) from the maintainers to push
the changes.
works.
Further comments
I'm happy to modify any logic or naming I somehow arbitrarily chosen!