Gary Jarrel
2013-05-24 00:33:13 UTC
Hi All,
I am reasonably new to OpenNMS and we are trialing it out to monitor a few
remote servers that are at our site offices and are connected to head
office via an ipsec VPN where the OpenNMS Server is installed.
What we are getting is some false notifications of services going down at
the remote sites. Probably due to heavy traffic across the VPNs. Eg, we
would get a HTTP service down at a remote site notification and then 60
seconds later (approximately) we get the RESOLVED notification.
Is there a way to delay the notification, such that at least two
consecutive failures have to occur before the notification is raised, or
even to increase the time out before notification is sent!
Thank you for your assistance. It seems something simple but I've been
reading the tutorials, Googling and can't seem to find the solution.
Thank you
GJ
I am reasonably new to OpenNMS and we are trialing it out to monitor a few
remote servers that are at our site offices and are connected to head
office via an ipsec VPN where the OpenNMS Server is installed.
What we are getting is some false notifications of services going down at
the remote sites. Probably due to heavy traffic across the VPNs. Eg, we
would get a HTTP service down at a remote site notification and then 60
seconds later (approximately) we get the RESOLVED notification.
Is there a way to delay the notification, such that at least two
consecutive failures have to occur before the notification is raised, or
even to increase the time out before notification is sent!
Thank you for your assistance. It seems something simple but I've been
reading the tutorials, Googling and can't seem to find the solution.
Thank you
GJ