Performance data parameters
Performance Data Processor Command Timeout
Format:
perfdata_timeout=<seconds>
...
perfdata_timeout=5
This is the maximum number of seconds that Shinken will allow a host performance data processor command or service performance data processor command to be run. If a command exceeds this time limit it will be killed and a warning will be logged.
Performance Data Processing Option
Format:
process_performance_data=<0/1>
...
- 1 = Process performance data (default)
Host/Service Performance Data Processing Command
Format:
host_perfdata_command=<configobjects/command>
service_perfdata_command=<configobjects/command>
...
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 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.
Advanced scheduling parameters
Orphaned Host/Service Check Option
Format:
check_for_orphaned_services=<0/1>
check_for_orphaned_hosts=<0/1>
...
- 1 = Check for orphaned service checks (default)
Performance tuning
Cached Host/Service Check Horizon
Format:
cached_host_check_horizon=<seconds>
cached_service_check_horizon=<seconds>
...
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 that were performed more recently than the time specified by this value) can improve host check performance immensely. Too high of a value for this option may result in (temporarily) inaccurate host/service states, while a low value may result in a performance hit for host/service checks. Use a value of 0 if you want to disable host/service check caching.
Flapping parameters
Flap Detection Option
Format:
enable_flap_detection=<0/1>
...
- 1 = Enable flap detection
Low Service/Host Flap Threshold
Format:
low_service_flap_threshold=<percent>
low_host_flap_threshold=<percent>
...
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 flapping. For more information on how flap detection and handling works (and how this option affects things) read this.
High Service/Host Flap Threshold
Format:
high_service_flap_threshold=<percent>
high_host_flap_threshold=<percent>
...
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 flapping. For more information on how flap detection and handling works (and how this option affects things) read this.
Various commands Timeouts
Format:
event_handler_timeout=<seconds> # default: 30s
notification_timeout=<seconds> # default: 30s
...
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 will kill it off thinking it is a runaway processes.
Freshness check
Host/Service Freshness Checking Option
Format:
check_service_freshness=<0/1>
check_host_freshness=<0/1>
...
- 1 = Check host/service freshness (default)
Host/Service Freshness Check Interval
Format:
service_freshness_check_interval=<seconds>
host_freshness_check_interval=<seconds>
...
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 freshness checking (with the check_service_freshness option), this option has no effect. More information on freshness checking can be found here.
Resource File
Format
resource_file=<file_name>
...
This is used to specify an optional resource file that can contain "$USERn$" Understanding Macros/Data and How They Work definitions. "$USERn$" macros are useful for storing usernames, passwords, and items commonly used in command definitions (like directory paths).
A classical variable used is $USER1$, used to store the plugins path, "/usr/lib/nagios/plugins" on a classic installation.
Notifications Option
Format:
enable_notifications=<0/1>
...
- 1 = Enable notifications (default)
Log Rotation Method (Not fully implemented)
Format:
log_rotation_method=<d>
...
- d = Daily (rotate the log at midnight each day)
External Command Check Option
Format:
check_external_commands=<0/1>
...
- 1 = Check external commands (default)
Scheduling parameters
Service/Host Check Execution Option
Format:
execute_service_checks=<0/1>
execute_host_checks=<0/1>
...
- 1 = Execute service checks (default)
Passive Service/Host Check Acceptance Option
Format:
accept_passive_service_checks=<0/1>
accept_passive_host_checks=<0/1>
...
- 1 = Accept passive service/host checks (default)
Event Handler Option
Format:
enable_event_handlers=<0/1>
...
- 1 = Enable event handlers (default)
Notification Logging Option
Format:
log_notifications=<0/1>
...
- 0 = Don't log notifications
- 1 = Log notifications
Event Handler Logging Option
Format:
log_event_handlers=<0/1>
...
- 0 = Don't log event handlers
- 1 = Log event handlers
External Command Logging Option
Format:
log_external_commands=<0/1>
...
- 1 = Log external commands (default)
Passive Check Logging Option (Not implemented)
Format:
log_passive_checks=<0/1>
...
- 1 = Log passive checks (default)
Timing Interval Length
Format:
interval_length=<seconds>
...
Note that set this option top 1 is not a good thing with Shinken. It's not design to be a hard real time (<5seconds) monitoring system.
Others
Illegal Object Name Characters
Format:
illegal_object_name_chars=<chars...>
...