Prometheus and OpenMetrics strongly recommend that the units for measuring durations should be seconds. However, the semantic conventions here are in milliseconds.
This creates a lot of confusion in users who are expecting durations to be seconds and requires an addition / 1e3 when doing math with metrics that come from traditional Prometheus sources. For example, today Kubernetes metrics are all in _seconds mainly because of the Prometheus conventions. This would be similar for other existing systems as well.
Given its all floats, I think we should try and revist the decision to use milliseconds and try to align with Prometheus.
Prometheus and OpenMetrics strongly recommend that the units for measuring durations should be
seconds. However, the semantic conventions here are inmilliseconds.This creates a lot of confusion in users who are expecting durations to be seconds and requires an addition
/ 1e3when doing math with metrics that come from traditional Prometheus sources. For example, today Kubernetes metrics are all in_secondsmainly because of the Prometheus conventions. This would be similar for other existing systems as well.Given its all floats, I think we should try and revist the decision to use
millisecondsand try to align with Prometheus.