IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing monitor models > Create monitor models

Defining monitor details models

The monitor details model contains the monitoring context definitions, which are containers for inbound event definitions (or event subscriptions), outbound event definitions (that is, events to be sent), and definitions for metrics, stopwatches, counters, and triggers.

You must already have created a monitor model within the business monitoring project.

To define a monitor details model:

Procedure

1. In the Project Explorer view, expand the Monitor Models folder and double-click the monitor model.
2. Define the attributes of the monitor details model as follows:

   1. Click

      Edit if you want to change the ID field. The ID is required, and must be an XML NCName (non-colonized name), which means that it must start with a letter or underscore, and can only contain letters, digits, underscores, hyphens, and periods.

   2. Optional: Type a new name in the Name field.

   3. Optional: Type a description in the Description field. The description is used only in the Monitor Model editor and is not displayed anywhere in Business Monitor. The character set is unrestricted.

   4. Click Edit or type a value into the Time Stamp field. The time stamp identifies the current monitor model and can be used to keep track of versions. The default value is the date and time of the creation of the monitor model. The time stamp is always expressed as Greenwich Mean Time (GMT). For consistency, all date and time metric data in Business Monitor is stored and displayed in the GMT time zone.

What to do next

The available XML Path Language (XPath) user-defined functions are shown in a table for your reference. You can use these functions anywhere that you can use an XPath expression in the model. See Manage user-defined functions for more information.

• Defining monitoring contexts
  A root-level monitoring context is automatically defined whenever you create a monitor details model. It must be completed with definitions of its elements, such as metrics, triggers, and event subscriptions.
• Generate a global monitoring context
  A global monitoring context incorporates metrics from separate monitoring contexts and creates a single monitoring context. Through the use of a global monitoring context, you can see from one view in the dashboard how a process instance runs end to end.
• Defining event groups
  An event group is a container for inbound events that enables you to group events without the additional work of creating a new monitoring context. Event groups are purely a visual construct and are not represented in the monitor model.
• Defining inbound events for monitoring contexts
  

  You define an inbound event to specify that you want this monitoring context to subscribe to a particular event.

• Defining metrics
  A metric is a holder for information in a monitoring context. Metrics are associated with one or more metric value expressions that, when evaluated, give the metric a value. Examples of metrics are the working duration of a process and a supplier's response time.
• Defining keys
  

  The key that uniquely identifies a monitoring context instance is based on the piece or pieces of information that characterize what you want to monitor.

  For example, if the monitoring context represents an order handling process, its key might correspond to the order ID. Each monitoring context must have at least one key.

• Defining stopwatches
  Stopwatches are used to measure the time between two events. Stopwatches can be started, stopped, and reset by triggers or by the arrival of inbound events.
• Defining counters
  Counters keep track of the number of occurrences of some situation or event. Counters can be incremented, decremented, or set to zero by triggers or by the arrival of inbound events.
• Defining triggers for monitoring contexts
  

  You must define triggers to cause outbound events to be sent, and you might also want to define triggers to update metrics, stopwatches, or counters based on special conditions. To define a trigger, you specify its evaluation times and its trigger condition.

• Defining outbound events for monitoring contexts
  

  You can define an outbound event that will be sent from this monitoring context. Outbound events with an extended data element named BusinessSituationName can be received by the Monitor action services, which allows an administrator to specify the actions to take in response to an event.

• Manage user-defined functions
  

  You can make classes of custom XML Path Language (XPath) functions accessible to the Monitor Model editor. After you have added the classes, expressions within the monitor model can use the user-defined XPath functions. The user-defined functions are shown in the table on the Monitor Details Model page and added to the available functions listed in content assist, where appropriate.

Create monitor models