Beware of Having More Modules

Oracle Dynamic Monitoring Service 6-3 A sensor full name consists of the sensor name, preceded by the name of its associated noun, and a delimiter. Examples: dmsDemoBasicBinomialcomputeSeries, dmsDemoBasicBinomialloops, dmsDemoBasicBinomiallastComputed. A DMS metric name consists of a sensor name plus the . character plus the metric. For example, computeSeries.time, loops.count, and lastComputed.value are valid DMS metric names.

6.1.1.2.2 General DMS Naming Conventions and Character Sets DMS names should be as

compact as possible. Whenever possible, when you define noun and sensor names, avoid special characters such as white space, slashes, periods, parenthesis, commas, and control characters. Table 6–2 shows DMS replacement for special characters in names.

6.1.1.2.3 Noun and Noun Type Naming Conventions The following conventions are used

when naming noun and noun types: ■ A noun name should identify a specific entity of interest. ■ Noun types should have names that clearly reflect the set of metrics being collected. For example, Servlet is the type for a noun under which the metrics that are specific to a given servlet fall. ■ Noun type names should start with a capital letter to distinguish them from other DMS names. All nouns of a given type should contain the same set of sensors. ■ The noun naming scheme uses a as the root of the hierarchy, with each noun acting as a container under the root, or under its parent noun. Note: The suffixes .time, .count, and .value are immutable. Sensor and noun names, however, can be modified as needed. Table 6–2 Replacement for Special Characters in DMS Names Character DMS Replacement Character Space character Underscore character: _ Period character: . Underscore character: _ Control character Underscore character: _ Less than character: Open parenthesis: Greater than character: Close parenthesis: Ampersand: Caret: Double quote: Backquote: ‘ Single quote: ’ Backquote: ‘ Note: Oracle Fusion Middleware includes several built-in metrics. The Oracle Fusion Middleware built-in metrics do not always follow the DMS naming conventions. 6-4 Oracle Fusion Middleware Performance and Tuning Guide

6.1.1.3 DMS Sensors

DMS sensors measure performance data and enable DMS to define and collect a set of metrics. Certain metrics are always included with a sensor and other metrics are optionally included with a sensor. DMS has three different kinds of sensors: ■ Section 6.1.1.3.1, DMS PhaseEvent Sensors ■ Section 6.1.1.3.2, DMS Event Sensors ■ Section 6.1.1.3.3, DMS State Sensors

6.1.1.3.1 DMS PhaseEvent Sensors A DMS PhaseEvent sensor measures the time spent

in a specific section of code that has a beginning and an end. Use a PhaseEvent sensor to track time in a method or in a block of code. DMS can calculate optional metrics associated with a PhaseEvent, including the average, maximum, and minimum time that is spent in the PhaseEvent sensor. Table 6–3 lists the metrics available with PhaseEvent sensors.

6.1.1.3.2 DMS Event Sensors A DMS event sensor counts system events. Use a DMS

event sensor to track system events that have a short duration, or where the duration of the event is not of interest but the occurrence of the event is of interest. Table 6–4 describes the metric that is associated with an event sensor. Table 6–3 DMS PhaseEvent Sensor Metrics Metric Description sensor_name .time Specifies the total time spent in the phase sensor_name. Default metric: time is a default PhaseEvent sensor metric. sensor_name .completed Specifies the number of times the phase sensor_name has completed since the process was started. Optional metric sensor_name .minTime Specifies the minimum time spent in the phase sensor_name, for all the times the sensor_name phase completed. Optional metric sensor_name .maxTime Specifies the maximum time spent in the phase sensor_name, for all the times the sensor_name phase completed. Optional metric sensor_name .avg Specifies the average time spent in the phase sensor_name, computed as the total timenumber of times the phase completed. Optional metric sensor_name .active Specifies the number of threads in the phase sensor_name, at the time the DMS statistics are gathered the value may change over time. Optional metric sensor_name .maxActive Specifies the maximum number of concurrent threads in the phase sensor_name, since the process started. Optional metric