Restrictions in the monitor model debugger

The monitor model debugger has the following restrictions:

• Only CEI-based monitor models are supported for use with the debugger.
• Only one monitor model can be debugged at a time.To debug two or more models at the same time, for example in a scenario where events produced by one model are consumed by the other, combine the models as described in "Combining monitor models" and then launch the debugger on the combined model.
• A monitor model that contains a global monitoring context generated by the Global Monitoring Context wizard cannot be debugged.
• Measures are calculated by aggregating the underlying metric, counter, or stopwatch values of all existing instances and without applying any dimensional filters or partitioning.
• The effects of events processed in the debugger cannot be visualized using Monitor dashboard spaces.
• Do not enable Java™ security when debugging. The XPath processor that the debugger uses might run into problems if Java security is enabled. (This restriction only affects the debugger, not the runtime environment.)
• The debugger treats errors that occur while key performance indicators (KPIs) or measures are being calculated or updated differently from how the Business Monitor server treats these errors. The debugger updates KPIs and measures each time an event is processed so that these values are always up to date. If an error occurs while updating the KPI or measure, the current event is sent to the error queue, and any effects it had are rolled back. However, KPIs that are shown in the Monitor dashboard space are calculated only when the display is refreshed. Because this update does not happen when the events are processed, the events are not sent to the error queue when these calculations cause errors.
  Important: Rolling back an event can lead to errors for subsequent events, if, for example, a monitoring context instance was created but was eliminated because the event was rolled back. After the errors in KPI or measure calculation have been fixed, event processing in the debugger and the Business Monitor server (for a given monitor model) yields the same results.
• The debugger does not support casting duration values to a decimal number of seconds, as in xs:decimal(myDuration). To convert a duration to seconds, divide the duration by one second, as in the following example:

  myDuration div xs:dayTimeDuration('PT1S')

  where myDuration is an xs:dayTimeDuration.
• All XPath functions should start with the correct namespace prefix, as defined in XQuery 1.0 and XPath 2.0 Functions and Operators; W3C Recommendation 23 January 2007; chapter 1.2 Namespaces and Prefixes.
  The following constructor functions should have a namespace prefix that is bound to http://www.w3.org/2001/XMLSchema (typically, xs):

  xs:boolean( ... ), xs:integer( ... ), xs:decimal( ... ), xs:string( ... ),
  xs:dayTimeDuration( ... ), xs:dateTime( ... ), xs:date( ... ), xs:time( ... )

  All other functions should have a namespace prefix that is bound to http://www.w3.org/2005/xpath-functions (typically, fn).

• The monitor model debugger does not support the expression analysis in the following cases:
  • If a model element from a different KPI context is referenced in the KPI expression
  • If a map is not triggered directly by an inbound event or trigger