I think a gauge is the right thing here: it represents the amount of time taken to rebuild the last configuration.
You can just scrape this periodically (say every minute), and easily see if it goes up or down over time. Of course, most of the time you'll be scraping the same value - but that's fine, it will compress extremely well. If you do two or more rebuilds in a minute, then you'll miss values - but you said they only happen once a day or once a week. If the configuration builder is persistent, it can just expose the value directly (the duration of the last rebuild). If the configuration builder fires up and then goes away, it can push the value to pushgateway. You could separately push another value containing either the time that the configuration was build, or a count of the total number of configuration rebuilds. Steps in this metric give an unambiguous indication of when the configuration builds took place. > -- 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/0b442867-f574-4ba6-a53f-9493140b9e39%40googlegroups.com.
