You could use netdata and call to the API to query the values you are
looking for. The bonus is you get a lot of other metrics too. It would
be possible to replace Icinga Client/NRPE with netdata.
On 6/5/2019 3:00 AM, Mueller, Simon wrote:
Hello Community,
we are searching for a possibilit
So I was going to go on a long diatribe about the necessity for
dependencies across zones, but I found, really by accident, that most of
what I was looking for was already in place. My goal is to have the
master zone send notifications based on dependency enforcement and not
the child zones.
For an initial query to sync up just query the objects tree. The
objects include the state. If you wanted to have a smaller query assume
that all objects are OK/UP and do a filtered query for all non-ok states.
On 10/4/2016 7:47 AM, Marcelus Trojahn wrote:
Hello,
I've been using the stream
Are the plugins installed on the client? Depending on your service
configuration it may be attempting to run this plugin on the client and
not the server.
On 5/13/2016 7:55 AM, Joel A Divekar wrote:
Hi All
I have just added a linux client for monitoring on Icinga2 server, the
dashboard sho
Your oid is a string and should be enclosed in quotes:
vars.snmp_oid = .1.3.6.1.4.1.9.9.13.1.5.1.2.2006 => vars.snmp_oid =
".1.3.6.1.4.1.9.9.13.1.5.1.2.2006"
On 2/8/2016 11:40 PM, Wesemeyer, Heiko wrote:
Good morning everyone,
I've got some troubles to check our Cisco Catalyst Stacks with I
I've been working on an HA setup and had a lot of difficulties. Most of
them self-induced. I worked through them all but 1. I seem to have a
database lock issue on the icinga_customvariables table.
I've got 2 machines in an HA pair. hostA is the "config master". When I
start hostA everythin
I'm tying to build the arguments dictionary dynamically from values in a
host dictionary object called hosts.vars.meta and not having a lot of
success. I did find the section in the docs that does something similar
to what I'm doing
(http://docs.icinga.org/icinga2/latest/doc/module/icinga2/cha
Question on the conversations around Feature 6228: delay or suppress
recovery notification if host/service is in a downtime
What is the state of that? From my perspective if I put a host in
downtime even after the down/critical notification came out then I don't
want to hear anything else fro
4 um 01:02 schrieb Barry Quiel:
Icinga1 had a notification number macro:
$HOSTNOTIFICATIONNUMBER$
$SERVICENOTIFICATIONNUMBER$
I don't see any Icinga2 doc on that macro. Was it not carried forward
to Icinga2?
Those macros are not valid if you consider the new notification object.
You cannot re
Icinga1 had a notification number macro:
$HOSTNOTIFICATIONNUMBER$
$SERVICENOTIFICATIONNUMBER$
I don't see any Icinga2 doc on that macro. Was it not carried forward to
Icinga2?
I can see that info in the web interface listed in the attempt column:
1/3(#112)
How can I get that data out to my
e as long as one check interval has been completed and the
interface is soft critical, the BGP session won't notify. Since we use
max_retries that will always be true.
On 11/1/2014 9:36 AM, Michael Friedrich wrote:
Am 17.10.2014 um 23:43 schrieb Barry Quiel:
I can't find any refe
I can't find any reference in the Icinga 2 docs to the Icinga 1 feature
soft_state_dependencies. I didn't find any reference on the
monitoring-portal boards or in the icinga users mail archive.
Was this option carried forward from Icinga 1?
Is in an implicit option now?
Was it renamed?
With ou
12 matches
Mail list logo