You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DateUtc provided by AmbientWeather, which should be the time the data was recorded at
The time the metric was scraped from ambientweather-local-server
Inherently, an Agent scraping prometheus metrics will store the time series data according to the scrape time. It assumes its getting a "live" reading of the current state of the metrics. This is how AWLS works today.
Depending on how much drift or delay there is between when AmbientWeather collected the metric and when it was scraped from the AWLS the metric data could be associated with a grossly incorrect timestamp.
Ideally, we would want our metrics associated with the time of measurement, not the scrape time. However, while prometheus does support writing a custom timestamp with a given metric, the library I'm using right now does not.
Regarding timestamps we have:
ambientweather-local-server
Inherently, an Agent scraping prometheus metrics will store the time series data according to the scrape time. It assumes its getting a "live" reading of the current state of the metrics. This is how AWLS works today.
Depending on how much drift or delay there is between when AmbientWeather collected the metric and when it was scraped from the AWLS the metric data could be associated with a grossly incorrect timestamp.
Ideally, we would want our metrics associated with the time of measurement, not the scrape time. However, while prometheus does support writing a custom timestamp with a given metric, the library I'm using right now does not.
Need to investigate alternatives.
https://www.reddit.com/r/PrometheusMonitoring/comments/9h9olw/is_there_way_to_deliver_dataset_with_timestamps/
https://prometheus.io/docs/instrumenting/exposition_formats/
The text was updated successfully, but these errors were encountered: