Viewing Metrics Using the Spy Servlet

Oracle Dynamic Monitoring Service 6-11 – Root RID = 0 2. Single sub-task on Oracle WebLogic Server: – Same ECID = B5C094FA...BE4AE8 – Sub-task RID = 0:1 3. Two Sub-tasks, one on each web service: – First web service invoked Same ECID = B5C094FA...BE4AE8 Sub-task RID = 0:1:1 – Second web service invoked Same ECID = B5C094FA...BE4AE8 Sub-task RID = 0:1:2

6.6.2 DMS Execution Context Usage

The most immediate benefits of the DMS execution context are realized when attempting to correlate log messages between servers. The Oracle standard format for logging involves a field dedicated to the ECID. Once the ECID is known, when its read from an ERROR level log message for example, it is possible to locate all other log messages associated with that task by querying the log files for messages containing that ECID. The following example shows a very specific case of using the command: displayLogsecid=B5C094FA...BE4AE8; In this example, any log files with messages that contain the ECID B5C094FA...BE4AE8 will be displayed.

6.6.3 DMS Execution Context Communication

Figure 6–2 shows the components that cooperate in order to communicate the DMS execution context between each other. Arrows pointing to a component indicate the protocols that are inspected for incoming context information. Outgoing arrows show protocols to which context information is added. It is possible for a single component to send requests to itself, passing context information in that request. 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