Right! state/type/attempt are only the _minimum_ arguments required. Of
coutse you can add the downtime depth yourself.
Good on you for not listening to me ;)
On Thu, Sep 26, 2013 at 10:52 PM, Paul Dubuc <w...@paul.dubuc.org> wrote:
> Anton L�fgren wrote:
>
>> On Wed, Sep 25, 2013 at 7:14 PM, Paul Dubuc <w...@paul.dubuc.org
>> <mailto:w...@paul.dubuc.org>> wrote:
>>
>> ...
>
>>
>> �I know notifications are
>>
>> suppressed, though checks still run. �I would like the event handler
>> for one
>> service not to run during a downtime. �Is that possible?
>>
>> That, I don't know - as I'm sure you already know, the downtime depth
>> ${HOST,SERVICE}DOWNTIME$ is not passed to the event handler, which
>> otherwise
>> would've been a viable solution to the problem.
>>
>
> Hmmm. The event handler is just another plugin with a command definition.
> I think I CAN pass $HOSTDOWNTIME$ or $SERVICEDOWNTIME$ to it by putting it
> as an arg in the command object. Then code it will do nothing if the host
> or service is in downtime. Thanks for the idea! I'll try it.
>
> Paul Dubuc
>
--
Anton Löfgren alofg...@op5.com
OP5 AB www.op5.com
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
