Important

If you do not know how to change the values of theses parameters, don’t touch them :) (and ask for help on the mailing list).

## Performance data parameters¶

### Performance Data Processor Command Timeout¶

Format:

perfdata_timeout=<seconds>


Example:

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>


Example:

process_performance_data=1


This value determines whether or not Shinken will process host and service check performance data.

• 0 = Don’t process performance data
• 1 = Process performance data (default)

If you want to use tools like PNP, NagiosGrapher or Graphite set it to 1.

### Host/Service Performance Data Processing Command¶

Format:

host_perfdata_command=<configobjects/command>
service_perfdata_command=<configobjects/command>


Example:

host_perfdata_command=process-host-perfdata
services_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.

### Host/Service Performance Data File¶

Format:

host_perfdata_file=<file_name>
service_perfdata_file=<file_name>


Example:

host_perfdata_file=/var/lib/shinken/host-perfdata.dat
service_perfdata_file=/var/lib/shinken/service-perfdata.dat


This option allows you to specify a file to which host/service performance data will be written after every host check. Data will be written to the performance file as specified by the Host Performance Data File Template option or the service one. Performance data is only written to this file if the Performance Data Processing Option option is enabled globally and if the “process_perf_data” directive in the host definition is enabled.

### Host Performance Data File Template¶

Format:

host_perfdata_file_template=<template>


Example:

host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$


This option determines what (and how) data is written to the host performance data file. The template may contain macros, special characters (t for tab, r for carriage return, n for newline) and plain text. A newline is automatically added after each write to the performance data file.

### Service Performance Data File Template¶

Format:

service_perfdata_file_template=<template>


Example:

service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$


This option determines what (and how) data is written to the service performance data file. The template may contain macros, special characters (t for tab, r for carriage return, n for newline) and plain text. A newline is automatically added after each write to the performance data file.

### Host/Service Performance Data File Mode¶

Format:

host_perfdata_file_mode=<mode>
service_perfdata_file_mode=<mode>


Example:

host_perfdata_file_mode=a
service_perfdata_file_mode=a


This option determines how the host performance data file (or the service one) is opened. Unless the file is a named pipe you’ll probably want to use the default mode of append.

• a = Open file in append mode (default)
• w = Open file in write mode
• p = Open in non-blocking read/write mode (useful when writing to pipes)

### Host/Service Performance Data File Processing Interval (Unused)¶

Format:

host_perfdata_file_processing_interval=<seconds>
service_perfdata_file_processing_interval=<seconds>


Example:

host_perfdata_file_processing_interval=0
service_perfdata_file_processing_interval=0


This option allows you to specify the interval (in seconds) at which the host performance data file (or the service one) is processed using the host performance data file processing command. A value of 0 indicates that the performance data file should not be processed at regular intervals.

### Host/Service Performance Data File Processing Command (Unused)¶

Format:

host_perfdata_file_processing_command=<configobjects/command>
service_perfdata_file_processing_command=<configobjects/command>


Example:

host_perfdata_file_processing_command=process-host-perfdata-file
service_perfdata_file_processing_command=process-service-perfdata-file


This option allows you to specify the command that should be executed to process the host performance data file (or the service one). The command argument is the short name of a command definition that you define in your object configuration file. The interval at which this command is executed is determined by the host_perfdata_file_processing_interval directive.

### Passive Host Checks Are SOFT Option (Not implemented)¶

Format:

passive_host_checks_are_soft=<0/1>


Example:

passive_host_checks_are_soft=1


This option determines whether or not Shinken will treat passive host checks as HARD states or SOFT states. By default, a passive host check result will put a host into a HARD state type. You can change this behavior by enabling this option.

• 0 = Passive host checks are HARD (default)
• 1 = Passive host checks are SOFT

### Predictive Host/Service Dependency Checks Option (Unused)¶

Format:

enable_predictive_host_dependency_checks=<0/1>
enable_predictive_service_dependency_checks=<0/1>


