On Monday 18 December 2023 at 06:41:41 UTC Kesavanand Chavali wrote: We have a node where time is not in sync. we implemented an exporter in Go that will scrape the metrics from other exporters and corrects the timestamp. Prometheus scrapes this exporter but errors out with the above said message.
I don't understand the problem. If the node where the exporter is running has a bad clock, it shouldn't make any difference. Firstly, the exported metrics generally won't have a timestamp (it's an optional field). Secondly, even if they do, Prometheus ignores it anyway unless you set "honor_timestamps: true", which is almost always the wrong thing to do. Do you mean you are using the remote_write protocol with the remote_write receiver, rather than scraping? Perhaps you can sketch a diagram of what the components are, and how they are talking to each other. -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/b23c1903-a779-409a-ba20-859227303643n%40googlegroups.com.
