21 KiB
About Icinga 2
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.
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.
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.
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/.
Icinga 2 Development
You can follow Icinga 2's development closely by checking out these resources:
- Development Bug Tracker: How to report a bug?
- Git Repositories: main mirror on icinga.org release mirror at github.com
- Git Checkins Mailinglist
- Development and Users Mailinglists
- #icinga-devel on irc.freenode.net including a Git Commit Bot
For general support questions, please refer to the community support channels.
How to Report a Bug or Feature Request
More details in the Icinga FAQ.
- Register an Icinga account.
- Create a new issue at the Icinga 2 Development Tracker.
- When reporting a bug, please include the details described in the Troubleshooting chapter (version, configs, logs, etc).
Demo VM
Icinga 2 is available as Vagrant Demo VM.
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
(source) - Table
programstatus
: New columnprogram_version
- Table
customvariables
andcustomvariablestatus
: New columnis_json
(required for custom attribute array/dictionary support)
- schema files in
- New features
- GelfWriter: Logging check results, state changes, notifications to GELF (graylog2, logstash) #7619
- Agent/Client/Node framework #7249
- Windows plugins for the client/agent parts #7242 #7243
- New CLI commands #7245
icinga2 feature {enable,disable}
replacesicinga2-{enable,disable}-feature
script #7250icinga2 object list
replacesicinga2-list-objects
script #7251icinga2 pki
replacesicinga2-build-{ca,key}
scripts #7247icinga2 repository
manages/etc/icinga2/repository.d
which must be included inicinga2.conf
#7255icinga2 node
cli command provides node (master, satellite, agent) setup (wizard) and management functionality #7248icinga2 daemon
for existing daemon arguments (-c
,-C
). Removed-u
and-g
parameters in favor of init.conf.- bash auto-completion & terminal colors #7396
- Configuration
- Former
localhost
example host is now defined in hosts.conf #7594 - All example services moved into advanced apply rules in services.conf
- Updated downtimes configuration example in downtimes.conf #7472
- Updated notification apply example in notifications.conf #7594
- Support for object attribute 'zone' #7400
- Support setting object variables in apply rules #7479
- Support arrays and dictionaries in custom attributes #6544 #7560
- Add apply for rules for advanced dynamic object generation #7561
- New attribute
accept_commands
for ApiListener #7559 - New init.conf file included first containing new constants
RunAsUser
andRunAsGroup
.
- Former
- Cluster
- Add CSR Auto-Signing support using generated ticket #7244
- Allow to execute remote commands on endpoint clients #7559
- Perfdata
- PerfdataWriter: Don't change perfdata, pass through from plugins #7268
- GraphiteWriter: Add warn/crit/min/max perfdata and downtime_depth stats values #7366 #6946
- Packages
python-icinga2
package dropped in favor of integrated cli commands #7245- Windows Installer for the agent parts #7243
Note
Please remove
conf.d/hosts/localhost*
after verifying your updated configuration!
Issues
-
Feature #6544: Support for array in custom variable.
-
Feature #6946: Add downtime depth as statistic metric for GraphiteWriter
-
Feature #7187: Document how to use multiple assign/ignore statements with logical "and" & "or"
-
Feature #7199: Cli commands: add filter capability to 'object list'
-
Feature #7241: Windows Wizard
-
Feature #7242: Windows plugins
-
Feature #7243: Windows installer
-
Feature #7244: CSR auto-signing
-
Feature #7245: Cli commands
-
Feature #7246: Cli command framework
-
Feature #7247: Cli command: pki
-
Feature #7248: Cli command: Node
-
Feature #7249: Node Repository
-
Feature #7250: Cli command: Feature
-
Feature #7251: Cli command: Object
-
Feature #7252: Cli command: SCM
-
Feature #7253: Cli Commands: Node Repository Blacklist & Whitelist
-
Feature #7254: Documentation: Agent/Satellite Setup
-
Feature #7255: Cli command: Repository
-
Feature #7262: macro processor needs an array printer
-
Feature #7319: Documentation: Add support for locally-scoped variables for host/service in applied Dependency
-
Feature #7334: GraphiteWriter: Add support for customized metric prefix names
-
Feature #7356: Documentation: Cli Commands
-
Feature #7366: GraphiteWriter: Add warn/crit/min/max perfdata values if existing
-
Feature #7370: CLI command: variable
-
Feature #7391: Add program_version column to programstatus table
-
Feature #7396: Implement generic color support for terminals
-
Feature #7400: Remove zone keyword and allow to use object attribute 'zone'
-
Feature #7415: CLI: List disabled features in feature list too
-
Feature #7421: Add -h next to --help
-
Feature #7423: Cli command: Node Setup
-
Feature #7452: Replace cJSON with a better JSON parser
-
Feature #7465: Cli command: Node Setup Wizard (for Satellites and Agents)
-
Feature #7467: Remove virtual agent name feature for localhost
-
Feature #7472: Update downtimes.conf example config
-
Feature #7478: Documentation: Mention 'icinga2 object list' in config validation
-
Feature #7479: Set host/service variable in apply rules
-
Feature #7480: Documentation: Add host/services variables in apply rules
-
Feature #7504: Documentation: Revamp getting started with 1 host and multiple (service) applies
-
Feature #7514: Documentation: Move troubleshooting after the getting started chapter
-
Feature #7524: Documentation: Explain how to manage agent config in central repository
-
Feature #7543: Documentation for arrays & dictionaries in custom attributes and their usage in apply rules for
-
Feature #7559: Execute remote commands on the agent w/o local objects by passing custom attributes
-
Feature #7560: Support dictionaries in custom attributes
-
Feature #7561: Generate objects using apply with foreach in arrays or dictionaries (key => value)
-
Feature #7566: Implement support for arbitrarily complex indexers
-
Feature #7594: Revamp sample configuration: add NodeName host, move services into apply rules schema
-
Feature #7596: Plugin Check Commands: disk is missing '-p', 'x' parameter
-
Feature #7619: Add GelfWriter for writing log events to graylog2/logstash
-
Feature #7620: Documentation: Update Icinga Web 2 installation
-
Feature #7622: Icinga 2 should use less RAM
-
Feature #7680: Conditionally enable MySQL and PostgresSQL, add support for FreeBSD and DragonFlyBSD
-
Bug #6547: delaying notifications with times.begin should postpone first notification into that window
-
Bug #7257: default value for "disable_notifications" in service dependencies is set to "false"
-
Bug #7268: Icinga2 changes perfdata order and removes maximum
-
Bug #7272: icinga2 returns exponential perfdata format with check_nt
-
Bug #7275: snmp-load checkcommand has wrong threshold syntax
-
Bug #7276: SLES (Suse Linux Enterprise Server) 11 SP3 package dependency failure
-
Bug #7302: ITL: check_procs and check_http are missing arguments
-
Bug #7324: config parser crashes on unknown attribute in assign
-
Bug #7327: Icinga2 docs: link supported operators from sections about apply rules
-
Bug #7331: Error messages for invalid imports missing
-
Bug #7338: Docs: Default command timeout is 60s not 5m
-
Bug #7339: Importing a CheckCommand in a NotificationCommand results in an exception without stacktrace.
-
Bug #7349: Documentation: Wrong check command for snmp-int(erface)
-
Bug #7351: snmp-load checkcommand has a wrong "-T" param value
-
Bug #7359: Setting snmp_v2 can cause snmp-manubulon-command derived checks to fail
-
Bug #7365: Typo for "HTTP Checks" match in groups.conf
-
Bug #7369: Fix reading perfdata in compat/checkresultreader
-
Bug #7372: custom attribute name 'type' causes empty vars dictionary
-
Bug #7373: Wrong usermod command for external command pipe setup
-
Bug #7378: Commands are auto-completed when they shouldn't be
-
Bug #7379: failed en/disable feature should return error
-
Bug #7380: Debian package root permissions interfere with icinga2 cli commands as icinga user
-
Bug #7392: Schema upgrade files are missing in /usr/share/icinga2-ido-{mysql,pgsql}
-
Bug #7417: CMake warnings on OS X
-
Bug #7428: Documentation: 1-about contribute links to non-existing report a bug howto
-
Bug #7433: Unity build fails on RHEL 5
-
Bug #7446: When replaying logs the secobj attribute is ignored
-
Bug #7473: Performance data via API is broken
-
Bug #7475: can't assign Service to Host in nested HostGroup
-
Bug #7477: Fix typos and other small corrections in documentation
-
Bug #7482: OnStateLoaded isn't called for objects which don't have any state
-
Bug #7483: Hosts/services should not have themselves as parents
-
Bug #7495: Utility::GetFQDN doesn't work on OS X
-
Bug #7503: Icinga2 fails to start due to configuration errors
-
Bug #7520: Use ScriptVariable::Get for RunAsUser/RunAsGroup
-
Bug #7536: Object list dump erraneously evaluates template definitions
-
Bug #7537: Nesting an object in a template causes the template to become non-abstract
-
Bug #7538: There is no __name available to nested objects
-
Bug #7573: link missing in documentation about livestatus
-
Bug #7577: Invalid checkresult object causes Icinga 2 to crash
-
Bug #7579: only notify users on recovery which have been notified before (not-ok state)
-
Bug #7585: Nested templates do not work (anymore)
-
Bug #7586: Exception when executing check
-
Bug #7597: Compilation Error with boost 1.56 under Windows
-
Bug #7599: Plugin execution on Windows does not work
-
Bug #7617: mkclass crashes when called without arguments
-
Bug #7623: Missing state filter 'OK' must not prevent recovery notifications being sent
-
Bug #7624: Installation on Windows fails
-
Bug #7625: IDO module crashes on Windows
-
Bug #7646: Get rid of static boost::mutex variables
-
Bug #7648: Unit tests fail to run
-
Bug #7650: Wrong set of dependency state when a host depends on a service
-
Bug #7681: CreateProcess fails on Windows 7
-
Bug #7688: DebugInfo is missing for nested dictionaries
Archive
Please check the ChangeLog
file.
Icinga 2 in a Nutshell
- Use Packages
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 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.
- Monitoring Remote Clients
Built on proven cluster stack, Icinga 2 clients can be installed acting as remote satellite or agent. Secured communication by SSL x509 certificates, install them with cli commands, and configure them either locally with discovery on the master, or use them for executing checks and event handlers remotely.
- 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
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 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 parallel allowing fast verification checks.
That way you are not blind (anymore) during a configuration reload and benefit from a real scalable architecture.
- Integrated CLI with Bash Auto-Completion
Enable only the features which are currently disabled, list objects generated from apply rules or generate SSL x509 certificates for remote clients or cluster setup. Start/stop the Icinga 2 daemon or validate your configuration, manage and install remote clients and service discovery helped with black- and whitelists.
- Modular & flexible 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.
Combine Icinga 2 Core with web user interfaces: Use Icinga Web 2, but also Web 1.x or Classic UI or your own preferred addon.
- Native support for the Livestatus protocol
In Icinga2, the 'Livestatus' protocol is available for use as either a UNIX, or TCP socket.
- Native support for Graphite
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.
- Native support for writing log events to GELF receivers (graylog2, Logstash)
Icinga 2 will write all check result, state change and notification event logs into a defined GELF input receiver. Natively provided by graylog2, and as additional input type provided by Logstash.
- Dynamic configuration language
Simple apply and assign rules for creating configuration object relationships based on patterns. More advanced features for dynamic object generation using apply for rules helped with arrays and dictionaries for custom attributes. Supported with duration literals for interval attributes, expression operators, function calls for pattern and regex matching and (global) constants. Check command configuration for common plugins is shipped with Icinga 2 as part of the Icinga Template Library.
- Revamped Commands
One command to rule them all - supporting optional and conditional command arguments. 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 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 in
the command line, environment variables and custom attribute assignments.
- Notifications simplified
Multiple 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 and delayed notifications are just notifications with an additional begin and/or end time attribute.
- Dependencies between Hosts and Services
Classic 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. Set parent host/services based on host/service custom attributes generated from your cloud inventory or CMDB and make your dependency rules simple and short.
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 and 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, logs, DB IDO MySQL/PostgreSQL, performance data, external command pipe and for migration reasons a checkresult file reader too. All Monitoring Plugins can be integrated into Icinga 2 with newly created check command configuration if not already provided. Configuration migration is possible through an external migration tool.
Detailed migration hints explain migration of the Icinga 1.x configuration objects into the native Icinga 2 configuration schema. Additional information on the differences is documented in the migration chapter.
- Configuration Syntax Highlighting
Icinga 2 ships 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
Used for demo cases and development tests. Get Icinga 2 running within minutes and spread the #monitoringlove to your friends and colleagues.