KBI 310207 Dynamic Monitoring Engines




20 Aug 2010


This article explains how the {Dynamic} setting for Monitoring Engines in a Relator works.

Technical Background

A Dynamic Monitoring Engine is a feature of convenience, introduced for customers who have many Relators, Monitoring Groups and Remote Monitoring Engines or Daughter Engines.

This feature determines which Monitoring Engine is responsible for executing the task for a particular target server.

In the case of Daughter Engines, the choice of Monitoring Engine also, by association, determines which Supervising Engine is responsible for the task.

Dynamic Monitoring Engines rely on the placement of servers and devices in a Network Group.

If the server to monitor exists in the same Network Group as a known Monitoring Engine, the {Dynamic} setting will always use this Monitoring Engine to execute the monitoring task.

What Happens If I Have No Monitoring Engines In My Network Group?

This is a possible scenario, and could happen due to ignorance or “accidentally” moving out a sole Monitoring Engine from an existing Network Group.

The short answer is — under a {Dynamic} setting, no Monitoring Engines will be found, and consequently, no monitoring will take place.

It is extremely important that Network Groups are properly analyzed when using the {Dynamic} setting.

These types of situations will typically be diagnosed and found during routine Health Checks by Argent technical staff.

What Happens If I Have Multiple Monitoring Engines In My Network Group?

If there are multiple Monitoring Engines in a single Network Group, the load will be evenly split across the available Monitoring Engines.