NeophyteHi all,
I'm trying to limit the number of times LM runs the alerts/poll schedule.. Under the collection scheule, I have it set to every 6 hours but that doesn't seem to take.
Any suggestions on where else I can look.
-thx
Number of times it checks works as well. I'll take a look.
-thx
NeophyteNumber of times it checks works as well. I'll take a look.
-thx
ProfessorWell that would depend on your setup and policies. Generally I wouldn't suggest making a global change just for a few servers, but if your whole setup is only those servers then I guess that is fine. I would suggest looking at the other various options to see if there are other options. For example if it's expected that the disk space will be high due to overnight backups, you may want to set time-based thresholds or even a reoccuring SDT for that period. Or if the alert is flapping a lot, perhaps setting the number of times it checks before it alerts (rather then how frequently) might work better. Keep in mind that setting it to 6hr might delay alerts, but it can also delay clearing them.
Also note that you can set the polling interval at the device/group level: https://www.logicmonitor.com/support/logicmodules/datasources/creating-managing-datasources/creating-datasources#h-collection-interval .
NeophyteI'm getting alot of warnings of the same 2 or 3 servers which I know about and is not a concern. I I can suppress it I guess for that server I guess but I feel probably better to have it set globally as oppose to turning off teh alarm for each server/volume.
-e
ProfessorThat should change that particular check's poll time. How do you know it's not working? Is it still showing raw data more frequently?
Are you attempting to just change this particular check's frequency or all checks in LogicMonitor? Each check in LM has it's own schedule.
