Am 06.10.2014 um 11:55 schrieb Linder, Rolf:
Hi all

We are running two monitoring nodes (one „big” Icinga_v1 cluster around 24k 
services, one “small” nagios-based around 300 services) which we both plan to 
migrate to icinga2.
Currently we’re setting up the small system and would like to use icinga2 
(instead of migrating it to icinga1).

We have seen two issues, where we we’re unable to find any hints on docs / 
google searches and we wonder if anyone else had seen these so far…

Command definitions which uses pipes
-------------------------------------------------
We’re using some plugins which uses the pipe (“|”) as argument (check_snmp_storage 
-> with the pipe you separate different partitions). The pipe sign does not 
generate a config-error but in command execution everything after pipe is ignored 
(maybe this is a missing security check / escaping?). it seems from a user 
perspective, that this way you could also do things which should not be able to 
(pipe and linux)?
Any help on how to use plugins which themselves uses “|” in arguments would be 
highly appreciated (we tried escaping with \ but with no luck). Here’s the 
corresponding command definition from icinga v1:

define command {
               command_name                          
usp_check_general_snmpstorage_command
               command_line                          $USER11$/check_snmp_storage.pl -f -C 
$_HOSTSNMPCOMMUNITY$  -H $HOSTADDRESS$ -q "FixedDisk|NetworkDisk" 
$_HOSTSNMPSTORAGELST$ -w $ARG1$ -c $ARG2$ -2
}

The custom macro “$_HOSTSNMPSTORAGELST$” is set to “-m '^/' -m 
'^/sys|^/dev/shm|^/net' –e”

And your Icinga 2 check command & service object definitions look like?



“excluding” timeperiods
-------------------------------
In icinga v1 you can setup different timeperiods (i.e. your SLA timeperiod and 
holiday) and later you can exclude one within. We’re using this on lower SLAs 
to exclude holidays (one timeperiod tracks all holidays and this is 
assigned/excluded in different other timeperiods).
In icinga2 there’s no hint in docs on how you can setup an exclude…some 
experiments block you with a config failure others will not show any config 
error but upon reload you won’t see any excludes (in config classic UI config 
view). Generally we would like to setup a behavior like 
http://docs.icinga.org/latest/en/sample-timeperiods.html but with icinga2. Does 
anyone know how to do this?

Timeperiod exlusions never really worked in Icinga 1.x / Nagios, there were 
certain bugs included for years, which never have been fixed properly.

When it comes to configuration viewing, I wouldn't use the old Classic UI 
interface which just present merged compatible objects, but rather relay on 
what Icinga 2 uses (list objects, etc).

Timeperiod exclusions haven't been implemented, as there was no such feature 
request in the past. If you do have a proposal on how to implement that 
properly (and timeperiods in general), feel free to open a feature request with 
a detailed description.

Kind regards,
Michael

-- 
Michael Friedrich, DI (FH)
Application Developer

NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
Tel: +49 911 92885-0 | Fax: +49 911 92885-77
GF: Julian Hein, Bernd Erk | AG Nuernberg HRB18461
http://www.netways.de | [email protected]

** Puppet Camp Duesseldorf 2014 - Oktober - netways.de/puppetcamp **
** OSMC 2014 - November - netways.de/osmc **
** OpenNebula Conf 2014 - Dezember - opennebulaconf.com **
** OSDC 2015 - April - osdc.de **
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users

Reply via email to