Example:

enable_predictive_host_dependency_checks=1
enable_predictive_service_dependency_checks=1


This option determines whether or not Shinken will execute predictive checks of hosts/services that are being depended upon (as defined in host/services dependencies) for a particular host/service when it changes state. Predictive checks help ensure that the dependency logic is as accurate as possible. More information on how predictive checks work can be found here.

• 0 = Disable predictive checks
• 1 = Enable predictive checks (default)

### Orphaned Host/Service Check Option¶

Format:

check_for_orphaned_services=<0/1>
check_for_orphaned_hosts=<0/1>


Example:

check_for_orphaned_services=1
check_for_orphaned_hosts=1


This option allows you to enable or disable checks for orphaned service/host checks. Orphaned checks are checks which have been launched to pollers but have not had any results reported in a long time.

Since 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 - it might happen if an external user or process killed off the process that was being used to execute a check.

If this option is enabled and Shinken finds that results for a particular check have not come back, it will log an error message and reschedule the check. If you start seeing checks that never seem to get rescheduled, enable this option and see if you notice any log messages about orphaned services.

• 0 = Don’t check for orphaned service checks
• 1 = Check for orphaned service checks (default)

### Soft State Dependencies Option (Not implemented)¶

Format: soft_state_dependencies=<0/1> Example: soft_state_dependencies=0

This option determines whether or not Shinken will use soft state information when checking host and service dependencies. Normally it will only use the latest hard host or service state when checking dependencies. If you want it to use the latest state (regardless of whether its a soft or hard state type), enable this option.

• 0 = Don’t use soft state dependencies (default)
• 1 = Use soft state dependencies

## Performance tuning¶

### Cached Host/Service Check Horizon¶

Format:

cached_host_check_horizon=<seconds>
cached_service_check_horizon=<seconds>


Example:

cached_host_check_horizon=15
cached_service_check_horizon=15


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. More information on cached checks can be found here.

Tip

Nagios default is 15s, but it’s a tweak that make checks less accurate. So Shinken use 0s as a default. If you have performances problems and you can’t add a new scheduler or poller, increase this value and start to buy a new server because this won’t be magical.

### Large Installation Tweaks Option¶

Format:

use_large_installation_tweaks=<0/1>


Example:

use_large_installation_tweaks=0


This option determines whether or not the Shinken daemon will take shortcuts to improve performance. These shortcuts result in the loss of a few features, but larger installations will likely see a lot of benefit from doing so. If you can’t add new satellites to manage the load (like new pollers), you can activate it. More information on what optimizations are taken when you enable this option can be found here.

• 0 = Don’t use tweaks (default)
• 1 = Use tweaks

## Flapping parameters¶

### Flap Detection Option¶

Format:

enable_flap_detection=<0/1>


Example:

enable_flap_detection=1


This option determines whether or not Shinken will try and detect hosts and services that are “flapping”. Flapping occurs when a host or service changes between states too frequently, resulting in a barrage of notifications being sent out. When Shinken detects that a host or service is flapping, it will temporarily suppress notifications for that host/service until it stops flapping.

More information on how flap detection and handling works can be found here.

• 0 = Don’t enable flap detection (default)
• 1 = Enable flap detection

### Low Service/Host Flap Threshold¶

Format:

low_service_flap_threshold=<percent>
low_host_flap_threshold=<percent>


Example:

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>


Example:

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
ocsp_timeout=<seconds>           # default: 15s
ochp_timeout=<seconds>           # default: 15s


Example:

event_handler_timeout=60
ocsp_timeout=5
ochp_timeout=5


This is the maximum number of seconds that Shinken will allow event handlers, notification, obsessive compulsive service processor command or a Obsessive Compulsive Host Processor Command to be run. If an 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, less for oc*p commands), 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.

## Old Obsess Over commands¶

### Obsess Over Services Option¶

Format:

obsess_over_services=<0/1>


Example:

obsess_over_services=1


This value determines whether or not Shinken will “obsess” over service checks results and run the obsessive compulsive service processor command you define. I know _ funny name, but it was all I could think of. This option is useful for performing distributed monitoring. If you’re not doing distributed monitoring, don’t enable this option.

• 0 = Don’t obsess over services (default)
• 1 = Obsess over services

### Obsessive Compulsive Service Processor Command¶

Format:

ocsp_command=<configobjects/command>


Example:

ocsp_command=obsessive_service_handler


This option allows you to specify a command to be run after every service check, which can be useful in distributed monitoring. This command is executed after any event handler or notification commands. The command argument is the short name of a command definition that you define in your object configuration file.

It’s used nearly only for the old school distributed architecture. If you use it, please look at new architecture capabilities that are far efficient than the old one. More information on distributed monitoring can be found here. This command is only executed if the Obsess Over Services Option option is enabled globally and if the “obsess_over_service” directive in the service definition is enabled.

### Obsess Over Hosts Option¶

Format:

obsess_over_hosts=<0/1>


Example:

obsess_over_hosts=1


This value determines whether or not Shinken will “obsess” over host checks results and run the obsessive compulsive host processor command you define. Same like the service one but for hosts :)

• 0 = Don’t obsess over hosts (default)
• 1 = Obsess over hosts

### Obsessive Compulsive Host Processor Command¶

Format:

ochp_command=<configobjects/command>


Example:

ochp_command=obsessive_host_handler


This option allows you to specify a command to be run after every host check, which can be useful in distributed monitoring. This command is executed after any event handler or notification commands. 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 Obsess Over Hosts Option option is enabled globally and if the “obsess_over_host” directive in the host definition is enabled.

## Freshness check¶

### Host/Service Freshness Checking Option¶

Format:

check_service_freshness=<0/1>
check_host_freshness=<0/1>


Example:

check_service_freshness=0
check_host_freshness=0


This option determines whether or not Shinken will periodically check the “freshness” of host/service checks. 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 freshness
• 1 = Check host/service freshness (default)

### Host/Service Freshness Check Interval¶

Format:

service_freshness_check_interval=<seconds>
host_freshness_check_interval=<seconds>


Example:

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.

### Additional Freshness Threshold Latency Option (Not implemented)¶

Format:

additional_freshness_latency=<#>


Example:

additional_freshness_latency=15


This option determines the number of seconds Shinken will add to any host or services freshness threshold it automatically calculates (e.g. those not specified explicitly by the user). More information on freshness checking can be found here.

### Human format for log timestamp¶

Say if the timespam should be a unixtime (default) or a human read one.

Format

human_timestamp_log=[0/1]


Example

human_timestamp_log=0


This directive is used to specify if the timespam before the log entry should be in unixtime (like [1302874960]) which is the default, or a human readable one (like [Fri Apr 15 15:43:19 2011]).

Beware : if you set the human format, some automatic parsing log tools won’t work!

### Resource File¶

Defined in shinken.cfg file.

Format

resource_file=<file_name>


Example:

resource_file=/etc/shinken/resource.cfg


This is used to specify an optional resource file that can contain “$USERn$” Understanding Macros 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.

### Triggers directory¶

Format

triggers_dir=<directory>


Example:

triggers_dir=triggers.d


Used to specify the trigger directory. It will open the directory and look recursively for .trig files.

### Bypass security checks for the Arbiter daemon¶

Defined in brokerd.ini, brokerd-windows.ini, pollerd.ini, pollerd-windows.ini, reactionnerd.ini, schedulerd.ini and schedulerd-windows.ini.

Format:

idontcareaboutsecurity=<0/1>


Example:

idontcareaboutsecurity=0


This option determines whether or not Shinken will allow the Arbiter daemon to run under the root account. If this option is disabled, Shinken will bailout if the nagios_user or the nagios_group is configured with the root account.

The Shinken daemons do not need root right. Without a good reason do not run thems under this account!
• 0 = Be a responsible administrator
• 1 = Make crazy your security manager

Format:

enable_notifications=<0/1>


Example:

enable_notifications=1


This option determines whether or not Shinken will send out notifications. If this option is disabled, Shinken will not send out notifications for any host or service.

Values are as follows:
• 1 = Enable notifications (default)

### Log Rotation Method (Not fully implemented)¶

Format:

log_rotation_method=<n/h/d/w/m>


Example:

log_rotation_method=d


This is the rotation method that you would like Shinken to use for your log file on the broker server. Values are as follows:

• n = None (don’t rotate the log - this is the default)
• h = Hourly (rotate the log at the top of each hour)
• d = Daily (rotate the log at midnight each day)
• w = Weekly (rotate the log at midnight on Saturday)
• m = Monthly (rotate the log at midnight on the last day of the month)

Tip

From now, only the d (Daily) parameter is managed.

### External Command Check Option¶

Format:

check_external_commands=<0/1>


Example:

check_external_commands=1


This option determines whether or not Shinken will check the External Command File for commands that should be executed with the arbiter daemon. More information on external commands can be found here.

• 0 = Don’t check external commands (default)
• 1 = Check external commands (default)

Note

FIX ME : Find the real default value

### External Command File¶

Defined in nagios.cfg file.

Format:

command_file=<file_name>


Example:

command_file=/var/lib/shinken/rw/nagios.cmd


This is the file that Shinken will check for external commands to process with the arbiter daemon. The command CGI writes commands to this file. The external command file is implemented as a named pipe (FIFO), which is created when Nagios starts and removed when it shuts down. More information on external commands can be found here.

Tip

This external command file is not managed under Windows system. Please use others way to send commands like the LiveStatus module for example.

### State Retention Option (Not implemented)¶

Format:

retain_state_information=<0/1>


Example:

retain_state_information=1

This option determines whether or not Shinken will retain state information for hosts and services between program restarts. If you enable this option, you should supply a value for the State Retention File variable. When enabled, Shinken will save all state information for hosts and service before it shuts down (or restarts) and will read in previously saved state information when it starts up again.
• 0 = Don’t retain state information
• 1 = Retain state information (default)

Note

Idea to approve : Mark it as Unused : Related topic. A Shinken module replace it.

### State Retention File¶

Format:

state_retention_file=<file_name>


Example:

state_retention_file=/var/lib/shinken/retention.dat


This is the file that Shinken scheduler daemons will use for storing status, downtime, and comment information before they shuts down. When Shinken is restarted it will use the information stored in this file for setting the initial states of services and hosts before it starts monitoring anything. In order to make Shinken retain state information between program restarts, you must enable the State Retention Option option.

Important

The file format is not the same between Shinken and Nagios! The retention.dat generated with Nagios will not load into Shinken.

## Scheduling parameters¶

### Service/Host Check Execution Option¶

Format:

execute_service_checks=<0/1>
execute_host_checks=<0/1>


Example:

execute_service_checks=1
execute_host_checks=1


This option determines whether or not Shinken will execute service/host checks. 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¶

Format:

accept_passive_service_checks=<0/1>
accept_passive_host_checks=<0/1>


Example:

accept_passive_service_checks=1
accept_passive_host_checks=1


This option determines whether or not Shinken will accept passive service/host checks. If this option is disabled, Nagios will not accept any passive service/host checks.

• 0 = Don’t accept passive service/host checks
• 1 = Accept passive service/host checks (default)

### Event Handler Option¶

Format:

enable_event_handlers=<0/1>


Example:

enable_event_handlers=1


This option determines whether or not Shinken will run event handlers.

• 0 = Disable event handlers
• 1 = Enable event handlers (default)

### Syslog Logging Option¶

Format:

use_syslog=<0/1>


Example:

use_syslog=1


