On Tue, 3 Feb 2015, Michael Friedrich wrote:
Nsca writes to cmd pipe or checkresult spooldir - features which can be
enabled in icinga2, enabling seamless migration.
Greetings from cfgmgmtcamp,
Michael
Ok.
Now I have nsca daemon working :-)
Added:
command_path = "/var/spool/icinga2/cmd/icinga.cmd"
in /etc/icinga2/features-available/command.conf.
It is time to say to Icinga as to treat the data received :-)
In 1.x I created templates like the following :
define host{
name generic-client
notifications_enabled 0
event_handler_enabled 1
flap_detection_enabled 0
failure_prediction_enabled 0
process_perf_data 1
retain_status_information 1
retain_nonstatus_information 1
notification_period 24x7
register 0
}
define host{
name windows-client
use generic-client
check_period 24x7
check_interval 2
retry_interval 1
max_check_attempts 1
check_command check_dummyA!3!$HOST$!$SERVICEDESC$!$SHORTDATETIME$
notification_period 24x7
notification_interval 30
notification_options d,r
contact_groups admins
hostgroups windows-clients
register 0
}
I am reading the docs and already migrated something, but it is a really
big issue for someone that isn't familiar with the product (the migration
script fail).
If anyone can kindly translate these templates in 2.x syntax I can use it
as reference.
Thanks, P.
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users
