Re: [icinga-users] NotificationCommand arguments not inherited

[Lee Clemens]

On 10/18/2016 08:50 AM, Markus Frosch wrote:
> On 17.10.2016 20:20, Lee Clemens wrote:
>> arguments = {
>> "--host-output" = {
>> required = true
>> value = "$host.output$"
>> }
>> "--host-state" = {
>> required = true
>> value = "$host.state$"
>> }
>> }
> 
> Hey Lee,
> your problem is that you are *replacing* arguments there.
> 
> What you should do: ( += )
> 
> Regards
> Markus Frosch
> 

Thank you Markus! That makes perfect sense. I created 
https://dev.icinga.org/issues/12941 to address being able to append (vs 
replace) arguments in Director.

Thanks,
Lee Clemens
___
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users

[icinga-users] Non-NRPE command timeouts

[Rob DeSanno]

I’m running into  a problem in the office whereby some of my non-NRPE
checks are taking more than 60 seconds to complete and icinga2 is killing
them and returning the following status:




So I have 2 questions:

   - Is there a way to increase the default, non-NRPE checks to run more
   than 60s without having to tweak each check?
   - Can I make non-nrpe checks that time out go into critical instead of
   unknown like you can with nrpe?

The last question is more important than the first and can’t seem to find a
way to do it.

TIA!
___
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users

Re: [icinga-users] how to ignore a Host

[Kai Nothdurft]

Hi Michael,

so what do you mean with ignore? If it's showing OK, you can ignore the
host, don't you? If you don't use a check_command, what should be shown
in the Web-interface? Or do you want the hosts be hidden from the
Webinterface? How do you want to hide them? If from the GUI, how would
you reenable the host? Or do you want to "disable" the hosts(s)
programmatically? Would be a reload of Icinga2 a problem then?

Though I don't really understand, what you are trying to achieve, you
may play around with parameter "check_period" and create a timeperiod
"never".

brgds
Kai


>>> On 18.10.2016 at 03:17, Michael Martinez  wrote:
> Hi Kai,
> 
> Yes, I understand that. But a dummy check that always returns OK is
> misleading. The hosts themselves may be Up, may be Down, but for a
> particular subset of hosts we don't want to know either way. We
would
> rather ignore them.
> 
> On Fri, Oct 7, 2016 at 5:04 AM, Kai Nothdurft
 
> wrote:
>> Hi Michael,
>>
>> I know, you wrote, that you don't want to assign a dummy check -
but
>> why not? You could use the built-in "dummy"-check for this:
>>
>>
>> object Host "unchecked-host" {
>>   import "generic-host"
>>
>>   check_command = "dummy"
>>
>>   vars.dummy_state  = 0
>>   vars.dummy_text   = "This host will never be checked and
shows
>> always OK"
>>
>> }
>>
>> hth
>> Kai>>> On 06.10.2016 at 19:18, Michael Martinez 
>> wrote:
>>> Hi Hasan, thanks for your reply. I should be more clear: I am
>> actually
>>> looking to ignore the Host check itself. What you've written works
>> for
>>> service checks only.
>>>
>>> On Wed, Oct 5, 2016 at 10:26 AM, hasan akgöz

>> wrote:
 Hello Michael,

 if you hostname or ip adress whatever is static you can use
ignore
>> keyword
 follow like ;

 apply Service "Service Name" {
   ...

   assign where match("web*.example.org", host.name)
   ignore where host.name
 }



 2016-10-05 19:51 GMT+03:00 Michael Martinez :
>
> we need to exclude certain hosts based on AWS
> attributes (VpcId






 ___
 icinga-users mailing list
 icinga-users@lists.icinga.org 
 https://lists.icinga.org/mailman/listinfo/icinga-users 

>>>
>>>
>>>
>>> --
>>> ---
>>> Michael Martinez
>>> http://www.michael--martinez.com 
>>> ___
>>> icinga-users mailing list
>>> icinga-users@lists.icinga.org 
>>> https://lists.icinga.org/mailman/listinfo/icinga-users 
>> ___
>> icinga-users mailing list
>> icinga-users@lists.icinga.org 
>> https://lists.icinga.org/mailman/listinfo/icinga-users 
> 
> 
> 
> -- 
> ---
> Michael Martinez
> http://www.michael--martinez.com 
> ___
> icinga-users mailing list
> icinga-users@lists.icinga.org 
> https://lists.icinga.org/mailman/listinfo/icinga-users
___
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users

Re: [icinga-users] NotificationCommand arguments not inherited

[Markus Frosch]

On 17.10.2016 20:20, Lee Clemens wrote:
> arguments = {
> "--host-output" = {
> required = true
> value = "$host.output$"
> }
> "--host-state" = {
> required = true
> value = "$host.state$"
> }
> }

Hey Lee,
your problem is that you are *replacing* arguments there.

What you should do: ( += )

arguments += {
"--host-output" = {
required = true
value = "$host.output$"
}
"--host-state" = {
required = true
value = "$host.state$"
}
}

So you are adding values to the existing dictionary, like a merge (you would 
replace keys that have the same name).

Regards
Markus Frosch
-- 
Icinga Open Source Monitoring
https://www.icinga.org
___
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users