Different timeperiods for the same service

[gilbertogm]

Hello guys,

I'd like to check a service and do different thins depending on the time:

Let's say:

define service{
use generic-service
service_description Service_PING
host_name host1
check_command check_ping!2000.0,80%!5500.0,99%
check_period nonworkhours
max_check_attempts 10
retry_check_interval 3
normal_check_interval 5
event_handler_enabled 1
event_handler retryPing
}

During non-working hours, it executes the event_handler.

define service{
use generic-service
service_description Service_PING
host_name host2
check_command check_ping!2000.0,80%!5500.0,99%
check_period workhours
normal_check_interval 5
}

And on working hours, just check as normal.

Does that work? Is there a better way to do this?

Thanks in advance.

[sreinhardt]

The only way I could think to do this would be to call the event handler each time and have it specifically check the time. You might also be able to pass the timeperiod to it via macro, but it would still need to be parsed and calculated within the script. Presently using timeperiods in this fashion is not really possible, but it does sound kinda cool!

Thinking about it a bit more, you could have a second service for the time when you want the alternative action. However if you plan to report on this service, you would need to be use the first idea of having the event handler manage it all. It really shouldn't be all that difficult to handle the time check within a script, just not really ideal.

[gilbertogm]

I have worked around and i found a way to do it.

on the command i added the macro $ISVALIDTIME:non-workinghours$

and then on the script i just added the condition

if [ "$6" = '1' ]; then
....
fi

[tmcdonald]

There is some logic that works best in the script itself, and this is definitely one of those cases. Cane we close the thread as solved?