| Info |
|---|
| With this guide, we will show you how to monitor a BI |
...
| aggregation. |
| Status | ||||
|---|---|---|---|---|
|
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
| Note |
|---|
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. |
Getting Started
Background information regarding this subject is available in our Official documentation
via the special agent
To get the availability in any case, you need to create a dummy BI Host with the following settings:
.
Now you can create a so-called datasource program to monitor your aggregations. Please insert your dummy host in the Host conditions.
Note 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
.After a discovery of the host, you will see your aggregation as a service. Now you can check the Availability for this aggregation.
via the active check
Note: The aggregation name is the title of the root rule
| Tip |
|---|
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. |
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...