Viewing metrics with JConsole

6-12 Oracle Fusion Middleware Performance and Tuning Guide Figure 6–2 DMS Execution Context Communication Protocols

6.7 DMS Tracing and Events

Starting with Oracle Fusion Middleware 11g Release 1 11.1.1.3.0, DMS can selectively trace the following: ■ DMS sensor lifecycle events create, update, delete of state sensors, event sensors and phase sensors ■ Context events start, stop ■ HTTP events start, stop The configuration that controls which of these types of events are traced, and how those events are processed, is recorded in the dms_config.xml file. The DMS trace configuration is split into three parts: 1. Filter Configuration Defines the rules that select the events that are of interest 2. Destination Configuration Defines how the events are used 3. eventRoute Configuration Defines which filters are wired to which destinations A filter can be associated with one or more destinations thus granting the administrator the ability to define a filter rule once and have the resulting subset of all possible events processed on one or more different destinations. The configuration can be modified using the DMS configuration MBean or WLST commands at runtime; this makes the DMS tracing feature invaluable for diagnosing issues within a specific time period or collecting specific data at a specific time for a specific set of criteria. The following types of filter rules are supported: ■ Event Type Conditions Oracle Dynamic Monitoring Service 6-13 Used to identify if an event was triggered from the START or STOP of a PHASE_ SENSOR ■ Context Type Conditions Used to identify if the event was generated from a unit of work whose context contains a value for example, USER ■ Noun Type Conditions Used to identify if the event was triggered from a sensor whose noun is of a specific type for example, JDBC_CONNECTION ■ Logical AND and OR combinations of the above conditions

6.7.1 Configuring the DMS Event System

Configuration is recorded in each servers dms_config.xml file. MBean updates can be made at runtime using command line interface CLI commands and through the Event Configuration Mbean. Configuration updates are applied to the running system in a thread safe, but non-atomic, manner. The object name of the DMS Event configuration MBean is: oracle.dms.event.config:name=DMSEventConfigMBean,type=JMXEventCo nfig To review the current state of your systems DMS event configuration, use the following command: listDMSEventConfiguration[server=server] The resulting output will look similar to this: Event routes: FILTER : auto662515911 DESTINATION : destination1 ENABLED : true FILTER : filter0 DESTINATION : q ENABLED : true Filters with no event route: Fred Destinations with no event route: des4

6.7.1.1 Adding and Editing Filters

Filters define the rules that select which events are considered for tracing. The following example shows how to add a filter that selects all events related to JDBC operations: addDMSEventFilterid=myJDBCFilter, props={condition: NOUNTYPE starts_with JDBC_} This filter assumes that all DMS sensor updates associated with JDBC operations are performed on nouns of types whose names begin JDBC_. If the rule must be modified, the filter may be updated as shown in the following example: updateDMSEventFilterid=myJDBCFilter, props={condition: NOUNTYPE starts_with