You're right I don't need the exact time when the metric is fetched. I only need it to differentiate between iterations within the batch job. Then is creating a separate metric the best way to go?
On Tuesday, August 8, 2023 at 4:09:24 AM UTC+5:30 Matt Doughty wrote: > I just wanted to chime in to say that you almost never need to know > exactly when a metric is updated. > Before you start exporting additional timestamp metrics, you should > really ask yourself whether you actually need them. What problem do > they actually solve? > > --Matt > > On Mon, Aug 7, 2023 at 5:54 PM Stuart Clark <stuart...@jahingo.com> wrote: > > > > On 07/08/2023 21:00, Moe wrote: > > > Thanks Brian that was really helpful, > > > > > > 2. The use case I want this for doesn't need continuous ingestion. In > > > that case is there a way for me to add time stamp to > MetricFamilySample? > > > > That isn't how Prometheus works. It will scrape that metric every 10 > > seconds to 2 minutes. If you need to know when that set of metrics was > > created a common pattern is to include a metric who's value is the > > timestamp. > > > > -- > > Stuart Clark > > > > -- > > 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 prometheus-use...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/prometheus-users/d401af4d-8583-d2d6-dbbe-89853000e421%40Jahingo.com > . > > > > -- > --Matt > -- 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 prometheus-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/bf01a491-2b12-4f10-b7db-fbf865647496n%40googlegroups.com.
