I am not seeing the frequency is more often than I expect. I am being told a log file is being created by the scrapes in a temp directory every minute. I am saying it is not Prometheus. So now i have to prove it is not Prometheus.
As an alternate solution, I am trying to use the Prometheus timestamp function on the metric being created by the scrape in Grafana to get the time history of the metric as proof. The thought being the time difference between the metric history is 3 minutes. But I am having trouble getting the value of the timestamp function to act as an epoch date. If I use the value returned in a web epoch translator, it translate to the correct date. If I multiple the value by 1000, as you do every epoch date in Grafana, it actually multiplies the value rather than putting it in human readable date format. Kevin On Tuesday, February 15, 2022 at 3:47:10 PM UTC-6 Stuart Clark wrote: > On 15/02/2022 18:41, [email protected] wrote: > > My end goal is to prove monitoring is not running every minute on the > > server. My word saying it is not, there's no way, the job is not > > configured to run every minute, is not good enough. > > > > There is a possibility that the two Prometheus servers are scraping at > > the same time but there is no way the scrapes are happening every > > minute. The scrape interval is 3m with a scrape time out of 2m45s. > > So are you seeing more frequent requests than you expect? How are you > telling this? Do you have request logs & what do they say/record? > > -- > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/9188e918-6750-43c3-80f7-7570803cad5fn%40googlegroups.com.
