This repository has been archived by the owner on Aug 13, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 180
Missing unit on lowest timestamp metric. #395
Comments
See #363 (comment) for the rationale. We have the same situation with the |
I don't think that rationale makes sense. If it's a timestamp, it has to have a unit, which we should know by the datatype. |
The unit is defined by the code that uses it though, not the tsdb. To the TSDB this is just a number. |
Maybe the TSDB shouldn't expose this metric, but we have Prometheus create the metric instead so we have an opinion on what the type is. |
What are we doing with this one? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In #363 a new metric,
prometheus_tsdb_lowest_timestamp
, was added.It seems like this is milliseconds, but is missing the unit.
Maybe we should convert this to seconds and make it
prometheus_tsdb_lowest_timestamp_seconds
.The text was updated successfully, but these errors were encountered: