Use the Dynamic Monitoring Service (DMS) commands to view a specific performance metric, a set of performance metrics, or all performance metrics for a particular server or component.
For additional details about metrics, see the chapter "Monitoring Oracle Fusion Middleware" in the Oracle Fusion Middleware Administrator's Guide.
Note:
To use these DMS custom WLST commands, you must invoke the WLST script from the Oracle Common home. See "Using Custom WLST Commands" in the Oracle Fusion Middleware Administrator's Guide.Use the commands in Table 7-1 to view information about performance metrics.
| Use this command... | To... | Use with WLST... |
|---|---|---|
|
Displays the names of the available DMS metric tables. |
Online |
|
|
Displays the content of the DMS metric tables. |
Online |
|
|
Displays available metrics. |
Online |
|
|
Reloads the metric rules. |
Online |
Use with WLST: Online
Displays the names of the available DMS metric tables. The returned value is a list of metric table names.
displayMetricTableNames([servers])
| Argument | Definition |
|---|---|
servers
|
Optional. Specifies the servers from which to retrieve metrics. Valid values are a list of WebLogic Server instance names and system component names.
To specify one server, use the following syntax:
servers='servername'
To specify multiple servers, use one of the following syntax options: servers=['servername1', 'servername2', ...] servers=('servername1', 'servername2', ...) If this argument is not specified, the command returns the list of metric table names for all WebLogic servers and system components. |
The following example displays metric table names for all WebLogic servers and system components:
displayMetricTableNames() ADF ADFc ADFc_Metadata_Service ADFc_Region ADFc_Taskflow ADFc_Viewport BAM_common_connectionpool BAM_common_connectionpool_main BAM_common_messaging BAM_common_messaging_consumers . . .
The following example displays metric table names for the WebLogic Managed Server soa_server1:
displayMetricTableNames(servers='soa_server1') ADF JVM JVM_ClassLoader JVM_Compiler JVM_GC JVM_Memory JVM_MemoryPool JVM_MemorySet JVM_OS JVM_Runtime . . .
The following example displays metric table names for two WebLogic Managed Servers:
displayMetricTableNames(servers=['soa_server1', 'bam-server1']) ADF ADFc ADFc_Metadata_Service ADFc_Region ADFc_Taskflow ADFc_Viewport BAM_common_connectionpool BAM_common_connectionpool_main BAM_common_messaging BAM_common_messaging_consumers . . .
Use with WLST: Online
Displays the content of the DMS metric tables.
The returned value is list of DMS metric tables, with the following information about each table:
The metric table name.
The metric table schema information.
Tthe metric table Rows.
The metric table schema information contains the following:
The name of the column.
The type of the column value.
The unit of the column.
The description of the column.
displayMetricTables([metricTable_1], [metricTable_2], [...,] [servers] [variables])
| Argument | Definition |
|---|---|
metricTable_n |
Optional. Specifies a list of metric tables. By default, this argument displays all available metrics. The metric table name can contain special characters for simple pattern matching. The character '?' matches any single character. The character '*' matches zero or more characters.
You specify the name of the metric table, without an argument name. You can multiple metric table names in a comma-separated list. These are the same names output by the WLST command 'displayMetricTableNames. |
servers
|
Optional. Specifies the servers from which to retrieve metrics. Valid values are a list of WebLogic Server instance names and system component names.
To specify one server, use the following syntax: servers='servername' To specify multiple servers, use one of the following syntax options: servers=['servername1', 'servername2', ...] servers=('servername1', 'servername2', ...) If this argument is not specified, the command returns the list of metric tables for all WebLogic servers and system components. |
variables
|
Optional. Defines the metric aggregation parameters. Valid values are a set of name-value pairs. It uses the following syntax:
variables={name1:value1, name2:value2, ...}
The specific name-value pairs depend on the aggregated metric tables. Each aggregated metric table has its specific set of variable names. |
The following example displays the data from the JVM and the weblogic.management.runtime.WebAppComponentRuntimeMBean metric tables, and limits it to data retrieved from soa_server1 and bam_server1:
displayMetricTables('JVM','weblogic.management.runtime.WebAppComponentRuntimeMBean', servers=['soa_server1','bam_server1']) . . . ApplicationRuntime: soa-infra ComponentName: /integration/services/IdentityService ContextRoot: /integration/services/IdentityService DeploymentState: 2 FilterDispatchedRequestsEnabled: false IndexDirectoryEnabled: false JSPDebug: false JSPKeepGenerated: false JSPPageCheckSecs: 1 JSPVerbose: true ModuleId: /integration/services/IdentityService ModuleURI: IdentityService.war Name: soa_server1_/integration/services/IdentityService ObjectName: com.bea:ApplicationRuntime=soa-infra,Name=soa_server1_/integration/services/IdentityService, ServerRuntime=soa_server1,Type=WebAppComponentRuntime OpenSessionsCurrentCount: 0 OpenSessionsHighCount: 0 . . .
The following example displays the aggregated metric tables with the specified metric aggregation parameters:
displayMetricTables('j2ee_application:webservices_port_rollup', servers=['soa_server1','bam_server1'], variables={'host':'hostname', 'servletName':'dms'}) ---------------------------------------- j2ee_application:webservices_port_rollup ---------------------------------------- Faults: 0 Requests: 0 Requests.averageTime: 0.0 Requests.totalTime: 0.0 ServerName: soa_server1 moduleName: RuntimeConfigService moduleType: WEBs portName: RuntimeConfigServicePortSAML processRequest.active: 0 service.throughput: 0.0 service.time: 0.0 startTime: 1238182359291 webserviceName: RuntimeConfigService Faults: 0 Requests: 0 Requests.averageTime: 0.0 Requests.totalTime: 0.0 ServerName: soa_server1 moduleName: TaskMetadataService moduleType: WEBs portName: TaskMetadataServicePort processRequest.active: 0 service.throughput: 0.0 service.time: 0.0 startTime: 1238182358096 webserviceName: TaskMetadataService . . .
The following example displays the metric tables which names match the specified patterns:
displayMetricTables('J??', 'JVM_*')
.
.
.
---------------
JVM_ThreadStats
---------------
Host: hostname.us.oracle.com
JVM: JVM
Name: threads
Parent: /JVM/MxBeans
Process: AdminServer:9001
ServerName: AdminServer
contention.value: enabled in JVM
daemon.value: 60 threads
deadlock.value: 0 threads
live.value: 61 threads
peak.value: 66 threads
started.value: 241 threads
Host: hostname.us.oracle.com
JVM: JVM
Name: threads
Parent: /JVM/MxBeans
Process: soa_server1:9001
ServerName: soa_server1
contention.value: enabled in JVM
daemon.value: 68 threads
deadlock.value: 0 threads
live.value: 74 threads
peak.value: 74 threads
started.value: 105 threads
.
.
.
Use with WLST: Online
Displays available metrics in the internal format or in XML. The returned value is a text document.
dumpMetrics([servers,] [format])
| Argument | Definition |
|---|---|
servers
|
Optional. Specifies the servers from which to retrieve metrics. Valid values are a list of WebLogic Server instance names and system component names.
To specify one server, use the following syntax:
servers='servername'
To specify multiple servers, use one of the following syntax options: servers=['servername1', 'servername2', ...] servers=('servername1', 'servername2', ...) If this argument is not specified, the command returns the list of metric tables for all WebLogic servers and system components. |
format
|
Optional. Specifies the command output format. Valid values are 'raw' (the default) and 'xml'. For example:
format='raw' format='xml' DMS raw format is a simple metric display format; it displays one metric per line. |
The following example outputs all available metrics, including native WebLogic Server metrics and internal DMS metrics, in the XML format:
dumpMetrics(format='xml')
<table name='weblogic_j2eeserver:jvm' keys='ServerName serverName'
componentId='bam_server1' cacheable='false'>
<row cacheable='false'>
<column name='serverName'><![CDATA[bam_server1]]></column>
<column name='nurserySize.value' type='DOUBLE'>0.0</column>
<column name='jdkVersion.value'><![CDATA[1.6.0_05]]></column>
<column name='jdkVendor.value'><![CDATA[BEA Systems, Inc.]]></column>
<column name='daemonThreads.active' type='LONG'>68</column>
<column name='cpuUsage.percentage' type='DOUBLE'>100.0</column>
<column name='threads.active' type='LONG'>71</column>
<column name='ServerName'><![CDATA[bam_server1]]></column>
<column name='heapUsed.value' type='DOUBLE'>0.0</column>
</row>
The following example outputs metrics from Server-0 in the default raw format:
dumpMetrics(servers='Server-0')
.
.
.
/JVM/MxBeans/threads/Thread-44 [type=JVM_Thread]
ECID.value: null
RID.value: null
blocked.value: 0 msec
blockedCount.value: 1 times
cpu.value: 40 msecs
lockName.value: null
lockOwnerID.value: null
lockOwnerName.value: null
name.value: LDAPConnThread-0 ldap://10.229.149.27:7001
state.value: RUNNABLE
waited.value: 0 msec
waitedCount.value: 0 times
/JVM/MxBeans/threads/Thread-45 [type=JVM_Thread]
ECID.value: null
RID.value: null
blocked.value: 0 msec
.
.
.
The following example outputs metrics from soa_server1 and bam_server1 in XML format:
dumpMetrics(servers=['soa_server1', 'bam_server1'], format='xml')
<table name='oracle_soainfra:high_latency_sync_composites' keys='ServerName
soainfra_composite soainfra_composite_revision soainfra_domain'
componentId='bam_server1' cacheable='false'>
</table>
<table name='weblogic_j2eeserver:ejb_transaction' keys='ServerName appName
ejbModuleName name serverName' componentId='bam_server1' cacheable='false'>
<row cacheable='false'>
<column name='serverName'><![CDATA[bam_server1]]></column>
<column name='name'><![CDATA[MessagingClientParlayX]]></column>
<column name='ejbTransactionCommit.percentage' type='DOUBLE'>0.0</column>
<column name='ejbTransactionRollback.completed' type='LONG'>0</column>
<column name='ejbTransactionTimeout.throughput' type='DOUBLE'>0.0</column>
<column name='ejbTransactionCommit.completed' type='LONG'>0</column>
<column name='ejbTransactionTimeout.completed' type='LONG'>0</column>
<column name='appName'><![CDATA[usermessagingserver]]></column>
<column name='ejbTransactionRollback.throughput' type='DOUBLE'>0.0</column>
<column name='ServerName'><![CDATA[bam_server1]]></column>
<column name='ejbTransactionCommit.throughput' type='DOUBLE'>0.0</column>
<column name='ejbModuleName'><![CDATA[sdpmessagingclient-ejb-parlayx.jar]]></column>
</row>
.
.
.
Use with WLST: Online
Reloads the metric rules. You must run this command after you deploy system components or after you modify metric rules. Generally, Oracle does not recommend that you modify metric rules.
reloadMetricRules([servers])
| Argument | Definition |
|---|---|
servers
|
Optional. Specifies the servers that should reload their metric rules. Valid values are a list of WebLogic Server instance names and system component names.
To specify one server, use the following syntax:
servers='servername'
To specify multiple servers, use the following syntax: servers=['servername1', 'servername2', ...] servers=('servername1', 'servername2', ...) If this argument is not specified, the command reloads the metric rules for all WebLogic servers and system components. |
The following example reloads metric rules for the specified Managed Server:
reloadMetricRules(servers='soa_server1')
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean
as the root.
For more help, use help(domainRuntime)
loaded 'server-oracle_eps_server-11.0.xml'
loaded 'server-weblogic_j2eeserver-11.0.xml'
loaded 'server-oracle_bamweb-11.0.xml'
loaded 'server-oracle_federation-11.0.xml'
loaded 'server-portal-11.0.xml'
loaded 'server-weblogic_j2ee_application_webcenter-11.0.xml
.
.
.