Last updated: July 08. 2016
1. The monitoring core
The monitoring core is at the heart of the Check_MK-System.
Its tasks are:
- the regular querying of checks and the collection of their results.
- providing current states to the GUI
- the recognition of changes to states and the notifications generated from these.
The diagram below shows the core and its connections to the primary elements of the Check_MK Enterprise Edition:
1.1. Nagios and Icinga
The Check_MK Raw Edition is a construction based on the core from the well-established Nagios
Open-Source Projekt. This offers numerous useful functions and has been proven over many years
by millions of users worldwide.
This inherent flexibility is one of the reasons for the success of Nagios.
Alternatively, the core from Icinga can also be utilised. This is particularly popular
in Germany, and is based on the same program code, but in recent years it has been developed independently.
Even though Nagios and Icinga perform exceptionally - being flexible, fast and well-proven -
there are still situations in which their limits are reached.
Where a large number of hosts and services are being monitored,
three problems in particular become evident:
- The high CPU consumption when executing checks
- The long restart time when changing a configuration
- The fact that the system is not available during such a restart
2. The Check_MK micro core
Since Check_MK is being used in ever-larger environments, and in order to overcome
the limitations of Nagios as described above, in 2013 we commenced a new development of
our own core specifically for the Check_MK Enterprise Edition.
The Check_MK Micro Core - or CMC - has not simply been created as a fork from Nagios,
rather it has a complete code basis of its own.
The CMC utilises a unique software architecture, and it has been perfectly-tailored for Check_MK.
Its primary advantages are:
|High efficiency when executing checks
||This applies for active checks as well as Check_MK-based checks. In
benchmarking, a desktop-PC (Core i7) achieved more than 600,000 checks
|Rapid activation of changes ||A configuration with
20,000 hosts and 600,000 services can be loaded in 0,5 seconds.|
|Configuration changes during live operations
||Currently-running checks and live status connections are not
interrupted. The procedure is undetectable to monitoring users.|
|Rapid availability queries ||Through the use of
special caches, availability analyses - even over long time periods - can
be calculated without a noticeable waiting time.|
|Additional features ||The CMC makes use of numerous
additional features, such as, e.g., recurring planned-downtimes and
acknowledgements with automatic expiry times.|
Other elements have also been optimised. For example, performance data is passed without detours
directly from the core to the RRD cache, notifications are created in a "KeepAlive"-mode,
and host checks are executed by a built-in ICMP helper.
All of these reduce costly process-creations and save CPU resources.
These characteristics bring numerous advantages - even in smaller installations:
- The low CPU consumption enables virtualisation to subsitute for hardware in many cases.
- The shock-free activation of changes allows frequent configuration changes.
- Demands such as cloud-monitoring can thus be satisfied, since servers can be added and removed in quick succession.
The graphic below shows the CPU consumption for a Check_MK server before and after the installation
of Nagios on the CMC. This graphic has been kindly provided by Munich Airport,
which monitors 730 hosts and 18,000 services with this server.
Another project shows similar results. The following graphs show a restructuring of Nagios as the core
on the CMC in an environment with 56,602 services on 2,230 monitored hosts on a virtual machine with two cores:
The magnitude of the difference in an individual case naturally depends on many factors.
In the above case a smaller instance that was not restructured runs on the same server.
Without this the difference in consumption would be even more noticeable.
Further articles on the CMC:
3. Frequently Asked Questions (FAQs)
3.1. Can the CMC also run normal Nagios Plug-ins?
The CMC can of course also run classic Nagios checks actively and passively.
3.2. Will Check_MK continue to support Nagios?
Check_MK is and will remain compatible with Nagios and will continue to fully-support the Nagios core.
Likewise the Check_MK Enterprise Edition will continue to have Nagios as an optional core.
3.3. Can I switch between Nagios and CMC?
Switching between the two cores is simple, as long as your configuration has been created cleanly
with WATO. Details on this can be found in the Migration to the CMC article.
By default the Check_MK Enterprise Edition creates new instances with the CMC as the core.
3.4. Is the CMC freely available?
The CMC is only available as a component of the Check_MK Enterprise Edition in conjunction with a subscription.