[icinga-users] More flexible host group assignment

Hi everyone, I'm setting up a new icinga2 site and ran into a small difficulty. The site in question already heavily uses ansible and it makes sense to integrate icinga2 setup with it as much as possible. Specifically, ansible roles should be translated into HostGroups etc. The problem starts whe

Re: [icinga-users] More flexible host group assignment

t; wrote: > Am 08.06.2015 um 13:31 schrieb Shay Rojansky: > > Hi everyone, I'm setting up a new icinga2 site and ran into a small > difficulty. > > The site in question already heavily uses ansible and it makes sense to > integrate icinga2 setup with it as much as possibl

[icinga-users] Piping application error logs to icinga2

Hi everyone. I'm looking to integrate logstash, which processes our application logs, with icinga2. The general idea is to define an icinga2 service that goes to state critical (or warning) when a logstash encounters a log message with the relevant severity. Setting this up (e.g. with NSCA) doesn'

Re: [icinga-users] Piping application error logs to icinga2

lt; icinga+us...@vonderkrone.info> wrote: > Hi Shay, > > you could enable passive checks for the service. Then you have to add an > URL (to submit the "OK" passive check result) to the plugin output. > > Regards, > Tobias > > > On 2015-06-18 11:37, Shay Rojansky wr

Re: [icinga-users] Piping application error logs to icinga2

Daniel, I may be misunderstanding this (the docs on volatile are extremely light), but I don't see how that helps... A service that goes into CRITICAL state because of an error log would be passive only (I think) - something like logstash with its nagios_nsca plugin - what does volatile mean for pa

Re: [icinga-users] Piping application error logs to icinga2

mail, then, in the > next check and if there is no more NEW errors, it becomes OK. > > Hope it helps. > > > João Graça > > > > On 19-06-2015 15:03, Shay Rojansky wrote: > > Daniel, I may be misunderstanding this (the docs on volatile are extremely > light), but I

Re: [icinga-users] NRPE checks

Just to add my experience, we're using icinga2 in command execution very successfully. Deployment and configuration is ansible-managed, and apart the initial setup work (especially around SSL) it's trivial to manage and install on new machines. (I can share the ansible scripts). >From what I under

Re: [icinga-users] NRPE checks

14 AM, Dustin Funk wrote: > Am 29.06.2015 um 07:01 schrieb Shay Rojansky: > > From what I understand arguments in icinga2 don't represent a security > risk > > simply because the connection itself is secured via SSL > > The question isn't whether the informoation chann

Re: [icinga-users] NRPE checks

On Tue, Jun 30, 2015 at 1:31 AM, Dustin Funk wrote: > Am 29.06.2015 um 07:01 schrieb Shay Rojansky: > > Just to add my experience, we're using icinga2 in command execution very > > successfully. Deployment and configuration is ansible-managed, and apart > > the init

[icinga-users] Problem with postgres CheckCommand

Icinga2 comes with plugins-contrib.d/databases.conf which contains the "postgres" CheckCommand. There seems to be an issue with the following line: set_if = {{ macro("$postgres_unixsocket$") == false }} This seems to never evaluate to true; the -H argument never seems to be passed regardless of w

Re: [icinga-users] Problem with postgres CheckCommand

could take place), maybe consider activating issues in github? Thanks for all your help and for making an awesome monitoring system! Shay On Wed, Jul 1, 2015 at 6:36 PM, Michael Friedrich < michael.friedr...@netways.de> wrote: > Am 30.06.2015 um 11:50 schrieb Shay Rojansky: > > I

Re: [icinga-users] Problem with postgres CheckCommand

Apologies, I just noticed that you guys already have an issue tracker, not sure how I missed that. Have opened an issue there ( https://dev.icinga.org/issues/9584) On Mon, Jul 6, 2015 at 4:46 PM, Shay Rojansky wrote: > Hi, sorry for the delayed response on this. > > My check looks

[icinga-users] [icingaweb2] HTML links in plugin output

The interfacetable plugins outputs an HTML link as part of its output, so that users can click and receive more information. However, in icingaweb2 this seems to be escaped, and I end up with this instead of the link: OK - 45 port(s), 0 free, 0 AdminUp and free [details] Anyone know how to solve

Re: [icinga-users] Icinga 2.3.7 breaks ido-pgsql

The same happened to me upon upgrading to 2.3.7. Truncating the icinga_endpointstatus fixed the issue. Markus, the issue link you sent points to an unrelated issue... On Thu, Jul 16, 2015 at 11:05 AM, Markus Joosten wrote: > Hi list, > > i just upgraded my central icinga2 instance to 2.3.7 and

[icinga-users] Dependencies not taken into account in icingaweb2?

Hi everyone. I'm just wondering... When a host fails, icingaweb2 seems to show its failed services as well; I'm guessing this happens because the service check happened to execute and fail before the host check, and the service's failed check continues to be shown in the UI even though the host is