mirror of https://github.com/Icinga/icinga2.git
203 lines
10 KiB
Markdown
203 lines
10 KiB
Markdown
# <a id="about-icinga2"></a> About Icinga 2
|
|
|
|
## <a id="what-is-icinga2"></a> What is Icinga 2?
|
|
|
|
Icinga 2 is an open source monitoring system which checks the availability of your
|
|
network resources, notifies users of outages, and generates performance data for reporting.
|
|
|
|
Scalable and extensible, Icinga 2 can monitor large, complex environments across
|
|
multiple locations.
|
|
|
|
## <a id="licensing"></a> Licensing
|
|
|
|
Icinga 2 and the Icinga 2 documentation are licensed under the terms of the GNU
|
|
General Public License Version 2, you will find a copy of this license in the
|
|
LICENSE file included in the source package.
|
|
|
|
## <a id="support"></a> Support
|
|
|
|
Support for Icinga 2 is available in a number of ways. Please have a look at
|
|
the support overview page at https://support.icinga.org.
|
|
|
|
## <a id="contribute"></a> Contribute
|
|
|
|
There are many ways to contribute to Icinga - whether it be sending patches, testing,
|
|
reporting bugs, or reviewing and updating the documentation. Every contribution
|
|
is appreciated!
|
|
|
|
Please get in touch with the Icinga team at https://www.icinga.org/community/.
|
|
|
|
### <a id="development"></a> Icinga 2 Development
|
|
|
|
You can follow Icinga 2's development closely by checking
|
|
out these resources:
|
|
|
|
* [Development Bug Tracker](https://dev.icinga.org/projects/i2): [How to report a bug?](https://www.icinga.org/icinga/faq/)
|
|
* Git Repositories: [main mirror on icinga.org](https://git.icinga.org/?p=icinga2.git;a=summary) [release mirror at github.com](https://github.com/Icinga/icinga2)
|
|
* [Git Checkins Mailinglist](https://lists.icinga.org/mailman/listinfo/icinga-checkins)
|
|
* [Development](https://lists.icinga.org/mailman/listinfo/icinga-devel) and [Users](https://lists.icinga.org/mailman/listinfo/icinga-users) Mailinglists
|
|
* [#icinga-devel on irc.freenode.net](http://webchat.freenode.net/?channels=icinga-devel) including a Git Commit Bot
|
|
|
|
For general support questions, please refer to the [community support channels](https://support.icinga.org).
|
|
|
|
### <a id="how-to-report-bug-feature-requests"></a> How to Report a Bug or Feature Request
|
|
|
|
More details in the [Icinga FAQ](https://www.icinga.org/icinga/faq/).
|
|
|
|
* [Register](https://exchange.icinga.org/authentication/register) an Icinga account.
|
|
* Create a new issue at the [Icinga 2 Development Tracker](https://dev.icinga.org/projects/i2).
|
|
* When reporting a bug, please include the details described in the [Troubleshooting](#troubleshooting-information-required) chapter (version, configs, logs, etc).
|
|
|
|
## <a id="demo-vm"></a> Demo VM
|
|
|
|
Icinga 2 is available as [Vagrant Demo VM](#vagrant).
|
|
|
|
## <a id="whats-new"></a> What's new
|
|
|
|
### What's New in Version 2.2.0
|
|
|
|
#### Changes
|
|
|
|
* DB IDO schema update to version `1.12.0`
|
|
* schema files in `lib/db_ido_{mysql,pgsql}/schema`
|
|
* New CLI commands #7245
|
|
* `icinga2-{enable,disable}-feature` tool = cli command `icinga2 feature {enable,disable}` #7250
|
|
* `icinga2-list-objects` tool = cli command `icinga2 object list` #7251
|
|
* `icinga2-build-{ca,key}` can be used with cli command `icinga2 pki` #7247
|
|
* `icinga2 repository` manages `/etc/icinga2/repository.d` which must be included in `icinga2.conf` #7255
|
|
|
|
* `python-icinga2` package dropped in favor of cli commands #7245
|
|
* GraphiteWriter: Add warn/crit/min/max perfdata and downtime_depth stats values #7366 #6946
|
|
|
|
#### Issues
|
|
|
|
|
|
|
|
### Archive
|
|
|
|
Please check the `ChangeLog` file.
|
|
|
|
## <a id="icinga2-in-a-nutshell"></a> Icinga 2 in a Nutshell
|
|
|
|
* Use [Packages](#getting-started)
|
|
|
|
Look for available packages on http://packages.icinga.org or ask your distribution's maintainer.
|
|
Compiling from source is not recommended.
|
|
|
|
* Real Distributed Architecture
|
|
|
|
[Cluster](#distributed-monitoring-high-availability) model for distributed setups, load balancing
|
|
and High-Availability installations (or a combination of them). On-demand configuration
|
|
synchronisation between zones is available, but not mandatory (for example when config management
|
|
tools such as Puppet are used). Secured by SSL x509 certificates, supporting IPv4 and IPv6.
|
|
High Availability for DB IDO: Only active on the current zone master, failover happens automatically.
|
|
|
|
* High Performance
|
|
|
|
Multithreaded and scalable for small embedded systems as well as large scale environments.
|
|
Running checks every second is no longer a problem and enables real-time monitoring capabilities.
|
|
Checks, notifications and event handlers [do not block Icinga 2](#differences-1x-2-async-event-execution)
|
|
in its operation. Same goes for performance data writers and the external command pipe, or any
|
|
file writers on disk (`statusdata`).
|
|
Unlike Icinga 1.x the [daemon reload](#differences-1x-2-real-reload) happens asynchronously.
|
|
A child daemon validates the new configuration, the parent process is still doing checks, replicating cluster events, triggering alert notifications, etc. If the configuration validation is ok, all remaining events are synchronized and the child process continues as normal.
|
|
The DB IDO configuration dump and status/historical event updates also runs asynchronously in a queue not blocking the core anymore. The configuration validation itself runs in paralell allowing fast verification checks.
|
|
That way you are not blind (anymore) during a configuration reload and benefit from a real scalable architecture.
|
|
|
|
|
|
* Modular & flexible [features](#features)
|
|
|
|
Enable only the features you require. Want to use Icinga Web 2 with DB IDO but no status data?
|
|
No problem! Just enable ido-mysql and disable statusdata. Another example: Graphite should be enabled
|
|
on a dedicated cluster node. Enable it over there and point it to the carbon cache socket.
|
|
|
|
* Native support for the [Livestatus protocol](#setting-up-livestatus)
|
|
|
|
In Icinga2, the 'Livestatus' protocol is available for use as either a UNIX, or TCP socket.
|
|
|
|
* Native support for [Graphite](#graphite-carbon-cache-writer)
|
|
|
|
Icinga 2 still supports writing performance data files for graphing addons, but also adds the
|
|
capability of writing performance data directly into a Graphite TCP socket simplifying realtime
|
|
monitoring graphs.
|
|
|
|
* Dynamic configuration language
|
|
|
|
Simple [apply](#using-apply) and [assign](#group-assign) rules for creating configuration object
|
|
relationships based on patterns. Supported with [duration literals](#duration-literals) for interval
|
|
attributes, [expression operators](#expression-operators), [function calls](#function-calls) for
|
|
pattern and regex matching and (global) [constants](#constants).
|
|
Sample configuration for common plugins is shipped with Icinga 2 as part of the [Icinga Template Library](#itl).
|
|
|
|
* Revamped Commands
|
|
|
|
One command to rule them all - supporting optional and conditional [command arguments](#command-arguments).
|
|
[Environment variables](#command-environment-variables) exported on-demand populated with
|
|
runtime evaluated macros.
|
|
Three types of commands used for different actions: checks, notifications and events.
|
|
Check timeout for commands instead of a global option. Commands also have custom attributes allowing
|
|
you to specify default values.
|
|
There is no plugin output or performance data length restriction anymore compared to Icinga 1.x.
|
|
|
|
* Custom Runtime Macros
|
|
|
|
Access [custom attributes](#custom-attributes) with their short name, for example $mysql_user$,
|
|
or any object attribute, for example $host.notes$. Additional macros with runtime and statistic
|
|
information are available as well. Use these [runtime macros](#runtime-custom-attributes) in
|
|
the command line, environment variables and custom attribute assignments.
|
|
|
|
* Notifications simplified
|
|
|
|
Multiple [notifications](#notifications) for one host or service with existing users
|
|
and notification commands. No more duplicated contacts for different notification types.
|
|
Telling notification filters by state and type, even more fine-grained than Icinga 1.x.
|
|
[Escalation notifications](#notification-escalations) and [delayed notifications](#first-notification-delay)
|
|
are just notifications with an additional begin and/or end time attribute.
|
|
|
|
* Dependencies between Hosts and Services
|
|
|
|
Classic [dependencies](#dependencies) between host and parent hosts, and services and parent services work the
|
|
same way as "mixed" dependencies from a service to a parent host and vice versa. Host checks
|
|
depending on an upstream link port (as service) are not a problem anymore.
|
|
No more additional parents settings - host dependencies already define the host parent relationship
|
|
required for network reachability calculations.
|
|
|
|
* [Recurring Downtimes](#recurring-downtimes)
|
|
|
|
Forget using cronjobs to set up recurring downtime - you can configure them as Icinga 2 configuration
|
|
objects and specify their active time window.
|
|
|
|
* Embedded Health Checks
|
|
|
|
No more external statistic tool but an [instance](#itl-icinga) and [cluster](#itl-cluster) health
|
|
check providing direct statistics as performance data for your graphing addon, for example Graphite.
|
|
|
|
* Compatibility with Icinga 1.x
|
|
|
|
All known interfaces are optionally available: [status files](#status-data), [logs](#compat-logging),
|
|
[DB IDO](#configuring-ido) MySQL/PostgreSQL, [performance data](#performance-data),
|
|
[external command pipe](#external-commands) and for migration reasons a
|
|
[checkresult file reader](#check-result-files) too.
|
|
All [Monitoring Plugins](#setting-up-check-plugins) can be integrated into Icinga 2 with
|
|
newly created check command configuration if not already provided.
|
|
[Configuration migration](#configuration-migration) is possible through an external migration tool.
|
|
|
|
Detailed [migration hints](#manual-config-migration-hints) explain migration the Icinga 1.x
|
|
configuration objects into the native Icinga 2 configuration schema.
|
|
Additional information on the differences is documented in the [migration](#differences-1x-2) chapter.
|
|
|
|
* Configuration Syntax Highlighting
|
|
|
|
Icinga 2 ships [syntax highlighting](#configuration-syntax-highlighting) for `vim` and `nano` to help
|
|
edit your configuration.
|
|
|
|
* Puppet modules, Chef Cookbooks, Ansible Playbooks, Salt Formulas, etc
|
|
|
|
This is a constant work-in-progress. For details checkout https://dev.icinga.org/projects/icinga-tools
|
|
If you want to contribute to these projects, do not hesitate to contact us at https://support.icinga.org
|
|
|
|
* [Vagrant Demo VM](#vagrant)
|
|
|
|
Used for demo cases and development tests. Get Icinga 2 running within minutes and spread the #monitoringlove
|
|
to your friends and colleagues.
|