-
Notifications
You must be signed in to change notification settings - Fork 38
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
Am I using the correct syntax to adjust polling rate. #149
Comments
Ok never mind I've found this discussion, which stipulates the use of quotation marks. It may be worth updating documentation here, specifying the required quotation marks: Also If you know what I can check, to identify my current rate somewhere I'd love that, please - thank you. |
As usual thank you so much for replying! Unfortunately the reason I asked, completely spiraled into a far larger problem for me, well beyond my limited understanding. I was wanting to stop getting alerts on my dashboard. Unfortunately the "delay" function on alert creation, will delay the notification of the alert, the alert itself still exists. This means my dashboard, for my colleagues has many alerts (and recovieries) for some systems, missing a single ping. I don't want to even know if some systems weren't down for at least 25 minutes. I discussed it here: I suspect I will need to learn vastly more about the content stored in the SQL database and how to manipulate the alerts significantly, to make different alerts for different priority systems. Example: very important system, basically the current ICMP default alert macros.device_down = yes & devices.status_reason= icmp However, less important system: macros.device_down = yes & devices.status_reason= icmp & macros.device_down = "was at least 600 seconds ago and hasn't come up once in that time" I have no idea how to code that in the alert rules but it seems the only way, I'm able to stop things appearing on my dashboard which are in a 'tentative' state but not officially down. |
I have added the following line to my docker-compose.yaml file, in the environment section.
- POLLERS_CRON=*/3 * * * *
I am unsure how I can actually tell if this is the current rate of polling, have I done this correctly?
I would like to adjust my alerting and poller rate as I'm tired of a machine having a single ping problem for 10 seconds, coming up in an alert.
I have identified, from the poller webui that my total polling time is currently 30 seconds, so I thought 3 minutes would be a nice middle ground - setting my alerts to say 7 minutes.
Does this make sense?
The text was updated successfully, but these errors were encountered: