tyler.durden
/
icinga2
mirror of https://github.com/Icinga/icinga2.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
icinga2/doc/1-about.md

11 KiB
Raw Blame History

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:

For general support questions, please refer to the community support channels.

Demo VM

Icinga 2 is available as Vagrant Demo VM.

What's new

What's New in Version 2.1.1

Issues

  • Bug #6147: Link libcJSON against libm
  • Bug #6696: make test fails on openbsd
  • Bug #6841: Too many queued messages
  • Bug #6862: SSL_read errors during restart
  • Bug #6981: SSL errors with interleaved SSL_read/write
  • Bug #7029: icinga2.spec: files-attr-not-set for python-icinga2 package
  • Bug #7032: "Error parsing performance data" in spite of "enable_perfdata = false"
  • Bug #7036: Remove validator for the Script type
  • Bug #7037: icinga2-list-objects doesn't work with Python 3
  • Bug #7038: Fix rpmlint errors
  • Bug #7042: icinga2-list-objects complains about Umlauts and stops output
  • Bug #7044: icinga2 init-script terminates with exit code 0 if $DAEMON is not in place or not executable
  • Bug #7047: service icinga2 status - prints cat error if the service is stopped
  • Bug #7058: Exit code is not initialized for some failed checks
  • Bug #7065: pipe2 returns ENOSYS on GNU Hurd and Debian kfreebsd
  • Bug #7072: GraphiteWriter should ignore empty perfdata value
  • Bug #7080: Missing differentiation between service and systemctl
  • Bug #7096: new SSL Errors with too many queued messages
  • Bug #7115: Build fails on Haiku
  • Bug #7123: Manubulon-Plugin conf Filename wrong
  • Bug #7139: GNUInstallDirs.cmake outdated
  • Bug #7167: Segfault using cluster in TlsStream::IsEof
  • Bug #7168: fping4 doesn't work correctly with the shipped command-plugins.conf
  • Bug #7186: Livestatus hangs from time to time
  • Bug #7195: fix memory leak ido_pgsql
  • Bug #7210: clarify on db ido upgrades
  • Feature #6719: Change log message for checking/sending notifications
  • Feature #7028: Document how to use @ to escape keywords
  • Feature #7033: Add include guards for mkclass files
  • Feature #7034: Ensure that namespaces for INITIALIZE_ONCE and REGISTER_TYPE are truly unique
  • Feature #7035: Implement support for unity builds
  • Feature #7039: Figure out a better way to set the version for snapshot builds
  • Feature #7040: Unity builds: Detect whether COUNTER is available
  • Feature #7041: Enable unity build for RPM/Debian packages
  • Feature #7070: Explain event commands and their integration by a real life example (httpd restart via ssh)
  • Feature #7158: Extend documentation for icinga-web on Debian systems

Archive

Please check the ChangeLog file.

Icinga 2 in a Nutshell

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.

  • 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 paralell allowing fast verification checks. That way you are not blind (anymore) during a configuration reload and benefit from a real scalable architecture.

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.

In Icinga2, the 'Livestatus' protocol is available for use as either a UNIX, or TCP socket.

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 and assign rules for creating configuration object relationships based on patterns. Supported with duration literals for interval attributes, expression operators, function calls for pattern and regex matching and (global) constants. Sample 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.

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 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.