This variable determines whether messages are logged to the syslog facility on your local host. Values are as follows:

• 0 = Don’t use syslog facility
• 1 = Use syslog facility

Tip

This is a Unix Os only option.

Format:

log_notifications=<0/1>


Example:

log_notifications=1


This variable determines whether or not notification messages are logged. If you have a lot of contacts or regular service 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.

• 0 = Don’t log notifications

### Service/Host Check Retry Logging Option (Not implemented)¶

Format:

log_service_retries=<0/1>
log_host_retries=<0/1>


Example:

log_service_retries=0
log_host_retries=0


This variable determines whether or not service/host check retries are logged. Service check retries occur when a service check results in a non-OK state, but you have configured Shinken to retry the service more than once before responding to the error. Services in this situation are considered to be in “soft” states. Logging service check retries is mostly useful when attempting to debug Shinken or test out service/host event handlers.

• 0 = Don’t log service/host check retries (default)
• 1 = Log service/host check retries

### Event Handler Logging Option¶

Format:

log_event_handlers=<0/1>


Example:

log_event_handlers=1


This variable determines whether or not service and host event handlers are logged. Event handlers are optional commands that can be run whenever a service or hosts changes state. Logging event handlers is most useful when debugging Shinken or first trying out your event handler scripts.

• 0 = Don’t log event handlers
• 1 = Log event handlers

### External Command Logging Option¶

Format:

log_external_commands=<0/1>


Example:

log_external_commands=1


This variable determines whether or not Shinken will log external commands that it receives.

• 0 = Don’t log external commands
• 1 = Log external commands (default)

### Passive Check Logging Option (Not implemented)¶

Format:

log_passive_checks=<0/1>


Example:

log_passive_checks=1


This variable determines whether or not Shinken will log passive host and service checks that it receives from the external command file.

• 0 = Don’t log passive checks
• 1 = Log passive checks (default)

### Global Host/Service Event Handler Option (Not implemented)¶

Format:

global_host_event_handler=<configobjects/command>
global_service_event_handler=<configobjects/command>


Example:

global_host_event_handler=log-host-event-to-db
global_service_event_handler=log-service-event-to-db


This option allows you to specify a host event handler command that is to be run for every host state change. The global event handler is executed immediately prior to the event handler that you have optionally specified in each host definition. The command argument is the short name of a command that you define in your Object Configuration Overview. The maximum amount of time that this command can run is controlled by the Event Handler Timeout option. More information on event handlers can be found here.

Such commands should not be so useful with the new Shinken distributed architecture. If you use it, look if you can avoid it because such commands will kill your performances.

### Timing Interval Length¶

Format:

interval_length=<seconds>


Example:

interval_length=60


This is the number of seconds per “unit interval” used for timing in the scheduling queue, re-notifications, etc. “Units intervals” are used in the object configuration file to determine how often to run a service check, how often to re-notify a contact, etc.

The default value for this is set to 60, which means that a “unit value” of 1 in the object configuration file will mean 60 seconds (1 minute).

Tip

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. Nearly no one need such hard real time (maybe only the Nuclear center or a market place like the London Exchange...).

## Unused parameters¶

The below parameters are inherited from Nagios but are not used in Shinken. You can defined them but if you don’t it will be the same :)

They are listed on another page unused Nagios parameters.

## All the others :)¶

### Date Format (Not implemented)¶

Format:

date_format=<option>


Example:

date_format=us


This option allows you to specify what kind of date/time format Shinken should use in date/time macros. Possible options (along with example output) include:

 Option Output Format Sample Output us MM/DD/YYYY HH:MM:SS 06/30/2002 03:15:00 euro DD/MM/YYYY HH:MM:SS 30/06/2002 03:15:00 iso8601 YYYY-MM-DD HH:MM:SS 2002-06-30 03:15:00 strict-iso8601 YYYY-MM-DDTHH:MM:SS 2002-06-30T03:15:00

