...
perfdata_timeout=5
This is the maximum number of seconds that Shinken will allow to run a host performance data processor command or service or check performance data processor command to be run. If a command exceeds this time limit it will be killed and a warning will be logged.
...
process_performance_data=1
This value determines whether or not if Shinken Enterprise will process host and service /check performance data.
- 0 = Don't process performance data
...
host_perfdata_command=process-host-perfdata
service_perfdata_command=process-service-perfdata
This option allows you to specify a command to be run after every host/service check to process host/service check performance data that may be returned from the check. The command argument is the short name of a command definition that you define in your object configuration file. This command is only executed if the Performance Data Processing Option option is enabled globally and if the "process_perf_data" directive in the host definition is enabled.
...
check_for_orphaned_services=1
check_for_orphaned_hosts=1
This option allows you to enable or disable checks for orphaned servicehost/host checkscheck. Orphaned checks are checks which have been launched to pollers but have did not had get any results reported in for a long time.
Since there is no results have come back in for it, it is not rescheduled in the event queue. This can cause checks to stop being executed. Normally it is very rare for this to happen should happen very rarely - it might happen if an external user or a process killed off the process that was being used to execute a check.
If this option is enabled and Shinken finds that results Enterprise does not find results back for a particular check have not come back, it will log an error message and reschedule the check. If you start seeing see checks that never seem to get rescheduled, enable this option and see if you notice any log messages about orphaned services.
...
cached_host_check_horizon=0
cached_service_check_horizon=0
This option determines the maximum amount of time (in seconds) that the state of a previous host check is considered current. Cached host states (from host/service checks check that were performed more recently than the time specified by this value) can hugely improve host check performance immensely. Too high of a value If the value is too high for this option it may result in (temporarily) inaccurate host/service states, while a check states. A low value may result in a performance hit for host/service checkscheck. Use a value of 0 if you want to disable host/service check caching.
Flapping parameters
...
enable_flap_detection=1
This option determines whether or not Shinken Enterprise will try and detect hosts and services checks that are “flapping". Flapping occurs when a host or service check changes between states too frequently, resulting in a barrage of notifications being sent out. When Shinken Enterprise detects that a flapping host or service is flappingcheck, it will temporarily suppress notifications for that host/service check until it stops flapping.
More information on how flap detection and handling works can be found here <advanced/flapping>`.
...
low_service_flap_threshold=25.0
low_host_flap_threshold=25.0
This option is used to set the low threshold for detection of host/service check flapping. For more information on how flap detection and handling works (and how this option affects things) read this.
...
high_service_flap_threshold=50.0
high_host_flap_threshold=50.0
This option is used to set the high threshold for detection of host/service check flapping. For more information on how flap detection and handling works (and how this option affects things) read this.
...
event_handler_timeout=60
notification_timeout=60
This is the maximum number of seconds that Shinken will allow to run event handlers & notification to be run notification. If an a command exceeds this time limit it will be killed and a warning will be logged.
There is often widespread confusion as to what this option really does. It is meant to be used as a last ditch mechanism to kill off commands which are misbehaving and not exiting in a timely manner. It should be set to something high (like 60 seconds or more for notification), so that each event handler command normally finishes executing within this time limit. If an event handler runs longer than this limit, Shinken Enterprise will kill it off thinking it is a runaway processesprocess.
Freshness check
Host/Service Freshness Checking Option
...
check_service_freshness=0
check_host_freshness=0
This option determines whether or not if Shinken Enterprise will periodically check the “freshness" of host/service checkscheck. Enabling this option is useful for helping to ensure that passive service checks are received in a timely manner. More information on freshness checking can be found here.
- 0 = Don't check host/service check freshness
- 1 = Check host/service check freshness (default)
Host/Service Freshness Check Interval
...
service_freshness_check_interval=60
host_freshness_check_interval=60
This setting determines how often (in seconds) Shinken will periodically check the “freshness" of host/service check results. If you have disabled host/service check freshness checking (with the check_service_freshness option), this option has no effect. More information on freshness checking can be found here.
...
enable_notifications=1
This option determines whether or not if Shinken Enterprise will send out notifications. If this option is disabled, Shinken will not send out notifications for any host or servicecheck.
Values are as follows:
- 0 = Disable notifications
...
This is the rotation method that you would like Shinken to use used by Shinken Enterprise for your log file on the broker server . Values are as follows:
...
check_external_commands=1
This option determines whether or not if Shinken Enterprise will check the External Command File for commands that should be executed with the arbiter daemon .
...
execute_service_checks=1
execute_host_checks=1
This option determines whether or not if Shinken Enterprise will execute servicehost/host checkscheck. Do not change this option unless you use a old school distributed architecture. And even if you do this, please change your architecture with a cool new one far more efficient.
- 0 = Don't execute service checks
- 1 = Execute service checks (default)
Passive Service/Host Check Acceptance Option
...
accept_passive_service_checks=1
accept_passive_host_checks=1
This option determines whether or not if Shinken will accept passive servicehost/host checks. If this option is disabled, Nagios will not accept any passive servicehost/host checks.
- 0 = Don't accept passive servicehost/host checks
- 1 = Accept passive servicehost/host checks (default)
Event Handler Option
...
enable_event_handlers=1
This option determines whether or not if Shinken Enterprise will run event handlers.
- 0 = Disable event handlers
...
log_notifications=1
This variable determines whether or not if notification messages are logged. If you have a lot of contacts or regular service check failures your log file will grow (let say some Mo by day for a huge configuration, so it's quite OK for nearly every one to log them). Use this option to keep contact notifications from being logged.
...
log_event_handlers=1
This variable determines whether or not service if check and host event handlers are logged. Event handlers are optional commands that can be run whenever a service check or hosts changes state. Logging event handlers is most useful when debugging Shinken Enterprise or first trying out your event handler scripts.
...
log_external_commands=1
This variable determines whether or not if Shinken Enterprise will log external commands that it receives.
...
log_passive_checks=1
This variable determines whether or not if Shinken Enterprise will log passive host and service /checks that it receives from the external commands.
...
Note that set this option top 1 is not a good thing with Shinken Enterprise. It's not design to be a hard real time (<5seconds) monitoring system.
...
illegal_object_name_chars=`-!$%^&*"|'<>?,()=
This option allows you to specify illegal characters that cannot be used in host names, service descriptions, or names of other object types. Shinken Enterprise will allow you to use most characters in object definitions, but I we recommend not using the characters shown in the example above. Doing may give you problems in the web interface, notification commands, etc.
...