1 # <a id="icinga2-features"></a> Icinga 2 Features
3 ## <a id="logging"></a> Logging
5 Icinga 2 supports three different types of logging:
8 * Syslog (on *NIX-based operating systems)
9 * Console logging (`STDOUT` on tty)
11 You can enable additional loggers using the `icinga2 feature enable`
12 and `icinga2 feature disable` commands to configure loggers:
15 ---------|------------
16 debuglog | Debug log (path: `/var/log/icinga2/debug.log`, severity: `debug` or higher)
17 mainlog | Main log (path: `/var/log/icinga2/icinga2.log`, severity: `information` or higher)
18 syslog | Syslog (severity: `warning` or higher)
20 By default file the `mainlog` feature is enabled. When running Icinga 2
21 on a terminal log messages with severity `information` or higher are
22 written to the console.
24 Packages will install a configuration file for logrotate on supported
25 platforms. This configuration ensures that the `icinga2.log`, `error.log` and
26 `debug.log` files are rotated on a daily basis.
28 ## <a id="db-ido"></a> DB IDO
30 The IDO (Icinga Data Output) modules for Icinga 2 take care of exporting all
31 configuration and status information into a database. The IDO database is used
32 by a number of projects including Icinga Web 1.x and 2.
34 Details on the installation can be found in the [Configuring DB IDO](2-getting-started.md#configuring-db-ido-mysql)
35 chapter. Details on the configuration can be found in the
36 [IdoMysqlConnection](9-object-types.md#objecttype-idomysqlconnection) and
37 [IdoPgsqlConnection](9-object-types.md#objecttype-idopgsqlconnection)
38 object configuration documentation.
39 The DB IDO feature supports [High Availability](6-distributed-monitoring.md#distributed-monitoring-high-availability-db-ido) in
42 The following example query checks the health of the current Icinga 2 instance
43 writing its current status to the DB IDO backend table `icinga_programstatus`
44 every 10 seconds. By default it checks 60 seconds into the past which is a reasonable
45 amount of time -- adjust it for your requirements. If the condition is not met,
46 the query returns an empty result.
50 > Use [check plugins](5-service-monitoring.md#service-monitoring-plugins) to monitor the backend.
52 Replace the `default` string with your instance name if different.
56 # mysql -u root -p icinga -e "SELECT status_update_time FROM icinga_programstatus ps
57 JOIN icinga_instances i ON ps.instance_id=i.instance_id
58 WHERE (UNIX_TIMESTAMP(ps.status_update_time) > UNIX_TIMESTAMP(NOW())-60)
59 AND i.instance_name='default';"
61 +---------------------+
62 | status_update_time |
63 +---------------------+
64 | 2014-05-29 14:29:56 |
65 +---------------------+
68 Example for PostgreSQL:
70 # export PGPASSWORD=icinga; psql -U icinga -d icinga -c "SELECT ps.status_update_time FROM icinga_programstatus AS ps
71 JOIN icinga_instances AS i ON ps.instance_id=i.instance_id
72 WHERE ((SELECT extract(epoch from status_update_time) FROM icinga_programstatus) > (SELECT extract(epoch from now())-60))
73 AND i.instance_name='default'";
76 ------------------------
77 2014-05-29 15:11:38+02
81 A detailed list on the available table attributes can be found in the [DB IDO Schema documentation](23-appendix.md#schema-db-ido).
84 ## <a id="external-commands"></a> External Commands
86 Icinga 2 provides an external command pipe for processing commands
87 triggering specific actions (for example rescheduling a service check
88 through the web interface).
90 In order to enable the `ExternalCommandListener` configuration use the
91 following command and restart Icinga 2 afterwards:
93 # icinga2 feature enable command
95 Icinga 2 creates the command pipe file as `/var/run/icinga2/cmd/icinga2.cmd`
96 using the default configuration.
98 Web interfaces and other Icinga addons are able to send commands to
99 Icinga 2 through the external command pipe, for example for rescheduling
100 a forced service check:
102 # /bin/echo "[`date +%s`] SCHEDULE_FORCED_SVC_CHECK;localhost;ping4;`date +%s`" >> /var/run/icinga2/cmd/icinga2.cmd
104 # tail -f /var/log/messages
106 Oct 17 15:01:25 icinga-server icinga2: Executing external command: [1382014885] SCHEDULE_FORCED_SVC_CHECK;localhost;ping4;1382014885
107 Oct 17 15:01:25 icinga-server icinga2: Rescheduling next check for service 'ping4'
109 A list of currently supported external commands can be found [here](23-appendix.md#external-commands-list-detail).
111 Detailed information on the commands and their required parameters can be found
112 on the [Icinga 1.x documentation](http://docs.icinga.com/latest/en/extcommands2.html).
114 ## <a id="performance-data"></a> Performance Data
116 When a host or service check is executed plugins should provide so-called
117 `performance data`. Next to that additional check performance data
118 can be fetched using Icinga 2 runtime macros such as the check latency
119 or the current service state (or additional custom attributes).
121 The performance data can be passed to external applications which aggregate and
122 store them in their backends. These tools usually generate graphs for historical
123 reporting and trending.
125 Well-known addons processing Icinga performance data are [PNP4Nagios](13-addons.md#addons-graphing-pnp),
126 [Graphite](13-addons.md#addons-graphing-graphite) or [OpenTSDB](14-features.md#opentsdb-writer).
128 ### <a id="writing-performance-data-files"></a> Writing Performance Data Files
130 PNP4Nagios and Graphios use performance data collector daemons to fetch
131 the current performance files for their backend updates.
133 Therefore the Icinga 2 [PerfdataWriter](9-object-types.md#objecttype-perfdatawriter)
134 feature allows you to define the output template format for host and services helped
135 with Icinga 2 runtime vars.
137 host_format_template = "DATATYPE::HOSTPERFDATA\tTIMET::$icinga.timet$\tHOSTNAME::$host.name$\tHOSTPERFDATA::$host.perfdata$\tHOSTCHECKCOMMAND::$host.check_command$\tHOSTSTATE::$host.state$\tHOSTSTATETYPE::$host.state_type$"
138 service_format_template = "DATATYPE::SERVICEPERFDATA\tTIMET::$icinga.timet$\tHOSTNAME::$host.name$\tSERVICEDESC::$service.name$\tSERVICEPERFDATA::$service.perfdata$\tSERVICECHECKCOMMAND::$service.check_command$\tHOSTSTATE::$host.state$\tHOSTSTATETYPE::$host.state_type$\tSERVICESTATE::$service.state$\tSERVICESTATETYPE::$service.state_type$"
140 The default templates are already provided with the Icinga 2 feature configuration
141 which can be enabled using
143 # icinga2 feature enable perfdata
145 By default all performance data files are rotated in a 15 seconds interval into
146 the `/var/spool/icinga2/perfdata/` directory as `host-perfdata.<timestamp>` and
147 `service-perfdata.<timestamp>`.
148 External collectors need to parse the rotated performance data files and then
149 remove the processed files.
151 ### <a id="graphite-carbon-cache-writer"></a> Graphite Carbon Cache Writer
153 While there are some [Graphite](13-addons.md#addons-graphing-graphite)
154 collector scripts and daemons like Graphios available for Icinga 1.x it's more
155 reasonable to directly process the check and plugin performance
156 in memory in Icinga 2. Once there are new metrics available, Icinga 2 will directly
157 write them to the defined Graphite Carbon daemon tcp socket.
159 You can enable the feature using
161 # icinga2 feature enable graphite
163 By default the [GraphiteWriter](9-object-types.md#objecttype-graphitewriter) feature
164 expects the Graphite Carbon Cache to listen at `127.0.0.1` on TCP port `2003`.
166 #### <a id="graphite-carbon-cache-writer-schema"></a> Current Graphite Schema
168 The current naming schema is defined as follows. The official Icinga Web 2 Graphite
169 module will use that schema too.
171 The default prefix for hosts and services is configured using
172 [runtime macros](3-monitoring-basics.md#runtime-macros)like this:
174 icinga2.$host.name$.host.$host.check_command$
175 icinga2.$host.name$.services.$service.name$.$service.check_command$
177 You can customize the prefix name by using the `host_name_template` and
178 `service_name_template` configuration attributes.
180 The additional levels will allow fine granular filters and also template
181 capabilities, e.g. by using the check command `disk` for specific
182 graph templates in web applications rendering the Graphite data.
184 The following characters are escaped in prefix labels:
186 Character | Escaped character
187 --------------|--------------------------
193 Metric values are stored like this:
195 <prefix>.perfdata.<perfdata-label>.value
197 The following characters are escaped in perfdata labels:
199 Character | Escaped character
200 --------------|--------------------------
206 Note that perfdata labels may contain dots (`.`) allowing to
207 add more subsequent levels inside the Graphite tree.
208 `::` adds support for [multi performance labels](http://my-plugin.de/wiki/projects/check_multi/configuration/performance)
209 and is therefore replaced by `.`.
211 By enabling `enable_send_thresholds` Icinga 2 automatically adds the following threshold metrics:
213 <prefix>.perfdata.<perfdata-label>.min
214 <prefix>.perfdata.<perfdata-label>.max
215 <prefix>.perfdata.<perfdata-label>.warn
216 <prefix>.perfdata.<perfdata-label>.crit
218 By enabling `enable_send_metadata` Icinga 2 automatically adds the following metadata metrics:
220 <prefix>.metadata.current_attempt
221 <prefix>.metadata.downtime_depth
222 <prefix>.metadata.acknowledgement
223 <prefix>.metadata.execution_time
224 <prefix>.metadata.latency
225 <prefix>.metadata.max_check_attempts
226 <prefix>.metadata.reachable
227 <prefix>.metadata.state
228 <prefix>.metadata.state_type
230 Metadata metric overview:
233 -------------------|------------------------------------------
234 current_attempt | current check attempt
235 max_check_attempts | maximum check attempts until the hard state is reached
236 reachable | checked object is reachable
237 downtime_depth | number of downtimes this object is in
238 acknowledgement | whether the object is acknowledged or not
239 execution_time | check execution time
240 latency | check latency
241 state | current state of the checked object
242 state_type | 0=SOFT, 1=HARD state
244 The following example illustrates how to configure the storage schemas for Graphite Carbon
248 # intervals like PNP4Nagios uses them per default
250 retentions = 1m:2d,5m:10d,30m:90d,360m:4y
252 #### <a id="graphite-carbon-cache-writer-schema-legacy"></a> Graphite Schema < 2.4
256 > This legacy mode will be removed in 2.8.
258 In order to restore the old legacy schema, you'll need to adopt the `GraphiteWriter`
261 object GraphiteWriter "graphite" {
263 enable_legacy_mode = true
265 host_name_template = "icinga.$host.name$"
266 service_name_template = "icinga.$host.name$.$service.name$"
269 The old legacy naming schema is
271 icinga.<hostname>.<metricname>
272 icinga.<hostname>.<servicename>.<metricname>
274 You can customize the metric prefix name by using the `host_name_template` and
275 `service_name_template` configuration attributes.
277 The example below uses [runtime macros](3-monitoring-basics.md#runtime-macros) and a
278 [global constant](17-language-reference.md#constants) named `GraphiteEnv`. The constant name
279 is freely definable and should be put in the [constants.conf](4-configuring-icinga-2.md#constants-conf) file.
281 const GraphiteEnv = "icinga.env1"
283 object GraphiteWriter "graphite" {
284 host_name_template = GraphiteEnv + ".$host.name$"
285 service_name_template = GraphiteEnv + ".$host.name$.$service.name$"
288 To make sure Icinga 2 writes a valid label into Graphite some characters are replaced
289 with `_` in the target name:
293 The resulting name in Graphite might look like:
295 www-01 / http-cert / response time
296 icinga.www_01.http_cert.response_time
298 In addition to the performance data retrieved from the check plugin, Icinga 2 sends
299 internal check statistic data to Graphite:
302 -------------------|------------------------------------------
303 current_attempt | current check attempt
304 max_check_attempts | maximum check attempts until the hard state is reached
305 reachable | checked object is reachable
306 downtime_depth | number of downtimes this object is in
307 acknowledgement | whether the object is acknowledged or not
308 execution_time | check execution time
309 latency | check latency
310 state | current state of the checked object
311 state_type | 0=SOFT, 1=HARD state
313 The following example illustrates how to configure the storage-schemas for Graphite Carbon
314 Cache. Please make sure that the order is correct because the first match wins.
317 pattern = ^icinga\..*\.(max_check_attempts|reachable|current_attempt|execution_time|latency|state|state_type)
321 # intervals like PNP4Nagios uses them per default
323 retentions = 1m:2d,5m:10d,30m:90d,360m:4y
325 ### <a id="influxdb-writer"></a> InfluxDB Writer
327 Once there are new metrics available, Icinga 2 will directly write them to the
328 defined InfluxDB HTTP API.
330 You can enable the feature using
332 # icinga2 feature enable influxdb
334 By default the [InfluxdbWriter](9-object-types.md#objecttype-influxdbwriter) feature
335 expects the InfluxDB daemon to listen at `127.0.0.1` on port `8086`.
337 More configuration details can be found [here](9-object-types.md#objecttype-influxdbwriter).
339 ### <a id="gelfwriter"></a> GELF Writer
341 The `Graylog Extended Log Format` (short: [GELF](http://www.graylog2.org/resources/gelf))
342 can be used to send application logs directly to a TCP socket.
344 While it has been specified by the [graylog2](http://www.graylog2.org/) project as their
345 [input resource standard](http://www.graylog2.org/resources/gelf), other tools such as
346 [Logstash](http://www.logstash.net) also support `GELF` as
347 [input type](http://logstash.net/docs/latest/inputs/gelf).
349 You can enable the feature using
351 # icinga2 feature enable gelf
353 By default the `GelfWriter` object expects the GELF receiver to listen at `127.0.0.1` on TCP port `12201`.
354 The default `source` attribute is set to `icinga2`. You can customize that for your needs if required.
356 Currently these events are processed:
361 ### <a id="logstash-writer"></a> Logstash Writer
363 [Logstash](https://www.elastic.co/products/logstash) receives
364 and processes event messages sent by Icinga 2 and the [LogstashWriter](9-object-types.md#objecttype-logstashwriter)
365 feature. As part of the Elastic Stack it allows you to
366 process and modify the messages and forward them to [Elasticsearch](https://www.elastic.co/products/elasticsearch)
369 Before proceeding with this integration guide please ensure
370 that you have Logstash, Elasticsearch and Kibana up and running
371 as part of the Elastic Stack.
375 > The LogstashWriter feature has been tested with Elastic Stack 5.x and therefore Logstash 5.x.
376 > Older versions are not supported.
378 Logstash supports `TCP` and `UDP` as input socket type. You must
379 further enable JSON support for input data processing. Logstash 5.x
380 comes without any pre-installed plugins and requires you to install
383 Example on CentOS 7 and UDP as socket type:
386 /usr/share/logstash/bin/logstash-plugin install logstash-input-udp
387 /usr/share/logstash/bin/logstash-plugin install logstash-codec-json
390 Add the Icinga 2 input and set the output to your running Elasticsearch instance.
391 You do not need to reload Logstash since version 5.x supports configuration changes
394 This example uses port `5555`. You are allowed to use any available port (note it for later).
397 # vim /etc/logstash/conf.d/icinga2.conf
407 hosts => [ "localhost:9200" ]
412 Modify the feature configuration and set the
413 socket type, host and port attributes. The port must be the same
414 as configured in your Logstash input, e.g. `5555`.
417 # vim /etc/icinga2/features-available/logstash.conf
419 object LogstashWriter "logstash" {
420 host = "192.168.33.7"
426 Enable the feature and restart Icinga 2.
429 # icinga2 feature enable logstash
430 # systemctl restart icinga2
433 Open [Kibana](https://www.elastic.co/products/kibana) or your
434 favorite Elasticsearch frontend and visualize the messages received
437 ### <a id="opentsdb-writer"></a> OpenTSDB Writer
439 While there are some OpenTSDB collector scripts and daemons like tcollector available for
440 Icinga 1.x it's more reasonable to directly process the check and plugin performance
441 in memory in Icinga 2. Once there are new metrics available, Icinga 2 will directly
442 write them to the defined TSDB TCP socket.
444 You can enable the feature using
446 # icinga2 feature enable opentsdb
448 By default the `OpenTsdbWriter` object expects the TSD to listen at
449 `127.0.0.1` on port `4242`.
451 The current naming schema is
453 icinga.host.<metricname>
454 icinga.service.<servicename>.<metricname>
456 for host and service checks. The tag host is always applied.
458 To make sure Icinga 2 writes a valid metric into OpenTSDB some characters are replaced
459 with `_` in the target name:
463 The resulting name in OpenTSDB might look like:
465 www-01 / http-cert / response time
466 icinga.http_cert.response_time
468 In addition to the performance data retrieved from the check plugin, Icinga 2 sends
469 internal check statistic data to OpenTSDB:
472 -------------------|------------------------------------------
473 current_attempt | current check attempt
474 max_check_attempts | maximum check attempts until the hard state is reached
475 reachable | checked object is reachable
476 downtime_depth | number of downtimes this object is in
477 acknowledgement | whether the object is acknowledged or not
478 execution_time | check execution time
479 latency | check latency
480 state | current state of the checked object
481 state_type | 0=SOFT, 1=HARD state
483 While reachable, state and state_type are metrics for the host or service the
484 other metrics follow the current naming schema
486 icinga.check.<metricname>
488 with the following tags
491 --------|------------------------------------------
492 type | the check type, one of [host, service]
493 host | hostname, the check ran on
494 service | the service name (if type=service)
498 > You might want to set the tsd.core.auto_create_metrics setting to `true`
499 > in your opentsdb.conf configuration file.
502 ## <a id="setting-up-livestatus"></a> Livestatus
504 The [MK Livestatus](http://mathias-kettner.de/checkmk_livestatus.html) project
505 implements a query protocol that lets users query their Icinga instance for
506 status information. It can also be used to send commands.
510 > Only install the Livestatus feature if your web interface or addon requires
511 > you to do so (for example, [Icinga Web 2](2-getting-started.md#setting-up-icingaweb2)).
512 > Icinga Classic UI 1.x and Icinga Web 1.x do not use Livestatus as backend.
514 The Livestatus component that is distributed as part of Icinga 2 is a
515 re-implementation of the Livestatus protocol which is compatible with MK
518 Details on the available tables and attributes with Icinga 2 can be found
519 in the [Livestatus Schema](23-appendix.md#schema-livestatus) section.
521 You can enable Livestatus using icinga2 feature enable:
523 # icinga2 feature enable livestatus
525 After that you will have to restart Icinga 2:
527 Debian/Ubuntu, RHEL/CentOS 6 and SUSE:
529 # service icinga2 restart
531 RHEL/CentOS 7 and Fedora:
533 # systemctl restart icinga2
535 By default the Livestatus socket is available in `/var/run/icinga2/cmd/livestatus`.
537 In order for queries and commands to work you will need to add your query user
538 (e.g. your web server) to the `icingacmd` group:
540 # usermod -a -G icingacmd www-data
542 The Debian packages use `nagios` as the user and group name. Make sure to change `icingacmd` to
543 `nagios` if you're using Debian.
545 Change `www-data` to the user you're using to run queries.
547 In order to use the historical tables provided by the livestatus feature (for example, the
548 `log` table) you need to have the `CompatLogger` feature enabled. By default these logs
549 are expected to be in `/var/log/icinga2/compat`. A different path can be set using the
550 `compat_log_path` configuration attribute.
552 # icinga2 feature enable compatlog
555 ### <a id="livestatus-sockets"></a> Livestatus Sockets
557 Other to the Icinga 1.x Addon, Icinga 2 supports two socket types
559 * Unix socket (default)
562 Details on the configuration can be found in the [LivestatusListener](9-object-types.md#objecttype-livestatuslistener)
563 object configuration.
565 ### <a id="livestatus-get-queries"></a> Livestatus GET Queries
569 > All Livestatus queries require an additional empty line as query end identifier.
570 > The `nc` tool (`netcat`) provides the `-U` parameter to communicate using
573 There also is a Perl module available in CPAN for accessing the Livestatus socket
574 programmatically: [Monitoring::Livestatus](http://search.cpan.org/~nierlein/Monitoring-Livestatus-0.74/)
577 Example using the unix socket:
579 # echo -e "GET services\n" | /usr/bin/nc -U /var/run/icinga2/cmd/livestatus
581 Example using the tcp socket listening on port `6558`:
583 # echo -e 'GET services\n' | netcat 127.0.0.1 6558
585 # cat servicegroups <<EOF
590 (cat servicegroups; sleep 1) | netcat 127.0.0.1 6558
593 ### <a id="livestatus-command-queries"></a> Livestatus COMMAND Queries
595 A list of available external commands and their parameters can be found [here](23-appendix.md#external-commands-list-detail)
597 $ echo -e 'COMMAND <externalcommandstring>' | netcat 127.0.0.1 6558
600 ### <a id="livestatus-filters"></a> Livestatus Filters
604 Operator | Negate | Description
605 ----------|------------------------
608 =~ | !=~ | Equality ignoring case
609 ~~ | !~~ | Regex ignoring case
612 <= | | Less than or equal
613 >= | | Greater than or equal
616 ### <a id="livestatus-stats"></a> Livestatus Stats
618 Schema: "Stats: aggregatefunction aggregateattribute"
620 Aggregate Function | Description
621 -------------------|--------------
626 std | standard deviation
627 suminv | sum (1 / value)
628 avginv | suminv / count
629 count | ordinary default for any stats query if not aggregate function defined
634 Filter: has_been_checked = 1
635 Filter: check_type = 0
636 Stats: sum execution_time
638 Stats: sum percent_state_change
639 Stats: min execution_time
641 Stats: min percent_state_change
642 Stats: max execution_time
644 Stats: max percent_state_change
646 ResponseHeader: fixed16
648 ### <a id="livestatus-output"></a> Livestatus Output
652 CSV output uses two levels of array separators: The members array separator
653 is a comma (1st level) while extra info and host|service relation separator
654 is a pipe (2nd level).
656 Separators can be set using ASCII codes like:
658 Separators: 10 59 44 124
664 ### <a id="livestatus-error-codes"></a> Livestatus Error Codes
667 ----------|--------------
669 404 | Table does not exist
670 452 | Exception on query
672 ### <a id="livestatus-tables"></a> Livestatus Tables
674 Table | Join |Description
675 --------------|-----------|----------------------------
676 hosts | | host config and status attributes, services counter
677 hostgroups | | hostgroup config, status attributes and host/service counters
678 services | hosts | service config and status attributes
679 servicegroups | | servicegroup config, status attributes and service counters
680 contacts | | contact config and status attributes
681 contactgroups | | contact config, members
682 commands | | command name and line
683 status | | programstatus, config and stats
684 comments | services | status attributes
685 downtimes | services | status attributes
686 timeperiods | | name and is inside flag
687 endpoints | | config and status attributes
688 log | services, hosts, contacts, commands | parses [compatlog](9-object-types.md#objecttype-compatlogger) and shows log attributes
689 statehist | hosts, services | parses [compatlog](9-object-types.md#objecttype-compatlogger) and aggregates state change attributes
690 hostsbygroup | hostgroups | host attributes grouped by hostgroup and its attributes
691 servicesbygroup | servicegroups | service attributes grouped by servicegroup and its attributes
692 servicesbyhostgroup | hostgroups | service attributes grouped by hostgroup and its attributes
694 The `commands` table is populated with `CheckCommand`, `EventCommand` and `NotificationCommand` objects.
696 A detailed list on the available table attributes can be found in the [Livestatus Schema documentation](23-appendix.md#schema-livestatus).
699 ## <a id="status-data"></a> Status Data Files
701 Icinga 1.x writes object configuration data and status data in a cyclic
702 interval to its `objects.cache` and `status.dat` files. Icinga 2 provides
703 the `StatusDataWriter` object which dumps all configuration objects and
704 status updates in a regular interval.
706 # icinga2 feature enable statusdata
708 Icinga 1.x Classic UI requires this data set as part of its backend.
712 > If you are not using any web interface or addon which uses these files,
713 > you can safely disable this feature.
716 ## <a id="compat-logging"></a> Compat Log Files
718 The Icinga 1.x log format is considered being the `Compat Log`
719 in Icinga 2 provided with the `CompatLogger` object.
721 These logs are not only used for informational representation in
722 external web interfaces parsing the logs, but also to generate
723 SLA reports and trends in Icinga 1.x Classic UI. Furthermore the
724 [Livestatus](14-features.md#setting-up-livestatus) feature uses these logs for answering queries to
727 The `CompatLogger` object can be enabled with
729 # icinga2 feature enable compatlog
731 By default, the Icinga 1.x log file called `icinga.log` is located
732 in `/var/log/icinga2/compat`. Rotated log files are moved into
733 `var/log/icinga2/compat/archives`.
735 The format cannot be changed without breaking compatibility to
736 existing log parsers.
738 # tail -f /var/log/icinga2/compat/icinga.log
740 [1382115688] LOG ROTATION: HOURLY
741 [1382115688] LOG VERSION: 2.0
742 [1382115688] HOST STATE: CURRENT;localhost;UP;HARD;1;
743 [1382115688] SERVICE STATE: CURRENT;localhost;disk;WARNING;HARD;1;
744 [1382115688] SERVICE STATE: CURRENT;localhost;http;OK;HARD;1;
745 [1382115688] SERVICE STATE: CURRENT;localhost;load;OK;HARD;1;
746 [1382115688] SERVICE STATE: CURRENT;localhost;ping4;OK;HARD;1;
747 [1382115688] SERVICE STATE: CURRENT;localhost;ping6;OK;HARD;1;
748 [1382115688] SERVICE STATE: CURRENT;localhost;processes;WARNING;HARD;1;
749 [1382115688] SERVICE STATE: CURRENT;localhost;ssh;OK;HARD;1;
750 [1382115688] SERVICE STATE: CURRENT;localhost;users;OK;HARD;1;
751 [1382115706] EXTERNAL COMMAND: SCHEDULE_FORCED_SVC_CHECK;localhost;disk;1382115705
752 [1382115706] EXTERNAL COMMAND: SCHEDULE_FORCED_SVC_CHECK;localhost;http;1382115705
753 [1382115706] EXTERNAL COMMAND: SCHEDULE_FORCED_SVC_CHECK;localhost;load;1382115705
754 [1382115706] EXTERNAL COMMAND: SCHEDULE_FORCED_SVC_CHECK;localhost;ping4;1382115705
755 [1382115706] EXTERNAL COMMAND: SCHEDULE_FORCED_SVC_CHECK;localhost;ping6;1382115705
756 [1382115706] EXTERNAL COMMAND: SCHEDULE_FORCED_SVC_CHECK;localhost;processes;1382115705
757 [1382115706] EXTERNAL COMMAND: SCHEDULE_FORCED_SVC_CHECK;localhost;ssh;1382115705
758 [1382115706] EXTERNAL COMMAND: SCHEDULE_FORCED_SVC_CHECK;localhost;users;1382115705
759 [1382115731] EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;localhost;ping6;2;critical test|
760 [1382115731] SERVICE ALERT: localhost;ping6;CRITICAL;SOFT;2;critical test
763 ## <a id="check-result-files"></a> Check Result Files
765 Icinga 1.x writes its check result files to a temporary spool directory
766 where they are processed in a regular interval.
767 While this is extremely inefficient in performance regards it has been
768 rendered useful for passing passive check results directly into Icinga 1.x
769 skipping the external command pipe.
771 Several clustered/distributed environments and check-aggregation addons
772 use that method. In order to support step-by-step migration of these
773 environments, Icinga 2 supports the `CheckResultReader` object.
775 There is no feature configuration available, but it must be defined
776 on-demand in your Icinga 2 objects configuration.
778 object CheckResultReader "reader" {
779 spool_dir = "/data/check-results"