Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 32 Next »

With this guide, we will show you how to monitor a BI aggregation.

LAST TESTED ON CHECKMK 2.2.0P1

Table of Contents


We always recommend using the special agent instead of the active check to monitor the BI aggregation. The special agent is more efficient than the active check.

via the special agent

  1. To get the availability in any case, you need to create a dummy BI Host with the following settings:

    Screenshot of IP address family set to No IP. Checkmk agent set to Configured API integrations, no Checkmk agent.

    .

  2. Now you can create a so-called datasource program to monitor your aggregations. Please insert your dummy host in the Host conditions.

    Screenshot of Dummy_BI_host set in Explicit host

    Filter aggregations: You can filter by a regex or an aggregation group for a specific BI aggregation

    Aggregation assignments: You should remove the explicit host when using that option. With this option, the piggyback mechanism will be used. So every affected host will get a service.

    To debug the special agent, please follow the manual: BI special agent


    .

  3. After a discovery of the host, you will see your aggregation as a service. Now you can check the Availability for this aggregation.

    Aggregation enabled

via the active check

Note: The aggregation name is the title of the root rule

With this solution, you're able to add the availability to your reports!

If you want to debug the active check, you may want to look here: Debugging check_http#ExecutetheactiveCheckmanually It's the same procedure for the BI.





  • No labels