Timestamps should be in seconds, eg in setToCurrentTime methods
See original GitHub issueThe implementation of setToCurrentTime for gauges uses the value of Date.now()
which is in milliseconds. The suggested conventions for client libraries is to use base units for all recorded metrics.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Using MySQL's TIMESTAMP vs storing timestamps directly
Arguments for TIMESTAMP. It implicitly stores data in UTC time zone. No matter what your session time-zone is. Useful if you need to...
Read more >Timestamp (IBM Streams Java Operator API)
A Timestamp represents a number of seconds and nanoseconds, ... e.g. an instance representing a delay of four seconds could be created as...
Read more >prometheus - Go Packages
Package prometheus is the core instrumentation package. It provides metrics primitives to instrument code for monitoring.
Read more >Timestamps, Time Zones, Time Ranges, and Date Formats
Learn how Sumo Logic manages timestamps, time zones, time ranges, and dates, and the configuration options that are available.
Read more >Metric Types in Prometheus and PromQL - PromLabs
Below, we will look at how these metric types manifest themselves across ... a convenience method to set a gauge to the current...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
+1 for just breaking. What we do now is wrong, I see no reason to keep supporting it
Happy to do either! 😃