Skip to content
This repository has been archived by the owner on Aug 13, 2019. It is now read-only.

Missing unit on lowest timestamp metric. #395

Closed
SuperQ opened this issue Sep 24, 2018 · 5 comments · Fixed by prometheus/prometheus#4888
Closed

Missing unit on lowest timestamp metric. #395

SuperQ opened this issue Sep 24, 2018 · 5 comments · Fixed by prometheus/prometheus#4888

Comments

@SuperQ
Copy link
Contributor

SuperQ commented Sep 24, 2018

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.

@simonpasquier
Copy link
Contributor

See #363 (comment) for the rationale. We have the same situation with the prometheus_tsdb_head_max_time and prometheus_tsdb_head_min_time metrics.

@SuperQ
Copy link
Contributor Author

SuperQ commented Sep 24, 2018

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.

@brian-brazil
Copy link
Contributor

The unit is defined by the code that uses it though, not the tsdb. To the TSDB this is just a number.

@SuperQ
Copy link
Contributor Author

SuperQ commented Sep 24, 2018

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.

@krasi-georgiev
Copy link
Contributor

What are we doing with this one?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants