Skip to content
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

What's the maximum of scrape_interval I could set? #3328

Closed
tangr opened this Issue Oct 20, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@tangr
Copy link

tangr commented Oct 20, 2017

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:

 - job_name: 'test'
   scrape_interval: 7m
   static_configs:
     - targets: ['nodeexporter:9100']

ALERT instance_down_debug
  IF up == 0
  FOR 5m
  LABELS {severity="debug"}
  ANNOTATIONS {detail="Host {{ $labels.instance }} is down.", short="{{ $labels.instance }} down"}
@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Oct 20, 2017

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.

@tangr

This comment has been minimized.

Copy link
Author

tangr commented Oct 20, 2017

ok, thank you, brian.

@lock

This comment has been minimized.

Copy link

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 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.
You can’t perform that action at this time.