MP Content

Unit Monitor

Unit Monitor naming

The ID of a unit monitor depends on what type of unit monitor it is. There is a general convention used for most unit monitors and a number of more specific depending on type, to make the ID/Display name clearer.

Monitor ID

The Unit Monitor Id is made up of the following parts.

Application MPID
The different parts are separated with dots.

Part Description
MPID This is the management pack ID. This must be included to make the monitor ID unique in the management group. To learn more about MPID, see Management pack naming
Description This is a description of the monitor. How to format this differs between the monitor types. See table below.
Monitor Type This is a description of the unit monitor type. See table below.
Suffix This should be UnitMonitor.


The following table describes the different monitor types and suggestions of descriptions.

Type of monitor Monitor Description Monitor Type
Windows Service Monitor Use the name of monitored service. Remove all white spaces and special characters, only letters and numbers. WindowsService
Eventlog Monitor The description should give a hint on what kind of events that are being monitored. If it's a single event id then include the event log and event id in the description. Eventlog
Windows Process Monitor The process name without the file extension should be used. WindowsProcess
Windows Script Monitor Short description on what the script does. Or the script name if that's clear enough to understand what the script does. Script
Windows Performance Monitor Use the name of the counter or a short description of the counter. WindowsPerformance
SNMP Probe Use the name or a description of the counter being sampled. SNMPProbe


Using the table above we get the following examples:

Monitor Type Monitor Information Monitor ID (MPID left out)
Windows Service.UnitMonitor Name: Spooler MPID.Spooler.WindowsService.UnitMonitor
Eventlog Log: Application
EventID: 155, 156, 167
MPID.SyncFailure.Eventlog.UnitMonitor
Eventlog Log: Application
EventID: 1432
MPID.ApplicationEventID1432.Eventlog.UnitMonitor
Windows Process Process name: ulisa.exe MPID.ulisa.WindowsProcess.UnitMonitor
Windows Process Process name: notepad.exe MPID.notepad.WindowsProcess.UnitMonitor
Script Script name: ConnectionTestAppServer.ps1 MPID.ConnectionTestAppServer.Script.UnitMonitor
Script Script name: CheckOutputFiles.ps1 MPID.CheckOutputFiles.Script.UnitMonitor
SNMP Probe Counter name: Temperature MPID.Temperature.SNMPProbe.UnitMonitor


Display name

The monitor display name is harder to set any fixed rules for. The display name is what is shown in the Health Explorer in the Operations Console and must be clear enought so that the operator knows what's being monitored.

Based on the examples above the following display names coud be used.

Monitor ID (MPID left out) Display Name
MPID.Spooler.WindowsService.UnitMonitor Spooler Service
MPID.SyncFailure.Eventlog.UnitMonitor Synchroniation Failure
MPID.ApplicationEventID1432.Eventlog.UnitMonitor Application, EventID 1432

This is not a very good display name. A name like this makes it hard for the operators to know what went wrong. Try to come up with a more descriptive name. For example: Connection Failure.
MPID.ulisa.WindowsProcess.UnitMonitor Ulisa process
MPID.notepad.WindowsProcess.UnitMonitor Notepad Process
MPID.ConnectionTestAppServer.Script.UnitMonitor Connection Test
MPID.CheckOutputFiles.Script.UnitMonitor Output files
MPID.Temperature.SNMPProbe.UnitMonitor Temperature

Version: 1.0
Created: 2016-05-23, 08:00