-
Notifications
You must be signed in to change notification settings - Fork 43
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
feat: track time to publish a message #451
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #451 +/- ##
==========================================
- Coverage 82.36% 82.30% -0.06%
==========================================
Files 48 48
Lines 12013 12035 +22
Branches 1279 1281 +2
==========================================
+ Hits 9894 9905 +11
- Misses 2119 2130 +11
☔ View full report in Codecov by Sentry. |
we can track metric in |
/** Total time in millisecond to publish a message */ | ||
msgPublishMs: register.histogram<{ topic: TopicLabel }>({ | ||
name: 'gossipsub_msg_publish_ms', | ||
help: 'Total time in millisecond to publish a message', |
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.
Prometheus standards suggest to use standard metrics, in the case of time seconds: https://prometheus.io/docs/practices/naming/#base-units we should respect the standard as it's used across all our codebase
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.
Motivation
Description
msgPublishMs
metric and track itrelated to #344