multi: Remove high card keys for payment metrics #1893
Merged
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.
What does this pull request do? Explain your changes. (required)
Remove high cardinality keys i.e. recipient/sender and manifestID from payment/ticket metrics. Now, only aggregate payment/ticket metrics are reported and there is no metrics reporting on a per recipient/sender or manifestID basis.
Prometheus doesn't like high cardinality keys/labels so when using Grafana to load Prometheus data a dashboard that uses payment/ticket metrics the dashboard might be really slow to render or may even cause the Grafana app to crash as reported in #1763.
Specific updates (required)
monitor
packageHow did you test each of these updates (required)
TBD.
Does this pull request close any open issues?
Fixes #1763
Checklist:
make
runs successfully./test.sh
pass