ROX-28151: Custom Prometheus metrics minimal aggregator#15784
ROX-28151: Custom Prometheus metrics minimal aggregator#15784parametalol wants to merge 1 commit intomichael/ROX-28151-minimal-configurationfrom
Conversation
|
Skipping CI for Draft Pull Request. |
|
Images are ready for the commit at 30cee42. To use with deploy scripts, first |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## michael/ROX-28151-minimal-configuration #15784 +/- ##
===========================================================================
+ Coverage 49.08% 49.09% +0.01%
===========================================================================
Files 2642 2644 +2
Lines 195747 195830 +83
===========================================================================
+ Hits 96081 96151 +70
- Misses 92159 92163 +4
- Partials 7507 7516 +9
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
0d622e8 to
018086d
Compare
018086d to
43dd7da
Compare
|
/retest |
stehessel
left a comment
There was a problem hiding this comment.
The code looks correct to me, but I think even more examples would go a long way here to take away some of the abstraction and complexity introduced by the custom types.
30d5b00 to
7df7ad8
Compare
841e4a0 to
25f4739
Compare
25f4739 to
a91a09a
Compare
7df7ad8 to
30cee42
Compare
|
Merged within #15797. |
Description
The PR introduces the data aggregation logic to support custom Prometheus metrics.
Every piece of source data sent for aggregation is called a finding. The aggregation process builds an aggregation key, which serves as the key for the aggregated numbers map.
For example, the keys for a single "Severity" label will be 4 known severity levels (LOW to CRITICAL), the aggregation map will have a key for each severity, and the number of findings as the value.
For multiple labels, the key is a joined value of all labels.
User-facing documentation
Testing and quality
Automated testing
How I validated my change
Unit tests.
Current dependencies on/for this PR: