Getting started with monitoring

Create the first site as root with the omd create command followed by the name of the site. The name may only consist of letters and numbers. The convention here is lower case letters. In the User guide, we use the name mysite in examples.

As you can see in the command output, when the site is created, an administrative Checkmk user with the name cmkadmin is automatically created, which you can use to log in to the Checkmk web interface. cmkadmin has been given a random password. Make a note of this password — or change it. You will learn how to do this in the paragraph following the next paragraph.

Once you have created the new site, subsequent administration is no longer carried out as the root, but instead as the site user. The easiest way to become a site user is with the following command:

As a site user, you can change the password of the cmkadmin user as follows:

A site can be started or stopped. Newly-created sites begin their lives in a stopped state. Therefore, you must start the site by command:

Tip: By the way, creating and starting a site is covered in more detail in the Beginner’s guide.

If your Checkmk server is called myserver and your site is called mysite, the web interface is accessed with http://myserver/mysite/ in the browser:

Now log in with the user name cmkadmin and the random password or with the password you edited at the beginning. This will take you to the start page of Checkmk.

Note: In the Docker container, you can find the password of the user cmkadmin in the log files of the container. When using the appliance, you set the user name and password yourself when creating the site.

The very first host you include in the monitoring is the monitoring server itself. To do this, you first need a monitoring agent.

Note: On the appliances this Checkmk agent is already pre-installed.

When working with your own Linux server or in a Docker container you must install the agent yourself.

To install the agent, you need the appropriate package file — in RPM file format for SLES and Red Hat Enterprise Linux (RHEL) based systems or in DEB file format for Debian and Ubuntu. You can obtain this package file in several ways, for example by downloading it from the Checkmk interface:

In this case, the host where the agent is to be installed is the monitoring server itself. Therefore, without downloading, you can directly access the package files, which can be found in your site directory (/omd/sites/mysite/) under ~/share/check_mk/agents/:

Install the package — with rpm -U for the RPM file or with dpkg -i for the DEB file, for example like this:

For detailed instructions on installing the agent, see Linux agent article.

Trust and TLS-encrypted data exchange between agent and Checkmk site are mandatory from Checkmk version 2.1.0 — even if communicating on the same host (the monitoring server). Therefore, after installation, the next step is to register the agent, or more precisely the Agent Controller, with the site.

Before a host can be registered, it must exist in the Checkmk configuration environment. The management of hosts to be monitored can be found in the Setup menu, more specifically at Setup > Hosts > Hosts. Click Add host, enter localhost as Hostname and click Save & go to folder.

Registration is then done by calling the Agent Controller cmk-agent-ctl on the command line. For the command you need the names of the Checkmk server (linux in the example), the Checkmk site (mysite) and the host (localhost) as just set up in Checkmk. Completing the options are the name (and password) of a Checkmk user with access to the REST API. You can use cmkadmin to do this:

If the specified values were correct, the server certificate will be displayed and you will be prompted to confirm the identity of the Checkmk site with Y. Then you will be asked for the password of the user cmkadmin. If no error message is displayed, the encrypted connection is established.

The registration is described in more detail in the Linux agent article.

You do the rest again via the Checkmk interface, in the host’s properties, which you reach via Setup > Hosts > Hosts and then Edit the properties of this host.

Click Save & go to service configuration:

In this list, add all services found but not yet monitored (Undecided) to the monitoring by clicking Accept all.

Then click on the orange button with the number of changes at the top right of the main page to activate the changes on the following page with Activate on selected sites. This takes the new host and its services from the configuration environment into the monitoring environment.

That’s it!

The server will now be monitored with with default settings, which you can see if you display all hosts in the Monitor menu with Monitor > Overview > All hosts and then select the new localhost:

You can include additional devices to your monitoring in the same way. Here are a couple of hints:

Tip: If you ever get stuck, we hope you will find the answer to your question in this User guide. If you have questions concerning details of the Checkmk interface, you can also display the context-sensitive inline help: on the main page in the Help menu with Help > Show inline help.