-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prometheus receiver scrape every 15s (wheras scrape_interval sets to 60s) #34381
Comments
Thanks for reporting @genseb13011, can you confirm how you're observing the 15s scrape? I'll transfer this issue to the contrib repo where i'll label it with prometheus receiver to get the code owners to review it |
Pinging code owners for receiver/prometheus: @Aneurysm9 @dashpole. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Hi, Sorry for the delay. I notice this in my Grafana dashboard which display metrics point every 15 secondes. Thanks |
You are scraping all of the nodes from a deployment with more than 1 replica, which can result in more frequent scrapes than expected. The reason why you see a point every 15 seconds is because that is the interval at which cAdvisor updates metrics internally. It uses explicit timestamps, which are used instead of the scrape time. The only odd thing to me is that you list it as having only 2 replicas. With that configuration, I would expect to see points every 30 seconds, instead of every 15 seconds. Did you ever use more than 2 replicas? To fix this, you either need to reduce your replicas to 1, or you need to shard targets between replicas using the hashmod operator, or using the target allocator. |
Hi,
I'm facing an issue with the scraping interval of prometheus receiver.
Even if i've set the scrape_interval value to 60s for each of my job and in the global variable, the scraping period is still 15s.
Technical informations:
` mode: deployment
The text was updated successfully, but these errors were encountered: