-
Notifications
You must be signed in to change notification settings - Fork 27
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
🐛 Fix issue with sending metrics that are None to Prometheus #6951
🐛 Fix issue with sending metrics that are None to Prometheus #6951
Conversation
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.
could you please double check other prometheus calls in case we have the same issue elsewhere? thx
Very good point. this also could happen for the start. I've also applied the same logic here |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6951 +/- ##
===========================================
- Coverage 88.08% 67.86% -20.22%
===========================================
Files 1589 632 -957
Lines 62243 30616 -31627
Branches 2012 262 -1750
===========================================
- Hits 54825 20779 -34046
- Misses 7082 9777 +2695
+ Partials 336 60 -276
Continue to review full report in Codecov by Sentry.
|
Quality Gate passedIssues Measures |
What do these changes do?
Prometheus client does not accept
None
values when callingobserve
on a metric.When stopping a service, if this one did not start, the stop metric would be set to None.
In the case where metrics are None we do not send them.
Traceback
Related issue/s
How to test
Dev-ops checklist