Oracle® Application Server Performance Guide 10g Release 3 (10.1.3.1.0) Part Number B28942-01 |
|
|
View PDF |
This appendix lists built-in metrics that can help you analyze Oracle Application Server performance. The metrics fall into several distinct areas, such as Oracle HTTP Server, Oracle Containers for J2EE (OC4J). Each table in this chapter lists the metrics that are included in a corresponding Dynamic Monitoring Services metric table.
This appendix contains:
The tables, Table C-1 through Table C-5 describe the Oracle HTTP Server metrics.
Table C-1 describes the HTTP server metrics. The metric table name is ohs_server
.
Table C-1 HTTP Server Metrics (ohs_server)
Metric | Description | Unit |
---|---|---|
Number of busy Child processes |
processes |
|
Number of child processes that finish |
processes |
|
Number of child processes that start |
processes |
|
Number of connections currently open |
threads |
|
Average time spent servicing HTTP connections |
usecs |
|
Number of times an HTTP connection was established. |
ops |
|
Maximum time spent servicing any HTTP connection |
usecs |
|
Minimum time spent servicing any HTTP connection |
usecs |
|
Total time spent servicing HTTP connections |
usecs |
|
Number of HTTP errors |
count |
|
Number of GET requests |
count |
|
Child servers currently in the handle processing phase |
threads |
|
Average time spent in module handler |
usecs |
|
Number of times the handle processing phase has completed |
ops |
|
Maximum time spent in module handler |
usecs |
|
Minimum time spent in module handler |
usecs |
|
Total time spent in module handler |
usecs |
|
Number of times a module redirected a request to a new, internal URI |
ops |
|
Time and date configuration was last modified |
time |
|
Total number of processes for request handling |
processes |
|
Number of loaded modules |
ops |
|
Number of POST requests |
ops |
|
Number of processes ready to handle a request |
processes |
|
Child servers currently in the request processing phase |
threads |
|
Average time required to service an HTTP request |
usecs |
|
Number of HTTP request completed |
ops |
|
Maximum time required to service an HTTP request |
usecs |
|
Minimum time required to service an HTTP request |
usecs |
|
Total time required to service HTTP requests |
usecs |
|
Size of response |
bytes |
Table C-2 describes the child server metrics.
The metric table name is ohs_child
.
Table C-2 Oracle HTTP Server Child Server Metrics (ohs_child)
Metric | Description | Unit |
---|---|---|
pid.value |
Child`s process identifier |
|
slot.value |
Child`s slot identifier |
|
status.value |
Current status of child |
|
time.value |
Time spent by this child in processing most recent request |
|
url.value |
URL of most recent request |
The Oracle HTTP Server responses metrics are included in the metric table type ohs_responses
. This metric table includes one metric containing the count, number of times the response was generated, for each HTTP response type.
For example, Success_OK_200.count: 28 ops
.
Table C-3 shows the Oracle HTTP Server virtual host metrics.
The metrics table type is ohs_vhostSet
.
The ohs_virtualHost
metric table type contains information on virtual host names and locations, and request and response metrics.
Table C-3 Oracle HTTP Server Virtual Host Metrics (ohs_virtualHost)
Metric | Description | Unit |
---|---|---|
Number of requests currently being processed by this host |
threads |
|
Average time spent processing requests for this virtual host |
usecs |
|
Number of requests processed by this virtual host |
ops |
|
Maximum time spent processing any single request for this virtual host |
usecs |
|
Minimum time spent processing any single request for this virtual host |
usecs |
|
Total time spent processing requests for this virtual host |
usecs |
|
Size of response |
bytes |
|
Type of virtual host |
There is one set of metrics for each module loaded into the server.
The metric table name is ohs_module
.
Table C-5 Oracle HTTP Server Modules/mod_*.c Metrics (ohs_module)
Metric | Description | Unit |
---|---|---|
Number of requests declined |
ops |
|
Number of requests currently being handled by this module |
requests |
|
Average time required for this module |
usecs |
|
Number of requests handled by this module |
ops |
|
Maximum time required for this module |
usecs |
|
Minimum time required for this module |
usecs |
|
Total time required for this module |
usecs |
Table C-6 shows the mod_oc4j
Failure Causes metrics. This table represents the categorization of errors that return an INTERNAL_SERVER_ERROR
to the client.
The metric table name is mod_oc4j_request_failure_causes
.
Table C-6 HTTP Server mod_oc4j Request Failure Causes Metrics
Metric | Description | Unit |
---|---|---|
The total number of times an internal error occurred. There could be a number of reasons, including: mod_oc4j not finding a connection endpoint, configuration errors, and others. |
ops |
|
The total number of times that an oc4j JVM could not be found to service requests. |
ops |
|
The total number of times mod_oc4j declined to handle a request. |
ops |
Table C-7 shows the mod_oc4j
Mount Point metrics. There is one mount point metric table for each mount point specified in mod_oc4j.conf. This table includes a set of metrics for each mount point specified, with each set grouped under the mntPtid. Where id is an integer that is automatically generated during module initialization.
The metric table name is mod_oc4j_mount_pt_metrics
.
Table C-7 HTTP Server mod_oc4j Mount Point Metrics
Metric | Description | Unit |
---|---|---|
Specifies the destination name. For example, with:
The |
String |
|
Specifies the total number of requests, both session and non-session, that mod_oc4j failed to route to an OC4J. |
ops |
|
Specifies the total number of non session requests that mod_oc4j failed to route to an oc4j process. |
ops |
|
Specifies the total number of session requests that mod_oc4j failed to route to an OC4J process. |
ops |
|
Shows the total number of requests that have had a failover (which means that the had an error while talking to a JVM and switched over to another JVM. |
ops |
|
Specifies the echo of the value specified as the path for Oc4jMount directive in mod_oc4j.conf. DMS changes certain characters, including: '/' and '*' to '_' . To preserve the actual path names specified, an internal table containing a mapping between mntPtid and the actual path name is created during |
String |
|
Specifies the total number of failovers for nonsession requests. Shows the number of requests that have had a failover (which means that the request had an error while talking to a JVM and switched over to another JVM. |
ops |
|
Specifies the total number of failovers for session requests. Shows the number of requests that have had a failover (which means that the request had an error while talking to a JVM and switched over to another JVM. |
ops |
|
Specifies the total number of requests, both session and non-session, that mod_oc4j successfully routed to an OC4J instance. |
ops |
|
Specifies the total number of non session requests that mod_oc4j successfully routed to an OC4J process. |
ops |
|
Specifies the total number of session requests that mod_oc4j successfully routed to an OC4J process. |
ops |
Table C-8 shows the mod_oc4j Destination Metrics. This table includes a set of metrics for a specific destination. Each destination can have multiple mount points. There is one mntPts subtree for each mount point specified in mod_oc4j.conf.
The metric table name is mod_oc4j_destination_metrics
.
Table C-8 HTTP Server mod_oc4j Destination Metrics
Metric | Description | Unit |
---|---|---|
Specifies the total number of requests, both session and non-session, that mod_oc4j failed to route to an OC4J. |
ops |
|
Specifies the total number of non session requests that mod_oc4j failed to route to an OC4J process. |
ops |
|
Specifies the total number of session requests that mod_oc4j failed to route to an OC4J process. |
ops |
|
Shows the total number of requests that have had a failover (which means that the had an error while talking to a JVM and switched over to another JVM.. |
ops |
|
Specifies the total number of routable OC4J JVMs that belong to this destination. |
Number of JVMs |
|
Specifies the echo of the value specified as destination for Oc4jMount directive in mod_oc4j.conf, a single destination may appear several times in mod_oc4j.conf.Example: Oc4jMount /j2ee/* home,oc4jinstance2 Name.value would be home,oc4jinstance2 |
String |
|
Specifies the total number of failovers for non session requests. |
ops |
|
Specifies the total number of failovers. |
ops |
|
Specifies the total number of requests, both session and non-session, that mod_oc4j successfully routed to an OC4J. |
ops |
|
Specifies the total number of non session requests that mod_oc4j successfully routed to an OC4J process. |
ops |
|
Specifies the total number of session requests that mod_oc4j successfully routed to an OC4J process. |
ops |
Table C-9 describes the OSSL metrics.
The metric table type ohs_ossl
.
Table C-9 OHS_OSSL Metrics
Metric | Description | Unit |
---|---|---|
SSL checkcrl was invoked |
time |
|
SSL connection was closed |
time |
|
SSL connection was established |
time |
|
OSSL Data received |
kilobytes |
|
OSSL Data Sent |
kilobytes |
|
SSL entercache was invoked |
time |
|
SSL getcache was invoked |
time |
|
SSL handshake was invoked |
time |
|
an encrypted message was received |
time |
|
an error occurred in receive |
ops |
|
an encrypted message was sent |
time |
|
an error occurred in send |
ops |
|
SSL setfixup was invoked |
time |
Table C-10 shows the JVM metrics. There is one set of metrics for each Java process (OC4J) running in the site.
Table C-10 JVM Metrics (JVM)
Metric | Description | Unit |
---|---|---|
The number of active thread groups in the JVM |
integer |
|
The minimum number of active thread groups in the JVM |
integer |
|
The maximum number of active thread groups in the JVM |
integer |
|
The number of active threads in the JVM |
threads |
|
The minimum number of active threads in the JVM |
threads |
|
The maximum number of active threads in the JVM |
threads |
|
Up time for the JVM |
msecs |
|
The amount of heap space free in the JVM |
kilobytes |
|
The minimum amount of heap space free in the JVM |
kilobytes |
|
The maximum amount of heap space free in the JVM |
kilobytes |
|
The total amount of heap space in the JVM |
kilobytes |
|
The minimum amount of total heap space in the JVM |
kilobytes |
|
The maximum amount of total heap space in the JVM |
kilobytes |
Oracle Application Server creates a metric to track the value of each Java Property available through a call to System.getProperties()
on any Java process. For each Java Property, a metric is created under the /JVM/Properties
noun.
For example, each process should have a metric that contains the value of the java.version
system property named, /JVM/Properties/java_version.value
. The system converts property name components with a period, '.' to '_'.
If, during the life of a process, a property is deleted from the JVM system properties, the corresponding metric is deleted. If the value changes, this is reflected in the metric value the next time it is accessed. If a new property is added to the system properties, a new metric is created.
Note: The JVM Properties metrics are only available for viewing using the Spiestext link in AggreSpy, or using the dmstool command to display metrics. |
The following tables list the Oracle Application Server JDBC metrics.
Table C-12 shows the JDBC driver metrics. There is one set of JDBC Driver metrics per JVM.
The metric table type is JDBC_Driver
.
Table C-12 /JDBC/Driver - JDBC_Driver Metrics
Metric | Description | Unit |
---|---|---|
Total number of connections that have been closed. |
ops |
|
Current number of threads creating connections. |
ops |
|
Average time spent creating connections. |
msecs |
|
Number of times this PhaseEvent has started and ended. |
ops |
|
Maximum time spent creating connections. |
msecs |
|
Minimum time spent creating connections. |
msecs |
|
Time spent creating connections. |
msecs |
|
Total number of connections that have been opened. |
ops |
Table C-13 shows the JDBC datasource metrics. There is one set of data source metrics per data source.
The metric table type is JDBC_DataSource
.
Table C-13 /JDBC/data-source-name
- JDBC_Data Source Metrics
Metric | Description | Unit |
---|---|---|
Total number of connections that have been closed. |
ops |
|
Current number of threads creating connections. |
ops |
|
Average time spent creating connections. |
msecs |
|
Number of times this PhaseEvent has started and ended. |
ops |
|
Maximum time spent creating connections. |
msecs |
|
|
Minimum time spent creating connections. |
msecs |
Time spent creating connections. |
msecs |
|
Total number of connections that have been opened. |
ops |
Table C-14 shows the JDBC driver connection metrics. There is one set of JDBC Connection metrics per connection.
The metric table type is JDBC_Connection
.
Table C-14 /JDBC/Driver/CONNECTION
- JDBC Driver Connection Metrics
Metric | Description | Unit |
---|---|---|
Average time spent creating a new statement. |
msecs |
|
|
Number of times a request for a statement failed to be satisfied from the cache. |
ops |
|
Maximum time spent creating a new statement. |
msecs |
|
Minimum time spent creating a new statement. |
msecs |
|
Time spent creating a new statement (this does not include the time required to parse the statement. For information on the metric that includes the parse time see |
msecs |
Average time spent getting a statement from the statement cache. |
msecs |
|
|
Number of times a request for a statement was satisfied from the cache. |
ops |
|
Maximum time spent getting a statement from the statement cache. |
msecs |
|
Minimum time spent getting a statement from the statement cache. |
msecs |
|
Time spent getting a statement from the statement cache. |
msecs |
Url specified for the connection |
||
User name used for the connection |
||
If this is a physical connection, then this refers to its logical connection, if any. |
||
Statement found in cache |
ops |
|
Statement not found in cache |
ops |
Table C-15 shows the JDBC data source metrics. There is one set of JDBC data source specific connection metrics per data source per connection.
The metric table type is JDBC_Connection
.
Table C-15 /JDBC/data-source-name
/CONNECTION
- JDBC Datasource Connection Metrics
Metric | Description | Unit |
---|---|---|
Average time spent creating a new statement. |
msecs |
|
|
Number of times a request for a statement failed to be satisfied from the cache. |
ops |
|
Maximum time spent creating a new statement. |
msecs |
|
Minimum time spent creating a new statement. |
msecs |
|
Time spent creating a new statement (this time does not include the time required to parse the statement. For information on the metric that includes the parse time see |
msecs |
Average time spent getting a statement from the statement cache. |
msecs |
|
|
Number of times a request for a statement was satisfied from the cache. |
ops |
|
Maximum time spent getting a statement from the statement cache. |
msecs |
|
Minimum time spent getting a statement from the statement cache. |
msecs |
|
Time spent getting a statement from the statement cache. |
msecs |
Url specified for the connection |
||
User name used for the connection |
||
If this is a physical connection, then this refers to its logical connection, if any. |
||
|
Statement found in cache |
|
Statement not found in cache |
Table C-16 shows the JDBC connection source metrics.
The metric table type is JDBC_ConnectionSource
.
Table C-16 JDBC Connection Source Metrics
Metric | Description | Unit |
---|---|---|
Number of free slots in the connection cache. |
ops |
|
Maximum number of free slots in the connection cache. |
connections |
|
Minimum number of free slots in the connection cache. |
connections |
|
Number of free slots in the connection cache. |
connections |
|
threads |
||
Average time spent getting a connection from the cache. |
msecs |
|
|
Number of times this PhaseEvent has started and ended. |
ops |
|
Maximum time spent getting a connection from the cache. |
msecs |
|
Minimum time spent getting a connection from the cache. |
msecs |
|
Time spent getting a connection from the cache or not. |
msecs |
Number of times a request for a connection has been satisfied from the cache. |
ops |
|
Number of times a request for a connection failed to be satisfied from the cache. |
ops |
|
Number of physical connections in the cache |
ops |
Table C-17 shows the JDBC statement metrics. There is a set of JDBC statement metrics per connection per statement.
The metric table type is JDBC_Statement
.
Note: The JDBC statement metrics are only available for JDBC connections that have enabled statement caching, and set the propertyoracle.jdbc.DMSStatementCachingMetrics to the value true . When JDBC statement caching is disabled, you can make the JDBC statement metrics available by setting the property oracle.jdbc.DMSStatementMetrics to true . To improve performance and to avoid collecting expensive metrics, by default these properties are both set to false . |
Table C-17 /JDBC/Driver/CONNECTION
/STATEMENT
JDBC Statement Metrics
Metric | Description | Unit |
---|---|---|
The time this statement has spent executing the SQL including the first fetch and the time required to parse the statement. |
msecs |
|
The time this statement has spent in other fetches. |
msecs |
|
The SQL being executed. |
Table C-18 shows the JDBC statement metrics. There is a set of statement metrics per data source per connection per statement.
The metric table type is JDBC_Statement
.
Note: The JDBC statement metrics are only available for JDBC connections that have enabled statement caching and set the propertyoracle.jdbc.DMSStatementCachingMetrics to the value true . When JDBC statement caching is disabled, you can make the JDBC statement metrics available by setting the property oracle.jdbc.DMSStatementMetrics to true . To improve performance and to avoid collecting expensive metrics, by default these properties are set to false . |
Table C-18 /JDBC/data-source-name
/CONNECTION
/STATEMENT
JDBC Statement Metrics
Metric | Description | Unit |
---|---|---|
The time this statement has spent executing the SQL including the first fetch and the time required to parse the statement. |
msecs |
|
The time this statement has spent in other fetches. |
msecs |
|
The SQL being executed. |
Table C-19 shows the JDBC connection pool stats metrics.
The metric table type is jdbc_connection_pool_stats
.
Table C-19 JDBC Connection Pool Stats Metrics
Metric | Description | Units |
---|---|---|
The number of connections closed. |
connections |
|
The number of connections created. |
connections |
|
|
The number of available connections in the pool. |
connections |
|
The upper bound of number of available connections in the pool. |
connections |
|
The upper bound of number of available connections in the pool |
connections |
The upper bound of number of available connections in the pool |
connections |
|
The total number of connections in the pool (used and available) |
connections |
|
|
The total number of connections in the pool (used and available) |
connections |
|
The total number of connections in the pool (used and available) |
connections |
The lower bound of total number of connections in the pool |
connections |
|
|
The upper bound of total number of connections in the pool |
connections |
The time spent using a connection |
time |
|
The time spent waiting for a connection to be available |
time |
|
The number of threads waiting for a connection |
count |
|
The number of threads waiting for a connection |
count |
|
|
The number of threads waiting for a connection |
count |
This section describes the Oracle Application Server mod_plsql
metrics.
Figure C-1, "mod_plsql Metric Tree" shows the structure of the mod_plsql
metrics. The tables in this section describe the relevant metrics.
The /modplsql/HTTPResponseCodes
Metrics lists the response codes returned by mod_plsql
.
The metric table name is modplsql_HTTPResponseCodes
. This metric table includes one metric containing the count, number of times the response was generated, for each HTTP response type.
[type=modplsql_HTTPResponseCodes]
For example, the http404.count
metric holds a count of the "HTTP 404: Not found" response codes.
Table C-20 lists the set of metrics for the mod_plsql
session cache.
The metric table name is modplsql_Cache
.
Table C-20 mod_plsql/SessionCache Metrics
Metric | Description | Unit |
---|---|---|
Status of the cache. This can be either enabled or disabled. |
status |
|
Number of session cache misses (new) |
ops |
|
Number of session cache misses (stale) |
ops |
|
Number of session cache hits |
ops |
|
Number of requests to the session cache |
ops |
Table C-21 lists the set of metrics for the mod_plsql
content cache.
The metric table name is modplsql_ContentCache
.
Table C-21 mod_plsql/ContentCache Metrics
Metric | Description | Unit |
---|---|---|
Status of the cache, either enabled or disabled. |
||
Number of content cache misses (new) |
ops |
|
Number of content cache misses (stale) |
ops |
|
Number of content cache hits |
ops |
|
Number of requests to the content cache |
ops |
The SQLErrorGroups
metrics show the predefined groupings of SQL errors. For each group, the metrics in Table C-22 are recorded.
The metric table name is modplsql_SQLErrorGroup
:
/modplsql/SQLErrorGroups/group [type=modplsql_SQLErrorGroup]
The group is based on the groupings in the Oracle Database Error Messages guide. For example, the metric name Ora24280Ora29249
represents the grouping Ora-24280 to Ora-29249. Each SQL error that occurs as a result of executing a request is put into the appropriate group based on its error code. If you are getting a high number of the same errors, you should investigate what is causing the problem, using the Oracle Database Error Messages guide for further details on the error message.
Table C-22 mod_plsql/SQLErrorGroups Metrics
Metric | Description | Unit |
---|---|---|
Date of the last request to cause the SQL error |
date |
|
Last request to cause the SQL error |
url |
|
SQL error text of the last error |
error |
|
Number of errors that have occurred within the group |
ops |
The LastNSQLErrors
statistics show the last 10 SQL errors that have occurred while executing requests. These are updated in a round robin fashion. For each error, the metrics in Table C-23 are recorded.
The metric table name is modplsql_LastNSQLError
:
/modplsql/LastNSQLErrors/<SQL Error Slot> [type=modplsql_LastNSQLError]
If you are getting a large number of the same errors, you should investigate what is causing the problem. Refer to the Oracle Database Error Messages guide for further details of the error represented by the errorText.value
metric.
Table C-23 mod_plsql/LastNSQLErrors Metrics
Metric | Description | Unit |
---|---|---|
Date the request caused the SQL error |
date |
|
Request causing the SQL error |
url |
|
SQL error text |
error |
Table C-24 lists the set of metrics for the Non-SSO connection pool.
The metric table name is modplsql_DatabaseConnectionPool
:
/modplsql/NonSSOConnectionPool [type=modplsql_DatabaseConnectionPool]
Table C-24 mod_plsql/NonSSOConnectionPool Metrics
Metric | Description | Unit |
---|---|---|
Maximum time to fetch a connection from the pool |
usecs |
|
Minimum time to fetch a connection from the pool |
usecs |
|
Average time to fetch a connection from the pool |
usecs |
|
Child servers currently in the pool fetch phase |
threads |
|
Total time spent fetching connections from the pool |
usecs |
|
Number of times a connection has been requested from the pool |
ops |
|
Number of connection pool misses (new) |
ops |
|
Number of connection pool misses (stale) |
ops |
|
Number of connection pool hits |
ops |
Table C-25 lists the set of metrics for the request owner connection pool.
The metric table name is modplsql_DatabaseConnectionPool
:
/modplsql/RequestOwnerConnectionPool [type=modplsql_DatabaseConnectionPool]
Table C-25 mod_plsql/RequestOwnerConnectionPool Metrics
Metric | Description | Unit |
---|---|---|
Maximum time to fetch a connection from the pool |
usecs |
|
Minimum time to fetch a connection from the pool |
usecs |
|
Average time to fetch a connection from the pool |
usecs |
|
Child servers currently in the pool fetch phase |
threads |
|
Total time spent fetching connections from the pool |
usecs |
|
Number of times a connection has been requested from the pool |
ops |
|
Number of connection pool misses (new) |
ops |
|
Number of connection pool misses (stale) |
ops |
|
Number of connection pool hits |
ops |
Table C-26 lists the set of metrics for the super user connection pool.
The metric table name is modplsql_DatabaseConnectionPool
:
/modplsql/SuperUserConnectionPool [type=modplsql_DatabaseConnectionPool]
Table C-26 mod_plsql/SuperUserConnectionPool Metrics
Metric | Description | Unit |
---|---|---|
Maximum time to fetch a connection from the pool |
usecs |
|
Minimum time to fetch a connection from the pool |
usecs |
|
Average time to fetch a connection from the pool |
usecs |
|
Threads currently in the pool fetch phase |
threads |
|
Total time spent fetching connections from the pool |
usecs |
|
Number of times a connection has been requested from the pool |
ops |
|
Number of connection pool misses (new) |
ops |
|
Number of connection pool misses (stale) |
ops |
|
Number of connection pool hits |
ops |
This sections lists the Oracle Process Manager and Notification Server (opmn) metrics.
This section includes the following:
The opmn_pm
metric table is the root of the process manager subtree for the OPMN DMS metrics. The metrics in this metric table contain statistics about OPMN requests. An OPMN request is a command that has been issued to OPMN from a client, for example DCM, to perform an operation on one or more OPMN managed processes.
Requests can have one of three possible results:
Success – success means OPMN handles the request successfully.
Partial Success – partial Success means OPMN only handles part of the request successfully. For example, if a client wants OPMN to start three OC4J processes, and only two are successfully started, the request result is partial success.
Failure – failure means the request fails.
Table C-27 shows the metric table type opmn_pm
.
Table C-27 OPMN_PM Metrics
Metric | Description | Unit |
---|---|---|
Specifies the number of jobs in the OPMN worker queue |
ops |
|
Specifies the number of local HTTP requests which OPMN handles |
ops |
|
Specifies the number of processes which die after the process manager starts them |
ops |
|
Specifies the number of processes which are restarted after the process manager detects they are dead |
ops |
|
Specifies the number of HTTP requests which fail |
ops |
|
Specifies the number of HTTP requests which partially succeed |
ops |
|
Specifies the number of HTTP requests which succeed |
ops |
|
Specifies the number of remote HTTP requests which OPMN handles |
ops |
|
Specifies the number of worker threads |
threads |
Table C-28 shows the OPMN OC4J proc metrics that provides information on the OC4J process.
The OPMN host statistics metric table provides information on the host running the OPMN process.
Table C-29 shows the metric table type opmn_host_statistics
.
Table C-29 OPMN_HOST_STATISTICS Metrics
Metric | Description | Unit |
---|---|---|
Specifies the number of milliseconds the cpu(s) have been idle since an unspecified time. |
milliseconds |
|
Specifies the amount of free physical memory on the host machine. |
kilobytes |
|
Specifies the number of processors available on the host machine. |
integer |
|
Specifies the time that host statistics are taken. The timestamp is the number of milliseconds from an unspecified time. |
milliseconds from an unspecified time |
|
Specifies the total physical memory available on the host machine. |
kilobytes |
The OPMN IAS instance subtree shows the Oracle Application Server instance node name.
Table C-30 shows the metric table type opmn_ias_instance
.
The OPMN IAS component subtree represents an Oracle Application Server component. The OPMN IAS component subtree includes several metric tables containing component information.
Table C-31 shows the metric table type opmn_process_type
.
Table C-31 OPMN_PROCESS_TYPE Metrics
Metric | Description | Unit |
---|---|---|
Specifies the values of attribute module-IDs, as specified in the process-type tag in the |
String |
Table C-32 shows the metric table type opmn_process_set
.
Table C-32 OPMN_PROCESS_SET Metrics
Metric | Description | Unit |
---|---|---|
Specifies the number, or maximum number, of processes configured for this process set. |
String (integer) |
|
numProcs.value |
Number of process that exist for this process set |
|
IsService.value |
Process set is configured as a service |
String |
Specifies the number of HTTP requests which fail for this process set. |
ops |
|
Specifies the number of HTTP requests which partially succeed for this process set. |
ops |
|
Specifies the number of HTTP requests which succeed for this process set |
ops |
|
Specifies whether, when a process dies, OPMN should restart the process. |
String (boolean) |
Table C-33 shows the metric table type opmn_process
.
Table C-33 OPMN_PROCESS Metrics
Metric | Description | Unit |
---|---|---|
Shows the amount of CPU time used by the process. |
CPU msecs |
|
Shows the heap size of the process. |
Kilobytes |
|
Shows the Oracle Application Server cluster name for the process |
String |
|
Shows the Oracle Application Server instance name for the process |
String |
|
Shows the process index in the process set. This value is only valid for OPMN managed processes, for OPMN unmanaged processes, this value has no meaning, and the value is always 0. |
String (integer) |
|
The amount of memory used by the process. This metric is calculated in an operating system specific manner. On UNIX, this is the process image memory used value. This is all the memory in use by the process. On Windows, this is the working set memory used value. This is the same value that is reported by the Task Manager under the mem usage column. The working set is the set of memory pages touched recently by the threads in the process. If free memory in the system is over a certain threshold, pages are left in the working set of a process, even if they are not in use. When free memory falls below a certain threshold, pages are trimmed from the working sets. If needed, pages are soft-faulted back into the working set before they leave main memory. |
||
The process ID for the process. |
||
The private memory of the process. |
Kilobytes |
|
The shared memory for the process |
Kilobytes |
|
The start time of the process. |
msecs |
|
The status of the process. The status can have the following values:
|
String |
|
The type of the process. See Table C-31 for information on process types. |
||
The OPMN assigned ID for the process. |
||
The uptime for the process. |
msecs |
Table C-34 shows the metric table type opmn_connect
.
The Oracle Process Manager and Notification Server ONS subtree contains Oracle Notification System (ONS) information.
Table C-35 shows the metric table type opmn_ons
.
Table C-35 OPMN_ONS Metrics
Metric | Description | Unit |
---|---|---|
The number of notifications processed by ONS. |
ops |
|
The number of notifications in the process queue. |
ops |
|
The number of notifications received by ONS. |
ops |
|
|
The number of notifications in the receive queue. |
ops |
The number of worker threads. |
String (threads) |
Table C-36 shows the local_port
metrics. The ../ons/local_port
subtree shows information about the ONS local port.
The metric table type is opmn_connect
Table C-36 OPMN ONS LOCAL_PORT Metrics
Metric | Description | Unit |
---|---|---|
Port description |
String |
|
Host name |
String |
|
Port number |
String |
Table C-37 shows the remote_port
metrics. The ../ons/remote_port
subtree shows information about the ONS remote port.
The metric table type is opmn_connect
Table C-37 OPMN ONS REMOTE_PORT Metrics
Metric | Description | Unit |
---|---|---|
|
Port description |
String |
|
Host name |
String |
|
Port number |
String |
Table C-38 shows the request_port
metrics. The ../ons/request_port
subtree shows information about the ONS request port.
The metric table type is opmn_connect
Table C-38 OPMN ONS REQUEST_PORT Metrics
Metric | Description | Unit |
---|---|---|
|
Port description |
String |
|
Host name |
String |
|
Port number |
String |
Table C-39 shows the opmn_ons_topo_entry
metrics.
Table C-40 shows the opmn_appctx
metrics.
Table C-41 shows the DMS internal clock metrics.
Table C-41 DMS-Internal Clock Metrics
Metric | Description | Unit |
---|---|---|
|
The current time as measured with the DMS clock. |
ticks |
|
Number of clock ticks per second - measured. |
ticks |
|
Time between ticks as measured with this clock. |
|
|
||
|
The average duration of a call to get the time with this clock. |
|
|
The number of ticks per second the clock time is reported in. |
ticks |
|
The string description of the units that times are reported in. |
Table C-42 shows the DMS internal log metrics.
Table C-42 DMS-Internal Log Metrics
Metric | Description | Unit |
---|---|---|
|
ops |
|
|
ops |
|
|
Table C-43 shows the DMS internal measurement metrics.
Table C-43 DMS-Internal Measurement Metrics
Metric | Description | Unit |
---|---|---|
|
ops |
|
|
ops |
|
|
ops |
|
|
ops |
|
|
||
|
ops |
|
|
||
|
||
|
Table C-44 shows the DMS internal collector metrics.
Table C-44 DMS-Internal Collector Metrics
Metric | Description | Unit |
---|---|---|
|
ops |
|
|
ops |
|
|
threads |
|
|
||
|
||
|
||
|
||
|
||
|
Table C-45 shows the DMS internal transtrace metrics.
Table C-45 DMS-Internal Transtrace Metrics
Metric | Description | Unit |
---|---|---|
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|