Topic Author
Most active users
- tcallway
55.52%
- opsera-support
41.35%
- tonvoon
25.98%
- awijntje
16.82%
- mattywhi
10.48%
- dferguson
8.53%
configure timed exceptions on a service check
Maybe someone here can help me with this.
As far as I can tell there are 2 ways of adding a timed exception to a check.
1. is through the host-configuration "Monitors" tab.
2. is through the host-template "monitors" tab.
Is this correct or is it possible to add a timed exception to a service_check directly?
I know it makes more sense to do it in the host-template, but I'm a very curious person....:-)..
sincerly Alan
He Ton,
hum that's a very good question.
Come to think of it, it is already possible to configure conflicting exceptions in Opsview??
As a test I configured a nonworkhours check_load exception in my host-template and added a non-timed (check_load ageinst a non-existing $ADDRESS1$) exception in the host-configuration.
Opsview did not throw an error on the reload.
When I check the status of the test-server it does not show any problems on the check_load service check (leading me to believe that the non-timed exception at the host-level is overruled).
At the service-check level both exceptions are displayed so I would assume both are applied??
To be honest in my opinion I would expect the exceptions not to be cumulative, and to be applied in an upwards motion.
So any exception at the check_level is overruled by an exception at the template level, which in turn is overruled by an exception a the host level.
But then again if the exceptions were cumulative that would open up a whole new scala off possibilities for monitoring.
I probably need to spend some more time thinking about this issue :-)
Sincerly,
Alan
That's a good question. We only have timed exceptions at the host or host template level. I guess we could add it to the service check level. One problem is: what happens with exceptions with no timed part? Should you use the exception at the host (or host template) level and use the service check's timed exception? Or should you assume that an exception at the host means that no timed exception should be set?