Service Template options?

Icinga 2
1

Hi everyone!

Is there a list of every options you can enable or disable?
For example : enable active checks, enable event handler, etc.
I found a couple ones but not all of them.

I have all of these to transfer from Nagios…

active_checks_enabled 1
passive_checks_enabled 1
parallelize_check 1
check_freshness 0
notifications_enabled 1
event_handler_enabled 0
flap_detection_enabled 0
failure_prediction_enabled 0
process_perf_data 1
retain_status_information 1
retain_nonstatus_information 1
is_volatile 0
check_period 24x7
max_check_attempts 3
normal_check_interval 5
retry_check_interval 1
contacts null_contact
notification_options n
notification_interval 60
notification_period none
notes_url /pnp4nagios/index.php/graph?host=$HOSTNAME$&srv=$SERVICEDESC$
register 0

thank you :slight_smile:

2

Hi,

the object types chapter has them all.
https://icinga.com/docs/icinga2/latest/doc/09-object-types/

Some old attributes cannot be mapped or their functionality differs - the migration chapter may be of help here.

Cheers,
Michel

2 Likes
3

Thank you Michael. I’m currently looking at this chapter.

Would you happen to know about those? I couldn’t find them…

-parallelize_check
-check_freshness
-failure_prediction_enabled
-retain_status_information
-retain_nonstatus_information
-contact (is set to null_contrat in my Nagios)
-notification_options (set to "n’ in Nagios)
-notification_interval
-notification_period
-register

Sorry I know it’s a lot :frowning:
thank you so much
Gen

4

Hi,

Irrelevant, Icinga 2 scales horizontally on its own.

Freshness checks are enabled by default, see this chapter.

https://icinga.com/docs/icinga2/latest/doc/08-advanced-topics/#check-result-freshness

Has no effect in Nagios either, their code has some ugly TODO statements in there.

status.dat relevancy, 2.x doesn’t support this. The state file persists runtime data over reload, as well as modified attributes. There is no way to additionally control this. These settings have weird names and weird behaviour.

Icinga 2 uses notification objects to manage users (previously called contacts) and commands, intervals, etc. These notification objects are tied to host and service objects.

https://icinga.com/docs/icinga2/latest/doc/03-monitoring-basics/#notifications
https://icinga.com/docs/icinga2/latest/doc/23-migrating-from-icinga-1x/#notifications

With the power of apply rules, one can create some simple notification rules and don’t need to edit each host/service object no more.

https://icinga.com/docs/icinga2/latest/doc/03-monitoring-basics/#apply-rules

Nagios had a strange way of defining templates. Each register 0 definition was read as a template, but not registered as object to the core.

Icinga 2 uses the keyword template for these object attribute providers.

https://icinga.com/docs/icinga2/latest/doc/03-monitoring-basics/#templates

Recommendation

I highly recommend to do an inventory of these objects as well, and use apply rules to not re-invent the wheel all the time.

Cheers,
Michael

5

Amazing thank you again Michael!

6

Please pick a reply and mark it as solution - this helps others to immediately see and search for such topics. More: Mark a topic as solved