We use cookies to ensure that we give you the best experience on our website.  Visit our Privacy Policy to learn more. If you continue to use this site, we will assume that you are okay with it.

Your choices regarding cookies on this site.
Your preferences have been updated.
In order for the changes to take effect completely please clear your browser cookies and cache. Then reload the page.

Checkmk Conference #6 goes digital. Get your tickets here!

Configuring Checkmk

Checkmk Manual
Last updated: April 21 2016

Search in the manual

1. Introduction

Checkmk differentiates between the configuration environment in which you manage the hosts, services and settings, and the actual monitoring in which the operational monitoring takes place.

Changes in the configuration – adding a new host, for example – will initially have no effect on the monitoring. Changes must first be enabled by an Activate Changes command, which will bring all changes that you have accumulated since the last activation command as a ‘bundle’ into the active production. This might seem a little cumbersome, but it does have the advantage that more complex changes can be prepared without haste in advance before being put into production. For example, after adding a new host you might want to define thresholds or remove some services before ‘arming’ the new component.

The tool for configuring Checkmk via GUI is called the WATO (Web Administration Tool). WATO maintains all configurations in a conventional text data format which experienced users can edit manually, or even create with scripts. WATO can be accessed via the corresponding element in the sidebar. This element is included as standard and offers direct access to all WATO modules.

Whenever you make a change to the monitoring configuration using WATO, this change will at first be picked up and held as pending. Such changes can be identified by the button in the WATO modules, and respectively the button in the sidebar. Both of these buttons open a list of the changes:

With the Activate Changes button the configuration data from WATO will be used to generate a new configuration for the monitoring core, and instruct the core to immediately begin using the new configuration:

The list of pending changes is subsequently cleared. These entries are not lost however – they can subsequently be called up with the Audit Log button. Here you can find a log file of all changes that have been made using WATO.

2. Snapshots

In version 1.2.8 or earlier, whenever you activate changes WATO automatically creates a backup of the configuration. The list of these backups is accessed via the Backup & Restore WATO module:

A click on (details of a snaphot), and then a click on Restore Snapshot copies this back into the configuration. Important note: Only the configuration will be restored – the monitoring’s state and history will not be affected.

Note: From Checkmk Version 1.4.0 this feature is no longer available, as it is being completely revised.

3. Important WATO modules

WATO includes numerous modules – one for each important function of Checkmk. The following modules are particularly important:

ModuleFunction
Main Menu A list of all WATO modules, each with a short description
Monitoring Agents Here you will find Checkmk agents for Linux, Windows and other operating systems. In the Enterprise Editions you can also configure, package and automatically update the agents via WATO.
Hosts Management of the hosts to be monitored – perhaps the most important module.
Global Settings Global settings – those that do not apply to specific hosts, services or users.
Host & Service Parameters All settings for specific hosts or services are found here. The configuration procedure is rule based.

4. Quick access

Once you have worked longer with WATO you will have learned its icons off by heart – then the smaller version of the WATO menu for the sidebar can be recommended: