Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upWhat's the maximum of scrape_interval I could set? #3328
Comments
This comment has been minimized.
This comment has been minimized.
|
It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided. |
brian-brazil
closed this
Oct 20, 2017
This comment has been minimized.
This comment has been minimized.
|
ok, thank you, brian. |
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 23, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
tangr commentedOct 20, 2017
•
edited
When I set scrape_interval to 7m just as the below example, and stop the target for test, the rule will not enter firing state, the alert go into pending state, and then Inactive after 2mins. I didn't see any state change log under debug log level.
I think the the scrape_interval will not set to more than 2m, is it right?
But I don't like the scrape to affect the system much, set the scrape_interval higher is better, or if the scrape running time of some exporter more than 3mins. Another scene is the aws Cloudwatch API request cost is high, so reduce the scrape number is the appropriate approach.
Prometheus version:
1.8.0
Prometheus configuration file: