59 Matching Annotations
  1. Feb 2018
  2. Aug 2017
    1. Now a last notification will be generated which informs that this status has been entered, and thereafter is quiet.

      When a service enters a flapping state, a notification will be generated which informs the user of the change, and silences further alerts.

    2. (please note here that omdadmin/cmkadmin at first is not a contact for any object)

      (please note that omdadmin/cmkadmin, by default, is not a contact for any objects)

  3. Jun 2017
    1. Here as well the procedure is as usual: install the desired packet, and change over the instances with omd update.

      Here as well, the procedure is the same as before: install the desired package, and update the instances with omd update.

    2. The updating of Check_MK to a new version proceeds somewhat differently from the way we are used to with other software. Why is that so?

      Updating Check_MK is a bit differnt than most other software packages that you may be familiar with. Why is that?

    1. In this way it is no problem, for example, to have version 1.4.0p2 of the  Check_MK Raw Edition and the  Check_MK Enterprise Edition installed simultaneously.

      This makes it possible to have, for example, version 1.4.0p2 of the Check_MK Raw Edition and the Check_MK Enterprise Edition, installed simultaneously.

    2. Because the software will now be put into service by a wider spectrum of users, problems that had not been noticeable during the beta phase will generally now be identified.

      Once deployment of the now stable branch has begun and a wider spectrum of users try out the new release, further issues will be identified.

    3. The only possibility for correcting an error in a daily build is to install a newer daily version in which the error has been corrected. Unfortunately, this newer version can of course contain a newer, diffent error.

      The only way to correct an error in a daily build, is to replace it with a newer daily build which may have its own problems.

  4. Mar 2017
    1. To monitor Windows use the MSI packages which automatically install the Check_MK Agent service.

      To monitor Windows, use the MSI packages which automatically install the Check_MK Agent service.

    2. In the same way you can add additional devices to your monitoring. Here are a couple of tips:

      You can add additional devices to your monitor in the same way. Here are a couple of tips:

    3. You have already installed Check_MK - either with our Appliances or with the package on an existing Linux Server. Further, you have created a monitoring instance (site). In the following examples we will assume that it has been named mysite. Your system is now ready to be brought to life. Here you will learn how to add your first devices to your monitoring.

      After installing Check_MK - with our appliance(LINK) or provided distribution packages(LINK), and creating your first site, it is time to add devices. In the following examples you will learn all about how to bring your site to life.