Monitor details models

A monitor model consists of several parts describing different aspects: the monitor details model, the KPI model, the dimensional model, the visual model, and the event model. The monitor details model is a container for monitoring contexts and their associated metrics, keys, counters, stopwatches, triggers, and events. The monitor details model holds most of the monitor model information.

The following image shows the elements that can be in a monitor details model: the monitoring context definition, the inbound event definition (event subscription), the outbound event definition, the metric definition, the counter definition, the stopwatch definition, the trigger definition, and maps, which are the expressions that set the content of metrics and outbound events at run time.

The arrows indicate the flow of control between these elements. For example, an incoming event might fire a trigger which in turn controls a stopwatch; it might also increment a counter and provide input to a map that updates a metric. Some elements, such as trigger and map definitions, carry expressions: trigger conditions control whether a trigger fires, and map expressions define a map's output as a function of its inputs. These expressions can depend on fields defined in the monitoring context (metrics, counters, and stopwatches) as well as on event attributes if their evaluation is caused by an inbound event.

Event sources send events to the monitor model, which in turn delivers the events to a monitoring context if they are events to which it has subscribed. Outbound events from a monitoring context are sent to interested monitor models.