[icinga-users] Icinga 2 and obsess_over_host / obsess_over_service

Hello list, I want to install some Icinga2-hosts on a couple of seagoing vessels, which are online only irregulary. I want to send the check-results to an Icinga2-host running on the shore-side via email. In a test-environment from the ships- network I have prepared a host with does the active ch

Re: [icinga-users] Icinga 2 and obsess_over_host / obsess_over_service

Hi Markus, you are great. With double quotes it's O.K. Thank you very much for your quick and correct response! -- best regards Kai Nothdurft >>> On 05.03.2015 at 15:55, Markus Joosten wrote: > Hi Kai, > > commands should be specified in double quotes (&quo

Re: [icinga-users] Icinga 2 and obsess_over_host / obsess_over_service

>>> On 05.03.2015 at 16:44, Michael Friedrich >>> wrote: > > I'm curious what makes you think that such an option "ohcp_command" > exists in Icinga 2. > > Michael Doesn't Icinga 2 inherit the option "ohcp_command" from Icinga, which inherited it from Nagios? Please don't tell me that this

Re: [icinga-users] Icinga 2 and obsess_over_host / obsess_over_service

Good morning Michael, >>> On 05.03.2015 at 20:20, Michael Friedrich wrote: > Am Donnerstag, 5. März 2015 schrieb Kai Nothdurft : >> >>> On 05.03.2015 at 16:44, Michael Friedrich > wrote: >> > >> > I'm curious what makes you think that

[icinga-users] apply|ignore where... in templates possible?

Hi all, I put an "ignore where..." statement into a service template. A service apply-rule, which imports the template ignores the ignore. Does it work as designed this way? Am I unable to use "apply|ignore" in templates? best regards Kai ___ icinga

Re: [icinga-users] Pushing passive check results from Icinga2 to Nagios

Hello Sergei, at first, I was missing the "obsess over services/hosts" as well. As a workaround I wrote a little cronjob, which parses the status.dat and creates a command-file from it. The script generates a "PROCESS_HOST|SERVICE_CHECK_RESULT" for ALL host- and service-stati. You have to filt

Re: [icinga-users] Pushing passive check results from Icinga2 to Nagios

Hi Sergei, before I forget, you should not use ".'~'.$hostName.'" in the two fwrite-lines of the script. This is for our special environment only. rgds Kai >>> On 29.04.2015 at 09:10, "Kai Nothdurft" wrote: > Hello Sergei, > > at first, I

Re: [icinga-users] Pushing passive check results from Icinga2 to Nagios

tomic way, so will probably write > a daemon with inotify watch on "close_write". > A second question: is the status file updated atomically? > > Thank you very much! > > I hoped there is an "official" way to achieve this. > > Sergei. > > On

[icinga-users] PNP4Nagios with Icinga 2

Hello list, I have a problem (understanding how) to configure PNP4Nagios with Icinga 2. The Icinga 2 doc at says: > If you're planning to use it configure it to use the >

Re: [icinga-users] PNP4Nagios with Icinga 2

Hello Martin, thx for feedback. That's too simple. ;) The documentation is misleading here. I have now set up PNP4Nagios and integrated it into the Classic-UI and into Icinga Web 2 as well. Works like a charm! thanks again and -- best regards Kai Nothdurft >>> On 31.07.2015 at

Re: [icinga-users] PNP4Nagios with Icinga 2

Good morning, what exactly are you looking for? Are you stucked somewhere? What distro are you using? If you are using some flavour of SuSE, I can send you snippets of my own documentation. best regards Kai >>> On 31.07.2015 at 23:51, Peltokangas Mikko >>> wrote: > Hi, I would like to have

Re: [icinga-users] Question about variables

Hello Bertalan, how about using an array instead? Example: vars.attribute = [ "value1" ] vars.attribute += [ "value2" ] apply1: assign where "value1" in vars.attribute apply2: assign where "value2" in vars.attribute hth Kai >>> On 10.09.2015 at 15:36, Bertalan Voros wrote: > Hello All, > >

[icinga-users] Passive host checks are soft

Hi list, in Icinga1 there is an option . Does anybody know, if there is an equivalent in Icinga2? thanks in advance Kai ___ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users

Re: [icinga-users] Passive host checks are soft

>>> On 17.03.2016 at 17:46, Michael Friedrich >>> wrote: >> On 16 Mar 2016, at 09:26, Kai Nothdurft wrote: [...] >> in Icinga1 there is an option . Does anybody >> know, if there is an equivalent in Icinga2? > > No, and it is not planned to imple

Re: [icinga-users] icinga2 agent default services

Hi, the default-services are only assigned, when specific attributes are set. For example, service is only assigned to hosts with an configured . Service is only assigned to hosts with configured . Nevertheless, you find the definitions in and can comment them out if you whish. best regards K

Re: [icinga-users] icinga2 agent default services

27;icinga' > * Service 'load' > * Service 'ping4' > * Service 'ping6' > * Service 'procs' > * Service 'ssh' > * Service 'swap' > * Service 'users' &

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

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

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

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 b

Re: [icinga-users] var and locals keywords

RTFM ;) The *local* scope contains variables which only exist during the invocation of the current function, object or apply statement. *Local* variables can be declared using the var keyword: function multiply(a, b) { var temp = a * b return temp } Each time the multiply function is i

Re: [icinga-users] var and locals keywords

Hi Tobias, AFAIK the usage of the keyword "locals" is more or less for readability. I'm not sure, if you can create the variable using your second example, but you can access it in your function using "locals.temp" afterwards. If you have already created variables named "temp" in different scop

Re: [icinga-users] var and locals keywords

Hi Tobias, >>> On 23.11.2017 at 13:31, Tobias Koeck wrote: [...] > just checked it out. It's possible to create a local variable with > > locals.temp = a * b > instead of > var temp = a * b. great, that you shared your test-results. Thanks. > The usage of the keywords locals, this and globals a