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 Manual
Last updated: March 30 2016

Search in the manual

1. Introduction

With commands influencing hosts, services and other objects, you can intervene in the monitoring process. The commands are most often used for acknowledging problems, and for setting scheduled downtime. There are numerous further commands however, some of which are reserved for the administrator. Which commands are available in a view depends on your access rights (Role), as well as on the type of object being displayed. Commands are accessed via the small hammer icon on a view’s title. This opens several entry fields such as those for acknowledging problems, for example:

Each button shown represents a type of command. Some require further information, such as e.g., a text for the acknowledgement. Please don’t forget the online help if you need information regarding a command. Clicking the button opens the confirmation panel:

Important: if you confirm with Yes here, the chosen command will be carried out on all objects shown in the current window! If you first wish to make a selection there are three possibilities:

  • Go into the host’s or service’s detail display so that the command only takes effect there.
  • Set further filters by clicking on in order to reduce the list of displayed objects.
  • Activate the checkboxes .

Activated checkboxes open an extra column on the view’s left side where objects can be selected which the command will act on. A click on the small x at the top of the column will switch all of a table’s checkboxes on or off.

2. Further commands

In the Downtimes panel you will find tools to manually enter maintenance times for the desired hosts and services. For a detailed explanation see the article Scheduled downtimes.

The next tool Fake Check Results allows you to manually-determine the results of any check, i.e., the output of a plug in, performance data or simply the status of a host or service. This is useful, for example, to test the effects of different outputs and statuses on monitoring, views or Notifications.

Finally, the section Various Commands offers all kinds of different tools – for example, for activating/deactivating notifications and checks in order to temporarily exclude certain areas of the infrastructure from monitoring. The options are essentially self-explanatory, but the Reschedule active checks item deserves a special mention. You can use this to manually trigger active checks, such as the Hardware/Software Inventory, outside its usual cycle. However, for many hosts this could cause short-term peaks in CPU usage. To counteract this the checks can be evenly distributed over a period of minutes.

Tip: In the comments at Acknowledge, Downtimes and Various Commands ➳ Add Comment you can enter URLs in the form https://www.example.com; these are then automatically converted to clickable links.