When I reboot a server, I don't get the SW alert for 8 minutes. I don't think that is reasonable. Any advice,
Thanks
Jdoe1
That delay seems like it could be a multiple of the default status polling interval of 2 minutes (if you are using that value). Check to see if the alert trigger has a delay of 8 minutes configured. It could also be partly due to simple process delay.
The up-time is determined during the statistic polling cycle of the Node, which by default is every 10 minutes. You can change how often you poll devices by going into Settings> Manage Nodes, edit the device(s) and under Node Statistics collection you can change the polling to as fast as 1 minute.
Be aware that making this change for some devices is fine, but applying 1 minute polling to hundreds or all systems will affect the polling job weight significantly, and you may see a warning about Polling thresholds, this is so that Orion Core can effectively poll device statistics from all devices within the scheduled time-frame that is set for all polling. Once the polling weight goes above 100%, then the polling will slow down for all devices, so that it can effectively poll the devices without negatively creating random gaps in data.
Actually, the status of a node is determined by ICMP at a default 2 minutes interval unless the user has selected SNMP as the method of choice. In any event, the alert trigger could still have a delay that explains the wait on getting the alert.
One other questions I did think of though... are you getting a node down alert or a node reboot alert, or both?
8 minutes after reboot I get the alert the node is down, then 2 minutes later I get the alert the server is up. Previously I used solar winds with the other company I worked for and the second a server went down, we were notified and it was real time. This lagging of 8 minutes can be significant for mission critical applications and or servers.
The person who configured SW said that this is expected given the separate modules in SW. Between the detection module, alerting module, and the sql queries. I wanted an expert opinion and or advice as to how to correct the lagging in time after a reboot or after a device goes offline.
Thanks,
Which process delay?
check the amount of time it is taking for server to be available post restart.
Post restart it would take time to sync also I guess... But ya 8 min is too long....
How is the alert trigger configured?
Is the Condition must exist for more than x minutes option configured?