### Illegal Object Name Characters¶

Format:

illegal_object_name_chars=<chars...>


Example:

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 will allow you to use most characters in object definitions, but I recommend not using the characters shown in the example above. Doing may give you problems in the web interface, notification commands, etc. ### Illegal Macro Output Characters¶ Format: illegal_macro_output_chars=<chars...>  Example: illegal_macro_output_chars=-$^&"|'<>


This option allows you to specify illegal characters that should be stripped from macros before being used in notifications, event handlers, and other commands. This DOES NOT affect macros used in service or host check commands. You can choose to not strip out the characters shown in the example above, but I recommend you do not do this. Some of these characters are interpreted by the shell (i.e. the backtick) and can lead to security problems. The following macros are stripped of the characters you specify:

• “$HOSTOUTPUT$”
• “$HOSTPERFDATA$”
• “$HOSTACKAUTHOR$”
• “$HOSTACKCOMMENT$”
• “$SERVICEOUTPUT$”
• “$SERVICEPERFDATA$”
• “$SERVICEACKAUTHOR$”
• “$SERVICEACKCOMMENT$”

### Regular Expression Matching Option (Not implemented)¶

Format:

use_regexp_matching=<0/1>


Example:

use_regexp_matching=0


This option determines whether or not various directives in your Object Configuration Overview will be processed as regular expressions. More information on how this works can be found here.

• 0 = Don’t use regular expression matching (default)
• 1 = Use regular expression matching

### True Regular Expression Matching Option (Not implemented)¶

Format:

use_true_regexp_matching=<0/1>


Example:

use_true_regexp_matching=0


If you’ve enabled regular expression matching of various object directives using the Regular Expression Matching Option option, this option will determine when object directives are treated as regular expressions. If this option is disabled (the default), directives will only be treated as regular expressions if they contain *, ?, +, or .. If this option is enabled, all appropriate directives will be treated as regular expression _ be careful when enabling this! More information on how this works can be found here.

• 0 = Don’t use true regular expression matching (default)
• 1 = Use true regular expression matching

Format:

admin_email=<email_address>


Example:

admin_email=root@localhost.localdomain


This is the email address for the administrator of the local machine (i.e. the one that Shinken is running on). This value can be used in notification commands by using the “$ADMINEMAIL$” macro.

Format:

admin_pager=<pager_number_or_pager_email_gateway>


Example:

admin_pager=pageroot@localhost.localdomain


This is the pager number (or pager email gateway) for the administrator of the local machine (i.e. the one that Shinken is running on). The pager number/address can be used in notification commands by using the $ADMINPAGER$ macro.

### Shinken.io api_key¶

Format:

api_key=<api_key>


Example:

api_key=AZERTYUIOP


This is the api_key/scret to exchange with shinken.io and especially the kernel.shinken.io service that will print your shinken metrics. To enable it you must fill the api_key and secret parameters. You must register to http://shinken.io and look at your profile http://shinken.io/~ for your api_key and your secret.

### Shinken.io secret¶

Format:

secret=<secret>


Example:

secret=QSDFGHJ


This is the api_key/scret to exchange with shinken.io and especially the kernel.shinken.io service that will print your shinken metrics. To enable it you must fill the api_key and secret parameters. You must register to http://shinken.io and look at your profile http://shinken.io/~ for your api_key and your secret.

### Statsd host¶

Format:

statsd_host=<host or ip>


Example:

statsd_host=localhost


### Statsd port¶

Format:

statsd_port=<int>


Example:

statsd_port=8125


Configure your local statsd daemon port. Notice that the port is in UDP

### Statsd prefix¶

Format:

statsd_prefix=<string>


Example:

statsd_prefix=shinken


The prefix to add before all your stats so you will find them easily in graphite

### Statsd enabled (or not)¶

Format:

statsd_enabled=<0/1>


Example:

statsd_enabled=0


Enable or not the statsd communication. By default it’s disabled.