Oracle® Enterprise Manager

Middleware Plug-in Metric Reference Manual

Plug-in Release 12.1.0.7

E25158-10

June 2015

Oracle Enterprise Manager Middleware Plug-in Metric Reference Manual, Plug-in Release 12.1.0.7

E25158-10

Copyright © 2006, 2015, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

What's Changed in this Guide?

How to Use This Manual

- Structure of the Oracle Enterprise Manager Middleware Plug-in Metric Reference Manual

- About Metrics, Thresholds, and Alerts

1 WebLogic Server

- 1.1 Active Applications

- 1.1.1 Application - Active Sessions (pre 11)

- 1.1.2 Application - Current Client Processing Time

- 1.1.3 Application - Average Response Time

- 1.2 Application Overview Metrics

- 1.2.1 Cached Beans

- 1.2.2 Cache Accesses (per minute)

- 1.2.3 Bean Activations (per minute)

- 1.2.4 Cache Hits (%)

- 1.2.5 Cache Misses (per minute)

- 1.2.6 Bean Accesses (per minute)

- 1.2.7 Bean Access Successes (%)

- 1.2.8 Free Bean Instances

- 1.2.9 Bean Destroys (per minute)

- 1.2.10 Bean Access Failures (per minute)

- 1.2.11 Beans in Use

- 1.2.12 Bean Transaction Commits (%)

- 1.2.13 Bean Transaction Commits (per minute)

- 1.2.14 Bean Transaction Rollbacks (per minute)

- 1.2.15 Bean Transaction Timeouts (per minute)

- 1.2.16 MDB Messages (per minute)

- 1.2.17 Requests (per minute)

- 1.2.18 Request Processing Time (ms)

- 1.2.19 Active Sessions

- 1.2.20 Work Manager Pending Requests

- 1.2.21 Work Manager Requests (per minute)

- 1.3 Application Work Manager

- 1.3.1 Work Manager Pending Requests

- 1.3.2 Work Manager Requests (per minute)

- 1.3.3 Work Manager Stuck Threads

- 1.4 Application Metrics

- 1.4.1 Application - Status

- 1.5 Certificate Monitoring

- 1.5.1 No of days left for expiry of the certificate

- 1.6 Connection Pool Metrics By Server

- 1.6.1 Open Connections

- 1.6.2 Free Connections

- 1.6.3 Unavailable Connections

- 1.6.4 Connection Waiters

- 1.6.5 Connections Closed (per minute)

- 1.6.6 Connections Created (per minute)

- 1.6.7 Connections Destroyed due to Error (per minute)

- 1.6.8 Connections Destroyed due to Shrinking (per minute)

- 1.6.9 Connections Destroyed (per minute)

- 1.6.10 Connection Requests Satisfied (per minute)

- 1.6.11 Connection Requests Rejected (per minute)

- 1.6.12 Connections Recycled (per minute)

- 1.7 Datasource Metrics

- 1.7.1 Available Connections

- 1.7.2 Cached Statements not Used (per minute)

- 1.7.3 Cached Statements Used (%)

- 1.7.4 Cached Statements Used (per minute)

- 1.7.5 Connection Creation Time (ms)

- 1.7.6 Connection Leaks (per minute)

- 1.7.7 Connection Pool Size

- 1.7.8 Connection Refresh Failures (per minute)

- 1.7.9 Connection Request Failures (per minute)

- 1.7.10 Connection Requests (per minute)

- 1.7.11 Connection Requests that Waited (%)

- 1.7.12 Connection Requests that Waited (per minute)

- 1.7.13 Connection Requests Waiting

- 1.7.14 Connection Wait Successes (%)

- 1.7.15 Connection Wait Successes (per minute)

- 1.7.16 Connections Created (per minute)

- 1.7.17 Connections in Use

- 1.7.18 Failed Waiting Connection Requests (per minute)

- 1.7.19 Statement Cache Size

- 1.7.20 Statements Added to Cache (per minute)

- 1.7.21 Statements Discarded from Cache (per minute)

- 1.7.22 Successful Connections (%)

- 1.7.23 Unavailable Connections

- 1.8 Datasource State Metric

- 1.8.1 State

- 1.9 EJB Metrics

- 1.9.1 EJB Pool - Threads Timed Out Waiting

- 1.9.2 EJB Pool - Current Failed Attempts For Instance

- 1.9.3 EJB Lock - Timed Out Threads Since Last Collection

- 1.9.4 EJB Lock - Threads Waited Since Last Collection

- 1.10 EJB Cache Metrics By Server

- 1.10.1 Cached Beans

- 1.10.2 Cache Hits (%)

- 1.10.3 Bean Activations (per minute)

- 1.10.4 Cache Accesses (per minute)

- 1.10.5 Cache Misses (per minute)

- 1.10.6 Cache Passivations (per minute)

- 1.11 EJB Lock Metrics at Application Level

- 1.11.1 EJB Lock - Threads Waited Since Last Collection For Application

- 1.12 EJB Module Metrics

- 1.12.1 Cached Beans

- 1.12.2 Cache Accesses (per minute)

- 1.12.3 EJB Activations (per minute)

- 1.12.4 EJB Cache Hits (%)

- 1.12.5 EJB Cache Misses (per minute)

- 1.12.6 EJB Passivations (per minute)

- 1.12.7 Bean Accesses (per minute)

- 1.12.8 Bean Successes (%)

- 1.12.9 Free Bean Instances

- 1.12.10 Bean Destroys (per minute)

- 1.12.11 Failed Bean Accesses (per minute)

- 1.12.12 Beans in Use

- 1.12.13 Bean Transaction Commits (per minute)

- 1.12.14 Bean Transaction Rollbacks (per minute)

- 1.12.15 Bean Transaction Timeouts (per minute)

- 1.12.16 MDB Messages (per minute)

- 1.13 EJB Metrics at Application Level

- 1.13.1 EJB Active Transactions Rolled Back For Application

- 1.13.2 EJB Active Transactions Timed Out For Application

- 1.14 EJB Metrics at Module Level

- 1.14.1 EJB Pool - Threads Timed Out Current Count For Module

- 1.14.2 EJB Pool - Miss Current Count For Module

- 1.14.3 EJB Transactions - Rolled Back Current Count For Module

- 1.14.4 EJB Transactions - Timed Out Current Count For Module

- 1.14.5 EJB Lock - Timed Out Thread Current Count For Module

- 1.15 EJB Pool Metrics

- 1.15.1 Bean Accesses (per minute)

- 1.15.2 Successful Bean Accesses (%)

- 1.15.3 Bean Destroys (per minute)

- 1.15.4 Bean Access Failures (per minute)

- 1.15.5 Beans in Use

- 1.16 EJB Pool Metrics at Application Level

- 1.16.1 EJB Pool - Threads Timed Out Waiting For Application

- 1.16.2 EJB Pool - Current Failed Attempts For Instance For Application

- 1.17 EJB Pool Metrics By Server

- 1.17.1 Bean Accesses (per minute)

- 1.17.2 Bean Destroys (per minute)

- 1.17.3 Bean Access Failures (per minute)

- 1.17.4 Beans in Use

- 1.17.5 Bean Successes (%)

- 1.17.6 Free Bean Instances

- 1.18 EJB Transaction Metrics

- 1.18.1 Bean Transaction Commits (%)

- 1.18.2 Bean Transaction Commits (per minute)

- 1.18.3 Bean Transaction Rollbacks (per minute)

- 1.18.4 Bean Transaction Timeouts (per minute)

- 1.18.5 EJB Active Transactions Rolled Back

- 1.18.6 EJB Active Transactions Timed Out

- 1.19 EJB Transaction Metrics By Server

- 1.19.1 Bean Transaction Commits (per minute)

- 1.19.2 Bean Transaction Rollbacks (per minute)

- 1.19.3 Bean Transaction Timeouts (per minute)

- 1.19.4 Bean Transaction Commits (per minute)

- 1.20 Execute Queue Metrics

- 1.20.1 Execute Queue - Pending Request Current Count

- 1.21 Execute Queue Rollup Metrics

- 1.21.1 Execute Queue Rollup - Pending Request Current Count

- 1.22 Incident Metrics

- 1.22.1 Problem Key

- 1.23 J2EE Application Metrics

- 1.23.1 Application Status

- 1.24 J2EE Server Wide Metrics

- 1.24.1 J2EE Server - Active Sessions

- 1.24.2 J2EE Server - Current Client Processing Time

- 1.25 JDBC Connection Pool Metrics (Detailed)

- 1.25.1 JDBC Connection Pool - Active Connections Current Count

- 1.26 JDBC Rollup - Active JDBC Connections

- 1.26.1 JDBC Rollup - Active Connections

- 1.27 JMS Metrics

- 1.27.1 JMS Connections

- 1.27.2 JMS Servers

- 1.28 JMS Destination Metrics

- 1.28.1 Bytes Stored

- 1.28.2 Bytes Pending

- 1.28.3 Bytes Received (per minute)

- 1.28.4 Consumers Active

- 1.28.5 Messages Stored

- 1.28.6 Messages Pending

- 1.28.7 Messages Received (per minute)

- 1.28.8 Messages Moved (per minute)

- 1.28.9 Messages Deleted (per minute)

- 1.28.10 JMS Destination - Bytes Pending

- 1.28.11 JMS Destination - Messages Pending

- 1.29 JMS Server Metrics

- 1.29.1 Bytes Pageable

- 1.29.2 Bytes Paged In (per minute)

- 1.29.3 Bytes Paged Out (per minute)

- 1.29.4 Bytes Pending

- 1.29.5 Bytes Received (per minute)

- 1.29.6 Bytes Stored

- 1.29.7 Destinations

- 1.29.8 Messages Paged In (per minute)

- 1.29.9 Messages Paged Out (per minute)

- 1.29.10 Messages Pending

- 1.29.11 Messages Received (per minute)

- 1.29.12 Messages Stored

- 1.29.13 Session Pools

- 1.30 JMS Server Metrics (Detailed)

- 1.30.1 JMS Server - Bytes Pending Count

- 1.30.2 JMS Server - Messages Pending Count

- 1.31 JMS Server Metrics By Server

- 1.31.1 Bytes Stored

- 1.31.2 Bytes Pageable

- 1.31.3 Bytes Paged In (per minute)

- 1.31.4 Bytes Paged Out (per minute)

- 1.31.5 Bytes Pending

- 1.31.6 Bytes Received (per minute)

- 1.31.7 Destinations

- 1.31.8 Current JMS Messages

- 1.31.9 Messages Paged In (per minute)

- 1.31.10 Messages Paged Out (per minute)

- 1.31.11 Pending JMS Messages

- 1.31.12 Messages Received (per minute)

- 1.31.13 Session Pools

- 1.32 JRockit VM Runtime Metrics

- 1.32.1 JRockit - Number Of Daemon Threads

- 1.32.2 JRockit - Total Number Of Threads

- 1.32.3 JRockit - CPU Usage( % )

- 1.32.4 JRockit - Used Heap

- 1.32.5 JRockit - Used Physical Memory

- 1.33 Jolt Connection Pool Metrics

- 1.33.1 Maximum Capacity

- 1.33.2 Pool State

- 1.33.3 Request Errors (per minute)

- 1.33.4 Requests (per minute)

- 1.33.5 Pending Requests

- 1.34 JTA Metrics

- 1.34.1 Abandoned Transactions (per minute)

- 1.34.2 Committed Transactions (%)

- 1.34.3 Committed JTA Transactions (per minute)

- 1.34.4 Committed Transaction Time (seconds)

- 1.34.5 Heuristic Transactions (per minute)

- 1.34.6 Transactions Processed (per minute)

- 1.34.7 JTA Transaction Rollbacks (per minute)

- 1.34.8 Transaction Rollbacks due to Application Error (per minute)

- 1.34.9 Transaction Rollbacks due to Resource Error (per minute)

- 1.34.10 Transaction Rollbacks due to System Error (per minute)

- 1.34.11 Transaction Rollbacks due to Timeout (per minute)

- 1.34.12 Active JTA Transactions

- 1.35 JTA Resource Metrics

- 1.35.1 Committed JTA Transactions (per minute)

- 1.35.2 JTA Transactions with Heuristic Commit Decision (per minute)

- 1.35.3 JTA Transactions with Heuristic Hazard Decision (per minute)

- 1.35.4 JTA Transactions with Heuristic Mixed Decision (per minute)

- 1.35.5 JTA Transactions with Heuristic Rollback Decision (per minute)

- 1.35.6 Heuristic JTA Transactions (per minute)

- 1.35.7 JTA Transaction Rollbacks (per minute)

- 1.35.8 Processed JTA Transactions (per minute)

- 1.35.9 Committed JTA Transactions (%)

- 1.36 JVM Metrics

- 1.36.1 CPU Usage (%)

- 1.36.2 Active Daemon Threads

- 1.36.3 Active Threads

- 1.36.4 Free Heap (MB)

- 1.36.5 Heap Usage (MB)

- 1.36.6 Heap Usage (%)

- 1.36.7 JDK Vendor

- 1.36.8 JDK Version

- 1.36.9 Nursery Size (MB)

- 1.37 JVM Class Loading

- 1.37.1 JVM Class Loading - Classes Currently Loaded

- 1.38 JVM Compilation Metrics

- 1.38.1 Compilation Time (since startup) (ms)

- 1.39 JVM Garbage Collectors

- 1.39.1 Name

- 1.39.2 Garbage Collector - Garbage Collection Invocations (since startup)

- 1.39.3 Garbage Collector -Invocations (per min)

- 1.39.4 Garbage Collector - Invocation Time (ms)

- 1.39.5 Garbage Collector - Execution Time (since startup) (ms)

- 1.39.6 Garbage Collector - Old Heap Percent Free after GC (%)

- 1.39.7 Garbage Collector - Percent Time spent (elapsed)

- 1.40 JVM Garbage Collection

- 1.40.1 JVM - Total Garbage Collection Time (ms)

- 1.40.2 JVM - Garbage Collection Time since Last Metric Collection (ms)

- 1.40.3 JVM - Total Garbage Collection Count

- 1.40.4 JVM - Garbage Collection Count since Last Metric Collection

- 1.41 JVM Memory Pools

- 1.41.1 Name

- 1.41.2 Type

- 1.41.3 Memory Pool - Current Usage (MB)

- 1.41.4 Memory Pool - Peak Usage (KB)

- 1.42 JVM Memory Usage

- 1.42.1 JVM Memory - Heap Memory Usage (KB)

- 1.42.2 Non-Heap Memory Usage (KB)

- 1.42.3 Objects Pending Finalization

- 1.43 JVM Runtime Metrics

- 1.43.1 JVM Runtime - Up Time (ms)

- 1.43.2 JVM Runtime - VM Name

- 1.43.3 JVM Runtime - VM Version

- 1.44 JVM ThreadContention

- 1.44.1 JVM Thread Contention - Blocked Count

- 1.44.2 JVM Thread Contention - Blocked Time (since startup) (seconds)

- 1.44.3 JVM Thread Contention - CPU Usage (since startup) (seconds)

- 1.44.4 JVM Thread Contention - Lock Name

- 1.44.5 Thread State

- 1.44.6 JVM Thread Contention - Wait Count

- 1.44.7 JVM Thread Contention - Wait Time (since startup) (seconds)

- 1.45 JVM Threads

- 1.45.1 JVM Threads - Active Daemon Threads

- 1.45.2 JVM Threads - Deadlocked Threads

- 1.45.3 JVM Threads - Peak Threads

- 1.45.4 JVM Threads - Active Threads

- 1.45.5 JVM Threads - Threads Started (since startup)

- 1.46 Limited Server Metrics

- 1.46.1 Active Sockets

- 1.47 Log File Monitoring Metrics

- 1.47.1 Log File Pattern Matched Content

- 1.47.2 Log File Pattern Matched Line Count

- 1.48 Message Driven EJB Metrics By Server

- 1.48.1 MDB Messages (per minute)

- 1.48.2 MDB Suspensions (per minute)

- 1.49 Module Metrics By Server

- 1.49.1 Active Sessions

- 1.50 Response

- 1.50.1 Status

- 1.51 Server Datasource Metrics

- 1.51.1 Available Connections

- 1.51.2 Connection Pool Size

- 1.51.3 Connection Requests (per minute)

- 1.51.4 Successful Connections (%)

- 1.51.5 Connection Requests Waiting

- 1.51.6 Connection Requests that Waited (per minute)

- 1.51.7 Connection Wait Successes (%)

- 1.51.8 Connection Wait Successes (per minute)

- 1.51.9 Statements Added to Cache (per minute)

- 1.51.10 Server Datasource - Cached Statements not Used (per minute)

- 1.51.11 Cached Statements Used (%)

- 1.51.12 Cached Statements Used (per minute)

- 1.51.13 Statement Cache Size

- 1.52 Server Health Metrics

- 1.52.1 Health

- 1.53 Server Jolt Connection Pool Metrics

- 1.53.1 Request Errors (per minute)

- 1.53.2 Pending Requests

- 1.53.3 Requests (per minute)

- 1.54 Server Level Work Manager Metrics

- 1.54.1 Work Manager Pending Requests

- 1.54.2 Work Manager Stuck Threads

- 1.54.3 Work Manager Requests (per minute)

- 1.55 Server State Metrics

- 1.55.1 Server State

- 1.56 Server Work Manager Metrics

- 1.56.1 Work Manager Pending Requests

- 1.56.2 Work Manager Requests (per minute)

- 1.56.3 Work Manager Stuck Threads

- 1.57 Servlet/JSP Metrics

- 1.57.1 Reloads (per minute)

- 1.57.2 Requests (per minute)

- 1.57.3 Request Processing Time (ms)

- 1.58 Servlet Rollup

- 1.58.1 Servlet - Active Invocations

- 1.58.2 Servlet - Current Client Processing Time

- 1.58.3 Servlet - Average Execution Time

- 1.58.4 Servlet - Total Execution Time

- 1.58.5 Servlet - Invocations Per Second

- 1.58.6 Servlet - Invocation Total Count

- 1.59 Thread Pool Metrics

- 1.59.1 Thread Pool - Idle Threads

- 1.59.2 Thread Pool - Total Threads

- 1.59.3 Thread Pool - Hogging Threads

- 1.59.4 Thread Pool - Pending User Requests

- 1.59.5 Thread Pool - Pending Requests

- 1.59.6 Thread Pool - Standby Threads

- 1.59.7 Thread Pool - Requests (per minute)

- 1.59.8 Thread Pool - Threads in Use

- 1.59.9 Thread Pool - Pending System Requests

- 1.60 Web Module Metrics

- 1.60.1 Web Module - Requests (per minute)

- 1.60.2 Web Module - Request Processing Time (ms)

- 1.60.3 Web Module - Active Sessions

- 1.61 Java EE Web Service Endpoints

- 1.61.1 Dispatch Time Total

- 1.61.2 Execution Time Total

- 1.61.3 Invocation Count

- 1.61.4 Response Count

- 1.61.5 Response Error Count

- 1.61.6 Response Time Total

- 1.62 Work Manager Metrics

- 1.62.1 Work Manager Pending Requests

- 1.62.2 Work Manager Requests (per minute)

- 1.62.3 Work Manager Stuck Threads

- 1.62.4 Work Manager - Pending Request Current Count

- 1.62.5 Work Manager - Stuck Thread Count

- 1.63 Work Manager Metrics for Application

- 1.63.1 Work Manager - Pending Request Current Count For Application

- 1.63.2 Work Manager - Stuck Thread Count For Application

- 1.64 Work Manager Metrics for Module

- 1.64.1 Work Manager - Pending Request Current Count For Module

- 1.64.2 Work Manager - Stuck Thread Count For Module

- 1.65 All Work Managers

- 1.65.1 All Work Managers - Pending Request Current Count

- 1.65.2 All Work Managers - Stuck Thread Count

2 Oracle WebLogic Cluster

- 2.1 Cluster Overview Metrics

- 2.1.1 Active JTA Transactions

- 2.1.2 Active Sessions

- 2.1.3 Bean Accesses (per minute)

- 2.1.4 Bean Access Failures (per minute)

- 2.1.5 Bean Activations (per minute)

- 2.1.6 Bean Destroys (per minute)

- 2.1.7 Bean Successes (%)

- 2.1.8 Bean Transaction Commits (%)

- 2.1.9 Bean Transaction Commits (per minute)

- 2.1.10 Bean Transaction Rollbacks (per minute)

- 2.1.11 Bean Transaction Timeouts (per minute)

- 2.1.12 Beans in Use

- 2.1.13 Cache Accesses (per minute)

- 2.1.14 Cache Hits (%)

- 2.1.15 Cache Misses (per minute)

- 2.1.16 Cached Beans

- 2.1.17 Committed JTA Transactions (per minute)

- 2.1.18 Current JMS Messages

- 2.1.19 Free Bean Instances

- 2.1.20 JDBC Connection Creates (per minute)

- 2.1.21 JMS Servers

- 2.1.22 JTA Transaction Rollbacks (per minute)

- 2.1.23 MDB Messages (per minute)

- 2.1.24 Open JDBC Connections

- 2.1.25 Pending JMS Messages

- 2.1.26 Request Processing Time (ms)

- 2.1.27 Requests (per minute)

- 2.1.28 Work Manager Pending Requests

- 2.1.29 Work Manager Requests (per minute)

- 2.2 Cluster Overview Metrics By Server

- 2.2.1 Active JTA Transactions

- 2.2.2 Active Sessions

- 2.2.3 Bean Access Failures (per minute)

- 2.2.4 Bean Accesses (per minute)

- 2.2.5 Bean Activations (per minute)

- 2.2.6 Bean Destroys (per minute)

- 2.2.7 Bean Successes (%)

- 2.2.8 Bean Transaction Commits (%)

- 2.2.9 Bean Transaction Commits (per minute)

- 2.2.10 Bean Transaction Rollbacks (per minute)

- 2.2.11 Bean Transaction Timeouts (per minute)

- 2.2.12 Beans in Use

- 2.2.13 Cache Accesses (per minute)

- 2.2.14 Cache Hits (%)

- 2.2.15 Cache Misses (per minute)

- 2.2.16 Cached Beans

- 2.2.17 Committed JTA Transactions (per minute)

- 2.2.18 Current JMS Messages

- 2.2.19 Free Bean Instances

- 2.2.20 JDBC Connection Creates (per minute)

- 2.2.21 JMS Servers

- 2.2.22 JTA Transaction Rollbacks (per minute)

- 2.2.23 MDB Messages (per minute)

- 2.2.24 Open JDBC Connections

- 2.2.25 Pending JMS Messages

- 2.2.26 Request Processing Time (ms)

- 2.2.27 Requests (per minute)

- 2.2.28 Work Manager Pending Requests

- 2.2.29 Work Manager Requests (per minute)

- 2.3 Deployment Information

- 2.3.1 Deployed Applications

- 2.4 JMS Destination Metrics

- 2.4.1 Bytes Pending

- 2.4.2 Bytes Received (per minute)

- 2.4.3 Bytes Stored

- 2.4.4 Consumers Active

- 2.4.5 Messages Deleted (per minute)

- 2.4.6 Messages Moved (per minute)

- 2.4.7 Messages Pending

- 2.4.8 Messages Received (per minute)

- 2.4.9 Messages Stored

- 2.5 Response

- 2.5.1 Status

- 2.6 Work Manager Metrics

- 2.6.1 Work Manager Stuck Threads

3 Oracle Access Manager

- 3.1 All Datasources Metrics

- 3.1.1 Available Connections

- 3.1.2 Cached Statements Not Used (per minute)

- 3.1.3 Cached Statements Used (%)

- 3.1.4 Cached Statements Used (per minute)

- 3.1.5 Connection Pool Size

- 3.1.6 Connection Requests (per minute)

- 3.1.7 Connection Requests that Waited (per minute)

- 3.1.8 Connection Requests Waiting

- 3.1.9 Connection Wait Successes (%)

- 3.1.10 Connection Wait Successes (per minute)

- 3.1.11 Connections Created (per minute)

- 3.1.12 Connections in Use

- 3.1.13 Statement Cache Size

- 3.1.14 Statements Added to Cache (per minute)

- 3.1.15 Successful Connections (%)

- 3.2 Application EJB Cache Metrics

- 3.2.1 Bean Activations (per minute)

- 3.2.2 Cache Accesses (per minute)

- 3.2.3 Cache Hits (%)

- 3.2.4 Cache Misses (per minute)

- 3.2.5 Cache Passivations (per minute)

- 3.2.6 Cached Beans

- 3.3 Application EJB Pool Metrics

- 3.3.1 Available Beans

- 3.3.2 Bean Accesses (per minute)

- 3.3.3 Bean Access Failures (per minute)

- 3.3.4 Bean Destroys (per minute)

- 3.3.5 Beans in Use

- 3.3.6 Successful Bean Accesses (%)

- 3.4 Application EJB Transaction Metrics

- 3.4.1 Bean Transaction Commits (%)

- 3.4.2 Bean Transaction Commits (per minute)

- 3.4.3 Bean Transaction Rollbacks (per minute)

- 3.4.4 Bean Transaction Timeouts (per minute)

- 3.5 Application Message Driven EJB Metrics

- 3.5.1 MDB Messages (per minute)

- 3.5.2 MDB Suspensions (per minute)

- 3.6 Application State Metrics

- 3.6.1 Application State

- 3.7 Audit Operations

- 3.7.1 Average Audit Latency (ms)

- 3.7.2 Audit Operations per second

- 3.7.3 Server Name

- 3.8 Authentication

- 3.8.1 Average Authentication Latency (ms)

- 3.8.2 Authentication Requests per second

- 3.8.3 Authentication Success Rate (%)

- 3.8.4 Server Name

- 3.9 Authorization

- 3.9.1 Average Authorization Latency (ms)

- 3.9.2 Authorization Requests per second

- 3.9.3 Authorization Success Rate (%)

- 3.9.4 Server Name

- 3.10 Connector Metrics

- 3.10.1 Connection Requests Rejected (per minute)

- 3.10.2 Connection Requests Satisfied (per minute)

- 3.10.3 Connection Waiters

- 3.10.4 Connections Closed (per minute)

- 3.10.5 Connections Created (per minute)

- 3.10.6 Connections Destroyed (per minute)

- 3.10.7 Connections Destroyed by Shrinking (per minute)

- 3.10.8 Connections Destroyed due to Error (per minute)

- 3.10.9 Connections Recycled (per minute)

- 3.10.10 Free Connections

- 3.10.11 Open Connections

- 3.10.12 Unavailable Connections

- 3.11 Connector Connection Pool Metrics

- 3.11.1 Connection Requests Rejected (per minute)

- 3.11.2 Connection Requests Satisfied (per minute)

- 3.11.3 Connection Waiters

- 3.11.4 Connections Closed (per minute)

- 3.11.5 Connections Created (per minute)

- 3.11.6 Connections Destroyed (per minute)

- 3.11.7 Connections Destroyed by Shrinking (per minute)

- 3.11.8 Connections Destroyed due to Error (per minute)

- 3.11.9 Connections Recycled (per minute)

- 3.11.10 Free Connections

- 3.11.11 Open Connections

- 3.11.12 Unavailable Connections

- 3.12 Datasource Metrics

- 3.12.1 Available Connections

- 3.12.2 Cached Statements not Used (per minute)

- 3.12.3 Cached Statements Used (%)

- 3.12.4 Cached Statements Used (per minute)

- 3.12.5 Connection Leaks (per minute)

- 3.12.6 Connection Refresh Failures (per minute)

- 3.12.7 Connection Request Failures (per minute)

- 3.12.8 Connection Requests (per minute)

- 3.12.9 Connection Requests that Waited (per minute)

- 3.12.10 Connection Requests Waiting

- 3.12.11 Connection Wait Successes (%)

- 3.12.12 Connection Wait Successes (per minute)

- 3.12.13 Connections Created (per minute)

- 3.12.14 Connections in Use

- 3.12.15 Failed Waiting Connection Requests (per minute)

- 3.12.16 Statements Added to Cache (per minute)

- 3.12.17 Statements Discarded from Cache (per minute)

- 3.12.18 Successful Connections (%)

- 3.12.19 Unavailable Connections

- 3.13 Datasource State Metric

- 3.13.1 State

- 3.14 Deployment Module Metrics

- 3.14.1 Active Sessions

- 3.15 Deployment Application Level Work Manager Metrics

- 3.15.1 Work Manager Pending Requests

- 3.15.2 Work Manager Stuck Threads

- 3.15.3 Work Manager Requests (per minute)

- 3.16 Deployment Module Metrics By Application

- 3.16.1 Active Sessions

- 3.17 Deployment Work Manager Metrics

- 3.17.1 Work Manager Pending Requests

- 3.17.2 Work Manager Requests (per minute)

- 3.17.3 Work Manager Stuck Threads

- 3.18 EJB Cache Metrics

- 3.18.1 Cached Beans

- 3.18.2 Cache Hits (%)

- 3.18.3 Bean Activations (per minute)

- 3.18.4 Cache Accesses (per minute)

- 3.18.5 Cache Misses (per minute)

- 3.18.6 Cache Passivations (per minute)

- 3.19 EJB Pool Metrics

- 3.19.1 Bean Accesses (per minute)

- 3.19.2 Bean Destroys (per minute)

- 3.19.3 Bean Access Failures (per minute)

- 3.19.4 Beans in Use

- 3.19.5 Successful Bean Accesses (%)

- 3.19.6 Available Beans

- 3.20 EJB Transaction Metrics

- 3.20.1 Bean Transaction Commits (%)

- 3.20.2 Bean Transaction Commits (per minute)

- 3.20.3 Bean Transaction Rollbacks (per minute)

- 3.20.4 Bean Transaction Timeouts (per minute)

- 3.21 Identity Federation - IdP Partner Federated Single Sign-Ons

- 3.21.1 Federated Single Sign-Ons (per second)

- 3.21.2 Federated Single Sign-On Latency (ms)

- 3.22 Identity Federation - Protocol Federated Single Sign-Ons

- 3.22.1 IdP Federated Single Sign-Ons (per second)

- 3.22.2 IdP Federated Single Sign-On Latency (ms)

- 3.22.3 SP Federated Single Sign-Ons (per second)

- 3.22.4 SP Federated Single Sign-On Latency (ms)

- 3.23 Identity Federation - SP Partner Federated Single Sign-Ons

- 3.23.1 Federated Single Sign-Ons (per second)

- 3.23.2 Federated Single Sign-On Latency (ms)

- 3.24 Identity Federation - Total Federated Single Sign-Ons

- 3.24.1 Total IdP Federated Single Sign-Ons (per second)

- 3.24.2 Total IdP Federated Single Sign-On Latency (ms)

- 3.24.3 Total SP Federated Single Sign-Ons (per second)

- 3.24.4 Total SP Federated Single Sign-On Latency (ms)

- 3.25 JEE Web Service Endpoint Metrics

- 3.25.1 JEE WS Endpoint - Avg Invocation Time per interval (ms)

- 3.25.2 JEE WS Endpoint - Response Error Throughput (per minute)

- 3.25.3 JEE WS Endpoint - Invocation Throughput (per minute)

- 3.26 LDAP Operations

- 3.26.1 LDAP Operations per second

- 3.26.2 Average LDAP Operation Latency (ms)

- 3.26.3 LDAP Success Rate (%)

- 3.26.4 Server Name

- 3.27 Log File Monitoring

- 3.27.1 Log File Pattern Matched Line Count

- 3.28 Log Operations

- 3.28.1 Average Log Latency (ms)

- 3.28.2 Log Operations per second

- 3.28.3 Server Name

- 3.29 MDS Metrics

- 3.29.1 IOs Per Document Get

- 3.29.2 IOs Per MO Content Get

- 3.29.3 Metadata Object Get Processing Time (seconds)

- 3.29.4 Metadata Update Processing Time (seconds)

- 3.30 Message-Driven EJB Metrics

- 3.30.1 MDB Messages (per minute)

- 3.30.2 MDB Suspensions (per minute)

- 3.30.3 MDB Status

- 3.31 Mobile and Social - Internet Identity Providers

- 3.31.1 Authentications (per second)

- 3.32 Mobile and Social - JWT Tokens

- 3.32.1 JWT Access Creation Tokens (per second)

- 3.32.2 JWT Access Creation Token Latency (ms)

- 3.32.3 JWT User Creation Tokens (per second)

- 3.32.4 JWT User Creation Token Latency (ms)

- 3.32.5 JWT Client Creation Tokens (per second)

- 3.32.6 JWT Client Creation Token Latency (ms)

- 3.32.7 JWT Get Tokens (per second)

- 3.32.8 JWT Get Token Latency (ms)

- 3.33 Mobile and Social - Local Logins and Registrations

- 3.33.1 Completed Local Logins (per second)

- 3.33.2 Failed Local Logins (per second)

- 3.33.3 Completed User Registrations (per second)

- 3.33.4 Incomplete User Registrations(per second)

- 3.34 Mobile and Social - Mobile JWT Tokens

- 3.34.1 JWT Access Creation Tokens (per second)

- 3.34.2 JWT Access Creation Token Latency (ms)

- 3.34.3 JWT User Creation Tokens (per second)

- 3.34.4 JWT User Creation Token Latency (ms)

- 3.34.5 JWT Client Creation Tokens (per second)

- 3.34.6 JWT Client Creation Token Latency (ms)

- 3.34.7 JWT Get Tokens (per second)

- 3.34.8 JWT Get Token Latency (ms)

- 3.35 Mobile and Social - Mobile OAM Tokens

- 3.35.1 OAM Access Creation Tokens (per second)

- 3.35.2 OAM Access Creation Token Latency (ms)

- 3.35.3 OAM User Creation Tokens (per second)

- 3.35.4 OAM User Creation Token Latency (ms)

- 3.35.5 OAM Client Creation Tokens (per second)

- 3.35.6 OAM Client Creation Token Latency (ms)

- 3.35.7 OAM Get Tokens (per second)

- 3.35.8 OAM Get Token Latency (ms)

- 3.35.9 OAM Termination Tokens (per second)

- 3.35.10 OAM Termination Token Latency (ms)

- 3.36 Mobile and Social - OAM Tokens

- 3.36.1 OAM Creation Tokens (per second)

- 3.36.2 OAM Creation Token Latency (ms)

- 3.36.3 OAM Get Tokens (per second)

- 3.36.4 OAM Get Token Latency (ms)

- 3.36.5 OAM Termination Tokens (per second)

- 3.36.6 OAM Termination Token Latency (ms)

- 3.37 Mobile and Social - User Profile Service - Group

- 3.37.1 Create Group Operations (per second)

- 3.37.2 Create Group Operation Latency (ms)

- 3.37.3 Read Group Operations (per second)

- 3.37.4 Read Group Operation Latency (ms)

- 3.37.5 Delete Group Operations (per second)

- 3.37.6 Delete Group Operation Latency (ms)

- 3.37.7 Update Group Operations (per second)

- 3.37.8 Update Group Operation Latency (ms)

- 3.37.9 Search Group Operations (per second)

- 3.37.10 Search Group Operation Latency (ms)

- 3.38 Mobile and Social - User Profile Service - People

- 3.38.1 Create People Operations (per second)

- 3.38.2 Create People Operation Latency (ms)

- 3.38.3 Read People Operations (per second)

- 3.38.4 Read People Operation Latency (ms)

- 3.38.5 Delete People Operations (per second)

- 3.38.6 Delete People Operation Latency (ms)

- 3.38.7 Update People Operations (per second)

- 3.38.8 Update People Operation Latency (ms)

- 3.38.9 Search People Operations (per second)

- 3.38.10 Search People Operation Latency (ms)

- 3.39 Mobile and Social - User Profile Service - Relationship

- 3.39.1 Create Relationship Operations (per second)

- 3.39.2 Create Relationship Operation Latency (ms)

- 3.39.3 Read Relationship Operations (per second)

- 3.39.4 Read Relationship Operation Latency (ms)

- 3.39.5 Delete Relationship Operations (per second)

- 3.39.6 Delete Relationship Operation Latency (ms)

- 3.39.7 Search Relationship Operations (per second)

- 3.39.8 Search Relationship Operation Latency (ms)

- 3.40 Module EJB Cache Metrics

- 3.40.1 Cached Beans

- 3.40.2 Cache Hits (%)

- 3.40.3 Bean Activations (per minute)

- 3.40.4 Cache Accesses (per minute)

- 3.40.5 Cache Misses (per minute)

- 3.40.6 Cache Passivations (per minute)

- 3.41 Module EJB Transaction Metrics

- 3.41.1 Bean Transaction Commits (%)

- 3.41.2 Bean Transaction Commits (per minute)

- 3.41.3 Bean Transaction Rollbacks (per minute)

- 3.41.4 Bean Transaction Timeouts (per minute)

- 3.42 Module Message Driven EJB Metrics

- 3.42.1 MDB Messages (per minute)

- 3.42.2 MDB Suspensions (per minute)

- 3.43 Number of Authentications

- 3.43.1 Number Of Invalid Credential Errors Against The LDAP User Identity Store

- 3.43.2 Number of LDAP Time Out Errors In The Last Collection

- 3.43.3 Number of User Not Found Errors In The Last Collection

- 3.44 Number of Authorizations

- 3.44.1 Number of Failed Authorizations in the last collection

- 3.44.2 Number of SSO Session Creation Failures

- 3.45 OAM Application Clients

- 3.45.1 Average Application Authentication Latency (ms)

- 3.45.2 Application Authentication Requests per second

- 3.45.3 Application Authentication Success Rate (%)

- 3.45.4 Average Application Authorization Latency (ms)

- 3.45.5 Application Authorization Requests per second

- 3.45.6 Application Authorization Success Rate (%)

- 3.46 OAM 10g Client

- 3.46.1 OAM Client Average Authentication Latency (ms)

- 3.46.2 OAM Client Authentication Requests per second

- 3.46.3 OAM Client Authentication Success Rate (%)

- 3.46.4 OAM Client Average Authorization Latency (ms)

- 3.46.5 OAM Client Authorization Requests per second

- 3.46.6 OAM Client Authorization Success Rate (%)

- 3.47 OAM Proxy

- 3.47.1 Proxy Failed Authentications in Last Collection

- 3.47.2 Proxy Failed Authorizations in Last Collection

- 3.47.3 Proxy Failed Resource Protected in Last Collection

- 3.48 Oracle SSO 10g Client

- 3.48.1 OSSO Client Average Authentication Latency (ms)

- 3.48.2 OSSO Client Authentication Requests per second

- 3.48.3 OSSO Client Authentication Success Rate (%)

- 3.49 Oracle Web Service Endpoint Metrics

- 3.49.1 Oracle WS Endpoint - Avg Invocation Time per interval(sec)

- 3.49.2 Oracle WS Endpoint - Fault Throughput(per minute)

- 3.49.3 Oracle WS Endpoint - Invocation Throughput(per minute)

- 3.50 Resource Utilization

- 3.50.1 CPU Utilization (%)

- 3.50.2 Memory Utilization (%)

- 3.51 Response

- 3.51.1 UpDown Status

- 3.52 RESTful Service Application Metrics

- 3.52.1 RESTful Service Invocation Throughput (per minute)

- 3.52.2 RESTful Service Error Count Throughput (per minute)

- 3.52.3 RESTful Service Execution Time Average (seconds)

- 3.53 RESTful Service Method Metrics

- 3.53.1 RESTful Service Invocation Throughput (per minute)

- 3.54 RESTful Service Resource Metrics

- 3.54.1 RESTful Service Invocation Throughput (per minute)

- 3.55 Security Token Service - Token Generation Operations

- 3.55.1 Issuance Latency (ms)

- 3.55.2 Tokens Issued

- 3.55.3 Token Issuances per second

- 3.56 Security Token Service - Token Validation Operations

- 3.56.1 Number of Tokens Validated

- 3.56.2 Token Validations per second

- 3.56.3 Token Validation Latency (ms)

- 3.57 Security Token Service - Partners

- 3.57.1 Tokens Issued

- 3.57.2 Issuance Latency (ms)

- 3.57.3 Token Issuances per second

- 3.57.4 Issuance Success Rate (%)

- 3.57.5 Number of Tokens Validated

- 3.57.6 Token Validation Latency (ms)

- 3.57.7 Token Validations per second

- 3.57.8 Validation Success Rate (%)

- 3.58 Security Token Service - Token Requests

- 3.58.1 Issuance Latency (ms)

- 3.58.2 Tokens Issued

- 3.58.3 Token Issuances per second

- 3.58.4 Issuance Success Rate (%)

- 3.58.5 Token Validation Latency (ms)

- 3.58.6 Number of Tokens Validated

- 3.58.7 Token Validations per second

- 3.58.8 Validation Success Rate (%)

- 3.59 Servlet/JSP Metrics

- 3.59.1 Request Processing Time (ms)

- 3.59.2 Requests (per minute)

- 3.59.3 Reloads (per minute)

- 3.60 Servlet/JSP Metrics By Application

- 3.60.1 Request Processing Time (ms)

- 3.60.2 Requests (per minute)

- 3.60.3 Reloads (per minute)

- 3.61 Servlet/JSP Metrics By Module

- 3.61.1 Request Processing Time (ms)

- 3.61.2 Requests (per minute)

- 3.61.3 Reloads (per minute)

- 3.62 Webgate Status

- 3.62.1 Webgate Status

4 Oracle Access Management Cluster

- 4.1 OAM Applications Domains (Aggregated)

- 4.1.1 Application Authentication Latency (ms)

- 4.1.2 Application Authentication Requests per second

- 4.1.3 Application Authentication Success Rate (%)

- 4.1.4 Application Authorization Latency (ms)

- 4.1.5 Application Authorization Requests per second

- 4.1.6 Application Authorization Success Rate (%)

- 4.2 OAM 10g Aggregates

- 4.2.1 OAM Client Average Authentication Latency (ms)

- 4.2.2 OAM Client Authentication Requests per second

- 4.2.3 OAM Client Authentication Success Rate (%)

- 4.2.4 OAM Client Average Authorization Latency (ms)

- 4.2.5 OAM Client Authorization Requests per second

- 4.2.6 OAM Client Authorization Success Rate (%)

- 4.3 OAM 10g Throughput (Aggregated)

- 4.3.1 OAM Client Authentications per second

- 4.3.2 OAM Client Authorizations per second

- 4.4 OSSO 10g (Aggregated)

- 4.4.1 OSSO Client Average Authentication Latency (ms)

- 4.4.2 OSSO Client Authentication Requests per second

- 4.4.3 Authentication Success Rate (%)

- 4.5 OSSO 10g Throughput (Aggregated)

- 4.5.1 OSSO Client Operations per second

- 4.6 Audit Operations (Aggregated)

- 4.6.1 Average Audit Latency (ms)

- 4.6.2 Audit Operations per second

- 4.7 Audit Operations Throughput (Aggregated)

- 4.7.1 Operations per second

- 4.8 Authentication Aggregates

- 4.8.1 Average Authentication Latency (ms)

- 4.8.2 Authentication Requests per second

- 4.8.3 Authentication Success Rate (%)

- 4.9 Authentications Throughput (Aggregated)

- 4.9.1 Authentication Requests per second

- 4.10 Authorizations (Aggregated)

- 4.10.1 Average Authorization Latency (ms)

- 4.10.2 Authorization Requests per second

- 4.10.3 Authorization Success Rate (%)

- 4.11 Authorizations Throughput (Aggregated)

- 4.11.1 Authorization Requests per second

- 4.12 Core Token Generation Operations

- 4.12.1 Number of Tokens Issued

- 4.12.2 Tokens Issued per second

- 4.12.3 Token Issuance Latency (ms)

- 4.13 Core Token Validation Operations

- 4.13.1 Custom Tokens Validated

- 4.13.2 Tokens Validated per second

- 4.13.3 Token Validation Latency (ms)

- 4.14 Log Operations (Aggregated)

- 4.14.1 Average Latency (ms)

- 4.14.2 Log Operations per second

- 4.15 Log Operations Throughput (Aggregated)

- 4.15.1 Log Operations per second

- 4.16 Token Service Clients

- 4.16.1 Token Issuance Latency (ms)

- 4.16.2 Tokens Issued

- 4.16.3 Tokens Issued per second

- 4.16.4 Token Issuance Success Rate (%)

- 4.16.5 Requester

- 4.16.6 Token Validation Success Rate (%)

- 4.16.7 Token Validation Latency (ms)

- 4.16.8 Tokens Validated

- 4.16.9 Token Validations per second

- 4.17 Response

- 4.17.1 Status

- 4.18 Token Issuances

- 4.18.1 Token Issuance Latency (ms)

- 4.18.2 Tokens Issued

- 4.18.3 Tokens Issued per second

- 4.18.4 Issuance Success Rate (%)

- 4.18.5 Validation Latency (ms)

- 4.18.6 Tokens Validated

- 4.18.7 Validations per second

- 4.18.8 Validation Success Rate (%)

- 4.19 LDAP Operations (Aggregated)

- 4.19.1 LDAP_Operations per second

- 4.19.2 Operation Name

- 4.19.3 Average Latency (ms)

- 4.19.4 LDAP Operations Success Rate (%)

- 4.20 LDAP Operations Throughput (Aggregated)

- 4.20.1 LDAP Operations per second

5 Oracle Adaptive Access Manager

- 5.1 Datasource Metrics

- 5.1.1 Available Connections

- 5.1.2 Connections Created (per minute)

- 5.1.3 Connections in Use

- 5.1.4 Connection Leaks (per minute)

- 5.1.5 Connection Pool Size

- 5.1.6 Connection Refresh Failures (per minute)

- 5.1.7 Connection Request Failures (per minute)

- 5.1.8 Connection Requests (per minute)

- 5.1.9 Successful Connections (%)

- 5.1.10 Unavailable Connections

- 5.1.11 Connection Requests Waiting

- 5.1.12 Failed Waiting Connection Requests (per minute)

- 5.1.13 Connection Requests that Waited (per minute)

- 5.1.14 Connection Wait Successes (%)

- 5.1.15 Connection Wait Successes (per minute)

- 5.2 Datasource - State

- 5.2.1 Statements Added to Cache (per minute)

- 5.2.2 Statements Discarded from Cache (per minute)

- 5.2.3 Cached Statements not Used (per minute)

- 5.2.4 Cached Statements Used (%)

- 5.2.5 Cached Statements Used (per minute)

- 5.2.6 Statement Cache Size

- 5.3 EJB Module Metrics

- 5.3.1 Cached Beans

- 5.3.2 Bean Activations (per minute)

- 5.3.3 Cache Hits (%)

- 5.3.4 Cache Misses (per minute)

- 5.3.5 Bean Accesses (per minute)

- 5.3.6 Bean Access Successes (%)

- 5.3.7 Free Bean Instances

- 5.3.8 Bean Destroys (per minute)

- 5.3.9 Bean Access Failures (per minute)

- 5.3.10 Beans in Use

- 5.3.11 Bean Transaction Commits (per minute)

- 5.3.12 Bean Transaction Rollbacks (per minute)

- 5.3.13 Bean Transaction Timeouts (per minute)

- 5.4 EJB Transaction Metrics

- 5.4.1 Bean Transaction Commits (%)

- 5.4.2 Bean Transaction Commits (per minute)

- 5.4.3 Bean Transaction Rollbacks (per minute)

- 5.4.4 Bean Transaction Timeouts (per minute)

- 5.5 Overview Metrics

- 5.5.1 Cached Beans

- 5.5.2 Cache Accesses (per minute)

- 5.5.3 Bean Activations (per minute)

- 5.5.4 Cache Hits (%)

- 5.5.5 Cache Misses (per minute)

- 5.5.6 Bean Accesses (per minute)

- 5.5.7 Bean Successes (%)

- 5.5.8 Free Bean Instances

- 5.5.9 Bean Destroys (per minute)

- 5.5.10 Bean Access Failures (per minute)

- 5.5.11 Beans in Use

- 5.5.12 Bean Transaction Commits (%)

- 5.5.13 Bean Transaction Commits (per minute)

- 5.5.14 Bean Transaction Rollbacks (per minute)

- 5.5.15 Bean Transaction Timeouts (per minute)

- 5.5.16 MDB Messages (per minute)

- 5.5.17 Requests (per minute)

- 5.5.18 Request Processing Time (ms)

- 5.5.19 Active Sessions

- 5.5.20 Work Manager Pending Requests

- 5.5.21 Work Manager Requests (per minute)

- 5.6 Servlet/JSP Metrics

- 5.6.1 Reloads (per minute)

- 5.6.2 Requests (per minute)

- 5.6.3 Request Processing Time (ms)

- 5.7 Web Module Metrics

- 5.7.1 Requests (per minute)

- 5.7.2 Request Processing Time (ms)

- 5.7.3 Active Sessions

- 5.8 Login Metrics Summary

- 5.8.1 Percentage of Blocked Logins during the Last 5 Minute Collection Interval

- 5.8.2 Number of Logins Blocked during the Last 5 Minute Collection Interval

- 5.8.3 Percentage of Challenged Logins during the Last 5 Minute Collection Interval

- 5.8.4 Number of Logins Challenged during the Last 5 Minute Collection Interval

- 5.8.5 Percentage of Failed Logins during the Last 5 Minute Collection Interval

- 5.8.6 Number of Failed Logins per Sec since the Server Startup

- 5.8.7 Number of Logins Failed during the Last 5 Minute Collection Interval

- 5.8.8 Percentage of Successful Logins during the Last 5 Minute Collection Interval

- 5.8.9 Number of Successful Logins per Sec Since the Server Startup

- 5.8.10 Number of Successful Logins during the Last 5 Minute Collection Interval

- 5.8.11 Number of Total Logins Attempted during the Last 5 Minute Collection Interval

- 5.9 Policy Execution Summary

- 5.9.1 Average Execution Time for All Policies since Server Startup (ms)

- 5.9.2 Total Number of Policies Processed

- 5.9.3 Total Number of Policies Processed since Last Sample

- 5.9.4 Maximum Time Taken by Any Policy since Server Startup (ms)

- 5.9.5 Minimum Time Taken by Any Policy Since Server Startup (ms)

- 5.9.6 Time Taken for Servicing All Policies Since Server Startup (ms)

- 5.10 Response

- 5.10.1 UpDown Status

- 5.11 Rule Execution Summary

- 5.11.1 Average Execution Time for All Requests Since Server Startup (ms)

- 5.11.2 Total Number of Requests Completed

- 5.11.3 Total Number of Requests Completed Since Last Sample

- 5.11.4 Maximum Time Taken by Any Request since Server Startup (ms)

- 5.11.5 Minimum Time Taken by Any Request Since Server Startup (ms)

- 5.11.6 Time Taken for Servicing All Requests Since Server Startup (ms)

- 5.12 Checkpoint Execution Summary

- 5.12.1 Average Checkpoint Processing Time for All Requests Since Server Startup (ms)

- 5.12.2 Total Number of Checkpoints Completed

- 5.12.3 Total Number of Checkpoints Completed Since Last Sample

- 5.12.4 Maximum Time Taken by Any CheckPoint Since Server Startup (ms)

- 5.12.5 Minimum Time Taken by Any Checkpoint Since Server Startup (ms)

- 5.12.6 Time Taken for Servicing All Checkpoint Since Server Startup (ms)

- 5.13 Update Authorization Status Summary

- 5.13.1 Average Execution Time for All Requests Since Server Startup (ms)

- 5.13.2 Total Number of Requests Completed

- 5.13.3 Total Number of Requests Completed Since Last Sample

- 5.13.4 Maximum Time Taken by Any Request Since Server Startup (ms)

- 5.13.5 Minimum Time Taken by Any Request Since Server Startup (ms)

- 5.13.6 Time Taken for Servicing All Requests Since Server Startup (ms)

- 5.14 Update Log Summary

- 5.14.1 Average Execution Time for All Requests Since Server Startup (ms)

- 5.14.2 Total Number of Requests Completed

- 5.14.3 Total Number of Requests Completed Since Last Sample

- 5.14.4 Maximum Time Taken by Any Request Since Server Startup (ms)

- 5.14.5 Minimum Time Taken by Any Request Since Server Startup (ms)

- 5.14.6 Time Taken for Servicing All Requests Since Server Startup (ms)

6 Oracle Adaptive Access Manager Cluster

- 6.1 Oracle Adaptive Access Manager Datastore Information

- 6.1.1 JDBC URL

- 6.2 Login Metrics Summary

- 6.2.1 Blocked Logins Rate (%)

- 6.2.2 Blocked Logins

- 6.2.3 Challenged Logins Rate (%)

- 6.2.4 Challenged Logins

- 6.2.5 Failed Logins Rate (%)

- 6.2.6 Failed Logins

- 6.2.7 Successful Logins Rate (%)

- 6.2.8 Successful Logins

- 6.2.9 Total Logins Attempted

- 6.3 Login Metrics Rate Summary

- 6.3.1 Failed Logins per second

- 6.3.2 Successful Logins per second

- 6.4 Response

- 6.4.1 Status

7 Oracle Identity Manager

- 7.1 Oracle Adaptive Metrics

- 7.1.1 Adapter Name

- 7.1.2 Average Adapter Execution Time (ms)

- 7.1.3 Completed Adapter Executions

- 7.1.4 Maximum Adapter Execution Time (ms)

- 7.1.5 Minimum Adapter Execution Time (ms)

- 7.2 Datasource Metrics

- 7.2.1 Datasource - Available Connections

- 7.2.2 Datasource - Connections Created (per minute)

- 7.2.3 Datasource - Connections in Use

- 7.2.4 Datasource - Connection Leaks (per minute)

- 7.2.5 Datasource - Connection Pool Size

- 7.2.6 Datasource - Connection Refresh Failures (per minute)

- 7.2.7 Datasource - Connection Request Failures (per minute)

- 7.2.8 Datasource - Connection Requests (per minute)

- 7.2.9 Datasource - Successful Connections (%)

- 7.2.10 Datasource - Unavailable Connections

- 7.2.11 Datasource - Connection Requests Waiting

- 7.2.12 Datasource - Failed Waiting Connection Requests (per minute)

- 7.2.13 Datasource - Connection Requests that Waited (per minute)

- 7.2.14 Datasource - Connection Wait Successes (%)

- 7.2.15 Datasource - Connection Wait Successes (per minute)

- 7.2.16 Datasource - State

- 7.2.17 Datasource - Statements Added to Cache (per minute)

- 7.2.18 Datasource - Statements Discarded from Cache (per minute)

- 7.2.19 Datasource - Cached Statements not Used (per minute)

- 7.2.20 Datasource - Cached Statements Used (%)

- 7.2.21 Datasource - Cached Statements Used (per minute)

- 7.2.22 Datasource - Statement Cache Size

- 7.3 EJB Module Metrics

- 7.3.1 Cached Beans

- 7.3.2 Bean Activations (per minute)

- 7.3.3 Cache Hits (%)

- 7.3.4 Cache Misses (per minute)

- 7.3.5 Bean Accesses (per minute)

- 7.3.6 Bean Access Successes (%)

- 7.3.7 Free Bean Instances

- 7.3.8 Bean Destroys (per minute)

- 7.3.9 Bean Access Failures (per minute)

- 7.3.10 Beans in Use

- 7.3.11 Bean Transaction Commits (per minute)

- 7.3.12 Bean Transaction Rollbacks (per minute)

- 7.3.13 Bean Destroys (per minute)

- 7.4 EJB Transaction Metrics

- 7.4.1 Bean Transaction Commits (%)

- 7.4.2 Bean Transaction Commits (per minute)

- 7.4.3 Bean Transaction Rollbacks (per minute)

- 7.4.4 Bean Transaction Timeouts (per minute)

- 7.5 Overview Metrics

- 7.5.1 Cached Beans

- 7.5.2 Cache Accesses (per minute)

- 7.5.3 Bean Activations (per minute)

- 7.5.4 Cache Hits (%)

- 7.5.5 Cache Misses (per minute)

- 7.5.6 Bean Accesses (per minute)

- 7.5.7 Bean Successes (%)

- 7.5.8 Free Bean Instances

- 7.5.9 Bean Destroys (per minute)

- 7.5.10 Bean Access Failures (per minute)

- 7.5.11 Beans in Use

- 7.5.12 Bean Transaction Commits (%)

- 7.5.13 Bean Transaction Commits (per minute)

- 7.5.14 Bean Transaction Rollbacks (per minute)

- 7.5.15 Bean Transaction Timeouts (per minute)

- 7.5.16 MDB Messages (per minute)

- 7.5.17 Requests (per minute)

- 7.5.18 Request Processing Time (ms)

- 7.5.19 Active Sessions

- 7.5.20 Work Manager Pending Requests

- 7.5.21 Work Manager Requests (per minute)

- 7.6 Servlet/JSP Metrics

- 7.6.1 Reloads (per minute)

- 7.6.2 Requests (per minute)

- 7.6.3 Request Processing Time (ms)

- 7.7 Web Module Metrics

- 7.7.1 Requests (per minute)

- 7.7.2 Request Processing Time (ms)

- 7.7.3 Active Sessions

- 7.8 Events Handler

- 7.8.1 Average Events Execution Time (ms)

- 7.8.2 Completed Events Executions

- 7.8.3 Maximum Events Execution Time (ms)

- 7.8.4 Minimum Events Execution Time (ms)

- 7.9 Java JEE Web Service Endpoints

- 7.9.1 Dispatch Time Total

- 7.9.2 Execution Time Total

- 7.9.3 Invocation Count

- 7.9.4 Response Count

- 7.9.5 Response Error Count

- 7.9.6 Response Time Total

- 7.10 JMS Queue

- 7.10.1 Average Processing Time (ms)

- 7.10.2 Number of Processed Messages

- 7.10.3 Maximum Processing Time (ms)

- 7.10.4 Minimum processing Time (ms)

- 7.11 MDS Metrics

- 7.11.1 Metadata Object Gets Per Second

- 7.11.2 Metadata Object Get Processing Time (seconds)

- 7.11.3 IOs Per Document Get

- 7.11.4 IOs Per MO Content Get

- 7.11.5 IOs Per Metadata Object Get

- 7.11.6 Metadata Updates Per Second

- 7.11.7 Metadata Update Processing Time (seconds)

- 7.12 Executions and Messages

- 7.12.1 Total Adapter Executions

- 7.12.2 Total Events Handler Executions

- 7.12.3 Total JMS Messages

- 7.13 SPML Web Services

- 7.13.1 Average Response Time (ms)

- 7.13.2 Incoming Calls

- 7.14 Response

- 7.14.1 Status

8 Oracle BI Instance

- 8.1 Oracle BI PS Requests Rate

- 8.1.1 Active Sessions

- 8.1.2 Bad Requests

- 8.1.3 Completed Requests

- 8.1.4 Completed Requests/sec

- 8.1.5 Current Requests

- 8.1.6 Failed Requests

- 8.1.7 GET Requests Throughput

- 8.1.8 GET Requests

- 8.1.9 GET/POST Requests Throughput

- 8.1.10 GET/POST Requests

- 8.1.11 Long Requests

- 8.1.12 Peak Requests

- 8.1.13 POST Requests Throughput

- 8.1.14 POST Requests

- 8.1.15 SOAP Requests Throughput

- 8.1.16 SOAP Requests

- 8.2 Oracle BI PS Aggregation

- 8.2.1 Active sessions

- 8.2.2 Completed Requests/sec

- 8.2.3 Current Requests

- 8.2.4 Failed Requests

- 8.2.5 GET/POST Throughput

- 8.2.6 SOAP Throughput

- 8.3 Oracle BI Aggregation

- 8.3.1 Avg Query Elapsed Time

- 8.3.2 Queries/sec

- 8.3.3 Total sessions

- 8.4 Oracle BI Data Cache

- 8.4.1 Hit Ratio as %

- 8.4.2 Hits/sec

- 8.4.3 Qualified queries misses / second

- 8.4.4 Unqualified queries misses / second

- 8.5 Oracle BI DB Connection Pool

- 8.5.1 Accumulated Opened Connections

- 8.5.2 Accumulated Requests

- 8.5.3 Accumulated Stolen Connections

- 8.5.4 Average Queued Requests

- 8.5.5 Average Queued Time (ms)

- 8.5.6 Avg. Opened Connections/sec

- 8.5.7 Avg. Request/sec

- 8.5.8 Avg. Stolen Connections/sec

- 8.5.9 Capacity

- 8.5.10 Current Busy Connection Count

- 8.5.11 Current Connection Count

- 8.5.12 Current Queued Requests

- 8.5.13 Current Queued Time (ms)

- 8.5.14 Lowest Queued Requests

- 8.5.15 Lowest Queued Time (ms)

- 8.5.16 Peak Busy Connection Count

- 8.5.17 Peak Connection Count

- 8.5.18 Peak Queued Requests

- 8.5.19 Peak Queued Time (ms)

- 8.5.20 Producer ID of the Oldest Queued Request

- 8.5.21 Request ID of the Oldest Queued Request

- 8.6 Oracle BI General

- 8.6.1 Active Execute Requests

- 8.6.2 Active Fetch Requests

- 8.6.3 Active File Handles

- 8.6.4 Active Initblock Executions

- 8.6.5 Active Logins

- 8.6.6 Active Prepare Requests

- 8.6.7 Avg. Failed Logins Elapsed Time

- 8.6.8 Avg. Initblock Executions Elapsed Time

- 8.6.9 Avg. query elapsed time

- 8.6.10 Avg. Succeeded Logins Elapsed Time

- 8.6.11 Busy File Handles

- 8.6.12 File Handle Waiters

- 8.6.13 Free File Handles

- 8.6.14 Max. Initblock Execution Elapsed Time

- 8.6.15 Max File Handles

- 8.6.16 New Execute Requests

- 8.6.17 New Fetch Requests

- 8.6.18 New Initblock Executions

- 8.6.19 New Logins

- 8.6.20 New Prepare Requests

- 8.6.21 New Requests

- 8.6.22 Queries/sec

- 8.6.23 Succeeded Initblock Execution Ratio as %

- 8.6.24 Succeeded Logins Ratio as %

- 8.6.25 Total sessions

- 8.7 Oracle BI Generic Cache

- 8.7.1 Average hits / second

- 8.7.2 Average misses / second

- 8.7.3 Average new entries / second

- 8.7.4 Average replacements / second

- 8.7.5 Average requests / second

- 8.7.6 Capacity

- 8.7.7 Total requests

- 8.7.8 Utilization ratio as %

- 8.8 Oracle BI LDAP Authentication

- 8.8.1 Active LDAP Requests

- 8.8.2 Avg. Failed LDAP Requests Elapsed Time

- 8.8.3 Avg. Succeeded LDAP Requests Elapsed Time

- 8.8.4 LDAP Requests Cache Hit Ratio as %

- 8.8.5 New Impersonated LDAP Requests

- 8.8.6 New LDAP Requests

- 8.8.7 Succeeded LDAP Requests Ratio as %

- 8.9 Oracle BI Physical DB

- 8.9.1 Active Executes

- 8.9.2 Active Fetches

- 8.9.3 Active Prepares

- 8.9.4 Avg. query request response time

- 8.9.5 Failed Queries/sec

- 8.9.6 KiloBytes/sec

- 8.9.7 New Executes

- 8.9.8 New Fetches

- 8.9.9 New Prepares

- 8.9.10 Queries/sec

- 8.9.11 Rows/sec

- 8.10 Oracle BI PS Caches

- 8.10.1 Cache Hits

- 8.10.2 Cache Misses

- 8.10.3 Cache Stale

- 8.10.4 Cleanups

- 8.10.5 Current Entries

- 8.10.6 Peak Entries

- 8.11 Oracle BI PS Catalog Access

- 8.11.1 Attribute Retrievals

- 8.11.2 Create Folders

- 8.11.3 Create Links

- 8.11.4 Delete Items

- 8.11.5 Read Objects

- 8.11.6 Searches

- 8.11.7 Write Objects

- 8.11.8 Write Objects Successfully

- 8.12 Oracle BI PS Catalog Attribute Cache

- 8.12.1 Cache Hits

- 8.12.2 Cache Misses

- 8.12.3 Cache Stale Misses

- 8.12.4 Current Cache Entries

- 8.12.5 Peak Cache Entries

- 8.13 Oracle BI PS Chart Engine

- 8.13.1 Cache Hits

- 8.13.2 Charts Submitted/sec

- 8.13.3 Current Cached Charts

- 8.13.4 Current Charts Queued

- 8.13.5 Current Running Charts

- 8.13.6 Peak Cached Charts

- 8.13.7 Peak Charts Queued

- 8.13.8 Peak Running Charts

- 8.13.9 Total Charts Rejected

- 8.13.10 Total Charts Submitted

- 8.14 Oracle BI PS Connection Pool

- 8.14.1 Current Authentications

- 8.14.2 Current Open Connections

- 8.14.3 New Connections/sec

- 8.14.4 Peak Authentications

- 8.14.5 Peak Open Connections

- 8.14.6 Total Connections

- 8.14.7 Total Failed

- 8.14.8 Total Rejected

- 8.15 Oracle BI PS DirectorySearches

- 8.15.1 Total Search Start Requests

- 8.15.2 Total Search Stop Requests

- 8.15.3 Total Searches Started

- 8.15.4 Total Searches Stopped

- 8.16 Oracle BI PS DXE

- 8.16.1 Total Actual Aggregate Queries Compiled

- 8.16.2 Total Actual Cube Queries Compiled

- 8.16.3 Total Actual Expression Queries Compiled

- 8.16.4 Total Actual Presort Cube Queries Compiled

- 8.16.5 Total Actual Presort Table Queries Compiled

- 8.16.6 Total Actual Regular Queries Compiled

- 8.16.7 Total Actual Union Queries Compiled

- 8.16.8 Total Input Aggregate Query Requests

- 8.16.9 Total Input Cube Query Requests

- 8.16.10 Total Input Regular Query Requests

- 8.16.11 Total Input Union Query Requests

- 8.16.12 Total Order By Requests

- 8.16.13 Total Order By Requests Optimized Away

- 8.16.14 Total Query Requests

- 8.17 Oracle BI PS File Accesses

- 8.17.1 Current Open Files

- 8.17.2 Peak Open File

- 8.17.3 Total Files

- 8.17.4 Total Files/sec

- 8.18 Oracle BI PS HTTP Socket Pool

- 8.18.1 Total Closed At Reuse

- 8.18.2 Total Closed Exception

- 8.18.3 Total Closed First Read

- 8.18.4 Total Closed HTTP

- 8.18.5 Total Closed Outstanding

- 8.18.6 Total Closed Timedout

- 8.18.7 Total Closed Unknown

- 8.18.8 Total Endpoints

- 8.18.9 Total New sockets

- 8.18.10 Total Reused

- 8.19 Oracle BI PS JavaHost Proxy Requests

- 8.19.1 Requests to Generate Briefing Books

- 8.19.2 Requests to Generate PDFs

- 8.19.3 Requests to Generate Powerpoints

- 8.20 Oracle BI PS Metadata

- 8.20.1 Current Subject Areas

- 8.20.2 Peak Subject Areas

- 8.20.3 Subject Area Loads/sec

- 8.20.4 Total Subject Area Loads

- 8.21 Oracle BI PS Query Cache

- 8.21.1 Cache Clean Ups/sec

- 8.21.2 Cache Hits/sec

- 8.21.3 Canceled Queries/sec

- 8.21.4 Current Cache Entries

- 8.21.5 Current Query Preps

- 8.21.6 Current Query Preps Cache Size

- 8.21.7 Current Queued Immediate Queries

- 8.21.8 Current Queued Queries

- 8.21.9 Current Running Immediate Queries

- 8.21.10 Current Running Queries

- 8.21.11 Errored Queries/sec

- 8.21.12 New Queries/sec

- 8.21.13 Peak Cache Entries

- 8.21.14 Peak Query Preps

- 8.21.15 Peak Query Preps Cache Size

- 8.21.16 Peak Queued Immediate Queries

- 8.21.17 Peak Queued Queries

- 8.21.18 Peak Running Immediate Queries

- 8.21.19 Peak Running Queries

- 8.21.20 Proactive Cache Clean Ups/sec

- 8.21.21 Query Piggybacks/sec

- 8.21.22 Query Preps Errors/sec

- 8.21.23 Query Preps/sec

- 8.21.24 Successful Queries/sec

- 8.21.25 Total Cache Clean Ups

- 8.21.26 Total Cache Hits

- 8.21.27 Total Canceled Queries

- 8.21.28 Total Errored Queries

- 8.21.29 Total Proactive Cache Clean Ups

- 8.21.30 Total Query Attempts

- 8.21.31 Total Query Piggybacks

- 8.21.32 Total Query Prep Cache Hits

- 8.21.33 Total Query Prep Cache Misses

- 8.21.34 Total Query Preps

- 8.21.35 Total Query Preps Errors

- 8.21.36 Total Successful Queries

- 8.22 Oracle BI PS Request Processor

- 8.22.1 Bad Requests

- 8.22.2 Completed Requests

- 8.22.3 Completed Requests/sec

- 8.22.4 Current Requests

- 8.22.5 Failed Requests

- 8.22.6 GET Requests

- 8.22.7 Long Requests

- 8.22.8 Peak Requests

- 8.22.9 POST Requests

- 8.22.10 SOAP Requests

- 8.23 Oracle BI PS Sessions

- 8.23.1 Active Sessions

- 8.23.2 Current Embryonic Sessions

- 8.23.3 Current Sessions

- 8.23.4 Failed Logins/sec

- 8.23.5 New Logins/sec

- 8.23.6 New Sessions/sec

- 8.23.7 Peak Active Sessions

- 8.23.8 Peak Embryonic Sessions

- 8.23.9 Peak Logged In

- 8.23.10 Peak Sessions

- 8.23.11 Sessions Logged In

- 8.23.12 Total Failed Logins

- 8.23.13 Total Lifetime Sessions

- 8.23.14 Total Logins

- 8.24 Oracle BI PS Sockets

- 8.24.1 Total Close Requests

- 8.24.2 Total Closed

- 8.24.3 Total Open Requests

- 8.24.4 Total Opened

- 8.25 Oracle BI PS Thread Pools

- 8.25.1 Current Jobs Queued

- 8.25.2 Current Jobs Running

- 8.25.3 Current Threads

- 8.25.4 Peak Jobs Queued

- 8.25.5 Peak Jobs Running

- 8.25.6 Peak Threads

- 8.25.7 Total Jobs Completed

- 8.25.8 Total Jobs Submitted

- 8.25.9 Total Jobs Unfinished

- 8.26 Oracle BI PS Threads

- 8.26.1 Total Close Requests

- 8.26.2 Total Closed

- 8.26.3 Total Created

- 8.26.4 Total Open Requests

- 8.27 Oracle BI PS User Population Searches

- 8.27.1 UserPopulationAPI.SearchByGUID

- 8.27.2 UserPopulationAPI.SearchByName

- 8.27.3 UserPopulationAPI.SearchByPattern

- 8.28 Oracle BI PS XML Document Caches

- 8.28.1 Current Disk Entries

- 8.28.2 Current Disk Usage (KB)

- 8.28.3 Current Memory Entries

- 8.28.4 Disk Added (KB)

- 8.28.5 Disk Cache Hits

- 8.28.6 Disk Cache Misses

- 8.28.7 Disk Deleted (KB)

- 8.28.8 Invalid Requests

- 8.28.9 Memory Cache Hits

- 8.28.10 Peak Memory Entries

- 8.28.11 Total Memory Entries

- 8.29 Oracle BI PS XML Validator

- 8.29.1 Current Validations

- 8.29.2 Current Validators in Pool

- 8.29.3 Peak Validations

- 8.29.4 Peak Validators in Pool

- 8.29.5 Total Validations

- 8.29.6 Validations/sec

- 8.30 Oracle BI Thread Pool

- 8.30.1 Accumulated Requests

- 8.30.2 Average Execution Time (ms)

- 8.30.3 Average Queued Requests

- 8.30.4 Average Queued Time (ms)

- 8.30.5 Avg. Request/sec

- 8.30.6 Capacity

- 8.30.7 Current Busy Thread Count

- 8.30.8 Current Execution Time (ms)

- 8.30.9 Current Queued Requests

- 8.30.10 Current Queued Time (ms)

- 8.30.11 Current Thread Count

- 8.30.12 Lowest Execution Time (ms)

- 8.30.13 Lowest Queued Requests

- 8.30.14 Lowest Queued Time (ms)

- 8.30.15 Maximum Stack Size (bytes)

- 8.30.16 Peak Busy Thread Count

- 8.30.17 Peak Execution Time (ms)

- 8.30.18 Peak Queued Requests

- 8.30.19 Peak Queued Time (ms)

- 8.30.20 Peak Thread Count

- 8.31 Weblogic BI Metrics By Server

- 8.31.1 Weblogic BI Action Framework Metrics

- 8.31.2 Requests (per minute)

- 8.31.3 Request Processing Time (ms)

- 8.32 Weblogic BI Analytics Metrics

- 8.32.1 Requests (per minute)

- 8.32.2 Request Processing Time (ms)

- 8.32.3 Active Sessions

- 8.33 Weblogic BI SOA Metrics

- 8.33.1 Requests (per minute)

- 8.33.2 Request Processing Time (ms)

- 8.34 Weblogic Server Metrics

- 8.34.1 CPU Usage Percentage

- 8.34.2 Heap Used (MB)

- 8.34.3 Requests (per minute)

- 8.34.4 Request Processing Time (ms)

- 8.34.5 Active Sessions

9 Glassfish Metrics

- 9.1 EJB Cache Metrics by Server

- 9.1.1 Cache Hits (per minute)

- 9.1.2 Cache Misses (per minute)

- 9.1.3 Cache Access Attempts (per minute)

- 9.1.4 Cache Hits (%)

- 9.2 EJB Pool Metrics By Server

- 9.2.1 Beans in Pool

- 9.2.2 Threads Waiting

- 9.3 JMS Connection Pool Metrics by Server

- 9.3.1 Connections in Use

- 9.3.2 Connections Pending

- 9.3.3 Connections Acquired (per minute)

- 9.4 JTA Metrics

- 9.4.1 Active JTA Transactions

- 9.4.2 Committed JTA Transactions (per minute)

- 9.4.3 JTA Transaction Rollbacks (per minute)

- 9.5 JVM Metrics

- 9.5.1 Heap Usage (MB)

- 9.5.2 Java Vendor

- 9.5.3 Java Version

- 9.5.4 CPU Usage (%)

- 9.5.5 Heap Usage (%)

- 9.6 JVM Class Loading

- 9.6.1 JVM Class Loading - Classes Currently Loaded

- 9.7 JVM Compilation Metrics

- 9.7.1 JVM Compilation - Compilation Time (since startup) (ms)

- 9.8 JVM Garbage Collectors Metrics

- 9.8.1 Garbage Collector - Invocations (per min)

- 9.8.2 Garbage Collector - Invocation Time (ms)

- 9.8.3 Garbage Collector - Old Heap Percent Free after GC (%)

- 9.8.4 Garbage Collector - Old Heap size after GC (MB)

- 9.8.5 Garbage Collector - Percent Time spent (%)

- 9.9 JVM Memory Pools Metrics

- 9.9.1 Name

- 9.9.2 Type

- 9.9.3 Memory Pool - Current Usage (MB)

- 9.10 JVM Memory Usage Metrics

- 9.10.1 JVM Memory - Heap Memory Usage (MB)

- 9.10.2 JVM Memory - Non-Heap Memory Usage (MB)

- 9.10.3 JVM Memory - Objects Pending Finalization

- 9.11 JVM Runtime Metrics

- 9.11.1 VM Name

- 9.11.2 VM Version

- 9.12 JVM Threads

- 9.12.1 JVM Threads - Active Daemon Threads

- 9.12.2 JVM Threads - Deadlocked Threads

- 9.12.3 JVM Threads - Peak Threads

- 9.12.4 JVM Threads - Active Threads

- 9.13 Module Metrics by Server

- 9.13.1 Active Sessions

- 9.14 Response

- 9.14.1 Status

- 9.15 Server Metrics

- 9.15.1 State

- 9.15.2 Start Time

- 9.16 Server Datasource Metrics

- 9.16.1 Connections in Use

- 9.16.2 Connections Created (per minute)

- 9.16.3 Connections Acquired (per minute)

- 9.17 Server Servlet Metrics

- 9.17.1 Request Processing Time (ms)

- 9.17.2 Requests (per minute)

10 Oracle Essbase Server Metrics

- 10.1 Server Information

- 10.1.1 Connected Users

- 10.1.2 Running Apps

- 10.1.3 Unaccessed Apps

- 10.1.4 Response (ms)

- 10.2 Resource Usage

- 10.2.1 CPU Usage (%)

- 10.2.2 Memory Usage (MB)

- 10.2.3 Memory Usage (%)

- 10.3 Response

- 10.3.1 Response - Status

11 Oracle Essbase Applications

- 11.1 Application Information

- 11.1.1 Response (ms)

- 11.1.2 Memory Usage (MB)

- 11.1.3 Threads

- 11.2 Response

- 11.2.1 Response - Status

12 Oracle Coherence Cache

- 12.1 Response

- 12.1.1 Cache Status

- 12.2 Aggregate Storage Manager Metrics

- 12.2.1 Aggregate Events Dispatched

- 12.2.2 Aggregate Events Dispatched Per Minute

- 12.2.3 Aggregate Evictions

- 12.2.4 Aggregate Evictions Per Minute

- 12.2.5 Aggregate Inserts

- 12.2.6 Aggregate Inserts Per Minute

- 12.2.7 Aggregate Listener Filters

- 12.2.8 Aggregate Listener Keys

- 12.2.9 Aggregate Locks Granted

- 12.2.10 Aggregate Locks Pending

- 12.2.11 Aggregate Removes

- 12.2.12 Aggregate Removes Per Minute

- 12.3 Aggregate Cache Usage Metrics (Coherence version 3.4)

- 12.3.1 Aggregate Puts

- 12.3.2 Aggregate Puts Per Minute

- 12.3.3 Aggregate Puts Time (ms) Per Minute

- 12.3.4 Aggregate Gets

- 12.3.5 Aggregate Gets Per Minute

- 12.3.6 Aggregate Gets Time (ms) Per Minute

- 12.3.7 Aggregate Hits

- 12.3.8 Aggregate Hits Per Minute

- 12.3.9 Aggregate Hits Time (ms) Per Minute

- 12.3.10 Aggregate Misses

- 12.3.11 Aggregate Misses Per Minute

- 12.3.12 Aggregate Misses Time (ms) Per Minute

- 12.3.13 Aggregate Writes

- 12.3.14 Aggregate Writes Per Minute

- 12.3.15 Aggregate Write Time (ms) Per Minute

- 12.3.16 Aggregate Reads

- 12.3.17 Aggregate Reads Per Minute

- 12.3.18 Aggregate Read Time (ms) Per Minute

- 12.3.19 Aggregate Failures Per Minute

- 12.3.20 Aggregate Queue Size

- 12.3.21 Hit Probability

- 12.3.22 Hits to Gets Ratio (%)

- 12.3.23 Average Time Per Get (ms)

- 12.3.24 Average Time Per Get-Hit (ms)

- 12.3.25 Average Time Per Get-Miss (ms)

- 12.3.26 Average Time Per Put (ms)

- 12.3.27 Average Time Per Read (ms)

- 12.3.28 Average Time Per Write (ms)

- 12.4 Aggregate Cache Usage Metrics (Coherence version 3.4.2 - 3.7.1)

- 12.4.1 Aggregate Puts

- 12.4.2 Aggregate Puts Per Minute

- 12.4.3 Aggregate Puts Time (ms) Per Minute

- 12.4.4 Aggregate Gets

- 12.4.5 Aggregate Gets Per Minute

- 12.4.6 Aggregate Gets Time (ms) Per Minute

- 12.4.7 Aggregate Hits

- 12.4.8 Aggregate Hits Per Minute

- 12.4.9 Aggregate Hits Time (ms) Per Minute

- 12.4.10 Aggregate Misses

- 12.4.11 Aggregate Misses Per Minute

- 12.4.12 Aggregate Misses Time (ms) Per Minute

- 12.4.13 Aggregate Writes

- 12.4.14 Aggregate Writes Per Minute

- 12.4.15 Aggregate Write Time (ms) Per Minute

- 12.4.16 Aggregate Reads

- 12.4.17 Aggregate Reads Per Minute

- 12.4.18 Aggregate Read Time (ms) Per Minute

- 12.4.19 Aggregate Failures Per Minute

- 12.4.20 Aggregate Queue Size

- 12.4.21 Aggregate Prunes

- 12.4.22 Aggregate Prunes Per Minute

- 12.4.23 Aggregate Prune Time (ms) Per Minute

- 12.4.24 Hit Probability

- 12.4.25 Hits to Gets Ratio (%)

- 12.4.26 Average Time Per Get (ms)

- 12.4.27 Average Time Per Get-Hit (ms)

- 12.4.28 Average Time Per Get-Miss (ms)

- 12.4.29 Average Time Per Put (ms)

- 12.4.30 Average Time Per Read (ms)

- 12.4.31 Average Time Per Write (ms)

- 12.5 Aggregate Cache Size Metrics

- 12.5.1 Aggregate Units

- 12.5.2 Unit Factor

- 12.5.3 Aggregate Cache Objects

- 12.5.4 Aggregate Memory Usage in Bytes (assuming BINARY Calculator)

- 12.5.5 Aggregate Memory Usage in MB (assuming BINARY Calculator)

- 12.5.6 Average Object Size in Bytes

- 12.6 Aggregate Query Optimization Metrics (Coherence version 3.7)

- 12.6.1 Maximum Query Duration (ms)

- 12.6.2 Aggregate Non Optimized Queries Executed Per Minute

- 12.6.3 Average Non Optimized Query Execution Time (ms)

- 12.6.4 Aggregate Non Optimized Query Time (ms) Per Minute

- 12.6.5 Aggregate Optimized Queries Executed Per Minute

- 12.6.6 Average Optimized Query Execution Time (ms)

- 12.6.7 Aggregate Optimized Query Time (ms) Per Minute

- 12.7 Aggregate Query Optimization Metrics (Coherence version 3.7.1)

- 12.7.1 Maximum Query Duration (ms)

- 12.7.2 Aggregate Non Optimized Queries Executed Per Minute

- 12.7.3 Average Non Optimized Query Execution Time (ms)

- 12.7.4 Aggregate Non Optimized Query Time (ms) Per Minute

- 12.7.5 Aggregate Optimized Queries Executed Per Minute

- 12.7.6 Average Optimized Query Execution Time (ms)

- 12.7.7 Aggregate Optimized Query Time (ms) Per Minute

- 12.7.8 Aggregate Query Contentions Per Minute

13 Oracle Coherence Cluster

- 13.1 Response

- 13.1.1 Cluster Status

- 13.2 Nodes Replenish and Entity Discovery Alert Metric

- 13.2.1 Cluster Size Change (For Node Process Replenish)

- 13.2.2 Cluster Size Change (For Node Entity Addition)

- 13.3 Departed Coherence Cluster Members

- 13.3.1 Recently Departed Members

- 13.4 Aggregate Node Metrics

- 13.4.1 Number of Nodes

- 13.4.2 Number of Nodes Departed

- 13.4.3 Average Publisher Success Rate (%)

- 13.4.4 Average Receiver Success Rate (%)

- 13.4.5 Aggregate Memory Consumed (MB)

- 13.4.6 Aggregate Memory Available (MB)

- 13.4.7 Aggregate Send Success Rate Per Minute (%)

- 13.4.8 Aggregate Receive Success Rate Per Minute (%)

- 13.5 Aggregate Cache Metrics

- 13.5.1 Number of Caches

- 13.5.2 Aggregate Number of Cache Objects

- 13.6 Aggregate Service Storage Enabled Nodes Alert Metric

- 13.6.1 Coherence Service Name

- 13.6.2 Storage Enabled Nodes

- 13.6.3 Storage Enabled Nodes Size Change (To Replenish Storage Nodes)

- 13.7 Aggregate Service Requests and Tasks

- 13.7.1 Service Name

- 13.7.2 Aggregate Requests Per Minute

- 13.7.3 Aggregate Pending Requests

- 13.7.4 Maximum Pending Request Time (ms)

- 13.7.5 Aggregate Timed-Out Requests Per Minute

- 13.7.6 Aggregate Tasks Executed Per Minute

- 13.7.7 Aggregate Tasks Backlog

- 13.7.8 Aggregate Timed-Out Tasks Per Minute

- 13.7.9 Aggregate Hung Tasks

- 13.7.10 Average Request Duration (ms)

- 13.7.11 Maximum Request Duration (ms)

- 13.7.12 Average Task Duration (ms)

- 13.7.13 Maximum Hung Task Duration (ms)

- 13.7.14 Maximum Task Backlog

- 13.7.15 Number of Nodes

- 13.7.16 Storage Enabled Nodes

- 13.8 Aggregate Service Partitions and Threads

- 13.8.1 Coherence Service Name

- 13.8.2 Aggregate Partitions Endangered

- 13.8.3 Aggregate Partitions Unbalanced

- 13.8.4 Aggregate Partitions Vulnerable

- 13.8.5 Aggregate Abandoned Threads

- 13.8.6 Average Active Threads

- 13.8.7 Aggregate Idle Threads

- 13.8.8 Aggregate Threads

- 13.9 Aggregate Transaction Manager Metrics

- 13.9.1 Service Name

- 13.9.2 Aggregate Commit Time (ms) Per Minute

- 13.9.3 Aggregate Timeout Time (ms) Per Minute

- 13.9.4 Aggregate Active Transactions Per Minute

- 13.9.5 Aggregate Transactions Committed Per Minute

- 13.9.6 Aggregate Transactions Recovered Per Minute

- 13.9.7 Aggregate Transactions Rolled Back Per Minute

- 13.9.8 Aggregate Transaction Duration (ms) Per Minute

- 13.10 Aggregate HTTP Session (Web) Metrics (Coherence version 3.4.2 – 3.5)

- 13.10.1 Web Application ID

- 13.10.2 Aggregate Attributes in Local Session

- 13.10.3 Aggregate Sessions in Local Session Cache

- 13.10.4 Aggregate Session Cache Updates Per Minute

- 13.10.5 Aggregate Overflow Cache Updates Per Minute

- 13.11 Aggregate HTTP Session (Web) Metrics (Coherence version 3.6 – 3.7.1)

- 13.11.1 Web Application ID

- 13.11.2 Aggregate Attributes in Local Session cache

- 13.11.3 Aggregate Sessions in Local Session Cache

- 13.11.4 Aggregate Session Cache Updates Per Minute

- 13.11.5 Aggregate Overflow Cache Updates Per Minute

- 13.11.6 Average Reap Duration (ms)

- 13.11.7 Average Reaped Sessions

- 13.12 Aggregate Weblogic HTTP Session (Web) Metrics

- 13.12.1 Web Application ID

- 13.12.2 Aggregate Attributes in Local Session cache

- 13.12.3 Aggregate Sessions in Local Session Cache

- 13.12.4 Aggregate Session Cache Updates Per Minute

- 13.12.5 Aggregate Overflow Cache Updates Per Minute

- 13.12.6 Average Reap Duration (ms)

- 13.12.7 Average Reaped Sessions

- 13.13 Cache Entities Discovery Alert Metric

- 13.13.1 Change in Number of Caches

14 Oracle Coherence Node

- 14.1 Response

- 14.1.1 Node Status

- 14.2 Storage Manager

- 14.2.1 Total Events Dispatched

- 14.2.2 Total Events Dispatched Per Minute

- 14.2.3 Total Evictions

- 14.2.4 Total Inserts

- 14.2.5 Total Inserts Per Minute

- 14.2.6 Listener Filters

- 14.2.7 Listener Keys

- 14.2.8 Total Listener Registrations

- 14.2.9 Locks Granted

- 14.2.10 Total Removes

- 14.2.11 Total Removes Per Minute

- 14.3 Cache Usage (Coherence version 3.4)

- 14.3.1 Total Puts

- 14.3.2 Total Puts Per Minute

- 14.3.3 Total Puts Time (ms) Per Minute

- 14.3.4 Total Gets

- 14.3.5 Total Gets Per Minute

- 14.3.6 Total Gets Time (ms) Per Minute

- 14.3.7 Total Hits

- 14.3.8 Total Hits Per Minute

- 14.3.9 Total Hits Time (ms) Per Minute

- 14.3.10 Total Misses

- 14.3.11 Total Misses Per Minute

- 14.3.12 Total Misses Time (ms) Per Minute

- 14.3.13 Total Writes

- 14.3.14 Total Writes Per Minute

- 14.3.15 Total Writes Time (ms) Per Minute

- 14.3.16 Total Reads

- 14.3.17 Total Reads Per Minute

- 14.3.18 Total Reads Time (ms) Per Minute

- 14.3.19 Total Failures Per Minute

- 14.3.20 Queue Size

- 14.3.21 Hit Probability

- 14.3.22 Hits to Gets Ratio (%)

- 14.3.23 Average Time Per Get (ms)

- 14.3.24 Average Time Per Get-Hit (ms)

- 14.3.25 Average Time Per Get-Miss (ms)

- 14.3.26 Average Time Per Put (ms)

- 14.3.27 Average Time Per Read (ms)

- 14.3.28 Average Time Per Write (ms)

- 14.4 Cache Usage (Coherence version 3.4.2 - 3.7.1)

- 14.4.1 Total Puts

- 14.4.2 Total Puts Per Minute

- 14.4.3 Total Puts Time (ms) Per Minute

- 14.4.4 Total Gets

- 14.4.5 Total Gets Per Minute

- 14.4.6 Total Gets Time (ms) Per Minute

- 14.4.7 Total Hits

- 14.4.8 Total Hits Per Minute

- 14.4.9 Total Hits Time (ms) Per Minute

- 14.4.10 Total Misses

- 14.4.11 Total Misses Per Minute

- 14.4.12 Total Misses Time (ms) Per Minute

- 14.4.13 Total Writes

- 14.4.14 Total Writes Per Minute

- 14.4.15 Total Writes Time (ms) Per Minute

- 14.4.16 Total Reads

- 14.4.17 Total Reads Per Minute

- 14.4.18 Total Reads Time (ms) Per Minute

- 14.4.19 Total Failures Per Minute

- 14.4.20 Queue Size

- 14.4.21 Total Prunes

- 14.4.22 Total Prunes Per Minute

- 14.4.23 Total Prune Time (ms) Per Minute

- 14.4.24 Hit Probability

- 14.4.25 Hits to Gets Ratio (%)

- 14.4.26 Average Time Per Get (ms)

- 14.4.27 Average Time Per Get-Hit (ms)

- 14.4.28 Average Time Per Get-Miss (ms)

- 14.4.29 Average Time Per Put (ms)

- 14.4.30 Average Time Per Read (ms)

- 14.4.31 Average Time Per Write (ms)

- 14.5 Cache Size

- 14.5.1 Cache Name

- 14.5.2 Service Name

- 14.5.3 Cache Tier

- 14.5.4 Cache Loader

- 14.5.5 Units

- 14.5.6 Unit Factor

- 14.5.7 Cache Objects

- 14.6 Query Optimization (Coherence version 3.7)

- 14.6.1 Cache Name

- 14.6.2 Service Name

- 14.6.3 Max Query Description

- 14.6.4 Max Query Duration (ms)

- 14.6.5 Total Non Optimized Queries Executed Per Minute

- 14.6.6 Average Non Optimized Query Execution Time (ms)

- 14.6.7 Total Non Optimized Query Time (ms) Per Minute

- 14.6.8 Total Optimized Queries Executed Per Minute

- 14.6.9 Average Optimized Query Execution Time (ms)

- 14.6.10 Total Optimized Query Time (ms) Per Minute

- 14.7 Service Requests and Tasks

- 14.7.1 Service Name

- 14.7.2 Service Name Backups For Cache Storage

- 14.7.3 Total Requests Per Minute

- 14.7.4 Pending Requests

- 14.7.5 Pending Duration (ms)

- 14.7.6 Total Timed-Out Requests Per Minute

- 14.7.7 Total Tasks Executed Per Minute

- 14.7.8 Total Tasks Backlog

- 14.7.9 Total Tasks Timed-Out Per Minute

- 14.7.10 Total Hung Tasks Per Minute

- 14.7.11 Average Request Duration (ms)

- 14.7.12 Maximum Request Duration (ms)

- 14.7.13 Storage Enabled Nodes

- 14.7.14 Average Task Duration (ms)

- 14.7.15 Maximum Hung Task Duration (ms)

- 14.7.16 HA Numeric Status

- 14.7.17 Maximum Task Backlog

- 14.7.18 Running

- 14.7.19 HA Status

- 14.7.20 HA Numeric Status

- 14.8 Service Partitions and Threads

- 14.8.1 Service Name

- 14.8.2 Owned Partitions Backup

- 14.8.3 Owned Partitions Primary

- 14.8.4 Partitions Endangered

- 14.8.5 Partitions Unbalanced

- 14.8.6 Partitions Vulnerable

- 14.8.7 Average Active Threads

- 14.8.8 Idle Threads

- 14.8.9 Threads

- 14.8.10 Threads Abandoned Per Minute

- 14.9 Heap Memory Usage

- 14.9.1 Heap Memory Initialized (bytes)

- 14.9.2 Heap Memory Max (bytes)

- 14.9.3 Heap Memory Used (bytes)

- 14.10 Garbage Collector

- 14.10.1 Name

- 14.10.2 Total Garbage Collections

- 14.10.3 Total Garbage Collections Per Minute

- 14.10.4 Total Garbage Collection Time (ms)

- 14.10.5 Total Collection Time (ms) Per Minute

- 14.10.6 Garbage Collector Start Time (ms)

- 14.10.7 Garbage Collector End Time (ms)

- 14.11 Garbage Collector Before GC

- 14.11.1 Name

- 14.11.2 Memory Usage Key Before GC

- 14.11.3 Memory Usage Key Before GC (bytes)

- 14.12 Garbage Collector After GC

- 14.12.1 Name

- 14.12.2 Memory Usage Key After GC

- 14.12.3 Memory Used After GC (bytes)

- 14.13 Memory Pool

- 14.13.1 Memory Pool Name

- 14.13.2 Memory Pool Heap Memory Initialized (bytes)

- 14.13.3 Memory Pool Heap Memory Max (bytes)

- 14.13.4 Memory Pool Heap Memory Used (bytes)

- 14.14 Node Process and Operating System

- 14.14.1 Free Physical Memory Size (MB)

- 14.14.2 Free Swap Space Size (MB)

- 14.14.3 Open File Descriptors

- 14.14.4 Total Process CPU Time (ms)

- 14.15 Node Process CPU Usage

- 14.15.1 CPU Usage (%)

- 14.16 Network Health Details

- 14.16.1 Publisher Success Rate (%)

- 14.16.2 Receiver Success Rate (%)

- 14.16.3 Total Packets Sent

- 14.16.4 Total Packets Sent Per Minute

- 14.16.5 Total Packets Resent

- 14.16.6 Total Packets Resent Per Minute

- 14.16.7 Send Success Rate Per Minute (%)

- 14.16.8 Total Packets Repeated

- 14.16.9 Total Packets Repeated Per Minute

- 14.16.10 Total Packets Received

- 14.16.11 Total Packets Received Per Minute

- 14.16.12 Receive Success Rate Per Minute (%)

- 14.17 Node Performance Details

- 14.17.1 Packet Delivery Efficiency

- 14.17.2 Total Packets Bundled Per Minute

- 14.17.3 Total Packets Resent Per Minute

- 14.17.4 Total Packets Resent Excess Per Minute

- 14.17.5 Send Queue Size

- 14.17.6 Total TCP Ring Failures Per Minute

- 14.17.7 Weakest Channel

- 14.17.8 Node Memory Available (MB)

- 14.17.9 Node Memory Used (MB)

- 14.18 Aggregate Node Performance for All Caches

- 14.18.1 Aggregate Gets

- 14.18.2 Aggregate Puts

- 14.18.3 Aggregate Puts Per Minute

- 14.18.4 Aggregate Gets Per Minute

- 14.19 Flash Journal

- 14.19.1 Journal Files

- 14.19.2 Journal Binary Stores

- 14.19.3 Total Data Size (bytes)

- 14.19.4 Total File Size (bytes)

- 14.19.5 Journal Backlog

- 14.19.6 Backlog Size (bytes)

- 14.19.7 Total Pool Size (bytes)

- 14.20 RAM Journal

- 14.20.1 Journal Files

- 14.20.2 Journal Binary Stores

- 14.20.3 Total Data Size (bytes)

- 14.20.4 Total File Size (bytes)

- 14.21 Connection Details

- 14.21.1 Service Name

- 14.21.2 Connection UUID

- 14.21.3 Connection Time (ms)

- 14.21.4 Outgoing Queue Backlog (bytes)

- 14.21.5 Outgoing Message Queue Backlog

- 14.21.6 Total Bytes Received Per Minute

- 14.21.7 Total Bytes Sent Per Minute

- 14.21.8 Total Messages Received Per Minute

- 14.21.9 Total Messages Sent Per Minute

- 14.22 Proxy (Connection Manager) Details

- 14.22.1 Service Name

- 14.22.2 Connections

- 14.22.3 Outgoing Backlog (bytes)

- 14.22.4 Outgoing Messages Backlog

- 14.22.5 Total Bytes Sent Per Minute

- 14.22.6 Total Bytes Received Per Minute

- 14.22.7 Total Messages Sent Per Minute

- 14.22.8 Total Messages Received Per Minute

- 14.23 Transaction Manager

- 14.23.1 Service Name

- 14.23.2 Total Commit Duration (ms) Per Minute

- 14.23.3 Timeout Duration (ms) Per Minute

- 14.23.4 Total Active Transactions Per Minute

- 14.23.5 Total Committed Transactions Per Minute

- 14.23.6 Total Recovered Transactions Per Minute

- 14.23.7 Total Rolled Back Transactions Per Minute

- 14.23.8 Total Transaction Duration (ms) Per Minute

- 14.24 Messaging

- 14.24.1 Destination

- 14.24.2 Destination ID

- 14.24.3 Subscription

- 14.24.4 Subscription ID

- 14.24.5 Total Messages Acknowledged

- 14.24.6 Total Messages Received

- 14.25 Publishing Service

- 14.25.1 Publisher ID

- 14.25.2 Cache Name

- 14.25.3 Publisher Name

- 14.25.4 Consecutive Publishing Failures Per Minute

- 14.25.5 Last Publishing Duration

- 14.25.6 Maximum Publishing Duration

- 14.25.7 Minimum Publishing Duration

- 14.25.8 Publish Count Per Minute

- 14.25.9 Replicated Entries Per Minute

- 14.25.10 Replication Entry Candidates Per Minute

- 14.25.11 Publishing Service State

- 14.25.12 Publishing Duration Per Minute

- 14.26 HTTP Session (Web) Metrics (Coherence version 3.4.2 – 3.5)

- 14.26.1 Web Application ID

- 14.26.2 Attributes in Local Session Cache

- 14.26.3 Sessions in Local Session Cache

- 14.26.4 Average Size for Attribute Overflows (bytes)

- 14.26.5 Maximum Size for Attribute Overflow (bytes)

- 14.26.6 Total Overflow Cache Updates Per Minute

- 14.26.7 Session Average Lifetime (seconds)

- 14.26.8 Session Average Size (bytes)

- 14.26.9 Session Maximum Size (bytes)

- 14.26.10 Session Minimum Size (bytes)

- 14.26.11 Number of Sticky Sessions

- 14.26.12 Total Session Updates Per Minute

- 14.27 HTTP Session (Web) Metrics (Coherence version 3.6 – 3.7.1)

- 14.27.1 Web Application ID

- 14.27.2 Attributes in Local Session Cache

- 14.27.3 Sessions in Local Session Cache

- 14.27.4 Average Size for Attribute Overflows (bytes)

- 14.27.5 Maximum Size for Attribute Overflow (bytes)

- 14.27.6 Total Overflow Cache Updates Per Minute

- 14.27.7 Session Average Lifetime (seconds)

- 14.27.8 Session Average Size (bytes)

- 14.27.9 Session Maximum Size (bytes)

- 14.27.10 Session Minimum Size (bytes)

- 14.27.11 Number of Sticky Sessions

- 14.27.12 Total Session Updates Per Minute

- 14.27.13 Average Reap Duration (ms)

- 14.27.14 Maximum Reap Duration (ms)

- 14.27.15 Last Reap Duration (ms)

- 14.27.16 Average Reaped Sessions

- 14.27.17 Maximum Reaped Sessions

- 14.27.18 Sessions Reaped in Last Reap Cycle

- 14.27.19 Total Reaped Sessions

- 14.27.20 Last Reap Cycle

- 14.27.21 Next Reap Cycle

- 14.28 Weblogic HTTP Session (Web) Metrics

- 14.28.1 Web Application ID

- 14.28.2 Attributes in Local Session Cache

- 14.28.3 Sessions in Local Session Cache

- 14.28.4 Average Size for Attribute Overflows (bytes)

- 14.28.5 Maximum Size for Attribute Overflow (bytes)

- 14.28.6 Total Overflow Cache Updates Per Minute

- 14.28.7 Session Average Lifetime (seconds)

- 14.28.8 Session Average Size (bytes)

- 14.28.9 Session Maximum Size (bytes)

- 14.28.10 Session Minimum Size (bytes)

- 14.28.11 Number of Sticky Sessions

- 14.28.12 Total Session Updates Per Minute

- 14.28.13 Average Reap Duration (ms)

- 14.28.14 Maximum Reap Duration (ms)

- 14.28.15 Last Reap Duration (ms)

- 14.28.16 Average Reaped Sessions

- 14.28.17 Maximum Reaped Sessions

- 14.28.18 Sessions Reaped in Last Reap Cycle

- 14.28.19 Total Reaped Sessions

- 14.28.20 Last Reap Cycle

- 14.28.21 Next Reap Cycle

15 Oracle HTTP Server

- 15.1 mod_oc4j Destination Metrics

- 15.1.1 Percentage of Requests that Were Failures

- 15.2 mod_oc4j General Metrics

- 15.2.1 Percentage of Requests Resulted in Internal Errors

- 15.2.2 Percentage of Requests that Were Failures

- 15.3 mod_oc4j MountPt Metrics

- 15.3.1 Percentage of Requests that Were Failures

- 15.4 modplsql_HTTPResponseCodes Metrics

- 15.4.1 400sPercentage

- 15.4.2 500sPercentage

- 15.5 OHS Module Metrics

- 15.5.1 Request Handling Throughput, for a Module (requests per second)

- 15.5.2 Request Handling Time, for a Module (seconds)

- 15.5.3 Total Handled Requests for a Module

- 15.6 OHS Process Metrics

- 15.6.1 Heap Usage (MB)

- 15.7 OHS Response Code Metrics

- 15.7.1 HTTP 4xx Errors Throughput

- 15.7.2 HTTP 4xx Errors

- 15.7.3 HTTP 5xx Errors Throughput

- 15.7.4 HTTP 5xx errors

- 15.8 OHS Server Metrics

- 15.8.1 Active HTTP Connections

- 15.8.2 Active HTTP Requests

- 15.8.3 Busy Processes

- 15.8.4 Busy Threads

- 15.8.5 Busy Threads (%)

- 15.8.6 Connection Duration (seconds)

- 15.8.7 Error Rate (%)

- 15.8.8 Idle Threads

- 15.8.9 Idle Processes

- 15.8.10 Number of Threads

- 15.8.11 Percentage of Busy Processes

- 15.8.12 Request Processing Time (milliseconds)

- 15.8.13 Request Processing Time (seconds)

- 15.8.14 Request Throughput (requests per second)

- 15.8.15 Response Data Processed (KB per response)

- 15.8.16 Response Data Throughput (KB per second)

- 15.9 OHS Virtual Host Metrics

- 15.9.1 Active Requests for a Virtual Host

- 15.9.2 Request Processing Time for a Virtual Host (seconds)

- 15.9.3 Request Throughput for a Virtual Host (requests per second)

- 15.9.4 Response Data Processed For a Virtual Host (KB per response)

- 15.9.5 Response Data Throughput For a Virtual Host (KB per second)

- 15.9.6 Virtual Host Type

- 15.10 Oracle HTTP Server General Metrics

- 15.10.1 Start Time (ms since Epoch)

- 15.11 Resource Usage

- 15.11.1 CPU Idle Time (%)

- 15.11.2 CPU Usage (%)

- 15.11.3 Free Memory (%)

- 15.11.4 Free Memory (MB)

- 15.11.5 Memory Usage (%)

- 15.11.6 Memory Usage (MB)

- 15.11.7 Other CPU Usage (%)

- 15.11.8 Other Memory Usage (%)

- 15.11.9 Other Memory Usage (MB)

- 15.11.10 Start Time (ms since Epoch)

- 15.11.11 Total Memory (MB)

- 15.12 Response

- 15.12.1 Response - Status

- 15.13 Virtual Host Summary

- 15.13.1 Number of Virtual Hosts

16 Apache Tomcat Metrics

- 16.1 All Applications

- 16.1.1 All Applications - Rejected Sessions

- 16.1.2 All Applications - Sessions Created

- 16.1.3 All Applications - Total Active Sessions

- 16.2 All Applications JSP Monitor Metrics

- 16.2.1 All Applications - JSP Access

- 16.2.2 All Applications - JSP Reload

- 16.3 All Global Request Processors Metrics

- 16.3.1 All Global Request Processors - Total Bytes Received

- 16.3.2 All Global Request Processors - Total Errors

- 16.3.3 All Global Request Processors - Total Requests

- 16.3.4 All Global Request Processors -Total Bytes Sent

- 16.4 Application Cache Metrics

- 16.4.1 Cache Access Count

- 16.4.2 Cache Hit Count

- 16.5 Applications Metrics

- 16.5.1 Active Session Since Last Collection

- 16.5.2 Average Processing Time (ms)

- 16.5.3 Processing Time Since last collection (ms)

- 16.5.4 Rejected Sessions Since Last collection

- 16.5.5 Request Count Since Last Collection

- 16.5.6 Sessions Created Since Last Collection

- 16.5.7 Total Active Sessions

- 16.5.8 Total Processing Time (ms)

- 16.5.9 Total Rejected Sessions

- 16.5.10 Total Request Count

- 16.5.11 Total Sessions Since Startup

- 16.6 DataSource Metrics

- 16.6.1 Active Datasource Connections

- 16.6.2 Idle Datasource Connections

- 16.7 Global Request Processor Metrics

- 16.7.1 Average Request Processing Time (ms)

- 16.7.2 Bytes Received Since Last Collection

- 16.7.3 Bytes Sent Since Last Collection

- 16.7.4 Errors Since Last Collection

- 16.7.5 Request Processing Time (ms)

- 16.7.6 Requests Since Last Collection

- 16.8 JSP Monitor Metrics

- 16.8.1 JSP Access

- 16.8.2 JSP Reload

- 16.9 JVM

- 16.9.1 Server CPU Usage (%)

- 16.10 JVM Garbage Collector

- 16.10.1 Name

- 16.10.2 Garbage Collector - Duration of last Garbage Collection (ms)

- 16.10.3 Garbage Collector - Invocation Time (ms)

- 16.10.4 Garbage Collector - Invocation Rate (per min)

- 16.10.5 Garbage Collector - Percentage Time spent (elapsed)

- 16.11 JVM Heap Memory Pool after GC

- 16.11.1 JVM Garbage Collector - Name

- 16.11.2 Memory Pool

- 16.11.3 Memory usage after GC (MB)

- 16.11.4 Percentage Memory usage after GC (%)

- 16.12 JVM Memory Pools

- 16.12.1 Name

- 16.12.2 Memory Pool - Type

- 16.12.3 Memory Pool - Current Usage (MB)

- 16.12.4 Memory Pool - Percentage Usage (%)

- 16.12.5 Memory Pool - Peak Usage (MB)

- 16.13 JVM Threads

- 16.13.1 JVM Threads - Active Threads

- 16.13.2 JVM Threads - Peak Threads

- 16.13.3 JVM Threads - Active Daemon Threads

- 16.13.4 JVM Threads - Threads created (per min)

- 16.14 Memory

- 16.14.1 JVM Heap Memory Usage (MB)

- 16.14.2 JVM Total Heap Memory Usage (MB)

- 16.14.3 JVM Non-Heap Memory Usage (MB)

- 16.14.4 JVM Total Non-Heap Memory Usage (MB)

- 16.14.5 JVM Heap Memory Usage (%)

- 16.14.6 JVM Non-Heap Memory Usage (%)

- 16.14.7 JVM Objects Pending Finalization

- 16.15 Memory Usage

- 16.15.1 Heap Memory Usage (MB)

- 16.15.2 Non Heap Memory Usage (MB)

- 16.16 Response Metrics

- 16.16.1 Status

- 16.17 Servlets Metrics

- 16.17.1 Average Processing Time (ms)

- 16.17.2 Maximum Servlet Request Processing Time (ms)

- 16.17.3 Number Of Errors Since Startup

- 16.17.4 Number Of Requests Since Startup

- 16.17.5 Number Of Servlet Errors Since Last Collection

- 16.17.6 Processing Time Since Last Collection

- 16.17.7 Requests Count Since Last Collection

- 16.17.8 Total Servlet Request Processing Time (ms)

- 16.18 Session Manager Metrics

- 16.18.1 Active Sessions Since Startup

- 16.18.2 Rejected Sessions Since Startup

- 16.18.3 Application Name

- 16.18.4 Sessions Created Since Startup

- 16.18.5 Sessions Created Since Last Collection

- 16.18.6 Active Sessions Since Last Collection

- 16.18.7 Rejected Sessions Since Last Collection

- 16.19 Thread Pools Metrics

- 16.19.1 Busy Threads

- 16.19.2 Threads

17 Java EE Application

- 17.1 ADFC Taskflow Metrics

- 17.1.1 Total Active Taskflows

- 17.1.2 Active Taskflows

- 17.1.3 Active throughput

- 17.1.4 Active Taskflows

- 17.1.5 Total Entered Taskflows

- 17.1.6 Entered Taskflows

- 17.1.7 Invoke Taskflows

- 17.1.8 Invoked Taskflows completed

- 17.1.9 Taskflow Invoke time

- 17.1.10 Average Time

- 17.1.11 Maximum Time

- 17.1.12 Minimum Time

- 17.2 Module Removals

- 17.3 Pool Checkouts

- 17.4 Average Creation time(ms)

- 17.5 Free Instances

- 17.6 Maximum Creation Time (ms)

- 17.7 Request Count

- 17.8 Available Instances in last 5 Minutes

- 17.9 Available Instances in last 1 min

- 17.10 Unavailable Instances in last 5 Minutes

- 17.11 Unavailable Instances in last 1 Minute

- 17.12 Activations

- 17.13 Pool check Ins

- 17.14 Pool Check Outs

- 17.15 Pool Check Out Failures

- 17.16 Referenced Modules Reused

- 17.17 Unreferenced Modules Recycled

- 17.18 Datasource Metrics

- 17.18.1 Datasource - Available Connections

- 17.18.2 Datasource - Connections Created (per minute)

- 17.18.3 Datasource - Connections in Use

- 17.18.4 Datasource - Connection Leaks (per minute)

- 17.18.5 Datasource - Connection Pool Size

- 17.18.6 Datasource - Connection Refresh Failures (per minute)

- 17.18.7 Datasource - Connection Request Failures (per minute)

- 17.18.8 Datasource - Connection Requests (per minute)

- 17.18.9 Datasource - Successful Connections (%)

- 17.18.10 Datasource - Unavailable Connections

- 17.18.11 Datasource - Connection Requests Waiting

- 17.18.12 Datasource - Failed Waiting Connection Requests (per minute)

- 17.18.13 Datasource - Connection Requests that Waited (per minute)

- 17.18.14 Datasource - Connection Wait Successes (%)

- 17.18.15 Datasource - Connection Wait Successes (per minute)

- 17.18.16 Datasource - State

- 17.18.17 Datasource - Statements Added to Cache (per minute)

- 17.18.18 Datasource - Statements Discarded from Cache (per minute)

- 17.18.19 Datasource - Cached Statements not Used (per minute)

- 17.18.20 Datasource - Cached Statements Used (%)

- 17.18.21 Datasource - Cached Statements Used (per minute)

- 17.18.22 Datasource - Statement Cache Size

- 17.19 EJB Module Metrics

- 17.19.1 EJB Module - Cached Beans

- 17.19.2 EJB Module - Bean Activations (per minute)

- 17.19.3 EJB Module - Cache Hits (%)

- 17.19.4 EJB Module - Cache Misses (per minute)

- 17.19.5 EJB Module - Bean Accesses (per minute)

- 17.19.6 EJB Module - Bean Access Successes (%)

- 17.19.7 EJB Module - Free Bean Instances

- 17.19.8 EJB Module - Bean Destroys (per minute)

- 17.19.9 EJB Module - Bean Access Failures (per minute)

- 17.19.10 EJB Module - Beans In Use

- 17.19.11 EJB Module - Bean Transaction Commits (per minute)

- 17.19.12 EJB Module - Bean Transaction Rollbacks (per minute)

- 17.19.13 EJB Module - Bean Transaction Timeouts (per minute)

- 17.20 EJB Transaction Metrics

- 17.20.1 EJB Transaction - Bean Transaction Commits (%)

- 17.20.2 EJB Transaction - Bean Transaction Commits (per minute)

- 17.20.3 EJB Transaction - Bean Transaction Rollbacks (per minute)

- 17.20.4 EJB Transaction - Bean Transaction Timeouts (per minute)

- 17.21 Overview Metrics

- 17.21.1 Cached Beans

- 17.21.2 Cache Accesses (per minute)

- 17.21.3 Bean Activations (per minute)

- 17.21.4 Cache Hits (%)

- 17.21.5 Cache Misses (per minute)

- 17.21.6 Bean Accesses (per minute)

- 17.21.7 Bean Successes (%)

- 17.21.8 Free Bean Instances

- 17.21.9 Bean Destroys (per minute)

- 17.21.10 Bean Access Failures (per minute)

- 17.21.11 Beans In Use

- 17.21.12 Bean Transaction Commits (%)

- 17.21.13 Bean Transaction Commits (per minute)

- 17.21.14 Bean Transaction Rollbacks (per minute)

- 17.21.15 Bean Transaction Timeouts (per minute)

- 17.21.16 MDB Messages (per minute)

- 17.21.17 Requests (per minute)

- 17.21.18 Request Processing Time (ms)

- 17.21.19 Active Sessions

- 17.21.20 Work Manager Pending Requests

- 17.21.21 Work Manager Requests (per minute)

- 17.22 Servlet/JSP Metrics

- 17.22.1 Servlet/JSP - Reloads (per minute)

- 17.22.2 Servlet/JSP - Requests (per minute)

- 17.22.3 Servlet/JSP - Request Processing Time (ms)

- 17.23 Status Metrics

- 17.23.1 Server Name

- 17.23.2 State

- 17.24 Web Module Metrics

- 17.24.1 Web Module - Requests (per minute)

- 17.24.2 Web Module - Request Processing Time (ms)

- 17.24.3 Web Module - Active Sessions

- 17.25 MDS Metrics

- 17.25.1 Metadata Object Gets Per Second

- 17.25.2 Metadata Object Get Processing Time (seconds)

- 17.25.3 IOs Per Document Get

- 17.25.4 IOs Per MO Content Get

- 17.25.5 IOs Per Metadata Object Get

- 17.25.6 Metadata Updates Per Second

- 17.25.7 Metadata Update Processing Time (seconds)

- 17.25.8 Response

- 17.25.9 UpDown Status

18 Oracle Service Bus

- 18.1 Flow Component Resource Details Metrics

- 18.1.1 Average Response Time (Flow Component)

- 18.1.2 Open Instance Count (FLOW_COMPONENT)

- 18.1.3 Error Instance Count (Flow Component)

- 18.2 End Point URI Resource Details Metrics

- 18.2.1 Average Response Time (End Point URI)

- 18.2.2 Open Instance Count (End Point URI)

- 18.2.3 Error Instance Count (End Point URI)

- 18.3 End Point Operation Resource Details Metrics

- 18.3.1 Average Response Time (End Point Operation)

- 18.3.2 Open Instance Count (End Point Operation)

- 18.3.3 Error Instance Count (End Point Operation)

- 18.4 OSB Service Details Metrics

- 18.4.1 Contains Sensitive Details

- 18.4.2 Created User

- 18.4.3 Created Time

- 18.4.4 End Point URI

- 18.4.5 Last Modified User

- 18.4.6 Last Modified Time

- 18.4.7 Protocol

- 18.4.8 Status

- 18.4.9 Version

- 18.5 OSB Service Metrics

- 18.5.1 Average Response Time

- 18.5.2 Total Average Response Time

- 18.5.3 Open Instance Count

- 18.5.4 Total Open Instance Count

- 18.5.5 Error Instance Count

- 18.5.6 Total Error Instance Count

- 18.5.7 Failure Rate

- 18.5.8 Maximum Response Time

- 18.5.9 Minimum Response Time

- 18.5.10 Service Name

- 18.5.11 Path

- 18.5.12 Project Name

- 18.5.13 Service Type

- 18.5.14 WebService Security Violation Instance Count

- 18.5.15 Total WebService Security Violation Instance Count

- 18.6 OSB Proxy Service Metrics

- 18.6.1 Average Response Time

- 18.6.2 Total Average Response Time

- 18.6.3 Open Instance Count

- 18.6.4 Total Open Instance Count

- 18.6.5 Error Instance Count

- 18.6.6 Total Error Instance Count

- 18.6.7 Failure Rate

- 18.6.8 Maximum Response Time

- 18.6.9 Minimum Response Time

- 18.6.10 Service Name

- 18.6.11 Path

- 18.6.12 Project Name

- 18.6.13 Service Type

- 18.6.14 WebService Security Violation Instance Count

- 18.6.15 Total WebService Security Violation Instance Count

- 18.7 OSB Service Dependency Metrics

- 18.7.1 Dependent Service ID

- 18.8 Response

- 18.8.1 Status

- 18.9 SLA Alert Metrics

- 18.9.1 Service Name

- 18.9.2 Project Name

- 18.9.3 SLA Severity Critical Alerts (per min)

- 18.9.4 Total SLA Severity Critical Alerts

- 18.9.5 SLA Severity Fatal Alerts (per min)

- 18.9.6 Total SLA Severity Fatal Alerts

- 18.9.7 SLA Severity Major Alerts (per min)

- 18.9.8 Total SLA Severity Major Alerts

- 18.9.9 SLA Severity Minor Alerts (per min)

- 18.9.10 Total SLA Severity Minor Alerts

- 18.9.11 SLA Severity Warning Alerts (per min)

- 18.9.12 Total SLA Severity Warning Alerts

- 18.9.13 Service Type

19 Oracle SOA Infra

- 19.1 B2B Active Entities Metrics

- 19.1.1 Number of Active Agreements

- 19.1.2 Number of Active Documents

- 19.1.3 Number of Active Trading Partners

- 19.2 B2B Document Metrics Table

- 19.2.1 Number of Inbound Messages

- 19.2.2 Number of inbound message faults

- 19.2.3 Inbound Message Size (KB)

- 19.2.4 Inbound Messages processing time

- 19.2.5 B2B Document Name

- 19.2.6 Number of Outbound Messages

- 19.2.7 Number of outbound message faults

- 19.2.8 Outbound Message Size (KB)

- 19.2.9 Outbound Messages processing time

- 19.3 B2B Inbound Endpoint Metrics

- 19.3.1 B2B Inbound Endpoint Status

- 19.4 B2B Outbound Endpoint Metrics

- 19.4.1 B2B Outbound Endpoint Status

- 19.5 B2B Trading Partner Metrics

- 19.5.1 Number of inbound messages

- 19.5.2 Number of inbound message faults

- 19.5.3 Inbound Message Size (KB)

- 19.5.4 Processing time of Inbound Messages

- 19.5.5 Trading partner name

- 19.5.6 Number of outbound messages

- 19.5.7 Number of outbound message faults

- 19.5.8 Outbound Message Size (KB)

- 19.5.9 Processing time of outbound messages

- 19.6 BPEL Engine Requests Rate Metric Table

- 19.6.1 Active request throughput in the last 5 minutes

- 19.6.2 Last active request value

- 19.6.3 Scheduled request throughput in the last 5 minutes

- 19.6.4 Last scheduled request value

- 19.7 Business Rules Engine Cache Metrics Table

- 19.7.1 Total Access Count since server startup

- 19.7.2 Last value of access count

- 19.7.3 Total Count since server startup

- 19.7.4 Last value of total count

- 19.8 Business Rule Engine Request Breakdown Rate Metric Table

- 19.8.1 Request count since server startup

- 19.8.2 Throughput of requests in the last 5 minutes

- 19.8.3 Last value of request

- 19.8.4 Average request processing time

- 19.8.5 Number of completed requests

- 19.8.6 Response

- 19.8.7 UpDown Status

- 19.9 SOA Infrastructure Bindings Rate Metric Table

- 19.9.1 Active request throughput in the last 5 minutes

- 19.9.2 Number of faults since server startup

- 19.9.3 Average request processing time

- 19.9.4 Total number of processed requests since server startup

- 19.10 SOA Composite Bindings/References Rate Metric

- 19.10.1 Total number of faults since server start

- 19.10.2 Throughput of faults in the last 5 minutes

- 19.10.3 Average Incoming Messages Processing Time

- 19.10.4 Total completed incoming messages since server start

- 19.10.5 Incoming messages throughput in the last 5 minutes

- 19.10.6 Total Incoming Messages Processing Time

- 19.10.7 Total Incoming Message processing time

- 19.10.8 Total number of incoming messages since server start

- 19.10.9 Incoming message throughput in the last 5 minutes

- 19.10.10 Average Outbound Messages Processing Time

- 19.10.11 Total completed outgoing messages since server start

- 19.10.12 Outbound messages throughput in the last 5 minutes

- 19.10.13 Total Outbound Messages Processing Time since server start

- 19.10.14 Total Outbound Message processing time

- 19.10.15 Total number of outgoing messages since server start

- 19.10.16 Outbound message events throughput in the last 5 minutes

- 19.11 BPEL Dispatcher Rate Metric Table

- 19.11.1 Total number of messages processed per thread since server startup

- 19.11.2 Throughput of total messages in the last 5 minutes

- 19.11.3 Last value of total message

- 19.11.4 Throughput of average thread allocation time in the last 5 minutes

- 19.11.5 Last value of average thread allocation time

- 19.11.6 Throughput of average thread lifetime in the last 5 minutes

- 19.11.7 Last value of average thread lifetime

- 19.11.8 Throughput of maximum threads in the last 5 minutes

- 19.11.9 Last value of maximum thread

- 19.11.10 Throughput of minimum threads in the last 5 minutes

- 19.11.11 Last value of minimum thread

- 19.11.12 Number of active threads since server startup

- 19.11.13 Throughput of thread count in the last 5 minutes

- 19.11.14 Last value of thread count

- 19.11.15 Number of thread highs since server startup

- 19.11.16 Throughput of thread high in the last 5 minutes

- 19.11.17 Last value of thread high

- 19.11.18 Number of pending threads since server startup

- 19.11.19 Throughput of pending threads in the last 5 minutes

- 19.11.20 Last value of pending thread

- 19.11.21 Total number of threads since server startup

- 19.11.22 Throughput of total threads in the last 5 minutes

- 19.11.23 Last value of total thread metric

- 19.12 BPMN Dispatcher Rate Metric Table

- 19.12.1 Last value of maximum thread

- 19.12.2 Number of active threads since server startup

- 19.12.3 Throughput of thread count in the last 5 minutes

- 19.13 SOA Mediator Engine Cache

- 19.13.1 Last value of metadata cache

- 19.13.2 Last value of transformation cache

- 19.13.3 SOA Mediator Engine Requests

- 19.13.4 Callback Requests

- 19.13.5 Delay Requests

- 19.13.6 Dequeue Requests

- 19.13.7 Timeout Requests

- 19.14 SOA Mediator Engine Request Breakdown Rate Metric Table

- 19.14.1 enqueue-phase.active

- 19.14.2 Avg Enqueue Time (ms)

- 19.14.3 Enqueued

- 19.14.4 Throughput of Enqueue phase

- 19.14.5 Total Enqueue Time (ms)

- 19.14.6 invoke-phase.active

- 19.14.7 Avg Invoke Time (ms)

- 19.14.8 Invoked

- 19.14.9 Throughput of Invoke phase

- 19.14.10 Total Invoke Time (ms)

- 19.14.11 invokeOneway-phase.active

- 19.14.12 Avg Oneway Invoke Processing Time (ms)

- 19.14.13 Oneway Invocations

- 19.14.14 Throughput of Oneway Invocations

- 19.14.15 Total Oneway Invocation Time (ms)

- 19.14.16 publish-phase.active

- 19.14.17 Avg Publication Time (ms)

- 19.14.18 Publications

- 19.14.19 Throughput of Publication phase

- 19.14.20 Total Publication Time (ms)

- 19.14.21 transformation-phase.active

- 19.14.22 Avg Transformation Time (ms)

- 19.14.23 Transformations

- 19.14.24 Throughput of Transformations

- 19.14.25 Total Transformation Time (ms)

- 19.15 SOA Infra Mesh

- 19.15.1 Number of active messages in the mesh

- 19.15.2 Total number of messages in the mesh since server startup

- 19.15.3 Number of faulted messages in the mesh

- 19.15.4 Throughput of messages in the mesh in the last 5 minutes

- 19.15.5 SOA Infra Mesh Message Count Table

- 19.15.6 Total number of messages in the mesh since server startup

- 19.15.7 Mesh Name

- 19.15.8 Throughput of faulted asynchronous messages in the last 5 minutes

- 19.15.9 Number of active asynchronous messages

- 19.15.10 Average processing time of asynchronous messages

- 19.15.11 Number of completed asynchronous messages

- 19.15.12 Throughput of asynchronous messages in the last 5 minutes

- 19.15.13 Total processing time of asynchronous messages

- 19.15.14 Throughput of faulted synchronous messages in the last 5 minutes

- 19.15.15 Number of active synchronous messages

- 19.15.16 Average processing time of synchronous messages

- 19.15.17 Number of completed synchronous messages

- 19.15.18 Throughput of synchronous messages in the last 5 minutes

- 19.15.19 Total processing time of synchronous messages

- 19.16 SOA Message Processing Rate Metric Table

- 19.16.1 Total number of active requests since server startup

- 19.16.2 Throughput of the active requests in the last 5 minutes

- 19.16.3 Last value of active request

- 19.16.4 Total number of BPEL messages since startup

- 19.16.5 Engine Name

- 19.16.6 Total number of decision service messages since startup

- 19.16.7 Engine Name

- 19.16.8 Number of faults since server startup

- 19.16.9 Throughput of faulted requests in the last 5 minutes

- 19.16.10 Rate of processing faulted requests

- 19.16.11 Total number of mediator messages since startup

- 19.16.12 Engine Name

- 19.16.13 Total number of messages since server startup

- 19.16.14 Total number of asynchronous requests since server startup

- 19.16.15 Throughput of asynchronous invocations in the last 5 minutes

- 19.16.16 Rate of processing asynchronous invocations

- 19.16.17 Average asynchronous message processing time since server startup

- 19.16.18 Total number of synchronous requests since server startup

- 19.16.19 Synchronous invocations throughput in the last 5 minutes

- 19.16.20 Rate of processing synchronous invocations

- 19.16.21 Average synchronous message processing time since server startup

- 19.16.22 Total number of workflow messages since startup

- 19.16.23 Engine Name

- 19.17 Total Composite Instances

- 19.17.1 Total number of instances since server startup

- 19.17.2 Domain Name

- 19.18 Total Composite Faults

- 19.18.1 Total number of faults since server startup

- 19.19 Workflow Request Breakdown Rate Metrics

- 19.19.1 Number of invocations since server startup

- 19.19.2 Service Name

- 19.19.3 Number of active requests

- 19.19.4 Average request processing time

- 19.19.5 Number of completed requests

20 SOA Composite

- 20.1 SOA Composite B2B Inbound Metrics

- 20.1.1 InBound Message Count

- 20.1.2 Inbound Messages Faults

- 20.1.3 Inbound Messages Size

- 20.1.4 Inbound Message Processing Time

- 20.1.5 ServerName

- 20.1.6 Total Outbound Messages Count

- 20.2 SOA Composite B2B Outbound Metrics

- 20.2.1 Name

- 20.2.2 OutBound Message Count

- 20.2.3 Outbound Messages Faults

- 20.2.4 Outbound Messages Size

- 20.2.5 Outbound Message Processing Time

- 20.2.6 ServerName

- 20.2.7 Total Outbound Messages Count

- 20.3 BPEL Activity Time Distribution

- 20.3.1 Average Execution Time (ms)

- 20.3.2 Activity Count

- 20.3.3 Activity Name

- 20.3.4 Server Name

- 20.4 SOA Composite - Response Metrics

- 20.4.1 Status

- 20.5 SOA Composite Bindings/References Rate Metric

- 20.5.1 Total number of faults since server start

- 20.5.2 Average Incoming Messages Processing Time

- 20.5.3 Total number of incoming messages since server start

- 20.5.4 Incoming message throughput in last 5 minutes

- 20.5.5 Average Outbound Messages Processing Time

- 20.5.6 Total number of outgoing messages since server start

- 20.5.7 Outbound message throughput in last 5 minutes

- 20.6 SOA Component References

- 20.6.1 Average Message Processing Time (secs) since server start up

- 20.6.2 Number of Faults

- 20.6.3 Number of Messages

- 20.6.4 Average Message Processing Time (secs) in last 5 mins

- 20.6.5 Reference Name

- 20.6.6 Component References

- 20.6.7 Component Type

- 20.7 SOA Component Rollup Metric

- 20.7.1 Business faults throughput in the last 5 minutes

- 20.7.2 Number of active faulted instances

- 20.7.3 Average processing time for faulted instances

- 20.7.4 Number of faulted instances

- 20.7.5 Throughput of faulted instances in the last 5 minutes

- 20.7.6 Total time spent on processing faulted instances

- 20.7.7 Total average faulted processing time

- 20.7.8 Instance throughput in the last 5 minutes

- 20.7.9 Server Name

- 20.7.10 Number of active successful instances

- 20.7.11 Average processing time for successful instances

- 20.7.12 Number of successful instances

- 20.7.13 Throughput of successful instances in the last 5 minutes

- 20.7.14 Total time spent on processing successful instances

- 20.7.15 Total average successful processing time

- 20.7.16 System faults throughput in the last 5 minutes

- 20.7.17 Total faults throughput in the last 5 minutes

- 20.8 SOA Composite - Rate Metrics

- 20.8.1 Instance throughput in the last 5 minutes

- 20.8.2 Asynchronous message event throughput in the last 5 minutes

- 20.8.3 Average asynchronous message Processing time

- 20.8.4 Asynchronous messages throughput in the last 5 minutes

- 20.8.5 Total asynchronous message processing time

- 20.8.6 Synchronous message event throughput in the last 5 minutes

- 20.8.7 Average synchronous message processing time

- 20.8.8 Synchronous messages throughput in the last 5 minutes

- 20.8.9 Total synchronous message processing time

- 20.8.10 Server Name

- 20.9 Mediator Case

- 20.9.1 Average processing time of invocations

- 20.9.2 Invocation throughput in the last 5 minutes

- 20.9.3 Total processing time for invocations

- 20.9.4 Failed filtered messages throughput in the last 5 minutes

- 20.9.5 Average processing time of faulted cases

- 20.9.6 Number of faulted cases

- 20.9.7 Faulted case throughput in the last 5 minutes

- 20.9.8 Total processing time for faulted cases

- 20.9.9 Filtered messages throughput in the last 5 minutes

- 20.9.10 Invocation Count throughput in the last 5 minutes

- 20.9.11 Component Type

- 20.9.12 Composite Label

- 20.9.13 Case Target

- 20.9.14 Mediator Flow

- 20.9.15 Flow Type

- 20.9.16 Average processing time of successful cases

- 20.9.17 Number of successful cases

- 20.9.18 Successful case throughput in the last 5 minutes

- 20.9.19 Total processing time for successful cases

- 20.10 Mediator Flow Metric

- 20.10.1 Deferred message count throughput in last 5 minutes

- 20.10.2 Failed filter case throughput in last 5 minutes

- 20.10.3 Average faulted instance processing time

- 20.10.4 Faulted instances throughput in last 5 minutes

- 20.10.5 Total faulted instance processing time

- 20.10.6 Instance throughput in last 5 minutes

- 20.10.7 Component Type

- 20.10.8 Composite Label

- 20.10.9 Flow Type

- 20.10.10 Average successful instance processing time

- 20.10.11 Successful instances throughput in last 5 minutes

- 20.10.12 Total successful instance processing time

- 20.11 Total Composite Instances

- 20.11.1 Total number of composite instances since server startup

- 20.11.2 Domain Name

- 20.12 Total Composite Faults

- 20.12.1 Total number of faults since server startup

- 20.13 Reference Binding Rollup

- 20.13.1 Average Incoming Messages Processing Time

- 20.13.2 Average Incoming Messages Processing Time (ms)

- 20.13.3 Average Outbound Messages Processing Time

- 20.13.4 Average Outbound Messages Processing Time (ms)

- 20.13.5 Binding - Error rate

- 20.13.6 Composite Revision

- 20.13.7 Composite Name

- 20.13.8 Domain Name

- 20.13.9 End Point URL

- 20.13.10 Incoming message throughput in last 5 minutes

- 20.13.11 Incoming message throughput in last 5 minutes (sec)

- 20.13.12 Outbound message throughput in last 5 minutes

- 20.13.13 Outbound message throughput in last 5 minutes (sec)

- 20.13.14 Reference Name

- 20.13.15 Reference Type

- 20.13.16 Total number of faults since last collection

- 20.13.17 Total number of faults since startup

- 20.13.18 Total number of incoming messages Since Last Collection

- 20.13.19 Total number of incoming messages since startup

- 20.13.20 Total number of outgoing messages since last collection

- 20.13.21 Total number of outgoing messages since startup

- 20.13.22 WSDL Port

- 20.13.23 WSDL URL of the service

- 20.14 Service Binding Rollup

- 20.14.1 Average Incoming Messages Processing Time

- 20.14.2 Average Incoming Messages Processing Time (ms)

- 20.14.3 Average Outbound Messages Processing Time

- 20.14.4 Average Outbound Messages Processing Time (ms)

- 20.14.5 Binding - Error rate

- 20.14.6 Composite Revision

- 20.14.7 Composite Name

- 20.14.8 Domain Name

- 20.14.9 End Point URL

- 20.14.10 Incoming message throughput in last 5 minutes

- 20.14.11 Incoming message throughput in last 5 minutes (sec)

- 20.14.12 Outbound message throughput in last 5 minutes

- 20.14.13 Outbound message throughput in last 5 minutes (sec)

- 20.14.14 Reference Name

- 20.14.15 Reference Type

- 20.14.16 Total number of faults since last collection

- 20.14.17 Total number of faults since startup

- 20.14.18 Total number of incoming messages Since Last Collection

- 20.14.19 Total number of incoming messages since startup

- 20.14.20 Total number of outgoing messages since last collection

- 20.14.21 Total number of outgoing messages since startup

- 20.14.22 WSDL Port

- 20.14.23 WSDL URL of the service

21 Forms

- 21.1 Forms Resource Usage

- 21.1.1 CPU Usage (%)

- 21.1.2 Total CPU Time (millisec)

- 21.1.3 instname.value

- 21.1.4 Total Private Memory (KB)

- 21.2 JVM Controllers

- 21.2.1 JVM CPU Usage (%)

- 21.2.2 CPU Time (millisec)

- 21.2.3 Number of JVMs running for this JVM Controller

- 21.2.4 JVM Private Memory (KB)

- 21.2.5 UP Time (millisec)

- 21.3 Number Of Sessions

- 21.3.1 Number Of Sessions

- 21.4 Response

- 21.4.1 instname.value

- 21.4.2 Status

- 21.5 Average Servlet Response Time

- 21.5.1 Average Response Time (millisec)

- 21.5.2 instname.value

22 Portal

- 22.1 Portlets (All)

- 22.1.1 Cache Hit (%)

- 22.1.2 Average Time (ms)

- 22.1.3 Requests (per minute)

- 22.1.4 Availability (%)

- 22.1.5 Producer Type

- 22.2 Portlets (Top 5)

- 22.2.1 Cache Hit (%)

- 22.2.2 Average Time (ms)

- 22.2.3 Requests (per minute)

- 22.2.4 Availability (%)

- 22.2.5 Producer Type

- 22.3 Producers (All)

- 22.3.1 Cache Hit (%)

- 22.3.2 Average Time (ms)

- 22.3.3 Requests (per minute)

- 22.3.4 Availability (%)

- 22.3.5 Producer Type

- 22.4 Producers (Top 5)

- 22.4.1 Cache Hit (%)

- 22.4.2 Average Time (ms)

- 22.4.3 Requests (per minute)

- 22.4.4 Availability (%)

- 22.4.5 Producer Type

- 22.5 Portal Cache

- 22.5.1 Average Expire Hit Time (ms)

- 22.5.2 Expire Hit (%)

- 22.5.3 Average New Time (ms)

- 22.5.4 New (%)

- 22.5.5 Average Ping Hit Time (ms)

- 22.5.6 Ping Hit (%)

- 22.5.7 Requests (per minute)

- 22.5.8 Average Stale Time (ms)

- 22.5.9 Stale (%)

- 22.6 Database Connection Pool Statistics

- 22.6.1 Average Fetch Time (ms)

- 22.6.2 Requests (per minute)

- 22.6.3 Hit (%)

- 22.6.4 New (%)

- 22.6.5 Stale (%)

- 22.7 Database Repository Response Code Statistics

- 22.7.1 Responses (per minute)

- 22.7.2 Average Processing Time (ms)

- 22.8 Page Engine Statistics

- 22.8.1 Average Queue Wait Time (ms)

- 22.8.2 Average Page Processing Time (ms)

- 22.8.3 Pages (per minute)

- 22.8.4 Average Page Metadata Fetch Time (ms)

- 22.8.5 Page Metadata Fetches (per minute)

- 22.8.6 Average Page Metadata Wait Time (ms)

- 22.8.7 Queue Timeouts (per minute)

- 22.8.8 HTTP200-HTTP299 (%)

- 22.8.9 HTTP300-HTTP399 (%)

- 22.8.10 HTTP400-HTTP499 (%)

- 22.8.11 HTTP500-HTTP599 (%)

- 22.8.12 Timeout (%)

- 22.8.13 WebCache Page Metadata Hits (%)

- 22.8.14 WebCache Page Metadata Misses (%)

- 22.8.15 WebCache Page Metadata Non-Cacheables (%)

- 22.9 Response

- 22.9.1 UpDown Status

23 Reports Bridge

- 23.1 Log Message Alerts

- 23.1.1 Log Monitoring Rules

- 23.2 Diagnostic Log Summary

- 23.2.1 Log Error Messages (over 15 minutes)

- 23.2.2 Log Incident Error Messages (over 15 minutes)

- 23.2.3 Log Notification Messages (over 15 minutes)

- 23.2.4 Log Trace Messages (over 15 minutes)

- 23.2.5 Log Unknown Messages (over 15 minutes)

- 23.2.6 Log Warning Messages (over 15 minutes)

- 23.3 Remote Elements Discovered

- 23.3.1 Host.value

- 23.3.2 Name

- 23.3.3 Discovery Time (ms)

- 23.3.4 Type of Element

- 23.4 Resource Usage

- 23.4.1 CPU Usage (%)

- 23.4.2 Memory Usage (MB)

- 23.4.3 Memory Usage (%)

- 23.5 Response

- 23.5.1 Up or Down Status

24 Virtual Directory

- 24.1 Adapter Metrics

- 24.1.1 Open Connections

- 24.1.2 Total No of Connections Processed

- 24.1.3 Total No of Connections Reused

- 24.1.4 Enabled

- 24.1.5 Add Operations

- 24.1.6 Total No of Operation Binds

- 24.1.7 Operations Count

- 24.1.8 Delete Operations

- 24.1.9 Operational Version

- 24.1.10 Modify Operations

- 24.1.11 Total No of Operations Renamed

- 24.1.12 Search Operations

- 24.1.13 Provisioned version

- 24.1.14 Type

- 24.1.15 Average Time to complete a search request

- 24.1.16 Maximum Time taken to complete a search request

- 24.1.17 Minimum Time taken to complete a search request

- 24.2 Connected IPs

- 24.2.1 Current Connections

- 24.2.2 Total Connections

- 24.3 getUsers

- 24.3.1 Current Connections

- 24.3.2 Total Connections

- 24.4 Resource Usage

- 24.4.1 CPU Usage (%)

- 24.4.2 CPU Idle Time (%)

- 24.4.3 Other CPU Usage (%)

- 24.4.4 Heap Usage (MB)

- 24.4.5 Memory Usage (MB)

- 24.4.6 Free Memory (MB)

- 24.4.7 Other Memory Usage (MB)

- 24.4.8 Total Memory (MB)

- 24.4.9 Memory Usage (%)

- 24.4.10 Free Memory (%)

- 24.4.11 Other Memory Usage (%)

- 24.4.12 Start Time (ms since Epoch)

- 24.4.13 Up Time (ms since Epoch)

- 24.5 Response

- 24.5.1 UpDown Status

- 24.6 Server Latency Metrics

- 24.6.1 Total Operations

- 24.6.2 Average time to complete an LDAP search request

- 24.6.3 Maximum Time to complete a search request

- 24.6.4 Minimum Time to complete a search request

- 24.6.5 Number of LDAP Add Requests

- 24.6.6 Number of LDAP Binds Requests

- 24.6.7 Number of LDAP Delete Requests

- 24.6.8 Number of LDAP Modify Requests

- 24.6.9 Number of LDAP Rename Requests

- 24.6.10 Number of LDAP Search Requests

- 24.7 Server wide Connection Metrics

- 24.7.1 Total No of IPs Currently Connected

- 24.7.2 Total No of Users Currently Connected

- 24.7.3 Total No of Operations

- 24.7.4 Total No of Open Connections

25 Internet Directory

- 25.1 Oracle Internet Directory

- 25.2 (Resource Statistics) LDAP Server's Active Database Connections

- 25.3 Active Database Sessions

- 25.4 Closed LDAP Logon Session Statistics

- 25.4.1 Total Closed Logon Sessions

- 25.5 (Historical Resource Statistics)LDAP Server's Database Usage

- 25.5.1 Active Database Sessions

- 25.5.2 Date and Time Stamp

- 25.5.3 Instance Number

- 25.5.4 Open Database Sessions

- 25.6 Failed Bind Operations

- 25.7 (Critical Events)General System Resource Events

- 25.7.1 Critical General Sys Resource Event Occurrences

- 25.8 LDAP Load

- 25.8.1 Server Load

- 25.9 Historical LDAP Load and Response

- 25.9.1 Date and Time Stamp

- 25.9.2 Instance Number

- 25.9.3 Server Load

- 25.9.4 Server Average Response Time (in Milliseconds)

- 25.10 (Resource Statistics)LDAP Server Memory Growth

- 25.10.1 Average memory growth (%)

- 25.11 New LDAP Logon Session Statistics

- 25.11.1 Total New Logon Sessions

- 25.12 (Resource Statistics) LDAP Server's Open Database Connections

- 25.12.1 Open Database Sessions

- 25.13 Open LDAP Logon Session Statistics

- 25.13.1 Total Open Logon Sessions

- 25.14 Historical LDAP Operation Response Time

- 25.14.1 Bind Operation Response Time

- 25.14.2 Compare Operation Response Time

- 25.14.3 Date and Time Stamp

- 25.14.4 Instance Number

- 25.14.5 Messaging Search Operation Response Time

- 25.15 LDAP Operation Response Time

- 25.15.1 Bind Operation Response Time

- 25.15.2 Compare Operation Response Time

- 25.15.3 Messaging Search Operation Response Time

- 25.16 LDAP Server Resource Usage

- 25.16.1 Total CPU Usage (%)

- 25.16.2 Total Memory Usage (KB)

- 25.16.3 Total Memory Usage (%)

- 25.17 LDAP Response

- 25.17.1 Server Response

- 25.18 Running instances of LDAP Server

- 25.18.1 Downtime Count

- 25.18.2 Host Name

- 25.18.3 Instance Number

- 25.18.4 Up Since

- 25.18.5 Non SSL Port Number

- 25.18.6 SSL Port Number

- 25.19 (Historical Resource Statistics)LDAP Server and System Memory

- 25.19.1 Date and Time Stamp

- 25.19.2 Instance Number

- 25.19.3 LDAP Server's average memory growth (%)

- 25.19.4 System's Total Free Physical Memory (KB)

- 25.20 (Critical Events)System Resource Events(3113 Errors)

- 25.20.1 Number of 3113 Error Occurrences

- 25.21 (Critical Events)System Resource Events(3114 Errors)

- 25.21.1 Number of 3114 Error Occurrences

- 25.22 (Historical Critical Events)System Resource Events

- 25.22.1 Last Event Time

- 25.22.2 Number of Event Occurrence

- 25.22.3 Event Name

- 25.22.4 Instance Number

- 25.22.5 Process ID

- 25.23 (Critical Events)System Resource Events(Ora Errors)

- 25.23.1 Critical Ora Error Occurrences

- 25.24 Historical LDAP Logon Session Statistics

- 25.24.1 Date and Time Stamp

- 25.24.2 Instance Number

- 25.24.3 Total LDAP Logon Sessions

- 25.25 Total Memory Usage

- 25.25.1 Total Mem. Size(in KB)

- 25.26 Historical LDAP Operations Profile

- 25.26.1 Date and Time Stamp

- 25.26.2 Instance Number

- 25.26.3 Completed Abandon Operations

- 25.26.4 Completed Add Operations

- 25.26.5 Completed Bind Operations

- 25.26.6 Completed Compare Operations

- 25.26.7 Completed Delete Operations

- 25.26.8 Completed Modify Operations

- 25.26.9 Completed Modrdn Operations

- 25.26.10 Completed Search Operations

- 25.26.11 Completed Unbind Operations

- 25.26.12 Failed Bind Operations

- 25.27 LDAP Operations Profile

- 25.27.1 Completed Abandon Operations

- 25.27.2 Completed Add Operations

- 25.27.3 Completed Bind Operations

- 25.27.4 Completed Compare Operations

- 25.27.5 Completed Delete Operations

- 25.27.6 Completed Modify Operations

- 25.27.7 Completed Modrdn Operations

- 25.27.8 Total Operations

- 25.27.9 Completed Search Operations

- 25.27.10 Completed Unbind Operations

- 25.28 LDAP Server Total User Sessions

- 25.28.1 Total Users Sessions

- 25.29 Directory Integration Profiles

- 25.29.1 Last Execution Time

- 25.29.2 Last Applied Change Number

- 25.29.3 Execution Errors

- 25.29.4 State

- 25.29.5 Execution Status

- 25.29.6 Schedule (secs)

- 25.29.7 Type

- 25.30 Directory Integration Server

- 25.30.1 Downtime Count

- 25.30.2 Directory Integration Server Host

- 25.30.3 Start Time

- 25.30.4 LDAP Server

- 25.31 Size of Audit Log Purge Queue

- 25.31.1 Total Number of Audit Log Objects in Purge Queue

- 25.32 Size of General Statistics Purge Queue

- 25.32.1 Total Number of General Statistics Objects in Purge Queue

- 25.33 Size of Health Statistics Purge Queue

- 25.33.1 Total Number of Health Statistics Objects in Purge Queue

- 25.34 Total Number ChangeLogs in Purge Queue

- 25.34.1 Total Number of Local Changelogs in Purge Queue

- 25.35 Total Number Remote ChangeLogs in Purge Queue

- 25.35.1 Total Number of Remote Changelogs in Purge Queue

- 25.36 Total Number of HIQ ChangeLogs

- 25.36.1 HIQ Changelog Count

- 25.37 Replication Server Configuration Set Information

- 25.37.1 Number of Threads per Supplier for Change Processing

- 25.37.2 Number of Threads per Supplier for Transporting Changes

- 25.38 Running instances of LDAP Replication Server

- 25.38.1 Downtime Count

- 25.38.2 Oracle Directory Server

- 25.38.3 Start Time

- 25.39 Total Number of Local ChangeLogs

- 25.39.1 Total Number of Local Changelogs

- 25.40 Total Number of New ChangeLogs

- 25.40.1 New Changelog Count

- 25.41 Total number ChangeLogs to be processed

- 25.41.1 Total Changelogs to be processed

- 25.42 Total Number of Retry ChangeLogs

- 25.42.1 Retry Changelog Count

- 25.43 OID Replication Server Virtual Memory Size

- 25.43.1 Replication Server Memory Size

- 25.44 OID Replication Server Percentage CPU

- 25.44.1 Replication Server Percentage CPU

- 25.45 Replication Supplier Details

- 25.45.1 Replication Agreement Type

- 25.45.2 HIQ Changelog Count

- 25.45.3 New Changelog Count

- 25.45.4 Retry Changelog Count

- 25.45.5 Name of the Supplier Replica

- 25.46 Size of Security Refresh events Purge Queue

- 25.46.1 Total Number of Security Refresh events Objects in Purge Queue

- 25.47 Historical LDAP Entry Cache Hit Ratio

- 25.47.1 User Action

- 25.47.2 Date and Time Stamp

- 25.47.3 Instance Number

- 25.47.4 Server Entry Cache Hit Ratio

- 25.47.5 Process ID

- 25.47.6 LDAP Entry Cache Hit Ratio

- 25.47.7 Server Entry Cache Hit Ratio

- 25.48 OID Server Virtual Memory Size

- 25.48.1 OID Server Memory Size

- 25.49 Stopped instances of LDAP Server

- 25.49.1 Config Set Number

- 25.49.2 Host Name

- 25.50 OID Server Percentage CPU Utilization

- 25.50.1 OID Server Percentage CPU

- 25.51 (Historical Critical Events)Security Events

- 25.51.1 Event Time

- 25.51.2 Event Result

- 25.51.3 Event Name

- 25.51.4 Instance Number

- 25.51.5 Process ID

- 25.51.6 User DN

- 25.52 (Critical Event)Super User Failed Logins

- 25.52.1 Failed LDAP Super User Login

- 25.53 (Critical Event)Super User Successful Logins

- 25.53.1 Successful LDAP Super User Login

- 25.54 Size of System Resource events Purge Queue

- 25.54.1 Total Number of System Resource events Objects in Purge Queue

- 25.55 Size of Tombstone Purge Queue

- 25.55.1 Total Number of Tombstone Objects in Purge Queue

- 25.56 TopProcesses

- 25.56.1 Process Name

- 25.57 Resource Usage

- 25.57.1 CPU Usage (%)

- 25.57.2 CPU Idle Time (%)

- 25.57.3 Other CPU Usage (%)

- 25.57.4 Memory Usage (MB)

- 25.57.5 Free Memory (MB)

- 25.57.6 Other Memory Usage (MB)

- 25.57.7 Total Memory (MB)

- 25.57.8 Memory Usage (%)

- 25.57.9 Free Memory (%)

- 25.57.10 Other Memory Usage (%)

- 25.57.11 Start Time (ms since Epoch)

- 25.58 Response

- 25.58.1 Status

- 25.58.2 Total Number

- 25.59 User LDAP Operations Stats

- 25.59.1 Abandon Operations

- 25.59.2 Failed Add Operations

- 25.59.3 Failed Base Search Operations

- 25.59.4 Failed Bind Operations

- 25.59.5 Failed Compare Operations

- 25.59.6 Failed Delete Operations

- 25.59.7 Failed Modify Operations

- 25.59.8 Failed ModRdn Operations

- 25.59.9 Failed OneLevel Search Operations

- 25.59.10 Failed Proxy Bind Operations

- 25.59.11 Failed Subtree Search Operations

- 25.59.12 Successful Add Operations

- 25.59.13 Successful Base Search Operations

- 25.59.14 Successful Bind Operations

- 25.59.15 Successful Compare Operations

- 25.59.16 Successful Delete Operations

- 25.59.17 Successful Modify Operations

- 25.59.18 Successful ModRdn Operations

- 25.59.19 Successful OneLevel Search Operations

- 25.59.20 Successful Proxy Bind Operations

- 25.59.21 Successful Subtree Search Operations

- 25.59.22 Unbind Operations

26 Directory Integration Platform

- 26.1 DIP Aggregated Metrics

- 26.1.1 Total Changes Attempted

- 26.1.2 Total Successful Changes

- 26.1.3 Average LDAP Search Time

- 26.1.4 Average LDAP Write Time

- 26.1.5 Average Profile Execution Time

- 26.2 DIP All Profiles (Consolidated)

- 26.2.1 Host

- 26.2.2 Last Change Number

- 26.2.3 Last Execution Error

- 26.2.4 Last Execution Time

- 26.2.5 Last Successful Execution Time

- 26.2.6 Status of Last Sync Operation

- 26.2.7 DIP Profile Name

- 26.2.8 DIP Process

- 26.2.9 Average Processing Time

- 26.2.10 Maximum Processing Time

- 26.2.11 Minimum Processing Time

- 26.2.12 Profile Job Status

- 26.3 DIP Prov profile runtime operational metrics

- 26.3.1 Failed Add Group operations

- 26.3.2 Failed Add Identity operations

- 26.3.3 Failed Add Subscription operations

- 26.3.4 Failed Add User operations

- 26.3.5 Failed Delete Group operations

- 26.3.6 Failed Delete Identity operations

- 26.3.7 Failed Delete Subscription operations

- 26.3.8 Failed Delete User operations

- 26.3.9 Failed Modify Group operations

- 26.3.10 Failed Modify Identity operations

- 26.3.11 Failed Modify User operations

- 26.3.12 Profile Name

- 26.3.13 Successful Add Group operations

- 26.3.14 Successful Add Identity operations

- 26.3.15 Successful Add Subscription operations

- 26.3.16 Successful Add User operations

- 26.3.17 Successful Delete Group operations

- 26.3.18 Successful Delete Identity operations

- 26.3.19 Successful Delete Subscription operations

- 26.3.20 Successful Delete User operations

- 26.3.21 Successful Modify Group operations

- 26.3.22 Successful Modify Identity operations

- 26.3.23 Successful Modify User operations

- 26.4 DIP Sync profile runtime operational metrics

- 26.4.1 Skipped Operations

- 26.4.2 Failed Add Operations

- 26.4.3 Failed Delete Operations

- 26.4.4 Failed Modify Operations

- 26.4.5 Profile Name

- 26.4.6 Successful Add Operations

- 26.4.7 Successful Delete Operations

- 26.4.8 Successful Modify Operations

- 26.5 DIP Health

- 26.5.1 Host

- 26.5.2 MBean Status

- 26.5.3 Name

- 26.5.4 Quartz Scheduler Status

- 26.5.5 WLS Server Name

- 26.6 DIP Provisioning Profiles

- 26.6.1 DIP Provisioning Profile Name

- 26.6.2 Host

- 26.6.3 Name

- 26.7 DIP Synchronization Profiles

- 26.7.1 DIP Synchronization Profile Name

- 26.7.2 Host

- 26.7.3 Name

- 26.8 Resource Usage

- 26.8.1 CPU Usage (%)

- 26.8.2 Memory Usage (%)

- 26.9 DIP server status

- 26.9.1 Status

27 WebCenter

- 27.1 Response

- 27.1.1 UpDown Status

- 27.2 WebCenter Spaces (Aggregated)

- 27.2.1 Application Name

- 27.2.2 Status

- 27.2.3 Successful Invocations (%)

- 27.2.4 Failed Invocations (%)

- 27.2.5 Invocations (per minute)

- 27.2.6 Page Throughput (per minute)

- 27.2.7 Average Page Processing Time (ms)

- 27.2.8 Service Name

- 27.3 WebCenter Content Repositories (Aggregated)

- 27.3.1 Application Name

- 27.3.2 Average Delete Time (ms)

- 27.3.3 Average Download Time (ms)

- 27.3.4 Average GetItem Time (ms)

- 27.3.5 Average ListFolder Time (ms)

- 27.3.6 Average Login Time (ms)

- 27.3.7 Average Processing Time (ms)

- 27.3.8 Average Search Time (ms)

- 27.3.9 Average Upload Time (ms)

- 27.3.10 Deletes (per minute)

- 27.3.11 Download (per minute)

- 27.3.12 GetItems (per minute)

- 27.3.13 Invocations (per minute)

- 27.3.14 ListFolder (per minute)

- 27.3.15 Logins (per minute)

- 27.3.16 Searches (per minute)

- 27.3.17 Status

- 27.3.18 Successful Invocations (%)

- 27.3.19 Failed Invocations (%)

- 27.3.20 Uploads (per minute)

- 27.3.21 Service Name

- 27.4 WebCenter Events (Aggregated)

- 27.4.1 Application Name

- 27.4.2 Average Create Time (ms)

- 27.4.3 Average Delete Time (ms)

- 27.4.4 Average List Time (ms)

- 27.4.5 Average Processing Time (ms)

- 27.4.6 Average Search Time (ms)

- 27.4.7 Average Update Time (ms)

- 27.4.8 Creates (per minute)

- 27.4.9 Deletes (per minute)

- 27.4.10 Failed Invocations (%)

- 27.4.11 Invocations (per minute)

- 27.4.12 Lists (per minute)

- 27.4.13 Searches (per minute)

- 27.4.14 Status

- 27.4.15 Successful Invocations (%)

- 27.4.16 Updates (per minute)

- 27.4.17 Service Name

- 27.5 WebCenter External Applications (Aggregated)

- 27.5.1 Application Name

- 27.5.2 Automated Logins (per minute)

- 27.5.3 Average Automated Login Time (ms)

- 27.5.4 Average Fetch Credentials Time (ms)

- 27.5.5 Average Fetch External Applications Time (ms)

- 27.5.6 Average Processing Time (ms)

- 27.5.7 Average Store Credentials Time (ms)

- 27.5.8 Credential Fetches (per minute)

- 27.5.9 Credential Stores (per minute)

- 27.5.10 External Applications Fetches (per minute)

- 27.5.11 Failed Invocations (%)

- 27.5.12 Invocations (per minute)

- 27.5.13 Status

- 27.5.14 Successful Invocations (%)

- 27.5.15 Service Name

- 27.6 WebCenter Portlets (Aggregated)

- 27.6.1 Application Name

- 27.6.2 Failed Invocations (%)

- 27.6.3 Average HTTP 2xx Time (ms)

- 27.6.4 Average HTTP 3xx Time (ms)

- 27.6.5 Average HTTP 4xx Time (ms)

- 27.6.6 Average HTTP 5xx Time (ms)

- 27.6.7 Average Processing Time (ms)

- 27.6.8 Average HTTP 2xx Requests (per minute)

- 27.6.9 Average HTTP 3xx Requests (per minute)

- 27.6.10 Average HTTP 4xx Requests (per minute)

- 27.6.11 Average HTTP 5xx Requests (per minute)

- 27.6.12 Invocations (per minute)

- 27.6.13 Status

- 27.6.14 Successful Invocations (%)

- 27.6.15 Service Name

- 27.7 WebCenter Producers (Aggregated)

- 27.7.1 Application Name

- 27.7.2 Average HTTP 2xx Time (ms)

- 27.7.3 Average HTTP 3xx Time (ms)

- 27.7.4 Average HTTP 4xx Time (ms)

- 27.7.5 Average HTTP 5xx Time (ms)

- 27.7.6 Average Processing Time (ms)

- 27.7.7 Failed Invocations (%)

- 27.7.8 Average HTTP 2xx Requests (per minute)

- 27.7.9 Average HTTP 3xx Requests (per minute)

- 27.7.10 Average HTTP 4xx Requests (per minute)

- 27.7.11 Average HTTP 5xx Requests (per minute)

- 27.7.12 Invocations (per minute)

- 27.7.13 Status

- 27.7.14 Successful Invocations (%)

- 27.7.15 Service Name

- 27.8 WebCenter Search (Aggregated)

- 27.8.1 Application Name

- 27.8.2 Average Processing Time (ms)

- 27.8.3 Failed Invocations (%)

- 27.8.4 Invocations (per minute)

- 27.8.5 Status

- 27.8.6 Successful Invocations (%)

- 27.8.7 Service Name

- 27.9 WebCenter Services

- 27.9.1 Application Name

- 27.9.2 Average Processing Time (ms)

- 27.9.3 Failed Invocations (%)

- 27.9.4 Invocations (per minute)

- 27.9.5 Status

- 27.9.6 Successful Invocations (%)

- 27.10 WebCenter BPEL Worklists (Aggregated)

- 27.10.1 Application Name

- 27.10.2 Average Processing Time (ms)

- 27.10.3 Failed Invocations (%)

- 27.10.4 Invocations (per minute)

- 27.10.5 Status

- 27.10.6 Successful Invocations (%)

- 27.10.7 Service Name

- 27.11 WebCenter Portlets

- 27.11.1 Application Name

- 27.11.2 Average HTTP 2xx Time (ms)

- 27.11.3 Average HTTP 3xx Time (ms)

- 27.11.4 Average HTTP 4xx Time (ms)

- 27.11.5 Average HTTP 5xx Time (ms)

- 27.11.6 Average Processing Time (ms)

- 27.11.7 Failed Invocations (%)

- 27.11.8 Average HTTP 2xx Requests (per minute)

- 27.11.9 Average HTTP 3xx Requests (per minute)

- 27.11.10 Average HTTP 4xx Requests (per minute)

- 27.11.11 Average HTTP 5xx Requests (per minute)

- 27.11.12 Invocations (per minute)

- 27.11.13 Status

- 27.11.14 Successful Invocations (%)

- 27.11.15 Producer Type

- 27.12 WebCenter Producers

- 27.12.1 Application Name

- 27.12.2 Average HTTP 2xx Time (ms)

- 27.12.3 Average HTTP 3xx Time (ms)

- 27.12.4 Average HTTP 4xx Time (ms)

- 27.12.5 Average HTTP 5xx Time (ms)

- 27.12.6 Average Processing Time (ms)

- 27.12.7 Failed Invocations (%)

- 27.12.8 Average HTTP 2xx Requests (per minute)

- 27.12.9 Average HTTP 3xx Requests (per minute)

- 27.12.10 Average HTTP 4xx Requests (per minute)

- 27.12.11 Average HTTP 5xx Requests (per minute)

- 27.12.12 Invocations (per minute)

- 27.12.13 Status

- 27.12.14 Successful Invocations (%)

- 27.12.15 Producer Type

- 27.13 WebCenter Announcements

- 27.13.1 Application Name

- 27.13.2 Average Create Time (ms)

- 27.13.3 Average List Time (ms)

- 27.13.4 Average Login Time (ms)

- 27.13.5 Average Logout Time (ms)

- 27.13.6 Average Processing Time (ms)

- 27.13.7 Average Search Time (ms)

- 27.13.8 Creates (per minute)

- 27.13.9 Failed Invocations (%)

- 27.13.10 Invocations (per minute)

- 27.13.11 Lists (per minute)

- 27.13.12 Logins (per minute)

- 27.13.13 Logouts (per minute)

- 27.13.14 Searches (per minute)

- 27.13.15 Status

- 27.13.16 Successful Invocations (%)

- 27.13.17 Service Name

- 27.14 WebCenter Spaces

- 27.14.1 Application Name

- 27.14.2 Failed Invocations (%)

- 27.14.3 Successful Invocations (%)

- 27.14.4 Invocations (per minute)

- 27.14.5 Page Throughput (per minute)

- 27.14.6 Errors (per minute)

- 27.14.7 Average Page Processing Time (ms)

- 27.15 WebCenter Content Repositories

- 27.15.1 Application Name

- 27.15.2 Average Delete Time (ms)

- 27.15.3 Average Download Time (ms)

- 27.15.4 Average Get Item Time (ms)

- 27.15.5 Average List Folder Time (ms)

- 27.15.6 Average Login Time (ms)

- 27.15.7 Average Processing Time (ms)

- 27.15.8 Average Search Time (ms)

- 27.15.9 Average Upload Time (ms)

- 27.15.10 Deletes (per minute)

- 27.15.11 Downloads (per minute)

- 27.15.12 Download Throughput (bytes per second)

- 27.15.13 Failed Invocations (%)

- 27.15.14 Get Item

- 27.15.15 Invocations (per minute)

- 27.15.16 List Folder

- 27.15.17 Logins (per minute)

- 27.15.18 Searches (per minute)

- 27.15.19 Status

- 27.15.20 Successful Invocations (%)

- 27.15.21 Uploads (per minute)

- 27.15.22 Upload Throughput (bytes per second)

- 27.16 WebCenter Events

- 27.16.1 Application Name

- 27.16.2 Average Create Time (ms)

- 27.16.3 Average Delete Time (ms)

- 27.16.4 Average List Time (ms)

- 27.16.5 Average Processing Time (ms)

- 27.16.6 Average Search Time (ms)

- 27.16.7 Average Update Time (ms)

- 27.16.8 Creates (per minute)

- 27.16.9 Deletes (per minute)

- 27.16.10 Failed Invocations (%)

- 27.16.11 Invocations (per minute)

- 27.16.12 Lists (per minute)

- 27.16.13 Searches (per minute)

- 27.16.14 Status

- 27.16.15 Successful Invocations (%)

- 27.16.16 Updates (per minute)

- 27.17 WebCenter External Applications Connections

- 27.17.1 Application Name

- 27.17.2 Invocations (per minute)

- 27.18 WebCenter External Applications

- 27.18.1 Application Name

- 27.18.2 Automated Logins (per minute)

- 27.18.3 Average Automated Login Time (ms)

- 27.18.4 Average Fetch Credential Time (ms)

- 27.18.5 Average Fetch External Application Time (ms)

- 27.18.6 Average Processing Time (ms)

- 27.18.7 Average Store Credentials Time (ms)

- 27.18.8 Credential Fetches (per minute)

- 27.18.9 Credential Stores (per minute)

- 27.18.10 External Application Fetches (per minute)

- 27.18.11 Failed Invocations (%)

- 27.18.12 Invocations (per minute)

- 27.18.13 Status

- 27.18.14 Successful Invocations (%)

- 27.18.15 Name

- 27.19 WebCenter Discussion Forum

- 27.19.1 Application Name

- 27.19.2 Average Create Forum Time (ms)

- 27.19.3 Average Create Topic Time (ms)

- 27.19.4 Average List Forums Time (ms)

- 27.19.5 Average List Topics Time (ms)

- 27.19.6 Average Login Time (ms)

- 27.19.7 Average Logout Time (ms)

- 27.19.8 Average Processing Time (ms)

- 27.19.9 Average Reply Time (ms)

- 27.19.10 Average Search Time (ms)

- 27.19.11 Create Forum (per minute)

- 27.19.12 Create Topic (per minute)

- 27.19.13 Failed Invocations (%)

- 27.19.14 Invocations (per minute)

- 27.19.15 List Forums (per minute)

- 27.19.16 List Topics (per minute)

- 27.19.17 Logins (per minute)

- 27.19.18 Logouts (per minute)

- 27.19.19 Replies (per minute)

- 27.19.20 Searches (per minute)

- 27.19.21 Status

- 27.19.22 Successful Invocations (%)

- 27.19.23 Service Name

- 27.20 WebCenter Pages

- 27.20.1 Application Name

- 27.20.2 Average Page Processing Time (ms)

- 27.20.3 Average Partial Page Processing Time (ms)

- 27.20.4 Errors (per minute)

- 27.20.5 Failed Invocations (%)

- 27.20.6 Invocations (per minute)

- 27.20.7 Page Throughput (per minute)

- 27.20.8 Partial Page Invocations (per minute)

- 27.20.9 Status

- 27.20.10 Successful Invocations (%)

- 27.21 WebCenter Import/Export

- 27.21.1 Application Name

- 27.21.2 Average Processing Time (ms)

- 27.21.3 Failed Invocations (%)

- 27.21.4 Invocations (per minute)

- 27.21.5 Status

- 27.21.6 Successful Invocations (%)

- 27.21.7 Service Name

- 27.22 WebCenter Lists

- 27.22.1 Application Name

- 27.22.2 Average Copy List Time (ms)

- 27.22.3 Average Copy List Type Time (ms)

- 27.22.4 Average Copy Rows Time (ms)

- 27.22.5 Average Create List Time (ms)

- 27.22.6 Average Create List Type Time (ms)

- 27.22.7 Average Create Row Time (ms)

- 27.22.8 Average Delete List Time (ms)

- 27.22.9 Average Delete List Type Time (ms)

- 27.22.10 Average Delete Row Time (ms)

- 27.22.11 Average Processing Time (ms)

- 27.22.12 Average Query Time (ms)

- 27.22.13 Average Retrieve Rows Time (ms)

- 27.22.14 Average Save Time (ms)

- 27.22.15 Average Update Row Time (ms)

- 27.22.16 Copy List (per minute)

- 27.22.17 Copy List Type (per minute)

- 27.22.18 Copy Rows (per minute)

- 27.22.19 Create List (per minute)

- 27.22.20 Create List Type (per minute)

- 27.22.21 Create Row (per minute)

- 27.22.22 Delete List (per minute)

- 27.22.23 Delete List Type (per minute)

- 27.22.24 Delete Row (per minute)

- 27.22.25 Failed Invocations (%)

- 27.22.26 Invocations (per minute)

- 27.22.27 Queries (per minute)

- 27.22.28 Retrieve Rows (per minute)

- 27.22.29 Saves (per minute)

- 27.22.30 Status

- 27.22.31 Successful Invocations (%)

- 27.22.32 Update Row (per minute)

- 27.22.33 Service Name

- 27.23 WebCenter Mail

- 27.23.1 Application Name

- 27.23.2 Average Login Time (ms)

- 27.23.3 Average Logout Time (ms)

- 27.23.4 Average Processing Time (ms)

- 27.23.5 Average Receive Time (ms)

- 27.23.6 Average Search Time (ms)

- 27.23.7 Average Send Time (ms)

- 27.23.8 Failed Invocations (%)

- 27.23.9 Invocations (per minute)

- 27.23.10 Logins (per minute)

- 27.23.11 Logout (per minute)

- 27.23.12 Receives (per minute)

- 27.23.13 Searches (per minute)

- 27.23.14 Sends (per minute)

- 27.23.15 Status

- 27.23.16 Successful Invocations (%)

- 27.23.17 Service Name

- 27.24 WebCenter Notes

- 27.24.1 Application Name

- 27.24.2 Average Create Time (ms)

- 27.24.3 Average Delete Time (ms)

- 27.24.4 Average Find Time (ms)

- 27.24.5 Average Processing Time (ms)

- 27.24.6 Average Save Changes Time (ms)

- 27.24.7 Average Update Time (ms)

- 27.24.8 Creates (per minute)

- 27.24.9 Deletes (per minute)

- 27.24.10 Failed Invocations (%)

- 27.24.11 Finds (per minute)

- 27.24.12 Invocations (per minute)

- 27.24.13 Save Changes (per minute)

- 27.24.14 Status

- 27.24.15 Successful Invocations (%)

- 27.24.16 Updates (per minute)

- 27.24.17 Service Name

- 27.25 WebCenter Page Service

- 27.25.1 Application Name

- 27.25.2 Average Copy Time (ms)

- 27.25.3 Average Create Time (ms)

- 27.25.4 Average Delete Time (ms)

- 27.25.5 Average Processing Time (ms)

- 27.25.6 Average Search Time (ms)

- 27.25.7 Average Update Time (ms)

- 27.25.8 Copies (per minute)

- 27.25.9 Creates (per minute)

- 27.25.10 Deletes (per minute)

- 27.25.11 Failed Invocations (%)

- 27.25.12 Invocations (per minute)

- 27.25.13 Searches (per minute)

- 27.25.14 Status

- 27.25.15 Updates (per minute)

- 27.25.16 Successful Invocations (%)

- 27.25.17 Service Name

- 27.26 WebCenter People Connections

- 27.26.1 Application name

- 27.26.2 Average Processing Time (ms)

- 27.26.3 Failed Invocations (%)

- 27.26.4 Get Feedback (per minute)

- 27.26.5 Get Feedback Average Time (ms)

- 27.26.6 Invocations (per minute)

- 27.26.7 Publish Activity (per minute)

- 27.26.8 Publish Activity Average Time (ms)

- 27.26.9 Retrieve Activities (per minute)

- 27.26.10 Retrieve Activities Average Time (ms)

- 27.26.11 Retrieve Connections Average Time (ms)

- 27.26.12 Retrieve Messages (per minute)

- 27.26.13 Retrieve Messages Average Time (ms)

- 27.26.14 Retrieve Profiles (per minute)

- 27.26.15 Retrieve Profiles Average Time (ms)

- 27.26.16 Status

- 27.26.17 Successful Invocations (%)

- 27.26.18 Service Name

- 27.27 WebCenter Polls

- 27.27.1 Application Name

- 27.27.2 Analyze Poll (per minute)

- 27.27.3 Analyze Poll Average Time (ms)

- 27.27.4 Average Processing Time (ms)

- 27.27.5 Create Poll (per minute)

- 27.27.6 Create Poll Average Time (ms)

- 27.27.7 Create Response (per minute)

- 27.27.8 Create Response Average Time (ms)

- 27.27.9 Delete Poll (per minute)

- 27.27.10 Delete Poll Average Time (ms)

- 27.27.11 Edit Poll (per minute)

- 27.27.12 Edit Poll Average Time (ms)

- 27.27.13 Failed Invocations (%)

- 27.27.14 Get Poll (per minute)

- 27.27.15 Get Poll By Id (per minute)

- 27.27.16 Get Poll By Id Average Time (ms)

- 27.27.17 Get Poll Response Average Time (per minute)

- 27.27.18 Status

- 27.27.19 Successful Invocations (%)

- 27.27.20 Invocations (per minute)

- 27.27.21 Service Name

- 27.28 WebCenter Recent Activity

- 27.28.1 Application Name

- 27.28.2 Average Processing Time (ms)

- 27.28.3 Failed Invocations (%)

- 27.28.4 Invocations (per minute)

- 27.28.5 Status

- 27.28.6 Successful Invocations (%)

- 27.28.7 Service Name

- 27.29 WebCenter RSS News Feeds

- 27.29.1 Application Name

- 27.29.2 Average Processing Time (ms)

- 27.29.3 Failed Invocations (%)

- 27.29.4 Invocations (per minute)

- 27.29.5 Status

- 27.29.6 Successful Invocations (%)

- 27.29.7 Service Name

- 27.30 WebCenter Instant Messaging and Presence

- 27.30.1 Application Name

- 27.30.2 Average Get Presence Time (ms)

- 27.30.3 Average Login Time (ms)

- 27.30.4 Average Logout Time (ms)

- 27.30.5 Average Processing Time (ms)

- 27.30.6 Failed Invocations (%)

- 27.30.7 Get Presence (per minute)

- 27.30.8 Invocations (per minute)

- 27.30.9 Logins (per minute)

- 27.30.10 Logouts (per minute)

- 27.30.11 Status

- 27.30.12 Successful Invocations (%)

- 27.30.13 Service Name

- 27.31 WebCenter Search

- 27.31.1 Application Name

- 27.31.2 Failed Invocations (%)

- 27.31.3 Successful Invocations (%)

- 27.31.4 Invocations (per minute)

- 27.31.5 Query Throughput (queries per minute)

- 27.31.6 Status

- 27.31.7 Average Processing Time (ms)

- 27.32 WebCenter BPEL Worklists

- 27.32.1 Application Name

- 27.32.2 Failed Invocations (%)

- 27.32.3 Status

- 27.32.4 Successful Invocations (%)

- 27.32.5 Invocations (per minute)

- 27.32.6 Average Processing Time (ms)

28 Web Cache

- 28.1 Performance by Web Cache Instance

- 28.1.1 Instance

- 28.1.2 Request Processing Time (milli seconds)

- 28.1.3 Request Throughput (per second)

- 28.2 Resource Usage

- 28.2.1 CPU Usage (%)

- 28.2.2 CPU Idle Time (%)

- 28.2.3 Other CPU Usage (%)

- 28.2.4 Memory Usage (MB)

- 28.2.5 Free Memory (MB)

- 28.2.6 Other Memory Usage (MB)

- 28.2.7 Total Memory (MB)

- 28.2.8 Memory Usage (%)

- 28.2.9 Free Memory (%)

- 28.2.10 Other Memory Usage (%)

- 28.2.11 Start Time (ms since Epoch)

- 28.2.12 Up Time (ms since Epoch)

- 28.3 Response

- 28.3.1 Response Admin

- 28.3.2 Admin Process Status

- 28.3.3 Response - Status

- 28.4 Performance of each Site with Summary

- 28.4.1 Total Number of Bytes Saved by Compression

- 28.4.2 Cache Size

- 28.4.3 Total Number Error Pages Served

- 28.4.4 Hit Rate (in %)

- 28.4.5 Number of Cached

- 28.4.6 Currently Open connections

- 28.4.7 Total Number of Requests Denied

- 28.4.8 Total Number of Requests Served

- 28.5 WebCache_nontimedHost

- 28.5.1 Capacity.value

- 28.5.2 Load.value

- 28.5.3 MaxLoad.value

- 28.5.4 Port.value

- 28.6 WebCache_timedHost

- 28.6.1 AvgLatency.value

- 28.6.2 Latency.value

- 28.6.3 Request.value

- 28.6.4 RequestFailure.value

29 Oracle Directory Server Enterprise Edition

- 29.1 Cache Memory Thresholds

- 29.1.1 Heap High Hits

- 29.1.2 Heap High Hits (per sec)

- 29.1.3 Heap High Hits (per sec) (since startup)

- 29.1.4 Heap High Hits (since startup)

- 29.1.5 Heap Low Hits

- 29.1.6 Heap Low Hits (per sec)

- 29.1.7 Heap Low Hits (per sec) (since startup)

- 29.1.8 Heap Low Hits (since startup)

- 29.2 Compare Operations Elapsed Time Metrics

- 29.2.1 Average Elapsed Time per Compare Operation (ms)

- 29.2.2 Average Elapsed Time per Compare Operation (since startup) (ms)

- 29.2.3 LDAP Compare operations (since startup)

- 29.2.4 Total Elapsed Time for all Compare Operations (ms)

- 29.2.5 Total Elapsed Time for Compare Operations (since startup) (ms)

- 29.2.6 Total Elapsed Time Squared for Search Operations (since startup) (ms)

- 29.3 Compare Operations Metrics

- 29.3.1 Compare Operations

- 29.3.2 Compare Operations (per sec)

- 29.3.3 Compare Operations (per sec) (since startup)

- 29.3.4 Compare Operations (since startup)

- 29.4 Connections Metrics

- 29.4.1 Connections Peak

- 29.4.2 Connections Per Sec

- 29.4.3 Connections Per Sec (s start)

- 29.4.4 Current Connections

- 29.5 Database Cache Metrics

- 29.5.1 Cache Clean Pages

- 29.5.2 Cache Dirty Pages

- 29.5.3 Cache Hits

- 29.5.4 Cache Page Reads

- 29.5.5 Cache Page Writes

- 29.5.6 Cache Tries

- 29.6 Errors Metrics

- 29.6.1 Bind Security Errors

- 29.6.2 Bind Security Errors (Since Start)

- 29.6.3 Operational Errors

- 29.6.4 Operational Errors (Since Start)

- 29.6.5 Security Errors

- 29.6.6 Security Errors (Since Start)

- 29.6.7 Total Errors

- 29.6.8 Total Errors (Since Start)

- 29.7 General Information

- 29.7.1 Backend

- 29.7.2 Current Time

- 29.7.3 Start Time

- 29.7.4 Version

- 29.8 Hashtable Metrics

- 29.8.1 Hash Elements Traversed

- 29.8.2 Hash Elements Traversed (per sec)

- 29.8.3 Hash Elements Traversed (per sec since startup)

- 29.8.4 Hash Elements Traversed (since startup)

- 29.8.5 Hash Table Lookups

- 29.8.6 Hash Table Lookups (per sec)

- 29.8.7 Hash Table Lookups (per sec since start)

- 29.8.8 Hash Table Lookups (since startup)

- 29.8.9 Longest Chain During Hash Lookups

- 29.9 In Out Operation

- 29.9.1 Bytes Returned

- 29.9.2 Bytes Returned (per sec)

- 29.9.3 Bytes Returned (per sec since startup)

- 29.9.4 Bytes Returned (since startup)

- 29.9.5 LDAP Entries Returned

- 29.9.6 LDAP Entries Returned (per sec)

- 29.9.7 LDAP Entries Returned (per sec) (since startup)

- 29.9.8 LDAP Entries Returned (since startup)

- 29.9.9 Referrals Returned

- 29.9.10 Referrals Returned (per sec)

- 29.9.11 Referrals Returned (per sec) (since startup)

- 29.9.12 Referrals Returned (since startup)

- 29.10 Locks and DeadLocks

- 29.10.1 Current Database Locks

- 29.10.2 Current Lockers

- 29.10.3 Detected Deadlocks

- 29.10.4 DeadLocks Detected (per sec)

- 29.10.5 DeadLocks Detected (per sec since startup)

- 29.10.6 DeadLocks Detected (since startup)

- 29.10.7 Lock Conflicts

- 29.10.8 Lock Conflicts (per sec)

- 29.10.9 Lock Conflicts (per sec since startup)

- 29.10.10 Lock Conflicts (since startup)

- 29.10.11 Maximum Database Locks

- 29.10.12 Total locks Requested

- 29.10.13 Total locks Requested (per sec)

- 29.10.14 Total locks Requested (per sec) (since startup)

- 29.10.15 Total locks Requested (since startup)

- 29.10.16 Waits before Database Lock

- 29.10.17 Waits before Database Lock (per sec)

- 29.10.18 Waits before Database Lock (per sec since startup)

- 29.10.19 Waits before Database Lock (since startup)

- 29.11 Operations Metrics

- 29.11.1 Average Elapsed Time per Operation (ms)

- 29.11.2 Average Elapsed Time per Operation (since startup )(ms)

- 29.11.3 Total Elapsed Time for all Operations (ms)

- 29.11.4 Total Elapsed Time for all Operations (since startup) (ms)

- 29.11.5 Total LDAP Operations Completed

- 29.11.6 Total LDAP Operations Completed (per sec)

- 29.11.7 Total LDAP Operations Completed (per sec) (since startup)

- 29.11.8 Total LDAP Operations Completed (since startup)

- 29.11.9 Total Operations Completed

- 29.11.10 Total Operations Completed (per sec)

- 29.11.11 Total Operations Completed (per sec) (since startup)

- 29.11.12 Total Operations Completed (since startup)

- 29.11.13 Total Operations Initiated

- 29.11.14 Total Operations Initiated (per sec)

- 29.11.15 Total Operations Initiated (per sec) (since startup)

- 29.11.16 Total Operations Initiated (since startup)

- 29.12 Other Operations

- 29.12.1 LDAP Referral Operations

- 29.12.2 LDAP Referral Operations (per sec)

- 29.12.3 LDAP Referral Operations (per sec) (since startup)

- 29.12.4 LDAP Referral Operations (since startup)

- 29.12.5 Persistent Searches Running

- 29.13 Queues Metrics

- 29.13.1 Operations In Progress

- 29.13.2 Operations Queue Back Log

- 29.13.3 Read Waiters Queue

- 29.14 Read Operations Elapsed Time Metrics

- 29.14.1 Average Elapsed Time per Bind Operation (ms)

- 29.14.2 Average Elapsed Time per Bind Operation (since startup) (ms)

- 29.14.3 Average Elapsed Time per Search Operation (ms)

- 29.14.4 Average Elapsed Time per Search Operation (since startup) (ms)

- 29.14.5 Average Elapsed Time per UnBind Operation (ms)

- 29.14.6 Average Elapsed Time per Unbind Operation (since startup) (ms)

- 29.14.7 LDAP Binds (since startup)

- 29.14.8 LDAP Searches (since startup)

- 29.14.9 Total Elapsed Time for Bind Operations (ms)

- 29.14.10 Total Elapsed Time for Bind Operations (since startup) (ms)

- 29.14.11 Total Elapsed Time for Search Operations (ms)

- 29.14.12 Total Elapsed Time for Search Operations (since startup) (ms)

- 29.14.13 Total Elapsed Time for UnBind Operations (ms)

- 29.14.14 Total Elapsed Time for UnBind Operations (since startup) (ms)

- 29.14.15 Total Elapsed Time Squared for Bind Operations (since startup) (ms)

- 29.14.16 Total Elapsed Time Squared for Search Operations (since startup) (ms)

- 29.14.17 Total Elapsed Time Squared for UnBind Operations (since startup) (ms)

- 29.15 Read Operations Metrics

- 29.15.1 Anonymous Binds

- 29.15.2 Anonymous binds (per sec)

- 29.15.3 Anonymous Binds (per sec) (since startup)

- 29.15.4 Anonymous Binds (since startup)

- 29.15.5 LDAP Binds

- 29.15.6 LDAP Binds (per sec)

- 29.15.7 LDAP Binds (per sec) (since startup)

- 29.15.8 LDAP Binds (since startup)

- 29.15.9 Simple Authorized Binds (per sec) (since startup)

- 29.15.10 Simple Authorized Binds (since startup)

- 29.15.11 Simple Binds

- 29.15.12 Simple Binds (per sec)

- 29.15.13 Strong Authorized Binds (per sec) (since startup)

- 29.15.14 Strong Authorized Binds (since startup)

- 29.15.15 Strong Binds

- 29.15.16 Strong Binds (per sec)

- 29.15.17 Unauthorized Binds

- 29.15.18 Unauthorized Binds (per sec)

- 29.15.19 Unauthorized Binds (per sec) (since startup)

- 29.15.20 Unauthorized Binds (since startup)

- 29.16 Resource Usage

- 29.16.1 CPU Utilization (%)

- 29.16.2 Memory Utilization (KB)

- 29.16.3 Memory Utilization (%)

- 29.17 Response

- 29.17.1 Status

- 29.18 Suffix-Backend Entry

- 29.18.1 Suffix-Backend Entry - Average Cache Size

- 29.18.2 Suffix-Backend Entry - Cache Count

- 29.18.3 Suffix-Backend Entry - Cache Hit Ratio

- 29.18.4 Suffix-Backend Entry - Cache Hits

- 29.18.5 Suffix-Backend Entry - Cache Hits (per sec)

- 29.18.6 Suffix-Backend Entry - Cache Hits (per sec) (since startup)

- 29.18.7 Suffix-Backend Entry - Cache Hits (since startup)

- 29.18.8 Suffix-Backend Entry - Cache Size

- 29.18.9 Suffix-Backend Entry - Cache Tries

- 29.18.10 Suffix-Backend Entry - Cache Tries (per sec)

- 29.18.11 Suffix-Backend Entry - Cache Tries (per sec) (since startup)

- 29.18.12 Suffix-Backend Entry - Cache Tries (since startup)

- 29.18.13 Suffix-Backend Name

- 29.19 Suffix-Backend File Metrics

- 29.19.1 Suffix-Backend File - Cache Hit Ratio

- 29.19.2 Suffix-Backend File - Cache Hits

- 29.19.3 Suffix-Backend File - Cache Hits (per sec)

- 29.19.4 Suffix-Backend File - Cache Hits (per sec) (since startup)

- 29.19.5 Suffix-Backend File - Cache Hits (since startup)

- 29.19.6 Suffix-Backend File - Cache Misses

- 29.19.7 Suffix-Backend File - Cache Misses (per sec)

- 29.19.8 Suffix-Backend File - Cache Misses (per sec) (since startup)

- 29.19.9 Suffix-Backend File - Cache Misses (since startup)

- 29.19.10 Suffix-Backend File - Pages in to Cache

- 29.19.11 Suffix-Backend File - Pages in to Cache (per sec)

- 29.19.12 Suffix-Backend File - Pages in to Cache (per sec) (since startup)

- 29.19.13 Suffix-Backend File - Pages in to Cache (since startup)

- 29.19.14 Suffix-Backend File - Pages Out to Disk

- 29.19.15 Suffix-Backend File - Pages Out to Disk (per sec)

- 29.19.16 Suffix-Backend File - Pages Out to Disk (per sec) (since startup)

- 29.19.17 Suffix-Backend File - Pages Out to Disk (since startup)

- 29.20 Suffix-Backends General Information

- 29.20.1 Suffix-Backend Name

- 29.20.2 Suffix-Backend Next DB entry ID

- 29.20.3 Suffix-Backend State

- 29.20.4 Suffix-Backend Total DB Entry Count

- 29.20.5 Suffix-Backend LDAP Entry Count

- 29.21 Transaction Log Metrics

- 29.21.1 Bytes wrote to log

- 29.21.2 Bytes wrote to log (per sec)

- 29.21.3 Bytes Wrote to Log (per sec) (since last check point)

- 29.21.4 Bytes Wrote to Log (since last check point)

- 29.21.5 Log Flushes

- 29.21.6 Log Flushes (per sec)

- 29.21.7 Log Flushes (per sec) (since startup)

- 29.21.8 Log Flushes (since startup)

- 29.21.9 Log Flushes by In-Memory Full

- 29.21.10 Log Flushes by In-Memory Full (per sec)

- 29.21.11 Log Flushes by In-Memory Full (per sec) (since startup)

- 29.21.12 Log Flushes by In-Memory Full (since startup)

- 29.21.13 Log Flushes with Commits

- 29.21.14 Log Flushes with Commits (per sec)

- 29.21.15 Log Flushes with Commits (per sec) (since startup)

- 29.21.16 Log Flushes with Commits (since startup)

- 29.21.17 Log Written to Disk

- 29.21.18 Log Written to Disk (per sec)

- 29.21.19 Log Written to Disk (per sec) (since startup)

- 29.21.20 Log Written to Disk (since startup)

- 29.21.21 Maximum Commits in Log Flush

- 29.21.22 Minimum Commits in Log Flush

- 29.21.23 Waits before getting the Log Lock

- 29.21.24 Waits before getting the Log Lock (per sec)

- 29.21.25 Waits before getting the Log Lock (per sec) (since startup)

- 29.21.26 Waits before getting the Log Lock (since startup)

- 29.22 Transactions

- 29.22.1 Aborted Transactions

- 29.22.2 Aborted Transactions (per sec)

- 29.22.3 Aborted Transactions (per sec) (since startup)

- 29.22.4 Aborted Transactions (since startup)

- 29.22.5 Committed Transactions

- 29.22.6 Committed Transactions (per sec)

- 29.22.7 Committed Transactions (per sec) (since startup)

- 29.22.8 Committed Transactions (since startup)

- 29.22.9 Current Active Transactions

- 29.22.10 Maximum Transactions Used

- 29.22.11 Waits before Transaction Locks

- 29.22.12 Waits before Transaction Locks (per sec)

- 29.22.13 Waits before Transaction Locks (per sec) (since startup)

- 29.22.14 Waits before Transaction Locks (since startup)

- 29.23 Write Operations Elapsed Time Metrics

- 29.23.1 Average Elapsed Time per Add Operation (ms)

- 29.23.2 Average Elapsed Time per Add Operation (since startup) (ms)

- 29.23.3 Average Elapsed Time per Delete Operation (ms)

- 29.23.4 Average Elapsed Time per Delete Operation (since startup) (ms)

- 29.23.5 Average Elapsed Time per Modify Operation (ms)

- 29.23.6 Average Elapsed Time per Modify Operation (since startup) (ms)

- 29.23.7 Average Elapsed Time per Modify RDN Operation (ms)

- 29.23.8 Average Elapsed Time per Modify RDN Operation (since startup) (ms)

- 29.23.9 LDAP Add operations (since startup)

- 29.23.10 LDAP Delete operations (since startup)

- 29.23.11 LDAP Modify operations (since startup)

- 29.23.12 LDAP Modify RDN operations (since startup)

- 29.23.13 Total Elapsed Time for Add Operations (since startup) (ms)

- 29.23.14 Total Elapsed Time for all Add Operations (ms)

- 29.23.15 Total Elapsed Time for all Delete Operations (ms)

- 29.23.16 Total Elapsed Time for all Modify Operations (ms)

- 29.23.17 Total Elapsed Time for all Modify RDN Operations (ms)

- 29.23.18 Total Elapsed Time for Delete Operations (since startup) (ms)

- 29.23.19 Total Elapsed Time for Modify Operations (since startup) (ms)

- 29.23.20 Total Elapsed Time for Modify RDN Operations (since startup) (ms)

- 29.23.21 Total Elapsed Time Squared for Add Operations (since startup) (ms)

- 29.23.22 Total Elapsed Time Squared for Delete Operations (since startup) (ms)

- 29.23.23 Total Elapsed Time Squared for Modify Operations (since startup) (ms)

- 29.23.24 Total Elapsed Time Squared for Modify RDN Operations (since startup) (ms)

- 29.24 Write Operations Metrics

- 29.24.1 Add Operations

- 29.24.2 Add Operations (per sec)

- 29.24.3 Add Operations (per sec) (since startup)

- 29.24.4 Add Operations (since startup)

- 29.24.5 Delete Operations

- 29.24.6 Delete Operations (per sec)

- 29.24.7 Delete Operations (per sec) (since startup)

- 29.24.8 Delete Operations (since startup)

- 29.24.9 Modify Operations

- 29.24.10 Modify Operations (per sec)

- 29.24.11 Modify Operations (per sec) (since startup)

- 29.24.12 Modify Operations (since startup)

- 29.24.13 Modify RDN (since startup)

- 29.24.14 Modify RDN Operations

- 29.24.15 Modify RDN Operations (per sec)

- 29.24.16 Modify RDN Operations (per sec) (since startup)

30 OC4J Metrics

- 30.1 OC4J All Instances Metrics

- 30.1.1 OC4J Instances - Active Sessions

- 30.1.2 OC4J Instances - Request Processing Time (seconds)

- 30.1.3 OC4J Instances - Requests Per Second

- 30.2 OC4J Application Metrics

- 30.2.1 Application - Active Requests

- 30.2.2 Application - Active Sessions

- 30.2.3 Application - EJB Method Execution Rate (per second)

- 30.2.4 Application - EJB Method Execution Time (seconds)

- 30.2.5 Application - Request Processing Time (seconds)

- 30.2.6 Application - Requests Per Second

- 30.2.7 Application - Active EJB Methods

- 30.3 OC4J EJB Metrics

- 30.3.1 EJB - Active Methods

- 30.3.2 EJB - Method Execution Rate (per second)

- 30.3.3 EJB - Method Execution Time (seconds)

- 30.3.4 Type of EJB

- 30.4 OC4J EJB Module Metrics

- 30.4.1 EJB Module - Active Methods

- 30.4.2 EJB Module - Method Execution Rate (per second)

- 30.4.3 EJB Module - Method Execution Time (seconds)

- 30.5 OC4J Instance Metrics

- 30.5.1 OC4J Instance - Active Transactions

- 30.5.2 OC4J Instance - Active EJB Methods

- 30.5.3 OC4J Instance - Active Requests

- 30.5.4 OC4J Instance - Active Sessions

- 30.5.5 OC4J Instance - EJB Method Execution Rate (per second)

- 30.5.6 OC4J Instance - EJB Method Execution Time (seconds)

- 30.5.7 OC4J Instance - Heap Usage (MB)

- 30.5.8 OC4J Instance - Open JDBC Connections

- 30.5.9 OC4J Instance - Request Processing Time (seconds)

- 30.5.10 OC4J Instance - Requests Per Second

- 30.5.11 OC4J Instance - Start Time (ms since Epoch)

- 30.6 OC4J JSP Metrics

- 30.6.1 Is multi-threaded?

- 30.6.2 JSP - Active Instances (STM only)

- 30.6.3 JSP - Active Requests

- 30.6.4 JSP - Available Instances

- 30.6.5 JSP - Available Instances (STM only)

- 30.6.6 JSP - Client Processing Time (seconds)

- 30.6.7 JSP - Requests Per Second

- 30.7 OC4J JVM Metrics

- 30.7.1 JVM - CPU Usage (%)

- 30.7.2 JVM - Active EJB Methods

- 30.7.3 JVM - Heap Usage (MB)

- 30.7.4 JVM - Memory Usage (MB)

- 30.7.5 JVM - Active Requests

- 30.7.6 JVM - Start Time (ms since Epoch)

- 30.7.7 JVM - Active Threads

- 30.7.8 PID

- 30.8 OC4J Servlet Metrics

- 30.8.1 Servlet - Active Requests

- 30.8.2 Servlet - Client Processing Time (seconds)

- 30.8.3 Servlet - Requests Per Second

- 30.9 OC4J Web Module Metrics

- 30.9.1 Web Module - Active Requests

- 30.9.2 Web Module - Active Sessions

- 30.9.3 Web Module - Class Load Time (seconds)

- 30.9.4 Web Module - Client Time (seconds)

- 30.9.5 Web Module - Request Processing Time (seconds)

- 30.9.6 Web Module - Requests Per Second

- 30.10 Resource Usage Metrics

- 30.10.1 CPU Usage (%)

- 30.10.2 CPU Idle Time (%)

- 30.10.3 Other CPU Usage (%)

- 30.10.4 Memory Usage (MB)

- 30.10.5 Free Memory (MB)

- 30.10.6 Other Memory Usage (MB)

- 30.10.7 Memory Usage (%)

- 30.11 Response Metrics

- 30.11.1 UpDown Status

- 30.12 OC4J JMS Metrics

- 30.12.1 JMS - Active Connections

- 30.12.2 JMS - Messages Waiting for Read

- 30.12.3 JMS - Messages Dequeued Rate

- 30.12.4 JMS - Messages Enqueued Rate

- 30.12.5 JMS - Messages Paged In Rate

- 30.12.6 JMS - Messages Paged Out Rate

- 30.12.7 JMS - Messages Committed Since Startup

- 30.12.8 JMS - Messages Discarded Since Startup

- 30.12.9 JMS - Messages Expired Since Startup

- 30.12.10 JMS - Messages Recovered Since Startup

- 30.12.11 JMS - Messages Rolledback Since Startup

- 30.12.12 JMS - Messages Waiting For Commit

- 30.12.13 JMS - Start Time

- 30.13 OC4J Web Services Metrics

- 30.13.1 WebService - Faults Since Startup

- 30.13.2 WebService - Active Requests

- 30.13.3 WebService - Requests Since Startup

- 30.13.4 WebService - Requests Per Second

- 30.13.5 WebService - Request Processing Time

- 30.13.6 WebService - Start Time

- 30.13.7 WebService - Error Rate

31 Oracle Application Server Metrics

- 31.1 Application Response Metrics

- 31.1.1 Application URL Response Time (seconds)

- 31.1.2 Application URL Status

- 31.2 OPMN Process Information Metrics

- 31.2.1 Component CPU Usage (%)

- 31.2.2 Component Memory Usage (%)

- 31.2.3 Component Memory Usage (MB)

- 31.2.4 Component Start Time (ms since epoch)

- 31.2.5 Component Up Time (ms)

- 31.2.6 Component Up/down Status

- 31.2.7 Free Memory (%)

- 31.2.8 Free Memory (MB)

- 31.2.9 Idle CPU Time (%)

- 31.2.10 Total Memory (MB)

- 31.3 Resource Usage Metrics

- 31.3.1 CPU Idle Time (%)

- 31.3.2 CPU Usage (%)

- 31.3.3 Free Memory (%)

- 31.3.4 Free Memory (MB)

- 31.3.5 Memory Usage (%)

- 31.3.6 Memory Usage (MB)

- 31.3.7 Other CPU Usage (%)

- 31.3.8 Other Memory Usage (%

- 31.3.9 Other Memory Usage (MB)

- 31.3.10 Total Memory (MB)

- 31.4 Response Metrics

- 31.4.1 UpDown Status

32 IBM WebSphere Application Server Metrics

- 32.1 Applications Metrics

- 32.1.1 Applications - Active Requests

- 32.1.2 Applications - Average EJB Method Execution Time

- 32.1.3 No. of Active EJB Methods

- 32.1.4 Request Processing Time

- 32.1.5 Applications - Status

- 32.2 Dynamic Cache Metrics

- 32.2.1 DynaCache - InMemory Cache Size

- 32.2.2 DynaCache - Max InMemory Cache Size

- 32.2.3 DynaCache - Total Timeout Invalidations

- 32.3 EJB Metrics

- 32.3.1 EJB - Active Methods

- 32.3.2 Current Average Execution Time

- 32.3.3 Method Execution Rate per second

- 32.3.4 Total Method Calls

- 32.4 EJBModule Metrics

- 32.4.1 Active Methods

- 32.4.2 Average Method Execution Time During Last Interval

- 32.4.3 Avg Method Response Time

- 32.4.4 Concurrent Lives

- 32.4.5 Current Average Method Execution Time

- 32.4.6 Destroys

- 32.4.7 Instantiates

- 32.4.8 Number of EJB Methods Executed During Last Interval

- 32.4.9 Ready Count

- 32.4.10 Total Method Calls

- 32.5 EntityBean Metrics

- 32.5.1 Activates

- 32.5.2 Activation Time

- 32.5.3 Active Methods

- 32.5.4 Average Method Execution Time During Last Interval

- 32.5.5 Avg Drain Size

- 32.5.6 Concurrent Lives

- 32.5.7 Creates

- 32.5.8 Current average execution time

- 32.5.9 Destroys

- 32.5.10 Drains From Pool

- 32.5.11 EJB Method Execution Rate per second

- 32.5.12 Gets Found

- 32.5.13 Gets From Pool

- 32.5.14 Instantiates

- 32.5.15 Load Time

- 32.5.16 Loads

- 32.5.17 No of EJB Methods Executed during last interval

- 32.5.18 Passivates

- 32.5.19 Passivation Time

- 32.5.20 Pool Size

- 32.5.21 Ready Count

- 32.5.22 Removes

- 32.5.23 Returns Discarded

- 32.5.24 Returns To Pool

- 32.5.25 Store Time

- 32.5.26 Stores

- 32.6 J2EE Server Metrics

- 32.6.1 J2EE Server - Active EJB Methods

- 32.6.2 J2EE Server - Active Requests

- 32.6.3 J2EE Server - Active Sessions

- 32.6.4 J2EE Server - Active Transactions

- 32.6.5 J2EE Server - Delta Method Call

- 32.6.6 J2EE Server - EJB Method Execution Rate per second

- 32.6.7 J2EE Server - EJB Method Execution Time

- 32.6.8 J2EE Server - Live Sessions

- 32.6.9 J2EE Server - Open JDBC Connections

- 32.6.10 J2EE Server - Request Processing Time

- 32.6.11 J2EE Server - Requests Processed for second

- 32.7 JDBCProvider Metrics

- 32.7.1 JDBCProvider - Average Wait Time

- 32.7.2 JDBCProvider - Avg Use Time

- 32.7.3 JDBCProvider - Concurrent Waiters

- 32.7.4 JDBCProvider - Faults

- 32.7.5 JDBCProvider - Free Pool Size

- 32.7.6 JDBCProvider - Jdbc Operation Timer

- 32.7.7 JDBCProvider - Number Allocates

- 32.7.8 JDBCProvider - Number Connection Handles

- 32.7.9 JDBCProvider - Number Creates

- 32.7.10 JDBCProvider - Number Destroys

- 32.7.11 JDBCProvider - Number of Managed Connections

- 32.7.12 JDBCProvider - Number Returns

- 32.7.13 JDBCProvider - Percent Maxed

- 32.7.14 JDBCProvider - Percent Used

- 32.7.15 JDBCProvider - Pool Size

- 32.7.16 JDBCProvider - Prepared Statement Cache Discards

- 32.8 JSP Metrics

- 32.8.1 JSP - Active Requests

- 32.8.2 JSP - Average Processing Time (seconds)

- 32.8.3 Concurrent Requests

- 32.8.4 Current Client Processing Time

- 32.8.5 Number Errors

- 32.8.6 JSP - Requests Per Second During Last Interval

- 32.8.7 JSP - Response Time

- 32.8.8 JSP - Time Taken During Last Interval

- 32.8.9 JSP - Total Requests

- 32.9 JVM Metrics

- 32.9.1 JVM - CPU Utilization (%)

- 32.9.2 JVM - Free Memory

- 32.9.3 JVM - Total Memory

- 32.9.4 JVM - Up Time

- 32.9.5 JVM - Used Memory

- 32.10 MessageDrivenBean Metrics

- 32.10.1 MessageDrivenBean - Active Methods

- 32.10.2 MessageDrivenBean - Avg Drain Size

- 32.10.3 MessageDrivenBean - Avg Server Session Wait Time

- 32.10.4 MessageDrivenBean - Avg method exec. time during last interval

- 32.10.5 MessageDrivenBean - Concurrent Lives

- 32.10.6 MessageDrivenBean - Current avg exec. time

- 32.10.7 MessageDrivenBean - Delta Method Calls

- 32.10.8 MessageDrivenBean - Destroys

- 32.10.9 MessageDrivenBean - Drains From Pool

- 32.10.10 MessageDrivenBean - EJB Method Execution Rate per second

- 32.10.11 MessageDrivenBean - Gets Found

- 32.10.12 MessageDrivenBean - Gets From Pool

- 32.10.13 MessageDrivenBean - Instantiates

- 32.10.14 MessageDrivenBean - Message Blackout Count

- 32.10.15 MessageDrivenBean - Message Count

- 32.10.16 MessageDrivenBean - Pool Size

- 32.10.17 MessageDrivenBean - Returns Discarded

- 32.10.18 MessageDrivenBean - Returns To Pool

- 32.10.19 MessageDrivenBean - Server Session Usage

- 32.11 ORB Metrics

- 32.11.1 Concurrent Requests

- 32.11.2 Reference Lookup Time

- 32.11.3 Total Requests

- 32.12 Response

- 32.12.1 Status

- 32.13 Servlet Metrics

- 32.13.1 Servlet - Active Requests

- 32.13.2 Servlet - Average Processing Time (seconds)

- 32.13.3 Servlet - Concurrent Requests

- 32.13.4 Servlet - Current Client Processing Time

- 32.13.5 Servlet - Number Errors

- 32.13.6 Servlet - Requests Per Second During Last Interval

- 32.13.7 Servlet - Response Time

- 32.13.8 Servlet - Time Taken During Last Interval

- 32.13.9 Servlet - Total Requests

- 32.14 SessionManager Metrics

- 32.14.1 Activate NonExist Sessions

- 32.14.2 Active Sessions

- 32.14.3 Affinity Breaks

- 32.14.4 Cache Discards

- 32.14.5 Created Sessions

- 32.14.6 External ReadSize

- 32.14.7 External ReadTime

- 32.14.8 External Write Size

- 32.14.9 External WriteTime

- 32.14.10 Invalidated Sessions

- 32.14.11 Invalidated Via Timeout

- 32.14.12 Live Sessions

- 32.14.13 No Room For New Session

- 32.14.14 Session Life Time

- 32.14.15 Time Since Last Activated

- 32.15 Stateful SessionBean Metrics

- 32.15.1 Average Method Execution Time

- 32.15.2 Activates

- 32.15.3 Activation Time

- 32.15.4 Active Methods

- 32.15.5 Concurrent Lives

- 32.15.6 Creates

- 32.15.7 Current Average Execution Time

- 32.15.8 Destroys

- 32.15.9 EJB Method Execution Rate per second

- 32.15.10 EJB Method Call Count during Last Interval

- 32.15.11 Instantiates

- 32.15.12 Passivates

- 32.15.13 Passivation Time

- 32.15.14 Ready Count

- 32.15.15 Removes

- 32.16 StatelessSessionBean Metrics

- 32.16.1 Active Methods

- 32.16.2 Avg Drain Size

- 32.16.3 Average Method Execution Time

- 32.16.4 Concurrent Lives

- 32.16.5 Current Average Execution Time

- 32.16.6 Delta Method Calls

- 32.16.7 Destroys

- 32.16.8 Drains From Pool

- 32.16.9 EJB Method Execution Rate per second

- 32.16.10 Gets Found

- 32.16.11 Gets From Pool

- 32.16.12 Instantiates

- 32.16.13 Pool Size

- 32.16.14 Ready Count

- 32.16.15 Returns Discarded

- 32.16.16 Returns To Pool

- 32.17 System Metrics

- 32.17.1 Avg CPU Utilization

- 32.17.2 CPU Utilization

- 32.17.3 Free Memory

- 32.18 ThreadPool Metrics

- 32.18.1 Active Threads

- 32.18.2 Percent Maxed

- 32.18.3 Pool Size

- 32.18.4 Thread Creates

- 32.18.5 Thread Destroys

- 32.19 TransactionService Metrics

- 32.19.1 Active Global Transactions

- 32.19.2 Global Before Completion Duration

- 32.19.3 Global Commit Duration

- 32.19.4 Global Prepare Duration

- 32.19.5 Global Transaction Duration

- 32.19.6 Global Transaction Timeout

- 32.19.7 Global Transactions Begun

- 32.19.8 Global Transactions Committed

- 32.19.9 Global Transactions Involved

- 32.19.10 Global Transactions RolledBack

- 32.19.11 Local Before Completion Duration

- 32.19.12 Local Commit Duration

- 32.19.13 Local Transaction Duration

- 32.19.14 Local Transaction Timeout

- 32.19.15 Local Transactions Begun

- 32.19.16 Local Transactions Committed

- 32.19.17 Local Transactions RolledBack

- 32.19.18 Number Optimizations

- 32.20 WebModule Metrics

- 32.20.1 Number Loaded Servlets

- 32.20.2 Number Reloads

- 32.21 WebServices Service Metrics

- 32.21.1 Dispatch Response Time

- 32.21.2 Number Dispatched

- 32.21.3 Number Loaded Services

- 32.21.4 Number Received

- 32.21.5 Number Successful

- 32.21.6 Reply Response Time

- 32.21.7 Reply Size

- 32.21.8 Request Response time

- 32.21.9 Request Size

- 32.21.10 Response Time

- 32.21.11 Size

33 IBM WebSphere MQ Queue Manager Metrics

- 33.1 Channel Current Status

- 33.1.1 Channel Current Status - Bytes Received

- 33.1.2 Channel Current Status - Bytes Sent

- 33.1.3 Channel Current Status - Delta Bytes Received

- 33.1.4 Channel Current Status - Delta Bytes Sent

- 33.1.5 Channel Current Status - Delta Messages Sent/Received

- 33.1.6 Channel Current Status - Messages Sent/Received

- 33.1.7 Channel Current Status - Status

- 33.2 Channel Saved Status Metrics

- 33.2.1 Last Seq Number

- 33.2.2 Status

- 33.2.3 Type

- 33.2.4 Transmission Queue

- 33.3 Channels Metrics

- 33.3.1 Alteration Date

- 33.3.2 Cluster Name

- 33.3.3 Cluster Name list

- 33.3.4 Connection Name

- 33.3.5 Max Message Length

- 33.3.6 Type

- 33.3.7 Transmission Queue Name

- 33.4 Dynamic Queues

- 33.4.1 Definition Type

- 33.4.2 Type

- 33.4.3 Usage

- 33.5 Local Queues

- 33.5.1 Cluster Name List

- 33.5.2 Definition Type

- 33.5.3 Depth

- 33.5.4 Max Depth

- 33.5.5 Max Message Length

- 33.5.6 Open Input Count

- 33.5.7 Open Output Count

- 33.5.8 Percent Usage

- 33.5.9 Type

- 33.5.10 Usage

- 33.5.11 Transmission Queue Name

- 33.6 Queue Manager Cluster

- 33.6.1 Queue Manager Name

- 33.6.2 Queue Manager Type

- 33.7 Queue Manager General

- 33.7.1 Command Queue

- 33.7.2 Dead Letter Queue

- 33.7.3 Default Transmission Queue

- 33.7.4 Max Handles

- 33.7.5 Max Message Length

- 33.7.6 Platform

- 33.7.7 Repository Name List

- 33.8 Queue Manager Load

- 33.8.1 Queue Manager Load - Bytes Received

- 33.8.2 Queue Manager Load - Bytes Sent

- 33.8.3 Queue Manager Load - Messages Sent/Received

- 33.9 Queues

- 33.9.1 Cluster Name List

- 33.9.2 Depth

- 33.9.3 Max Depth

- 33.9.4 Max Message Length

- 33.9.5 Open Input Count

- 33.9.6 Open Output Count

- 33.9.7 Remote Queue Manager

- 33.9.8 Remote Queue Name

- 33.9.9 Type

- 33.9.10 Use

- 33.9.11 Transmission Queue Name

- 33.10 Response Metrics

- 33.10.1 Response

- 33.11 Sender Channel Queues

- 33.11.1 Transmission Queue Name

34 JBoss Application Server Metrics

- 34.1 BoundedQueue ThreadPools

- 34.1.1 Active Threads

- 34.1.2 Maximum Threads at any time

- 34.1.3 Rejected threads - last interval

- 34.2 Clustering Service Metrics

- 34.2.1 Partition Name

- 34.2.2 Clustering Service - Bind Address

- 34.2.3 Clustering Service - Port

- 34.2.4 Clustering Service - Rmi Port

- 34.2.5 Clustering Service - State

- 34.2.6 Clustering Service - State (Text)

- 34.3 CPU Usage

- 34.3.1 Server CPU Usage (%)

- 34.4 Datasource Metrics

- 34.4.1 Datasource - Available Connections

- 34.4.2 Datasource - Connection Pool Size

- 34.4.3 Datasource - Current Waiting Thread Count

- 34.4.4 Datasource - Connections Created (per min)

- 34.4.5 Datasource - Connections Closed (per min)

- 34.4.6 Datasource - Connections in Use

- 34.5 DataSource Bind Metrics

- 34.5.1 JNDI Name

- 34.6 Entity Ejb Metrics

- 34.6.1 Entity EJB - Cache Size

- 34.6.2 Entity EJB - Current Instances Pooled Count

- 34.6.3 Entity EJB - Current Ready Instances Count

- 34.6.4 Entity EJB - Current Size

- 34.6.5 Entity EJB - Instances Created Count

- 34.6.6 Entity EJB - Instances Removed Count

- 34.6.7 Entity EJB - Maximum Instances in the Pool

- 34.6.8 Entity EJB - Minimum Instances in the Pool

- 34.6.9 Entity EJB - Minimum Ready Instances Count

- 34.6.10 Entity EJB - Name

- 34.6.11 Entity EJB - Parent

- 34.6.12 Entity EJB - State String

- 34.6.13 Statistic Provider

- 34.7 Ejb Modules Metrics

- 34.7.1 Name

- 34.7.2 Statistic Provider

- 34.8 Global Request Processor

- 34.8.1 Data Received (KB per min)

- 34.8.2 Data Sent (KB per min)

- 34.8.3 Errors (per min)

- 34.8.4 Requests (per min)

- 34.8.5 Processing time (ms) - last interval

- 34.9 Connection Pools Metrics

- 34.9.1 Criteria

- 34.9.2 Maximum Size

- 34.9.3 Minimum Size

- 34.10 JBoss JCA Metrics

- 34.10.1 JCA - Count Use Time

- 34.10.2 JCA - Count Use Time (Sec)

- 34.10.3 JCA - Count Wait Time

- 34.10.4 JCA - Current Free Pool Size

- 34.10.5 JCA - Current Pool Size

- 34.10.6 JCA - Current Waiting Thread Count

- 34.10.7 JCA - High Pool Size

- 34.10.8 JCA - Instances Close Count

- 34.10.9 JCA - Instances Created Count

- 34.10.10 JCA - Low Pool Size

- 34.10.11 JCA - Lower Bound Free Pool Size

- 34.10.12 JCA - Lower Bound Pool Size

- 34.10.13 JCA - Max Wait Time

- 34.10.14 JCA - Maximum Pool Size

- 34.10.15 JCA - Maximum Use Time

- 34.10.16 JCA - Maximum Waiting Thread Count

- 34.10.17 JCA - Min Wait Time

- 34.10.18 JCA - Minimum Pool Size

- 34.10.19 JCA - Minimum Used Time

- 34.10.20 JCA - Minimum Waiting Thread Count

- 34.10.21 JCA - Total Used Time

- 34.10.22 JCA - Total Wait Time

- 34.10.23 JCA - Upper Bound Free Pool Size

- 34.10.24 JCA - Upper Bound Pool Size

- 34.10.25 Name

- 34.10.26 Parent

- 34.10.27 Statistics Provider

- 34.11 JMS Queue Metrics

- 34.11.1 Consumers

- 34.11.2 Messages being delivered

- 34.11.3 Messages in Queue

- 34.11.4 Messages currently scheduled

- 34.11.5 Messages added (per min)

- 34.12 JVM Metrics

- 34.12.1 JVM - Free Heap (%)

- 34.12.2 JVM - Heap Size (MB)

- 34.12.3 JVM Name

- 34.12.4 JVM Version

- 34.12.5 Vendor

- 34.13 Mail Service Metrics

- 34.13.1 Service - Default Sender

- 34.13.2 Service - JNDI Name

- 34.13.3 Service - POP3 Server Host

- 34.13.4 Service - SMTP Server Host

- 34.13.5 Service - State

- 34.13.6 Service - State (text)

- 34.13.7 Service - Store Protocol

- 34.13.8 Service - Transport Protocol

- 34.14 Message Driven Ejb Metrics

- 34.14.1 MDB - Current Size

- 34.14.2 MDB - Instances Created Count

- 34.14.3 MDB - Instances Removed Count

- 34.14.4 MDB - Messages Count

- 34.14.5 MDB - Name

- 34.14.6 MDB - Parent

- 34.14.7 MDB - State String

- 34.14.8 Statistic Provider

- 34.15 Naming Service Metrics

- 34.15.1 Listen Port

- 34.15.2 RMI Port

- 34.15.3 Service Name

- 34.15.4 Service State

- 34.16 Protocols Ports Metrics

- 34.16.1 JBoss - Connection Linger Value

- 34.16.2 JBoss - Connection Timeout

- 34.16.3 JBoss - KeyStore File

- 34.16.4 KeyStore Type

- 34.16.5 JBoss - Protocol

- 34.16.6 JBoss - Redirect Port

- 34.16.7 JBoss - Redirect Port Protocol

- 34.17 Server Configuration Metrics

- 34.17.1 JBoss - Base Directory

- 34.17.2 JBoss - Configuration Name

- 34.17.3 JBoss - Deployment Filename

- 34.17.4 JBoss - Home Directory

- 34.17.5 JBoss - Server Home Directory

- 34.18 Server Details Metrics

- 34.18.1 JBoss - Active Thread Count

- 34.18.2 JBoss - Active Thread Group Count

- 34.18.3 JBoss - Available No. of Processors

- 34.18.4 JBoss - Free Heap Size

- 34.18.5 JBoss - Free Heap Size %

- 34.18.6 JBoss - Heap Size

- 34.18.7 JBoss - Heap Size (MB)

- 34.18.8 JBoss - Host Name

- 34.18.9 JBoss - Java Vendor Name

- 34.18.10 JBoss - Java Version

- 34.18.11 JBoss - Java VM Name

- 34.18.12 JBoss - Java VM Vendor Name

- 34.18.13 JBoss - Java VM Version

- 34.18.14 JBoss - Maximum Memory

- 34.18.15 JBoss - OS Architecture

- 34.18.16 JBoss - OS Name

- 34.18.17 JBoss - OS Version

- 34.18.18 JBoss - Total Heap Size

- 34.18.19 JBoss - Total Heap Size(MB)

- 34.19 JBoss Server Metrics

- 34.19.1 Host Address

- 34.19.2 Host Name

- 34.19.3 Host Operating System

- 34.19.4 JBoss - Build Date

- 34.19.5 JBoss - Build ID

- 34.19.6 JBoss - Listen Port

- 34.19.7 JBoss - Start Time

- 34.19.8 JBoss - Version

- 34.19.9 JBoss - Version Name

- 34.20 JBoss Servlets Raw Metrics

- 34.20.1 Parent

- 34.20.2 Servlet - Active Requests / Sec

- 34.20.3 Servlet - Active Requests since last Upload

- 34.20.4 Servlet - Active Requests, Response Time (Sec)

- 34.20.5 Servlet - Maximum Response Time

- 34.20.6 Servlet - Minimum Response Time

- 34.20.7 Servlet - Response Time Unit

- 34.20.8 Servlet - Total Requests

- 34.20.9 Servlet - Total Response Time

- 34.20.10 Servlet Name

- 34.20.11 Statistic Description

- 34.20.12 Statistic Name

- 34.20.13 Statistic Provider

- 34.21 Server Servlet/JSP Metrics

- 34.21.1 Active Sessions

- 34.21.2 Servlet and JSP - Requests (per min)

- 34.21.3 Servlet and JSP - Request Processing Time (ms)

- 34.22 Stateful Session EJB Metrics

- 34.22.1 Stateful Ejb - Current Method Ready Count

- 34.22.2 Stateful Ejb - Current Passive Instances Count

- 34.22.3 Stateful Ejb - Current Size

- 34.22.4 Stateful Ejb - Instances Created Count

- 34.22.5 Stateful Ejb - Instances Removed Count

- 34.22.6 Stateful Ejb - Maximum Method Ready Count

- 34.22.7 Stateful Ejb - Maximum Passive Instances Count

- 34.22.8 Stateful Ejb - Minimum Method Ready Count

- 34.22.9 Stateful Ejb - Minimum Passive Instances Count

- 34.22.10 Stateful Ejb - Name

- 34.22.11 Stateful Ejb - Parent

- 34.22.12 Stateful Ejb - State String

- 34.22.13 Statistic Provider

- 34.23 Stateless Session EJB Metrics

- 34.23.1 Stateless Ejb - Current Method Ready Count

- 34.23.2 Stateless Ejb - Instances Created Count

- 34.23.3 Stateless Ejb - Instances Removed Count

- 34.23.4 Stateless Ejb - Maximum Method Ready Count

- 34.23.5 Stateless Ejb - Minimum Method Ready Count

- 34.23.6 Stateless Ejb - Name

- 34.23.7 Stateless Ejb - Parent

- 34.23.8 Statistic Provider

- 34.23.9 Stateless Ejb - Current Size

- 34.23.10 Stateless Ejb - State String

- 34.24 Top EJBs Metrics

- 34.24.1 JBoss - Ejb Create Count

- 34.24.2 JBoss - Ejb Remove Count

- 34.24.3 JBoss - Ejb Type

- 34.25 Top Servlets Metrics

- 34.25.1 Servlet WAR Name

- 34.25.2 Web Component Type

- 34.25.3 Servlet - Requests Processed Per Sec

- 34.25.4 Servlet - Requests Processing Time (ms)

- 34.26 Transactions Metrics

- 34.26.1 Committed last interval

- 34.26.2 JBoss - Active Transactions Count

- 34.26.3 JBoss - Transactions / Sec

- 34.26.4 JBoss - Transactions Committed / Sec

- 34.26.5 JBoss - Transactions Committed Count

- 34.26.6 JBoss - Transactions Rolled Back / Sec

- 34.26.7 JBoss - Transactions RolledBack Count

- 34.26.8 JBoss - Transactions Timeout (Secs)

- 34.26.9 Rolledback last interval

- 34.26.10 Transaction last interval

- 34.27 JBoss Web Applications Metrics

- 34.27.1 Web Apps - Active requests since last agent upload

- 34.27.2 Web Apps - Average maximum response time

- 34.27.3 Web Apps - Average minimum response time

- 34.27.4 Web Apps - Average Response Time

- 34.27.5 Web Apps - Requests rate per second

- 34.27.6 Web Apps - Total Requests

- 34.27.7 Web Apps - Total Response Time

- 34.27.8 Web Apps - Total Response time for Active Requests

- 34.28 Web Service Metrics

- 34.28.1 Service - Bind Address

- 34.28.2 Service - Host

- 34.28.3 Service - Port

- 34.28.4 Service - State

- 34.28.5 Service - State (text)

- 34.29 Resource Usage Metrics

- 34.29.1 Free Memory (%)

- 34.29.2 Maximum Memory Size (MB)

- 34.29.3 Memory Usage (MB)

- 34.30 Response Metrics

- 34.30.1 UpDown Status

Preface

This manual is a compilation of the Middleware-related target metrics provided in Oracle Enterprise Manager.

Audience

This document is intended for Oracle Enterprise Manager users interested in Middleware target metrics.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information about Enterprise Manager, see the Oracle Enterprise Manager 12c documentation set at the following website:

http://www.oracle.com/pls/em121/homepage

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

What's Changed in this Guide?

In addition to updating books for an incremental software release or a patch set release, Oracle revises its books regularly to incorporate bug fixes and value-added feedback from customers, product managers, support teams, and other key stakeholders. Every time a book is revised, the revision number of the book is increased by one and then published.

This chapter lists the changes incorporated in the latest revision (E25158-10) of this book.

Since the last revision, the following changes have been made:

- Modified: Updated the descriptions and examples for the Log File Monitoring metrics in Chapter 1, "WebLogic Server".

- Updated the metric descriptions in the following chapters:

- Chapter 12, "Oracle Coherence Cache"

- Chapter 13, "Oracle Coherence Cluster"

- Chapter 14, "Oracle Coherence Node"

How to Use This Manual

This document lists all the Middleware target metrics that Enterprise Manager monitors.

This preface describes:

- Structure of the Oracle Enterprise Manager Middleware Plug-in Metric Reference Manual

- About Metrics, Thresholds, and Alerts

Structure of the Oracle Enterprise Manager Middleware Plug-in Metric Reference Manual

This manual contains a chapter for each Middleware target for which there are metrics.

The metrics in each chapter are in alphabetical order according to category.

Metric Information

The information for each metric comprises a description, summary of the metric's "vital statistics", data source (if available), and user action. The following list provides greater detail:

- Description
Explanation following the metric name. This text defines the metric and, when available, provides additional information pertinent to the metric.

- Metric Summary
Explains in table format the target version, default collection frequency, upload frequency, default warning threshold, default critical threshold, and alert text for the metric.

- Data Source
How the metric is calculated. In some metrics, data source information is not available.

- User Action
Suggestions of how to solve the problem causing the alert.

Examples of Metric Summary Tables

This section provides examples of Metric Summary tables that you will see in this document.

When default thresholds are not defined for a metric, only the target version and default collection frequency are available.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Metric Terminology

The following table provides descriptions of the terminology used with metrics.

Column Header

Column Definition

Target Version

Version of the target, for example, 11g and 12c.

Evaluation and Collection Frequency

The rate at which the metric is collected and evaluated to determine whether it has crossed its threshold. The evaluation frequency is the same as the collection frequency.

Server Evaluation Frequency

The rate at which the metric is evaluated to determine whether it has crossed its threshold. For server-generated alerts, the evaluation frequency is determined by Oracle Database internals. For example, if the evaluation frequency is 10 minutes, then when the Average File Write Time degrades to the point an alert should trigger, it could be almost 10 minutes before Enterprise Manager receives indication of the alert. This column is present in the Metric Collection Summary table only for Oracle Database 10g metrics.

Collection Frequency

The rate at which the Management Agent collects data. The collection frequency for a metric comes from the Enterprise Manager default collection file for that target type.

Upload Frequency

The rate at which the Management Agent moves data to the Management Repository. For example, upload every nth collection. The upload frequency for a metric comes from the Enterprise Manager default collection file for that target type. This column is present in the Metric Collection Summary table only when the Upload Frequency is different from the Collection Frequency.

Default Warning Threshold

Value that indicates whether a warning alert should be initiated. If the evaluation of the warning threshold value returns a result of TRUE for the specified number of consecutive occurrences defined for the metric, an alert triggers at the warning severity level.

Default Critical Threshold

Value that indicates whether a critical alert should be initiated. If the evaluation of the critical threshold value returns a result of TRUE for the specified number of consecutive occurrences defined for the metric, an alert triggers at the critical severity level.

Alert Text

Message indicating why the alert was generated. Words that display between percent signs (%) denote variables. For example, Disk Utilization for %keyValue% is %value%% could translate to Disk Utilization for d0 is 80%.

About Metrics, Thresholds, and Alerts

A metric is a unit of measurement used to determine the health of a target. It is through the use of metrics and associated thresholds that Enterprise Manager sends out alerts notifying you of problems with the target.

Thresholds are boundary values against which monitored metric values are compared. For example, for each disk device associated with the Disk Utilization (%) metric, you can define a different warning and critical threshold. Some of the thresholds are predefined by Oracle.

When a threshold is reached, Enterprise Manager generates an alert. An alert is an indicator signifying that a particular condition has been encountered and is triggered when one of the following conditions is true:

- A threshold is reached.

- An alert has been cleared.

- The availability of a monitored service changes. For example, the availability of an application server changes from up to down.

- A specific condition occurs. For example, an alert is triggered whenever an error message is written to a database alert log file.

Alerts are detected through a polling-based mechanism by checking for the monitored condition from a separate process at regular, predefined intervals.

See Also:
See the Oracle Enterprise Manager Concepts manual and the Enterprise Manager online help for additional information about metrics, thresholds, and alerts

Accessing Metrics

To access metrics from the Cloud Control Console, use the All Metrics page:

1. From the Cloud Control Console, choose the target.

2. From the target's home page, select the target type name, then Monitoring, and then All Metrics.

Editing Metrics

Out of the box, Enterprise Manager comes with thresholds for critical metrics. Warning and critical thresholds are used to generate an alert, letting you know of impending problems so that you can address them in a timely manner.

To better suit the monitoring needs of your organization, you can edit the thresholds provided by Enterprise Manager and define new thresholds.

When defining thresholds:

- Choose acceptable values to avoid unnecessary alerts, while still being notified of issues in a timely manner.

- Adjust your metric thresholds based on metric trends. One of the more important actions you can perform with your monitoring system is to track metric trends for some period of time so you can make informed decisions about what metrics are important as well as what levels your thresholds should be set at.

- Set the number of occurrences appropriately. If some events occur only once or twice, for example, you might not need to be notified of them. You can set the number of occurrences of a metric that must be reached before you are notified.

To modify metric thresholds:

1. From the Cloud Control console, right-click the target name, select Monitoring, and then All Metrics.

2. From the All Metrics page, select the metric that you want to modify.

3. Click Modify Thresholds.

4. In the Modify Thresholds window, you can set values for settings such as:

- Warning Threshold

- Critical Threshold

- Occurrences Before Alert

Note:
You must have at least OPERATOR privilege on the target to make changes. Without OPERATOR privilege, the content of the Metric Threshold table is read-only.

5. Click Save Thresholds to upload the new metric settings to the Management Repository.

Specifying Multiple Thresholds

The Specifying Multiple Thresholds functionality allows you to define various subsets of data that can have different thresholds. By specifying multiple thresholds, you can refine the data used to trigger alerts, which are one of the key benefits of using Enterprise Manager.The key in specifying multiple thresholds is to determine how the comparison relates to the metric threshold as a whole. What benefit will be realized by defining a more stringent or lax threshold for that particular device, mount point, and so on?For example, using the Average Disk I/O Service Time metric, you can define warning and critical thresholds to be applied to all disks (sd0 and sd1), or you can define different warning and critical thresholds for a specific disk (sd0). This allows you to adjust the thresholds for sd0 to be more stringent or lax for that particular disk.

1 WebLogic Server

The Oracle WebLogic Server metrics provide for each metric the following information:

- Description

- Metric summary. The metric summary can include some or all of the following: target version, collection frequency, default warning threshold, default critical threshold, and alert text.

- Multiple Thresholds (where applicable)

1.1 Active Applications

This metric category provides information about active applications (earlier than Oracle Web Server 10g)

1.1.1 Application - Active Sessions (pre 11)

This metric provides the number of current open sessions for an active application. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7,8,9

Every 15 Minutes

Not Defined

Not Defined

The number of Current Open Sessions for application %ApplicationName% is %value%

1.1.2 Application - Current Client Processing Time

This metric provides the current client processing time for the active application. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7,8,9

Every 15 Minutes

Not Defined

Not Defined

The Current Client Processing time for application %ApplicationName% is %value%

1.1.3 Application - Average Response Time

This metric provides the average response time for the active application. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7,8,9

Every 15 Minutes

Not Defined

Not Defined

The Average execution time for application %ApplicationName% is %value%.

1.2 Application Overview Metrics

This category provides information about application metrics.

1.2.1 Cached Beans

For the selected application, the total number of Enterprise JavaBeans (EJB) currently in the EJB cache. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of cached beans is %value%.

1.2.2 Cache Accesses (per minute)

For the selected application, the number of cache access attempts per minute in the last five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The cache accesses is %value% (per minute).

1.2.3 Bean Activations (per minute)

For the selected application, this metric shows the total number of EJB that have been activated since the server started. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bean activations are %value% (per minute).

1.2.4 Cache Hits (%)

For the selected application, the percentage of cache accesses that completed successfully in the last five minutes. The value of this metric can range between zero and 100. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The EJB cache hit rate is %value%%%

1.2.5 Cache Misses (per minute)

For the selected application, the number of cache misses per minute in the last five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The cache misses are %value% (per minute).

1.2.6 Bean Accesses (per minute)

For the selected application, the EJB pool accesses per minute in the last five minutes. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.2.7 Bean Access Successes (%)

For the selected application, the percentage of pool accesses that were successful in the last five minutes. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.2.8 Free Bean Instances

For the selected application, the current number of available bean instances in the free pool. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.2.9 Bean Destroys (per minute)

For the selected application, the bean destroys performed per minute in the last five minutes. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.2.10 Bean Access Failures (per minute)

For the selected application, failed EJB pool accesses per minute in the last five minutes. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.2.11 Beans in Use

For the selected application, the number of bean instances currently being used from the free pool. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.2.12 Bean Transaction Commits (%)

For the selected application, the percentage of transactions that were committed during the last five minutes. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.2.13 Bean Transaction Commits (per minute)

For the selected application, the transaction commits per minute for the last five minutes. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.2.14 Bean Transaction Rollbacks (per minute)

For the selected application, the total number of transactions that have been rolled back for this EJB since the server started. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.2.15 Bean Transaction Timeouts (per minute)

For the selected application, the transaction timeouts per minute for the last five minutes. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.2.16 MDB Messages (per minute)

For the selected application, the number of messages processed by message-driven beans (MDBs) per minute in the last five minutes. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.2.17 Requests (per minute)

For the selected application, this metric shows the average number of servlet and JSP invocations per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.2.18 Request Processing Time (ms)

For the selected application, this metric shows the average amount of time (in milliseconds) spent executing servlets and/or JSPs over the last five minutes. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.2.19 Active Sessions

This metric shows the number of active sessions for the selected application. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.2.20 Work Manager Pending Requests

For the selected application, the number of waiting requests in the work manager queue. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.2.21 Work Manager Requests (per minute)

For the selected application, the number of requests processed per minute in the last five minutes. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.3 Application Work Manager

This metric category provides information about Work Manager.

1.3.1 Work Manager Pending Requests

For the selected application, this metric shows the number of work manager requests waiting in the queue. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.3.2 Work Manager Requests (per minute)

For the selected application, this metric shows the number of work manager requests processed per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.3.3 Work Manager Stuck Threads

For the selected application, this metric shows the number of work manager threads that are considered stuck on the basis of any stuck thread constraints. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.4 Application Metrics

This category provides information about application metrics.

1.4.1 Application - Status

This metric shows the current status of the application, indicated as an integer value:

- 1 - the application is considered up and running

- 0 - the application is considered down

On an Enterprise Manager page, the status is shown by an icon that graphically indicates whether the application is up and running or not.

1.5 Certificate Monitoring

This metric category provides information about the expiry time of the certificate.

For Oracle WebLogic Server 12c (12.1.3), Oracle supports certificates in PEM format and JKS keystore type. For more information about certificates, see your Oracle WebLogic Server documentation.

1.5.1 No of days left for expiry of the certificate

This metric tracks the number of days remaining before a certificate expires. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 1 Day

30

7

The value of %columnName% for %keyValue% is %value%

1.6 Connection Pool Metrics By Server

This metric category provides information about all the connection pool metrics for this server.

1.6.1 Open Connections

This metric tracks the number of open connector connections. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

NotDefined

Not Defined

The number of open connector connections is %value%.

1.6.2 Free Connections

This metric tracks the number of free connector connections. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

NotDefined

Not Defined

The number of free connector connections is %value%.

1.6.3 Unavailable Connections

This metric tracks the number of unavailable connector connections. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

NotDefined

Not Defined

The number of unavailable connector connections is %value%.

1.6.4 Connection Waiters

This metric tracks the number of applications waiting for a connection. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

NotDefined

Not Defined

The number of connector connection waiters is %value%.

1.6.5 Connections Closed (per minute)

This metric tracks the number of connections closed each minute. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

NotDefined

Not Defined

The number of closed connector connections is %value% (per minute).

1.6.6 Connections Created (per minute)

This metric tracks the number of connections created each minute. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

NotDefined

Not Defined

The number of created connector connections is %value% (per minute).

1.6.7 Connections Destroyed due to Error (per minute)

This metric tracks the number of destroyed connections each minute due to errors. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

NotDefined

Not Defined

The connector connection destroys due to error are %value% (per minute).

1.6.8 Connections Destroyed due to Shrinking (per minute)

This metric tracks the number of destroyed connections each minute due to shrinking. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

NotDefined

Not Defined

The connector connection destroys due to shrinking are %value% (per minute).

1.6.9 Connections Destroyed (per minute)

This metric tracks the total number of destroyed connections each minute. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

NotDefined

Not Defined

The connector connection destroys are %value% (per minute).

1.6.10 Connection Requests Satisfied (per minute)

This metric tracks the number of successful connection requests each minute. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

NotDefined

Not Defined

The number of satisfied connector connections is %value% (per minute).

1.6.11 Connection Requests Rejected (per minute)

This metric tracks the number of rejected connection requests each minute. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

NotDefined

Not Defined

The number of rejected connector connections is %value% (per minute).

1.6.12 Connections Recycled (per minute)

This metric tracks the number of recycled connections each minute. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

NotDefined

Not Defined

The number of recycled connector connections is %value% (per minute).

1.7 Datasource Metrics

This category provides information about datasource metrics.

Note:
Datasource metrics collected for Application Deployment targets are app-scoped datasources (not global). An app-scoped datasource is only available to the application that deployed this datasource. A global datasource is available to all applications.
For information about global datasources and app-scoped datasources, see Oracle Fusion Middleware Developing JDBC Applications for Oracle WebLogic Server JA.

1.7.1 Available Connections

For the selected data source, this metric shows the number of database connections currently available (not in use). The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of available connections for datasource %name%, application %appName% is %value%.

1.7.2 Cached Statements not Used (per minute)

For the selected data source, this metric shows the number of statements per minute not satisfied by the statement cache, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The cache statements not used for datasource %name%, application %appName% are %value% (per minute)..

1.7.3 Cached Statements Used (%)

For the selected data source, this metric shows the percentage of statements satisfied by the statement cache during the last five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of available connections for datasource %name%, application %appName% is %value%.

1.7.4 Cached Statements Used (per minute)

For the selected data source, this metric shows the number of statements per minute satisfied by the statement cache, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The cached statements used rate for datasource %name%, application %appName% is %value%%%.

1.7.5 Connection Creation Time (ms)

For the selected data source, this metric shows the time it took to create the JDBC connection in milliseconds. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The time to create connections for datasource %name%, application %appName% is %value% (ms).

1.7.6 Connection Leaks (per minute)

For the selected data source, this metric shows the number of JDBC connection leaks per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The connection leaks for datasource %name%, application %appName% are %value% (per minute).

1.7.7 Connection Pool Size

For the current data source, this metric shows the current count of JDBC connections in the JDBC connection pool. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of connections in the connection pool for datasource %name%, application %appName% is %value%.

1.7.8 Connection Refresh Failures (per minute)

For the selected data source, this metric shows the number of failed JDBC connection refreshes per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The connection refresh failures for datasource %name%, application %appName% are %value% (per minute)..

1.7.9 Connection Request Failures (per minute)

For the selected data source, this metric shows the number of failed JDBC connection requests per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The connection request failures for datasource %name%, application %appName% are %value% (per minute).

1.7.10 Connection Requests (per minute)

For the selected data source, this metric shows the number of requests for a JDBC connection from this data source per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The connection requests for datasource %name%, application %appName% are %value% (per minute).

1.7.11 Connection Requests that Waited (%)

For the selected data source, this metric shows the percentage of JDBC connection waits. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

%value%%% of connection requests waited for datasource %name%, application %appName%.

1.7.12 Connection Requests that Waited (per minute)

For the selected data source, this metric shows the number of JDBC connection waits per minute, averaged over the past five minutes.

A JDBC connection wait is a request for a connection from this data source that had to wait before getting a connection, including those that eventually got a connection and those that did not get a connection The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The connections that waited for datasource %name%, application %appName% are %value% (per minute).

1.7.13 Connection Requests Waiting

For the selected data source, this metric shows the current number of JDBC connection requests waiting for a database connection. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of connection requests waiting for datasource %name%, application %appName% is %value%..

1.7.14 Connection Wait Successes (%)

For the selected data source, this metric shows the percentage of requests waiting for a JDBC connection that successfully got a connection during the last five minutes.

A JDBC connection wait is a request for a connection from this data source that had to wait before getting a connection, including those that eventually got a connection and those that did not get a connection. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The connection wait success rate for datasource %name%, application %appName% is %value%%%.

1.7.15 Connection Wait Successes (per minute)

For the selected data source, this metric shows the number of JDBC connection wait successes per minute, averaged over the past five minutes.

A wait success is a request for a connection from this data source that had to wait before getting a connection and eventually succeeded in getting a connection. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The connection wait successes for datasource %name%, application %appName% are %value% (per minute).

1.7.16 Connections Created (per minute)

For the selected data source, this metric shows the number of database connections created per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The connections created for datasource %name%, application %appName% are %value% (per minute).

1.7.17 Connections in Use

For the selected data source, this metric shows the number of JDBC connections currently in use by applications. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of connections in use for datasource %name%, application %appName% is %value%.

1.7.18 Failed Waiting Connection Requests (per minute)

For the selected data source, this metric shows the number of JDBC connection wait failures per minute, averaged over the past five minutes.

A wait failure is a request for a connection from this data source that had to wait before getting a connection and eventually failed to get a connection. Waiting connection requests can fail for a variety of reasons, including waiting for longer than the ConnectionReserveTimeoutSecond. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The connection wait failures for datasource %name%, application %appName% are %value% (per minute).

1.7.19 Statement Cache Size

For the current data source, this metric shows the number of prepared and callable JDBC statements currently cached in the connection pool.

Each JDBC connection in the connection pool has its own cache of statements. This number is the sum of the number of statements in the caches for all connections in the connection pool. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The size of the statement cache for datasource %name%, application %appName% is %value%.

1.7.20 Statements Added to Cache (per minute)

For the selected data source, this metric shows the number of statements per minute added to the statement cache, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The statements added to cache for datasource %name%, application %appName% are %value% (per minute).

1.7.21 Statements Discarded from Cache (per minute)

For the current data source, this metric shows the number of statements per minute discarded from the statement cache, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The statements discarded from the cache for datasource %name%, application %appName% are %value% (per minute).

1.7.22 Successful Connections (%)

For the selected data source, this metric shows the percentage of requests that successfully returned JDBC connections during the last five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The successful connection rate for datasource %name%, application %appName% is %value%%%..

1.7.23 Unavailable Connections

For the selected data source, this metric shows the number of database connections that are currently unavailable (in use or being tested by the system). The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of unavailable connections for datasource %name%, application %appName% is %value%..

1.8 Datasource State Metric

This metric category provides information about the state of the data source.

1.8.1 State

This metric tracks the state of the data source. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The state of datasource %name%, application %appName% is %value%.

1.9 EJB Metrics

This metric category provides information about Enterprise JavaBeans (EJB).

1.9.1 EJB Pool - Threads Timed Out Waiting

This metric tracks the number of threads that time out while waiting for a bean instance during the last collection interval for EJB. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The Number of Threads that have timed out waiting for a bean instance during last collection interval for EJB %Name% is %value%.

1.9.2 EJB Pool - Current Failed Attempts For Instance

This metric tracks the number of failed attempts during the last collection interval for EJB. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The Number of Failed Attempts during last collection interval for EJB %Name% is %value%.

1.9.3 EJB Lock - Timed Out Threads Since Last Collection

This metric tracks the number of the threads that timed out during the last collection interval for EJB. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The Number of Threads that have waited for a lock during last collection interval for EJB %Name% is %value%.

1.9.4 EJB Lock - Threads Waited Since Last Collection

This metric tracks the number of the threads that timed out waiting for a lock during the last collection interval for EJB. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The Number of Threads that have waited for a lock during last collection interval for EJB %Name% is %value%

1.10 EJB Cache Metrics By Server

This metric category provides information about EJB cache metrics.

1.10.1 Cached Beans

This metric trackes the total number of beans in the EJB cache. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of cached beans is %value%.

1.10.2 Cache Hits (%)

This metric tracks the cache hit percentage, that is, the percentage of successful attempts to access a bean from the cache. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The EJB cache hit rate is %value%%%.

1.10.3 Bean Activations (per minute)

This metric tracks the total number of beans that have been activated per minute. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bean activations are %value% (per minute).

1.10.4 Cache Accesses (per minute)

This metric tracks the total number of attempts to access a bean from the cache per minute. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The cache accesses is %value% (per minute).

1.10.5 Cache Misses (per minute)

This metric tracks the total number of times an attempt to access a bean from the cache failed per minute. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The cache misses are %value% (per minute).

1.10.6 Cache Passivations (per minute)

This metric tracks the total number of beans that have been passivated.The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The EJB Passivations are %value% (per minute).

1.11 EJB Lock Metrics at Application Level

This metric category provides information about EJB locks at application level.

1.11.1 EJB Lock - Threads Waited Since Last Collection For Application

This metric tracks the number of threads that have waited for a lock during the last collection interval. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The Number of Threads that have waited for a lock during last collection interval for Application %ApplicationName% is %value%.

1.12 EJB Module Metrics

This category provides information about EJB module metrics.

1.12.1 Cached Beans

This metric shows the total number of beans currently in the EJB cache. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of cached beans is %value%.

1.12.2 Cache Accesses (per minute)

For the current EJB module, this metric shows the number times per minute that an attempt was made to access the EJB cache. This value is averaged over the last five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The cache accesses is %value% (per minute).

1.12.3 EJB Activations (per minute)

For the current EJB module, this metric shows the total number of beans per minute that have been activated in the last five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bean activations are %value% (per minute).

1.12.4 EJB Cache Hits (%)

For the current EJB module, this metric shows the percentage of cache accesses that completed successfully in the last five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The EJB cache hit rate is %value%%%.

1.12.5 EJB Cache Misses (per minute)

For the current EJB module, this metric shows the number of cache misses per minute in the last five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The cache misses are %value% (per minute).

1.12.6 EJB Passivations (per minute)

For the current EJB module, this metric shows the total number of beans per minute that have been passivated in the last five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The EJB Passivations are %value% (per minute).

1.12.7 Bean Accesses (per minute)

For the current EJB module, this metric shows how many times the EJB pool has been accessed per minute. This is averaged over the last five minutes. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.12.8 Bean Successes (%)

For the current EJB module, this metric shows the percentage of pool accesses that were successful in the last five minutes. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.12.9 Free Bean Instances

For the selected EJB, this metric shows the current number of available bean instances in the free pool. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.12.10 Bean Destroys (per minute)

For the selected EJB Module, this metric shows the bean destroys per minute in the last five minutes. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.12.11 Failed Bean Accesses (per minute)

For the selected EJB module, this metric shows the failed pool accesses per minute over the past five minutes. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.12.12 Beans in Use

For the current EJB module, this metric shows the number of bean instances currently being used from the free pool. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.12.13 Bean Transaction Commits (per minute)

For the selected EJB module, this metric shows the transaction commits per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.12.14 Bean Transaction Rollbacks (per minute)

For the selected EJB module, this metric shows the number of transaction rollbacks per minute over the past five minutes. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.12.15 Bean Transaction Timeouts (per minute)

For the current EJB module, this metric shows the number of times a transaction timed out per minute, averaged over the last five minutes. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.12.16 MDB Messages (per minute)

For the selected EJB module, this metric shows the number of messages processed by message-driven beans (MDBs) per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.13 EJB Metrics at Application Level

This metric category describes the EJB Metrics at application level.

1.13.1 EJB Active Transactions Rolled Back For Application

This metric tracks the total number of EJB active transactions that have been rolled back for this application. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The Number of Transactions Rolled Back during last collection interval for Application %ApplicationName% is %value%

1.13.2 EJB Active Transactions Timed Out For Application

This metric tracks the total number of EJB active transactions that timed out for this application. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The Number of Transactions Timed Out during last collection interval for Application %ApplicationName% is %value%.

1.14 EJB Metrics at Module Level

This metric category provides information about EJB metrics at the module level.

1.14.1 EJB Pool - Threads Timed Out Current Count For Module

This metric tracks the total number of threads that have timed out waiting for a bean instance during last collection interval for the EJB module. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The Number of Threads that have timed out waiting for a bean instance during last collection interval for EJB Module %EJBModName% is %value%

1.14.2 EJB Pool - Miss Current Count For Module

This metric tracks the total number of failed attempts during the last collection interval for the EJB Module. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The Number of Failed Attempts during last collection interval for EJB Module %EJBModName% is %value%

1.14.3 EJB Transactions - Rolled Back Current Count For Module

This metric tracks the total number of transactions rolled back during the last collection interval for EJB Module. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The Number of Transactions Rolled Back during last collection interval for EJB Module %EJBModName% is %value%

1.14.4 EJB Transactions - Timed Out Current Count For Module

This metric tracks the number of transactions timed out during the last collection interval for the EJB Module. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The Number of Transactions Timed Out during last collection interval for EJB Module %EJBModName% is %value%.

1.14.5 EJB Lock - Timed Out Thread Current Count For Module

This metric tracks the total number of threads that have waited for a lock during the last collection interval for the EJB Module. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The Number of Threads that have waited for a lock during last collection interval for EJB Module %EJBModName% is %value%.

1.15 EJB Pool Metrics

This category provides information about EJB pool metrics.

1.15.1 Bean Accesses (per minute)

This metric shows how many times per minute that the selected EJB pool has been accessed over the last five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bean accesses are %value% (per minute).

1.15.2 Successful Bean Accesses (%)

This metric shows the percentage of attempts to access the pool that were successful in the last five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The successful bean access rate is %value%%%.

1.15.3 Bean Destroys (per minute)

For the selected EJB pool, this metric shows the bean destroys per minute over the last five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bean destroys are %value% (per minute).

1.15.4 Bean Access Failures (per minute)

This metric shows the number of times per minute that an attempted access to the EJB pool has failed, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bean access failures are %value% (per minute).

1.15.5 Beans in Use

This metric shows the number of bean instances currently being used from the free pool. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of beans in use is %value%.

1.16 EJB Pool Metrics at Application Level

This metric category provides information about the EJB pool metrics at application level.

1.16.1 EJB Pool - Threads Timed Out Waiting For Application

This metric tracks the number of threads that have waited for a lock during the last collection interval for this application. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The Number of Threads that have waited for a lock during last collection interval for Application %ApplicationName% is %value%

1.16.2 EJB Pool - Current Failed Attempts For Instance For Application

This metric tracks the number of failed attempts during the last collection interval for this application. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The Number of Failed Attempts during last collection interval for Application %ApplicationName% is %value%

1.17 EJB Pool Metrics By Server

This metric category provides information about the EJB pool metrics by server.

1.17.1 Bean Accesses (per minute)

This metric shows how many times per minute that the EJB pool has been accessed. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bean accesses are %value% (per minute).

1.17.2 Bean Destroys (per minute)

For the EJB pool, this metric shows the number of bean destroys per minute. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bean destroys are %value% (per minute).

1.17.3 Bean Access Failures (per minute)

This metric shows the number of times per minute that an attempted access to the EJB pool has failed.The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bean access failures are %value% (per minute).

1.17.4 Beans in Use

This metric shows the number of bean instances currently being used from the free pool. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of beans in use is %value%.

1.17.5 Bean Successes (%)

This metric shows the percentage of attempts to access the pool that were successful. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The successful bean access rate is %value%%%.

1.17.6 Free Bean Instances

This metric shows the current number of available EJB instances in the free pool. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of available beans is %value%.

1.18 EJB Transaction Metrics

This category provides information about EJB transaction metrics.

1.18.1 Bean Transaction Commits (%)

This metric shows the percentage of EJB transactions that were committed during the last five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bean transaction commit rate is %value%%%.

1.18.2 Bean Transaction Commits (per minute)

This metric shows the EJB transaction commits per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bean transaction commits are %value% (per minute).

1.18.3 Bean Transaction Rollbacks (per minute)

This metric shows the EJB transaction rollbacks per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bean transaction rollbacks are %value% (per minute).

1.18.4 Bean Transaction Timeouts (per minute)

This metric shows the EJB transaction timeouts per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bean transaction timeouts are %value% (per minute).

1.18.5 EJB Active Transactions Rolled Back

This metric shows the number of rolled back transactions during the last collection interval. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The Number of Transactions Rolled back during last collection interval for EJB %Name% is %value%.

1.18.6 EJB Active Transactions Timed Out

This metric shows the number of transactions that timed out during the last collection interval.The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The Number of Transactions Timed out during last collection interval for EJB %Name% is %value%.

1.19 EJB Transaction Metrics By Server

This metric category provides information about all the EJB transaction metrics for this server.

1.19.1 Bean Transaction Commits (per minute)

This metric shows the EJB transaction commits per minute.The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bean transaction commits are %value% (per minute).

1.19.2 Bean Transaction Rollbacks (per minute)

This metric shows the EJB transaction rollbacks per minute. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bean transaction rollbacks are %value% (per minute).

1.19.3 Bean Transaction Timeouts (per minute)

This metric shows the EJB transaction timeouts per minute.The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bean transaction timeouts are %value% (per minute).

1.19.4 Bean Transaction Commits (per minute)

This metric shows the EJB transaction commits per minute. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bean transaction commit rate is %value%%%.

1.20 Execute Queue Metrics

This metric category provides information about the execute queue metrics.

An execute queue contains requests to a WebLogic Server instance.

1.20.1 Execute Queue - Pending Request Current Count

This metric shows the current pending request count for the execute queue. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 5 Minutes

Not Defined

Not Defined

The Current Pending Request Count for Execute Queue %Name% is %value%

1.21 Execute Queue Rollup Metrics

This metric category provides information about the execute queue rollup metrics.

1.21.1 Execute Queue Rollup - Pending Request Current Count

This metric shows the number of current pending requests for the J2EE server. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The Current Pending Request Count for J2EE Server is %value%.

1.22 Incident Metrics

This metric category provides information about incidents detected in the alert log file.

1.22.1 Problem Key

This metric shows incidents detected in the alert log file. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 5 Minutes

Not Defined

.*

Incident (%adr_problemKey%) detected in %alertLogName% at time/line number: %timeLine%

1.23 J2EE Application Metrics

This metric provides status information about the selected J2EE application.

1.23.1 Application Status

This metric shows the status of the selected application. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Down

Application %ApplicationName% on %Parent% is down

1.24 J2EE Server Wide Metrics

This metric category provides information about J2EE server wide metrics.

1.24.1 J2EE Server - Active Sessions

This metric shows the number of current open sessions for the J2EE server. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The number of Current Open Sessions for J2EE Server is %value%.

1.24.2 J2EE Server - Current Client Processing Time

This metric shows the current client processing time for the J2EE server. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The Current Client Processing time for J2EE Server is %value%

1.25 JDBC Connection Pool Metrics (Detailed)

This metric category provides information about the JDBC Connection Pool metrics.

1.25.1 JDBC Connection Pool - Active Connections Current Count

This metric shows the total number of active JDBC connections for this connection pool. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8

Every 15 Minutes

Not Defined

Not Defined

The Number of Active JDBC Connections for Connection Pool %Name% is %value%.

1.26 JDBC Rollup - Active JDBC Connections

This metric category provides information about the JDBC Rollup - Active JDBC Connections metrics.

1.26.1 JDBC Rollup - Active Connections

This metric shows the total number of active JDBC connections. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The Number of Active JDBC Connections are %value%.

1.27 JMS Metrics

This metric category provides information about Java Message Service (JMS) metrics.

1.27.1 JMS Connections

This metric shows the total number of JMS connections. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of JMS connections is %value%.

1.27.2 JMS Servers

This metric shows the total number of JMS servers. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of JMS Servers is %value%.

1.28 JMS Destination Metrics

This category provides information about JMS Destination metrics.

1.28.1 Bytes Stored

This metric shows the stored bytes count. The rest of the information in this section is only valid for this metric when it appears in either Enterprise Manager Cloud Control or Enterprise Manager Database Control (if applicable). The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

Stored bytes in %type%, name %name%, JMS server %jmsServer% is %value%.

1.28.2 Bytes Pending

This metric shows the pending bytes count

The rest of the information in this section is only valid for this metric when it appears in either Enterprise Manager Cloud Control or Enterprise Manager Database Control (if applicable). The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

Pending bytes in %type%, name %name%, JMS server %jmsServer% is %value%.

1.28.3 Bytes Received (per minute)

This metric shows the number of bytes received per minute. The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The received bytes in %type%, name %name%, JMS server %jmsServer% are %value% (per minute).

1.28.4 Consumers Active

This metric shows the number of the current consumers. The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

Active consumers of %type%, name %name%, JMS server %jmsServer% is %value%.

1.28.5 Messages Stored

This metric shows the number of stored messages. The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The stored messages in %type%, name %name%, on JMS server %jmsServer% is %value%.

1.28.6 Messages Pending

This metric shows the number of pending messages. The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The pending messages in %type%, name %name%, on JMS server %jmsServer% is %value%.

1.28.7 Messages Received (per minute)

This metric shows the number of messages received.The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The received messages in %type%, name %name%, JMS server %jmsServer% are %value% (per minute).

1.28.8 Messages Moved (per minute)

This metric shows the number of messages moved per minute.

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The moved messages in %type%, name %name%, JMS server %jmsServer% are %value% (per minute).

1.28.9 Messages Deleted (per minute)

This metric shows the number of messages deleted per minute.The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The deleted messages in %type%, name %name%, JMS server %jmsServer% are %value% (per minute).

1.28.10 JMS Destination - Bytes Pending

This metric shows the pending bytes count. The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The total size of pending messages in the JMS %DestinationType% %Name% on %Parent% is %value%

1.28.11 JMS Destination - Messages Pending

This metric shows the number of pending messages. The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The number of pending messages in the JMS %DestinationType% %Name% on %Parent% is %value%

1.29 JMS Server Metrics

This category provides information about JMS server metrics.

1.29.1 Bytes Pageable

For the current JMS server, this metric shows the number of bytes in all the messages that are currently available to be paged out, but which have not yet been paged out.

The JMS server attempts to keep this number smaller than the "MessageBufferSize" parameter.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of bytes pageable for JMS server %name% is %value%.

1.29.2 Bytes Paged In (per minute)

For the selected JMS server, this metric shows the number of bytes per minute that were read from the paging directory, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bytes paged in for JMS server %name% are %value% (per minute).

1.29.3 Bytes Paged Out (per minute)

For the current JMS server, this metric shows the number of bytes per minute that were written to the paging directory, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bytes paged out for JMS server %name% are %value% (per minute).

1.29.4 Bytes Pending

This metric shows the current number of bytes pending (unacknowledged or uncommitted) stored on the selected JMS server. Pending bytes are over and above the current number of bytes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of bytes pending for JMS server %name% is %value%.

1.29.5 Bytes Received (per minute)

This metric shows the number of bytes received by the selected JMS server in the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bytes received for JMS server %name% are %value% (per minute).

1.29.6 Bytes Stored

This metric shows the current number of bytes stored on this JMS server. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of bytes stored for JMS server %name% is %value%.

1.29.7 Destinations

This metric shows the current number of destinations defined for the selected JMS server. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of destinations for JMS server %name% is %value%.

1.29.8 Messages Paged In (per minute)

This metric shows the current number of messages stored on this JMS server. This number does not include the pending messages. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The messages paged in for JMS server %name% are %value% (per minute).

1.29.9 Messages Paged Out (per minute)

This metric shows the number of messages per minute that were written to the paging directory, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The messages paged out for JMS server %name% are %value% (per minute).

1.29.10 Messages Pending

This metric shows the current number of pending messages (unacknowledged or uncommitted) stored on this JMS server. Pending messages are over and above the current number of messages. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of messages pending for JMS server %name% is %value%.

1.29.11 Messages Received (per minute)

This metric shows the number of messages received by this JMS server in the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The messages received for JMS server %name% are %value% (per minute).

1.29.12 Messages Stored

This metric shows the current number of messages stored on the selected JMS server. This number does not include the pending messages. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of messages stored for JMS server %name% is %value%.

1.29.13 Session Pools

This metric shows the current number of session pools instantiated on the selected JMS server. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of session pools for JMS server %name% is %value%.

1.30 JMS Server Metrics (Detailed)

This metric category provides information about the JMS server metrics.

1.30.1 JMS Server - Bytes Pending Count

This metric shows the current number of bytes pending (unacknowledged or uncommitted) stored on the selected JMS server. Pending bytes are over and above the current number of bytes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The total size of pending messages in the JMS server %Name% is %value%.

1.30.2 JMS Server - Messages Pending Count

This metric shows the current number of pending messages (unacknowledged or uncommitted) stored on this JMS server. Pending messages are over and above the current number of messages. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The number of pending messages in the JMS server %Name% is %value%.

1.31 JMS Server Metrics By Server

This metric category provides information about the JMS server metrics by server.

1.31.1 Bytes Stored

This metric shows the current number of bytes stored on this JMS server. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of bytes stored is %value%.

1.31.2 Bytes Pageable

For the current JMS server, this metric shows the number of bytes in all the messages that are currently available to be paged out, but which have not yet been paged out.

The JMS server attempts to keep this number smaller than the "MessageBufferSize" parameter.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of bytes pageable is %value%.

1.31.3 Bytes Paged In (per minute)

For the selected JMS server, this metric shows the number of bytes per minute that were read from the paging directory, averaged over the past five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bytes paged in are %value% (per minute).

1.31.4 Bytes Paged Out (per minute)

For the current JMS server, this metric shows the number of bytes per minute that were written to the paging directory, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bytes paged out are %value% (per minute).

1.31.5 Bytes Pending

This metric shows the current number of bytes pending (unacknowledged or uncommitted) stored on the selected JMS server. Pending bytes are over and above the current number of bytes.The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of bytes pending is %value%.

1.31.6 Bytes Received (per minute)

This metric shows the number of bytes received by the selected JMS server in the past five minutes.The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The bytes received are %value% (per minute).

1.31.7 Destinations

This metric shows the current number of destinations defined for the selected JMS server. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of destinations is %value%.

1.31.8 Current JMS Messages

This metic shows the total number of current JMS messages. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of messages stored is %value%.

1.31.9 Messages Paged In (per minute)

This metric shows the current number of messages stored on this JMS server. This number does not include the pending messages. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The messages paged in are %value% (per minute).

1.31.10 Messages Paged Out (per minute)

This metric shows the number of messages per minute that were written to the paging directory. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The messages paged out are %value% (per minute).

1.31.11 Pending JMS Messages

This metric shows the current number of pending messages (unacknowledged or uncommitted) stored on this JMS server. Pending messages are over and above the current number of messages.The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of messages pending is %value%.

1.31.12 Messages Received (per minute)

This metric shows the number of messages received per minute by this JMS server. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The messages received for are %value% (per minute).

1.31.13 Session Pools

This metric shows the current number of session pools instantiated on the selected JMS server. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of session pools is %value%.

1.32 JRockit VM Runtime Metrics

This metric category provides information about the JRockit VM runtime metrics.

The JRockit Java Virtual Machine (JVM) is one component of the Oracle JRockit Java development kit (JDK). In addition to the JRockit JVM, the JDK is comprised of the Java Runtime Environment (JRE), which contains the JVM and Java class libraries (as specified by the Java Platform, Standard Edition 6 API Specification), as well as a set of development tools, such as a compiler.

1.32.1 JRockit - Number Of Daemon Threads

This metric shows the number of daemon Java threads currently running in the Virtual Machine across all processors. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The Number of Daemon Threads are %value%

1.32.2 JRockit - Total Number Of Threads

This metric shows the number of Java threads (daemon and nondaemon) that are currently running in the Virtual Machine across all processors.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The total number of Threads are %value%

1.32.3 JRockit - CPU Usage( % )

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The CPU Usage by VM is %value%.

1.32.4 JRockit - Used Heap

This metric shows the amount (in bytes) of Java heap memory that is currently being used by the Virtual Machine.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The Heap Usage by VM is %value%.

1.32.5 JRockit - Used Physical Memory

This metric shows the amount (in bytes) of physical memory that is currently being used on the host computer.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Weblogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

The Physical Memory Usage by VM is %value%

1.33 Jolt Connection Pool Metrics

This category provides information about Oracle Jolt metrics for each Jolt connection pool.

Oracle Jolt is a Java-based client API that manages requests to Oracle Tuxedo services through a Jolt Service Listener (JSL) running on the Tuxedo server. The Jolt API is embedded within the WebLogic API, and is accessible from a servlet or any other Oracle WebLogic application.

1.33.1 Maximum Capacity

This metric shows the maximum capacity for the Jolt connection pool.

Note:
This metric is disabled by default.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The maximum capacity for jolt connection pool %name% is %value% connections.

1.33.2 Pool State

This metric shows the state of the Jolt connection pool.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Suspended

Jolt connection pool %name% is suspended.

1.33.3 Request Errors (per minute)

The metric shows the number of request errors encountered per minute for the Jolt connection pool.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

Request errors for jolt connection pool %name% are %value% (per minute).

1.33.4 Requests (per minute)

This metric shows the number of requests processed per minute for the Jolt connection pool.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

Requests for jolt connection pool %name% are %value% (per minute).

1.33.5 Pending Requests

This metric shows the current number of pending requests for the Jolt connection pool.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

Pending requests for jolt connection pool %name% are %value%.

1.34 JTA Metrics

This category provides information about JTA metrics.

1.34.1 Abandoned Transactions (per minute)

For the selected server, this metric shows the number of transactions abandoned per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The abandoned transactions are %value% (per minute).

1.34.2 Committed Transactions (%)

For the selected server, this metric shows the percentage of transactions committed over the last five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The committed transaction rate is %value%%%.

1.34.3 Committed JTA Transactions (per minute)

For the selected server, this metric shows the total number of transactions committed per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The committed transactions are %value% (per minute).

1.34.4 Committed Transaction Time (seconds)

For the selected server, this metric shows the total number of seconds that JTA transactions were active for all committed transactions. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The committed transaction time is %value% seconds.

1.34.5 Heuristic Transactions (per minute)

For the selected server, this metric shows the number of transactions that completed with a heuristic status per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The heuristic transactions are %value% (per minute).

1.34.6 Transactions Processed (per minute)

For the selected server, this metric shows the number of transactions processed per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The transactions processed are %value% (per minute).

1.34.7 JTA Transaction Rollbacks (per minute)

For the selected server, this metric shows the number of transactions rolled back per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The transaction rollbacks are %value% (per minute).

1.34.8 Transaction Rollbacks due to Application Error (per minute)

For the selected server, this metric shows the number of transactions rolled back due to an application error per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The transaction rollbacks due to application error are %value% (per minute).

1.34.9 Transaction Rollbacks due to Resource Error (per minute)

For the selected server, this metric shows the number of transactions rolled back due to a resource error per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The transaction rollbacks due to resource error are %value% (per minute).

1.34.10 Transaction Rollbacks due to System Error (per minute)

For the selected server, this metric shows the number of transactions rolled back due to an internal system error per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The transaction rollbacks due to system error are %value% (per minute).

1.34.11 Transaction Rollbacks due to Timeout (per minute)

For the selected server, this metric shows the number of transactions rolled back due to a timeout expiration per minute, averaged over the past five minutes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The transaction rollbacks due to timeout are %value% (per minute).

1.34.12 Active JTA Transactions

This metric shows the number of currently active JTA transactions on the selected server. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of active JTA transactions is %value%.

1.35 JTA Resource Metrics

This metric category provides information about the Java Transaction API (JTA) Resource metrics.

1.35.1 Committed JTA Transactions (per minute)

This metric shows the total number of JTA transactions committed per minute on this server. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The committed transactions for resource %resourceName% are %value% (per minute).

1.35.2 JTA Transactions with Heuristic Commit Decision (per minute)

This metric shows the total number of JTA transactions committed per minute for which the resource reported a heuristic commit.The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The transactions with heuristic commit decision for resource %resourceName% are %value% (per minute).

1.35.3 JTA Transactions with Heuristic Hazard Decision (per minute)

This metric shows the total number of JTA transactions committed per minute for which the resource reported a heuristic hazard decision. In a heuristic hazard decision, the Transaction Manager is aware that a transaction might have resulted in a mixed outcome, where some participating resources committed and some rolled back, but system or resource failures make it impossible to know for sure whether a heuristic mixed outcome definitely occurred. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The transactions with heuristic hazard decision for resource %resourceName% are %value% (per minute).

1.35.4 JTA Transactions with Heuristic Mixed Decision (per minute)

This metric shows the total number of JTA transactions committed per minute for which the resource reported a mixed heuristic decision. In a mixed heuristic decision, the Transaction Manager is aware that a transaction resulted in a mixed outcome, where some participating resources committed and some rolled back.The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The transactions with heuristic mixed decision for resource %resourceName% are %value% (per minute).

1.35.5 JTA Transactions with Heuristic Rollback Decision (per minute)

This metric shows the total number of JTA transactions committed per minute for which the resource reported a heuristic rollback. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The transactions with heuristic rollback decision for resource %resourceName% are %value% (per minute).

1.35.6 Heuristic JTA Transactions (per minute)

This metric shows the number of transactions for which the resource reported a heuristic decision, either a heuristic commit, a heuristic rollback, a mixed heuristic decision, or a heuristic hazard decision. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The heuristic transactions for resource %resourceName% are %value% (per minute).

1.35.7 JTA Transaction Rollbacks (per minute)

This metric shows the number of transactions in which the resource rolled back the transaction. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The transaction rollbacks for resource %resourceName% are %value% (per minute).

1.35.8 Processed JTA Transactions (per minute)

This metric shows the number of transactions processed per minute for this resource. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The transactions processed for resource %resourceName% are %value% (per minute).

1.35.9 Committed JTA Transactions (%)

This metric shows the total number of transactions committed per minute for this resource. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The committed transaction rate for resource %resourceName% is %value%%%.

1.36 JVM Metrics

This category provides information about JVM metrics.

1.36.1 CPU Usage (%)

This metric shows the percentage of the CPU currently in use by the Java Virtual Machine (JVM). This includes the load that the JVM is placing on all processors in the host computer.

For example, if the host uses multiple processors, the value represents a snapshot of the average load on all the processors. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The CPU usage is %value%%%.

1.36.2 Active Daemon Threads

This metric shows the number of daemon Java threads currently running in the Java Virtual Machine (JVM) across all processors. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of active daemon threads is %value%.

1.36.3 Active Threads

This metric shows the current number of active threads in the selected Java Virtual Machine (JVM). The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of active threads is %value%.

1.36.4 Free Heap (MB)

This metric shows the current size of free memory in the Java Virtual Machine (JVM) memory heap, in megabytes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The heap has %value% MB of free space.

1.36.5 Heap Usage (MB)

This metric shows the current size of the Java Virtual Machine (JVM) memory heap, in megabytes. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The heap usage is %value% MB.

1.36.6 Heap Usage (%)

This metric shows the current size of the Java Virtual Machine (JVM) memory heap, in percent. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

80

90

The heap usage is %value%%%.

1.36.7 JDK Vendor

This metric shows the name vendor responsible for the current Java Development Kit (JDK) that is being used for the current Java Virtual Machine.

For example, when you install and configure an Oracle WebLogic Server domain, you can choose to use the standard Sun Microsystems JDK or the Oracle WebLogic Server JRockit JDK.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

10gR3, 11g, 12c

Every 15 Minutes

1.36.8 JDK Version

This metric shows the version of the Java Development Kit (JDK) that is currently in use by the selected server. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

10gR3, 11g, 12c

Every 15 Minutes

1.36.9 Nursery Size (MB)

This metric shows the amount of memory that is currently allocated to the nursery, in megabytes.

The nursery is the area of the Java heap that the virtual machine allocates to most objects. Instead of garbage collecting the entire heap, generational garbage collectors focus on the nursery.

Most objects do not last a long time in memory; as a result, in most cases, it is sufficient to perform garbage collect on only the nursery and not on the entire memory heap.

If you are not using a generational garbage collector, the nursery size is zero.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The nursery size is %value% MB.

1.37 JVM Class Loading

This metric category provides information about the JVM class loading metric.

1.37.1 JVM Class Loading - Classes Currently Loaded

This metric tracks and raises an alert when the number of classes currently loaded exceeds the defined thresholds.The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of classes currently loaded is %value%.

1.38 JVM Compilation Metrics

This category provides information about JVM compilation metrics.

1.38.1 Compilation Time (since startup) (ms)

For the selected Java Virtual Machine (JVM), this metric shows the total time spent by the JVM in compilation. The value of the metric is in milliseconds and shows the time spent in compilation since the JVM was last started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.39 JVM Garbage Collectors

This category provides information about JVM garbage collectors metrics.

1.39.1 Name

This is the name of the garbage collector (this differs based on the kind of JVM being used on the weblogic server ). It is a key column for this metric.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.39.2 Garbage Collector - Garbage Collection Invocations (since startup)

This metric shows the number of times the Java Virtual Machine (JVM) garbage collector was invoked since the JVM was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.39.3 Garbage Collector -Invocations (per min)

This is the number of times the garbage collector was invoked per minute during the last metric collection interval.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g (10.3.3, 10.3.4)

Every 15 Minutes

Not Defined

Not Defined

The invocations for garbage collector %Name% are %value% (per minute).

1.39.4 Garbage Collector - Invocation Time (ms)

This metric shows the average time ( in millisecs) spent per invocation of the garbage collector during the last metric collection interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.39.5 Garbage Collector - Execution Time (since startup) (ms)

This metric shows the total time spent by the Java Virtual Machine (JVM) in garbage collection since the JVM was started. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g (10.3.3, 10.3.4)

Every 15 Minutes

Not Defined

Not Defined

The invocation time for garbage collector %Name% is %value% ms.

1.39.6 Garbage Collector - Old Heap Percent Free after GC (%)

This metric tracks and raises an alert when the percentage of the old heap free space after garbage collection is less than the percentage defined in the thresholds. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

Percent of old heap free after GC for garbage collector %Name% is %value%%%.

1.39.7 Garbage Collector - Percent Time spent (elapsed)

This metric shows the percentage of time spent by the Java Virtual Machine (JVM) in garbage collection since the JVM was started. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g (10.3.3, 10.3.4)

Every 15 Minutes

Not Defined

Not Defined

The percentage of time spent in Garbage Collection is %value%.

1.40 JVM Garbage Collection

This metric category provides information about JVM Garbage Collection metrics.

1.40.1 JVM - Total Garbage Collection Time (ms)

This metric shows the percentage of time spent by the Java Virtual Machine (JVM) in garbage collection since the JVM was started. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

Garbage collection elapsed time in milliseconds is %value%.

1.40.2 JVM - Garbage Collection Time since Last Metric Collection (ms)

This metric shows the total time spent by the Java Virtual Machine (JVM) in garbage collection since the last metric collection. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

Garbage collection elapsed time since Last Metric Collection in milliseconds is %value%.

1.40.3 JVM - Total Garbage Collection Count

This metric shows the total number of garbage collections since the JVM was started. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

Total Number of collections that have occurred are %value%.

1.40.4 JVM - Garbage Collection Count since Last Metric Collection

This metric shows the total number of garbage collections since the last metric collection. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 7, 8, 9

Every 15 Minutes

Not Defined

Not Defined

Number of collections that have occurred since Last Metric collection are %value%.

1.41 JVM Memory Pools

This category provides information about JVM memory pools metrics.

1.41.1 Name

This metric shows the name of the JVM memory pool.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.41.2 Type

This metric shows the type of the JVM memory pool.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.41.3 Memory Pool - Current Usage (MB)

This metric shows the current memory usage (in megabytes) of the selected Java Virtual Machine (JVM). The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The memory usage for pool %Name% is %value% MB.

1.41.4 Memory Pool - Peak Usage (KB)

This metric shows the maximum (peak) memory used by the Java Virtual Machine (JVM) in kilobytes, since the JVM was started. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.42 JVM Memory Usage

This category provides information about JVM memory usage metrics.

1.42.1 JVM Memory - Heap Memory Usage (KB)

This metric shows the total heap memory (in kilobytes) currently in use by the selected Java Virtual Machine (JVM). The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The heap memory usage is %value% KB

1.42.2 Non-Heap Memory Usage (KB)

This metric shows the total nonheap memory (in kilobytes) currently in use by the selected Java Virtual Machine (JVM). The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The non-heap memory usage is %value% KB

1.42.3 Objects Pending Finalization

This metric shows the number of objects pending finalization in the selected Java Virtual Machine (JVM). The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of objects pending finalization is %value%

1.43 JVM Runtime Metrics

This metric category provides information about the JVM runtime metrics.

1.43.1 JVM Runtime - Up Time (ms)

This metric shows how long the selected Java Virtual Machine (JVM) has been up in running (in milliseconds).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.43.2 JVM Runtime - VM Name

This metric shows the name of the selected Java Virtual Machine (JVM).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.43.3 JVM Runtime - VM Version

This metric shows the version number of the selected Java Virtual Machine (JVM).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.44 JVM ThreadContention

This category provides information about JVM thread contention metrics.

1.44.1 JVM Thread Contention - Blocked Count

This metric shows the number of times the selected Java Virtual Machine (JVM) thread has been blocked since the thread was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 30 Minutes

1.44.2 JVM Thread Contention - Blocked Time (since startup) (seconds)

This metric shows how long (in seconds) this thread has been blocked since it was started or since thread contention monitoring was enabled.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 30 Minutes

1.44.3 JVM Thread Contention - CPU Usage (since startup) (seconds)

This metric shows the amount of CPU (in seconds) that is currently being used by the selected Java Virtual Machine (JVM) thread.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 30 Minutes

1.44.4 JVM Thread Contention - Lock Name

This metric shows the name of the lock the selected Java Virtual Machine (JVM) thread is blocked on (if applicable).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 30 Minutes

1.44.5 Thread State

This metric shows the state of the selected Java Virtual Machine (JVM) thread.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 30 Minutes

1.44.6 JVM Thread Contention - Wait Count

This metric shows the number of times the selected Java Virtual Machine (JVM) thread has entered wait states since the thread was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 30 Minutes

1.44.7 JVM Thread Contention - Wait Time (since startup) (seconds)

This metric shows how long (in seconds) the selected Java Virtual Machine (JVM) thread has been in wait states since the thread was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 30 Minutes

1.45 JVM Threads

This category provides information about JVM threads metrics.

1.45.1 JVM Threads - Active Daemon Threads

This metric shows the current number of active daemon threads in the selected Java Virtual Machine (JVM).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 30 Minutes

1.45.2 JVM Threads - Deadlocked Threads

This metric shows the current number of deadlocked threads in the selected Java Virtual Machine (JVM). The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 30 Minutes

Not Defined

Not Defined

The number of deadlocked threads is %value%.

1.45.3 JVM Threads - Peak Threads

This metric shows the maximum (peak) number of threads started in this Java Virtual Machine (JVM) since the JVM was started. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 30 Minutes

Not Defined

Not Defined

The number of peak threads is %value%.

1.45.4 JVM Threads - Active Threads

This metric shows the current number of active threads in the selected Java Virtual Machine (JVM).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 30 Minutes

1.45.5 JVM Threads - Threads Started (since startup)

This metric shows the total number of threads started in this Java Virtual Machine (JVM) since the JVM was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 30 Minutes

1.46 Limited Server Metrics

This metric category provides information about limited server metrics.

1.46.1 Active Sockets

This metric shows the current number of active sockets listening on this server. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of active sockets is %value%.

1.47 Log File Monitoring Metrics

This metric category provides information about the Log File Monitoring metrics.

Log File Monitoring metrics enable you to monitor log files for the occurrence of one or more string patterns in the content of a file. In addition, you can specify a string pattern to be ignored in the log file. Periodic scanning is performed against new content added since the last scan as follows:

- Lines matching the string specified by Ignore Pattern in Perl will be ignored first

- Lines matching the string specified by Match Pattern in Perl will result in one record being uploaded to the Management Repository for each matching pattern.

Examples of Matching Log File Patterns

Example 1

To match a pattern from the following log file:

1. Enter %SDP-25700% in the Match Pattern in Perl column

2. Keep the Ignore pattern in Perl column empty.

For this example, the occurrence count for the pattern is 2.

[2014-12-20T04:30:02.276+00:00] [soa_server1] [ERROR] [SDP-25700]
[oracle.sdp.messaging.jms] [tid: DaemonWorkThread: '0' of WorkManager: 'default']
[ecid: f91a6181964da5b4:7e5b4e7f:149d672ea2d:-8000-00000000000001f6,0] [APP: usermessagingserver]
An unexpected exception was caught.[[oracle.jms.AQjmsException: weblogic.common.ResourceException:

[2014-12-20T04:30:02.276+00:00] [soa_server1] [ERROR] [SDP-25700]
[oracle.sdp.messaging.jms] [tid: DaemonWorkThread: '0' of WorkManager: 'default']
[ecid: f91a6181964da5b4:7e5b4e7f:149d672ea2d:-8000-00000000000001f6,0] [APP: usermessagingserver]
An unexpected exception was caught.[[oracle.jms.AQjmsException: weblogic.common.ResourceException:

Example 2

To search for the pattern "ERROR" in the following log file, but to ignore the occurrence if the same line contains the text "ADFContext":

1. Enter %ERROR% for the pattern to be matched in the Match Pattern in Perl column

2. Enter %ADFContext% in the Ignore pattern in Perl column.

In this case the occurrence count for the pattern is 2. The occurrence of "ERROR" in the first line is ignored due to the presence of the ignore pattern "ADFContext".

[2014-12-20T12:23:56.618+00:00] [soa_server1] [ERROR] []
[oracle.adf.share.ADFContext] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)']
[ecid: 4f47280aa18c4fa8:62a22ea7:14a67a208f7:-8000-0000000000000002,0] ADF detected an ADFContext leak.[[Please see the documentation for more information about handling ADFContext leaks.
For more information about the leaking ADFContext please enable logging for oracle.adf.share.ADFContext at FINEST level.

[2014-12-20T04:30:02.276+00:00] [soa_server1] [ERROR] [SDP-25700]
[oracle.sdp.messaging.jms] [tid: DaemonWorkThread: '0' of WorkManager: 'default']
[ecid: f91a6181964da5b4:7e5b4e7f:149d672ea2d:-8000-00000000000001f6,0]
APP: usermessagingserver] An unexpected exception was caught.
[[oracle.jms.AQjmsException: weblogic.common.ResourceException:

[2014-12-20T04:30:02.276+00:00] [soa_server1] [ERROR] [SDP-25700]
[oracle.sdp.messaging.jms] [tid: DaemonWorkThread: '0' of WorkManager: 'default']
[ecid: f91a6181964da5b4:7e5b4e7f:149d672ea2d:-8000-00000000000001f6,0] [APP: usermessagingserver]
An unexpected exception was caught.[[oracle.jms.AQjmsException: weblogic.common.ResourceException:

Example 3

To search for all patterns beginning with BEA- or WLS- or OWSM- in a log file, you have a few options:

1. You can have three different entries for each pattern for the same log file as three different rows in the UI.

2. Create a regular expression with all the patterns and add it as a single entry for the log file in the Match Pattern in Perl column:

%BEA-%|%WLS-%|%OWSM%

3. If you want to search for BEA-, or WLS-, or OWSM- but to ignore if the line contains <BEA-000000>, then:

1. Enter %BEA-%|%WLS-%|%OWSM% for the pattern to be matched in the Match Pattern in Perl column

2. Enter %<BEA-000000>% in the Ignore pattern in Perl column.

See Also:
For more information about log file monitoring, such as setting values for the metrics, see:

- "Monitoring Log Files" in the Enterprise Manager Cloud Control Administrator's Guide

- "Configuring Generic Log File Monitor Criteria" in the Enterprise Manager Lifecycle Management Administrator's Guide

1.47.1 Log File Pattern Matched Content

This metric returns the matched content if this file has been specifically registered for content uploading.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 60 Minutes

1.47.2 Log File Pattern Matched Line Count

This metric returns the number of lines matching the pattern specified by this file. Setting warning or critical thresholds against this column for a specific log file name triggers the monitoring of specified criteria against this log file.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 60 Minutes

Not Defined

Not Defined

%log_file_message%. %sys_occurrence_count% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

1.48 Message Driven EJB Metrics By Server

This metric category provides information about the Message Driven EJB Metrics by Server.

1.48.1 MDB Messages (per minute)

This metric shows the average number of messages processed by Message Driven Beans (MDBs) per minute for this application. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The MDB messages are %value% (per minute).

1.48.2 MDB Suspensions (per minute)

This metric shows the average number of MDB suspensions per minute for this application. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 30 Minutes

Not Defined

Not Defined

The MDB suspensions are %value% (per minute).

1.49 Module Metrics By Server

This metric category provides information about the Module Metrics by Server.

1.49.1 Active Sessions

This metric shows the number of active sessions for the selected module. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of active sessions is %value%.

1.50 Response

This category provides information about response metrics.

1.50.1 Status

This metric shows the status of the selected server. The value is an integer, where "1" means that the server is up and running and "0" means the server is not up and running, but in a different state such as shutdown, starting, shutting down, standby, admin, resuming, suspending, or force suspending. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every Minute

Not Defined

0

The WebLogic Server is down

1.51 Server Datasource Metrics

This category provides information about server datasource metrics.

1.51.1 Available Connections

The number of database connections currently available (not in use) in this data source.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of available connections is %value%.

1.51.2 Connection Pool Size

For the current server, the current count of JDBC connections in the connection pool in the data source.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The size of connection pool is %value%.

1.51.3 Connection Requests (per minute)

The number of connection requests per minute for a connection from this data source in the last five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The connection requests are %value% (per minute).

1.51.4 Successful Connections (%)

The percentage of connection requests that successfully returned connections during the last five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The successful connection rate is %value%%%.

1.51.5 Connection Requests Waiting

The current number of connection requests waiting for a database connection.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of connection requests waiting is %value%.

1.51.6 Connection Requests that Waited (per minute)

The number of connection waits per minute in the last five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The connections that waited are %value% (per minute).

1.51.7 Connection Wait Successes (%)

The percentage of requests waiting for a connection that successfully got a connection during the last five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The connection wait success rate is %value%%%.

1.51.8 Connection Wait Successes (per minute)

The number of connection wait successes per minute in the last five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The connection wait successes are %value% (per minute).

1.51.9 Statements Added to Cache (per minute)

The number of statements per minute added to the statement cache in the last five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The statements added to cache are %value% (per minute).

1.51.10 Server Datasource - Cached Statements not Used (per minute)

The number of statements per minute not satisfied by the statement cache in the last five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The cache statements not used are %value% (per minute).

1.51.11 Cached Statements Used (%)

The percentage of statements satisfied by the statement cache during the last five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The cached statements used rate is %value%%%.

1.51.12 Cached Statements Used (per minute)

The number of statements per minute satisfied by the statement cache in the last five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The cache statements used are %value% (per minute).

1.51.13 Statement Cache Size

The number of prepared and callable statements currently cached in the statement.

Each connection in the connection pool has its own cache of statements. This number is the sum of the number of statements in the caches for all connections in the connection pool.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The statement cache size is %value%.

1.52 Server Health Metrics

This metric category provides information about the Server Health metrics.

1.52.1 Health

This metric shows the health of the selected server.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 12c

Every 15 Minutes

Not Defined

Not Defined

The server health is %value%

Setting Thresholds

You can configure the threshold for this metric to enable you to receive alerts when the status is in a specific state.

The following list provides the supported values that you can set as thresholds:

Note:
Ensure that you enter the string exactly as it appears in the list in uppercase.

- HEALTH_OK

- HEALTH_WARN

- HEALTH_CRITICAL

- HEALTH_FAILED

- HEALTH_OVERLOADED

1.53 Server Jolt Connection Pool Metrics

This category provides information about the Server Jolt Connection Pool metrics for all the Jolt connection pools on this WebLogic server.

1.53.1 Request Errors (per minute)

This metric displays the number of request errors encountered per minute.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

Request errors for jolt connection pools are %value% (per minute).

1.53.2 Pending Requests

This metric displays the current number of pending requests.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

Pending requests for jolt connection pools are %value%.

1.53.3 Requests (per minute)

This metric displays the number of requests processed per minute during the last collection interval.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

Requests for jolt connection pools are %value% (per minute).

1.54 Server Level Work Manager Metrics

This metric category provides information about the Server Level Work Manager metrics.

1.54.1 Work Manager Pending Requests

This metric shows the number of work manager requests processed per minute.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of pending requests for work manager %name% is %value%.

1.54.2 Work Manager Stuck Threads

This metric shows the number of work manager threads that are considered stuck on the basis of any stuck thread constraints.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of stuck threads for work manager %name% is %value%.

1.54.3 Work Manager Requests (per minute)

This metric shows the number of requests processed by the work manager per minute.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The work manager requests for work manager %name% are %value% (per minute).

1.55 Server State Metrics

This metric category provides the current state of the server. At any time, a WebLogic Server instance is in a particular operating state. Commands such as start, stop, and suspend, cause specific changes to the operational state of a server instance.

1.55.1 Server State

The server state metric contains a string value of the current state of the server.

For more information about server states and the server life cycle, see the Oracle Fusion Middleware Administering Server Startup and Shutdown for Oracle WebLogic Server guide or the equivalent guide for your Oracle Fusion Middleware release.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Note:
When you view the collection frequency for this metric from the Cloud Control console, it displays every 5 days. This is incorrect. The default collection frequency for this metric is every minute.
The server state metric collection frequency is based on the Response Status metric collection frequency. If you change the collection frequency for the Response Status metric, then the collection frequency for the Server State metric changes also. For more information about Response metrics, see Section 1.50, "Response".

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic 9, 10,11gR1, 12c

Every Minute

Not Defined

Not Defined

The server state is %value%.

Setting Thresholds

You can configure the threshold for this metric to enable you to receive alerts when the status is in a specific state.

Note:
In some cases, thresholds cannot be set on these different states, and Oracle recommends that you use the server Response metric to set thresholds instead.

The following list provides the supported values that you can set as thresholds:

Note:
Ensure that you enter the string exactly as it appears in the list in uppercase.

- ACTIVATE_LATER

- ADMIN

- FAILED

- FAILED_NOT_RESTARTABLE

- FAILED_RESTARTING

- FORCE_SHUTTING_DOWNFoot 1

- FORCE_SUSPENDINGFootref 1

- RESUMING

- RUNNING

- SHUTDOWN

- SHUTDOWN_IN_PROCESS

- SHUTDOWN_PENDING

- SHUTTING_DOWN

- STANDBY

- STARTING

- SUSPENDING

- UNKNOWN

1.56 Server Work Manager Metrics

This category provides information about server work manager metrics.

Note:
The server level metrics includes all work managers. This includes both application level work managers and server level work managers. Some of the server-level work managers perform system work such as timers or cluster synchronization. This work may be done even when the applications are idle.

1.56.1 Work Manager Pending Requests

For the selected server, this metric shows the number of work manager requests pending in the queue.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of work manager pending requests is %value%.

1.56.2 Work Manager Requests (per minute)

For the selected server, this metric shows the number of work manager requests processed per minute, averaged over the past five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The work manager requests are %value% (per minute).

1.56.3 Work Manager Stuck Threads

For the selected server, this metric shows the number of work manager threads that are considered stuck on the basis of any stuck thread constraints.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of work manager stuck threads is %value%.

1.57 Servlet/JSP Metrics

This category provides information about server/JSP metrics.

1.57.1 Reloads (per minute)

This metric shows the average number of reloads per minute of the selected servlet or JSP in the last five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The reloads is %value% (per minute).

1.57.2 Requests (per minute)

This metric shows the average number of invocations per minute of the selected servlet or JSP in the last five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The requests processed is %value% (per minute).

1.57.3 Request Processing Time (ms)

This metric shows the average number of invocations per minute of the selected servlet or JSPs in the last five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The request processing time is %value% ms.

1.58 Servlet Rollup

This category provides information about servlet rollup metrics.

1.58.1 Servlet - Active Invocations

This metric provides details about the servlet invocations that are active and are currently in the web container. Active invocation refers to the number of requests that are currently being processed by the server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic 7, 8.x, 9.x

Every 15 Minutes

1.58.2 Servlet - Current Client Processing Time

This metric indicates the time taken to execute the servlet during the last interval.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic 7, 8.x, 9.x

Every 15 Minutes

Not Defined

Not Defined

The Current Client Processing time for servlet %Name% is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name", "Application Name", and "Web Application Name" objects.

If warning or critical threshold values are currently set for any unique combination of "Name", "Application Name", and "Web Application Name" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Name", "Application Name", and "Web Application Name" objects, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

1.58.3 Servlet - Average Execution Time

This metric indicates the average time taken by a servlet to respond.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic 7, 8.x, 9.x

Every 15 Minutes

1.58.4 Servlet - Total Execution Time

This metric indicates the total execution time for a request.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic 7, 8.x, 9.x

Every 15 Minutes

1.58.5 Servlet - Invocations Per Second

This metric indicates the number of number of requests to the server per second.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic 7, 8.x, 9.x

Every 15 Minutes

Not Defined

Not Defined

The invocations per second for Servlet %Name% is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name", "Application Name", and "Web Application Name" objects.

If warning or critical threshold values are currently set for any unique combination of "Name", "Application Name", and "Web Application Name" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Name", "Application Name", and "Web Application Name" objects, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

1.58.6 Servlet - Invocation Total Count

This metric indicates the total number of invocations for this servlet.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic 7, 8.x, 9.x

Every 15 Minutes

1.59 Thread Pool Metrics

This metric category provides information about the Thread Pool metrics.

1.59.1 Thread Pool - Idle Threads

The number of currently idle threads in the thread pool.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 9, 10g, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of idle threads is %value%.

1.59.2 Thread Pool - Total Threads

This metric shows the total number of threads in the thread pool.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of threads is %value%.

1.59.3 Thread Pool - Hogging Threads

This metric shows the number of threads that are being hogged by a request.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 9, 10g, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of hogged threads is %value%.

1.59.4 Thread Pool - Pending User Requests

This metric shows the number of pending user requests in the priority queue

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of pending user requests is %value%.

1.59.5 Thread Pool - Pending Requests

This metric shows the number of pending requests.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 9, 10g, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of pending requests is %value%.

1.59.6 Thread Pool - Standby Threads

This metric shows the number of threads in the standby pool. Threads that are not needed to handle the present work load are designated as standby and added to the standby pool. These threads are activated when more threads are needed.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 9, 10g, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of standby threads is %value%.

1.59.7 Thread Pool - Requests (per minute)

This metric shows the number of work manager requests processed per minute.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 9, 10g, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The request throughput is %value% threads per minute.

1.59.8 Thread Pool - Threads in Use

This metric shows the number of threads in use.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 9, 10g, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of threads in use is %value%.

1.59.9 Thread Pool - Pending System Requests

This metric shows the number of pending system requests.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 9, 10g, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of pending system requests is %value%.

1.60 Web Module Metrics

This category provides information about Web module metrics.

1.60.1 Web Module - Requests (per minute)

For the selected Web module, this metric shows the average number of invocations per minute of servlets and/or JSPs in the last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.60.2 Web Module - Request Processing Time (ms)

For the selected Web module, this metric shows the average amount of time spent (in milliseconds) executing servlets and/or JSPs in the last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.60.3 Web Module - Active Sessions

This metric shows the number of active sessions for the selected web module.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.61 Java EE Web Service Endpoints

This category provides information about Java JEE service endpoints metrics.

1.61.1 Dispatch Time Total

This metric shows the total amount of dispatch time since the Web service was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.61.2 Execution Time Total

This metrics represents the total time that the Web service port has spent executing since the Web service was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.61.3 Invocation Count

This metric represents the total number of invocations for the selected Web services port since the Web service was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.61.4 Response Count

This metric shows the total number of responses since the Web service was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.61.5 Response Error Count

This number provides the total number of response errors since the Web service was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.61.6 Response Time Total

This metric represents the total response time of this Web services port since the Web service was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

1.62 Work Manager Metrics

This category provides information about work manager metrics.

1.62.1 Work Manager Pending Requests

This metric shows the number of pending work manager requests per minute, averaged over the past five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of work manager pending requests is %value%.

1.62.2 Work Manager Requests (per minute)

This metric shows the number of requests processed by the work manager per minute, averaged over the past five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The work manager requests are %value% (per minute).

1.62.3 Work Manager Stuck Threads

This metric shows the number of work manager threads that are considered stuck on the basis of any stuck thread constraints.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 10gR3, 11g, 12c

Every 15 Minutes

Not Defined

Not Defined

The number of work manager stuck threads is %value%.

1.62.4 Work Manager - Pending Request Current Count

This metric shows the number of pending work manager requests per minute.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 9

Every 15 Minutes

Not Defined

Not Defined

The Current Pending Request Count for Work Manager %Name% associated with Application %ApplicationName% is %value%.

1.62.5 Work Manager - Stuck Thread Count

This metric shows the number of work manager threads that are considered stuck on the basis of any stuck thread constraints.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server9

Every 15 Minutes

Not Defined

Not Defined

The Stuck Thread count for Work Manager %Name% associated with Application %ApplicationName% is %value%.

1.63 Work Manager Metrics for Application

This metric category provides information about the Work Manager metrics for a selected application.

1.63.1 Work Manager - Pending Request Current Count For Application

This metric shows the current number of pending work manager requests across all work managers for the selected application.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 9

Every 15 Minutes

Not Defined

Not Defined

The Current Pending Request count across all Work Managers for %ApplicationName% is %value%.

1.63.2 Work Manager - Stuck Thread Count For Application

This metric shows the number of work manager threads across all work managers for this application that are considered stuck on the basis of any stuck thread constraints.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 9

Every 15 Minutes

Not Defined

Not Defined

The Stuck Thread count across all Work Managers for %ApplicationName% is %value%.

1.64 Work Manager Metrics for Module

This metric category provides information about the Work Manager metrics for a selected module.

1.64.1 Work Manager - Pending Request Current Count For Module

This metric shows the current number of pending work manager requests across all work managers for the selected module.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 9

Every 15 Minutes

Not Defined

Not Defined

The Current Pending Request count across all Work Managers for %ModuleName% is %value%

1.64.2 Work Manager - Stuck Thread Count For Module

This metric shows the number of work manager threads across all work managers for this module that are considered stuck on the basis of any stuck thread constraints.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 9

Every 15 Minutes

Not Defined

Not Defined

The Stuck Thread count across all Work Managers for %ModuleName% is %value%

1.65 All Work Managers

This metric category provides information about the Work Manager metrics for all the work managers for this WebLogic server.

1.65.1 All Work Managers - Pending Request Current Count

This metric shows the current number of pending work manager requests across all work managers.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 9

Every 15 Minutes

Not Defined

Not Defined

The Current Pending Request count across all Work Managers for J2EE Server is %value%

1.65.2 All Work Managers - Stuck Thread Count

This metric shows the number of work manager threads across all work managers that are considered stuck on the basis of any stuck thread constraints.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebLogic Server 9

Every 15 Minutes

Not Defined

Not Defined

The Stuck Thread count across all Work Managers for J2EE Server is %value%

Footnote Legend

Footnote 1: This value is deprecated.

2 Oracle WebLogic Cluster

The Oracle WebLogic Cluster metrics provide for each metric the following information:

- Description

- Metric summary. The metric summary can include some or all of the following: target version, collection frequency, default warning threshold, default critical threshold, and alert text.

- Multiple Thresholds (where applicable)

2.1 Cluster Overview Metrics

This category provides information about the Oracle WebLogic cluster.

2.1.1 Active JTA Transactions

This metric shows the number of currently active JTA transactions on the selected cluster.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of active JTA transactions is %value%.

2.1.2 Active Sessions

This metric shows the number of active sessions for the selected cluster.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of active sessions is %value%.

2.1.3 Bean Accesses (per minute)

This metric shows the average EJB pool accesses per minute since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The bean accesses are %value% (per minute).

2.1.4 Bean Access Failures (per minute)

This metric shows the average number of failed pool accesses per minute for this cluster since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The bean access failures are %value% (per minute).

2.1.5 Bean Activations (per minute)

This metric shows the average number of beans per minute that have been activated since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The bean activations are %value% (per minute).

2.1.6 Bean Destroys (per minute)

This metric shows the bean destroys per minute since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The bean destroys are %value% (per minute).

2.1.7 Bean Successes (%)

This metric shows the percentage of pool accesses that were successful since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The bean success rate is %value%%%.

2.1.8 Bean Transaction Commits (%)

This metric shows the percentage of EJB transactions that were committed since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The bean transaction commit rate is %value%%%.

2.1.9 Bean Transaction Commits (per minute)

This metric shows the average number of EJB transaction commits per minute for this cluster since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The bean transaction commits are %value% (per minute).

2.1.10 Bean Transaction Rollbacks (per minute)

This metric shows the average number of EJB transaction rollbacks per minute for this application since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The bean transaction rollbacks are %value% (per minute).

2.1.11 Bean Transaction Timeouts (per minute)

This metric shows the average number of EJB transaction timeouts per minute for this cluster since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The bean transaction timeouts are %value% (per minute).

2.1.12 Beans in Use

This metric shows the number of bean instances currently being used from the free pool.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of beans in use is %value%.

2.1.13 Cache Accesses (per minute)

This metric shows the total number of attempts to access a bean from the cache per minute since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The cache accesses are %value% (per minute).

2.1.14 Cache Hits (%)

This metric shows the percentage of cache accesses that completed successfully since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The cache hit rate is %value%%%.

2.1.15 Cache Misses (per minute)

This metric shows the average number of cache misses per minute since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The cache misses are %value% (per minute).

2.1.16 Cached Beans

This metric shows the total number of beans currently in the EJB cache.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of cached beans is %value%.

2.1.17 Committed JTA Transactions (per minute)

This metric shows the total number of transactions committed per minute, since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The committed JTA transactions are %value% (per minute).

2.1.18 Current JMS Messages

This metric shows the number of JMS messages currently stored. This number does not include pending messages.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of JMS messages stored is %value%.

2.1.19 Free Bean Instances

This metric shows the number of available EJB instances in the free pool.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of free bean instances is %value%.

2.1.20 JDBC Connection Creates (per minute)

This metric shows the number of JDBC connections created per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The connections created are %value% (per minute).

2.1.21 JMS Servers

This metric shows the total number of JMS servers.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of JMS Servers is %value%.

2.1.22 JTA Transaction Rollbacks (per minute)

This metric shows the number of transactions rolled back per minute, averaged over the metric collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The JTA transaction rollbacks are %value% (per minute).

2.1.23 MDB Messages (per minute)

This metric specifies the number of messages processed by message-driven beans (MDBs) per minute since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The MDB messages are %value% (per minute).

2.1.24 Open JDBC Connections

This metric shows the number of open connections.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of connections in use is %value%.

2.1.25 Pending JMS Messages

This metric shows the number of unacknowledged or uncommitted messages currently pending stored in the selected JMS server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of JMS messages pending is %value%.

2.1.26 Request Processing Time (ms)

This metric shows the average time taken (in milliseconds) to process requests since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The request processing time is %value% ms.

2.1.27 Requests (per minute)

This metric shows the number of requests processed per minute for this cluster.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The requests processed are %value% (per minute).

2.1.28 Work Manager Pending Requests

This metric shows the number of work manager requests processed per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of work manager pending requests is %value%.

2.1.29 Work Manager Requests (per minute)

This metric shows the number of requests processed by the work manager per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The work manager requests are %value% (per minute).

2.2 Cluster Overview Metrics By Server

This category provides overview information about the Oracle WebLogic cluster for the selected server.

2.2.1 Active JTA Transactions

This metric shows the number of currently active JTA transactions on the selected server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of active JTA transactions for server %serverName% is %value%.

2.2.2 Active Sessions

This metric shows the number of active sessions for the selected server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of active sessions for server %serverName% is %value%.

2.2.3 Bean Access Failures (per minute)

This metric shows the average number of times per minute that a failed attempt was made to get an instance from the free pool since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The bean access failures for server %serverName% are %value% (per minute).

2.2.4 Bean Accesses (per minute)

For the selected server, this metric shows how many times the EJB pool has been accessed per minute since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The bean accesses for server %serverName% are %value% (per minute).

2.2.5 Bean Activations (per minute)

For the selected server, this metric shows the total number of beans that have been activated per minute since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The bean activations for server %serverName% are %value% (per minute).

2.2.6 Bean Destroys (per minute)

For the selected server, this metric shows the bean destroys performed per minute since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The bean destroys for server %serverName% are %value% (per minute).

2.2.7 Bean Successes (%)

For the selected server, this metric shows the percentage of pool accesses that were successful since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The bean success rate for server %serverName% is %value%%%.

2.2.8 Bean Transaction Commits (%)

For the selected server, this metric shows the percentage of transactions that were committed since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The bean transaction commit rate for server %serverName% is %value%%%.

2.2.9 Bean Transaction Commits (per minute)

For the selected server, this metric shows the transaction commits per minute since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The bean transaction commits for server %serverName% are %value% (per minute).

2.2.10 Bean Transaction Rollbacks (per minute)

For the selected server, this metric shows the average number of EJB transaction rollbacks per minute since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The bean transaction rollbacks for server %serverName% are %value% (per minute).

2.2.11 Bean Transaction Timeouts (per minute)

For the selected server, this metric shows the average number of EJB transaction timeouts per minute since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The bean transaction timeouts for server %serverName% are %value% (per minute).

2.2.12 Beans in Use

For the selected server, this metric shows the number of EJB instances currently being used from the free pool.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of beans in use for server %serverName% is %value%.

2.2.13 Cache Accesses (per minute)

For the selected server, this metric shows the average number of EJB cache access attempts per minute since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The cache accesses for server %serverName% are %value% (per minute).

2.2.14 Cache Hits (%)

For the selected server, this metric indicates the percentage of cache accesses that completed successfully since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The cache hit rate for server %serverName% is %value%%%.

2.2.15 Cache Misses (per minute)

For the selected server, this metric shows the average number of EJB cache misses per minute since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The cache misses for server %serverName% are %value% (per minute).

2.2.16 Cached Beans

For the selected server, this metric shows the total number of EJBs currently active in the EJB cache.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of cached beans for server %serverName% is %value%.

2.2.17 Committed JTA Transactions (per minute)

This metric shows the number of transactions per minute that have been committed on the selected server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The committed JTA transactions for server %serverName% are %value% (per minute).

2.2.18 Current JMS Messages

For the selected server, this metric shows the total number of current JMS messages.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of JMS messages stored for server %serverName% is %value%.

2.2.19 Free Bean Instances

For the selected server, this metric shows the current number of available EJB instances in the free pool.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of free bean instances for server %serverName% is %value%.

2.2.20 JDBC Connection Creates (per minute)

For the selected server, this metric shows the number of database connections created per minute since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The connections created for server %serverName% are %value% (per minute).

2.2.21 JMS Servers

This metric shows the number of JMS servers that are deployed on this WebLogic Server instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of JMS Servers for server %serverName% is %value%.

2.2.22 JTA Transaction Rollbacks (per minute)

This metric shows the number of JTA transactions rolled back per minute since the last metric collection on the selected server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The JTA transaction rollbacks for server %serverName% are %value% (per minute).

2.2.23 MDB Messages (per minute)

For the selected server, this metric shows the number of messages processed by message-driven beans (MDBs) per minute since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The MDB messages for server %serverName% are %value% (per minute).

2.2.24 Open JDBC Connections

For the selected server, this metric shows the number of JDBC connections currently open.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of connections in use for server %serverName% is %value%.

2.2.25 Pending JMS Messages

This metric shows the current number of messages pending (unacknowledged or uncommitted) stored on the JMS servers deployed on this WebLogic Server instance. Pending messages are over and above the current number of messages.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of JMS messages pending for server %serverName% is %value%.

2.2.26 Request Processing Time (ms)

For the selected server, this metric shows the average amount of time (in milliseconds) spent running servlets and JSPs since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The request processing time for server %serverName% is %value% ms.

2.2.27 Requests (per minute)

For the selected server, this metric shows the average number of servlet and JSP invocations per minute since the last metric collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The requests processed for server %serverName% are %value% (per minute).

2.2.28 Work Manager Pending Requests

For the selected server, this metric shows the number of work manager requests waiting in the queue.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The number of work manager pending requests for server %serverName% is %value%.

2.2.29 Work Manager Requests (per minute)

This metric shows the number of work manager requests processed per minute since the last metric collection on the selected server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

Not Defined

Not Defined

The work manager requests for server %serverName% are %value% (per minute).

2.3 Deployment Information

This category provides information about the deployed applications on the WebLogic Cluster.

2.3.1 Deployed Applications

This metric shows the number of applications deployed on the WebLogic Cluster.

Target Version

Collection Frequency

Oracle WebLogic Server 11g Release 1 (10.3.1, 10.3.3) and later

Every 30 Minutes

2.4 JMS Destination Metrics

This metric category provides information about all JMS destinations running on servers that are members of the cluster. Each destination is identified by a topic or queue name, type (topic or queue), and JMS module name.

2.4.1 Bytes Pending

This metric shows the pending bytes count for the destination.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1) and later

Every 30 Minutes

Not Defined

Not Defined

There are %value% pending bytes for %type% %name%, module %moduleName%.

2.4.2 Bytes Received (per minute)

This metric shows the number of bytes received per minute for the destination.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1) and later

Every 30 Minutes

Not Defined

Not Defined

There are %value% received messages (per minute) for %type% %name%, module %moduleName%.

2.4.3 Bytes Stored

This metric shows the stored bytes for the destination.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1) and later

Every 30 Minutes

Not Defined

Not Defined

There are %value% stored bytes for %type% %name%, module %moduleName%.

2.4.4 Consumers Active

This metric shows the number of active consumers for the destination.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1) and later

Every 30 Minutes

Not Defined

Not Defined

There are %value% active consumers for %type% %name%, module %moduleName%.

2.4.5 Messages Deleted (per minute)

This metric shows the number of messages deleted per minute for the destination.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1) and later

Every 30 Minutes

Not Defined

Not Defined

There are %value% deleted messages (per minute) for %type% %name%, module %moduleName%.

2.4.6 Messages Moved (per minute)

This metric shows the number of messages moved per minute for the destination.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1) and later

Every 30 Minutes

Not Defined

Not Defined

There are %value% moved messages (per minute) for %type% %name%, module %moduleName%.

2.4.7 Messages Pending

This metric shows the number of pending messages for the destination.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1) and later

Every 30 Minutes

Not Defined

Not Defined

There are %value% pending messages for %type% %name%, module %moduleName%.

2.4.8 Messages Received (per minute)

This metric shows the number of messages received per minute for the destination.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1) and later

Every 30 Minutes

Not Defined

Not Defined

There are %value% received bytes (per minute) for %type% %name%, module %moduleName%.

2.4.9 Messages Stored

This metric shows the number of stored messages for the destination.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1) and later

Every 30 Minutes

Not Defined

Not Defined

There are %value% stored messages for %type% %name%, module %moduleName%.

2.5 Response

This category provides information about the Response Status metric.

2.5.1 Status

This metric provides information about the status of the WebLogic Cluster

2.6 Work Manager Metrics

This category provides information about the number of stuck threads across all work managers for a cluster member.

2.6.1 Work Manager Stuck Threads

This metric shows the number of work manager threads that are considered stuck.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Oracle WebLogic Server 11g Release 1 (10.3.1) and later

Every 30 Minutes

Not Defined

Not Defined

There are %value% stuck threads in all work managers for this cluster.

3 Oracle Access Manager

Oracle Enterprise Manager can be used to manage Oracle Access Manager (OAM) metrics that show the performance for Oracle Access Manager 11g servers and OAM server clusters.

The Oracle Access Manager metrics provide for each metric the following information:

- Description

- Metric summary. The metric summary can include some or all of the following: target version, collection frequency, default warning threshold, default critical threshold, and alert text.

- Multiple Thresholds (where applicable)

- Data source

- User action

3.1 All Datasources Metrics

This metric category describes the Datasources metrics.

3.1.1 Available Connections

This metric shows the number of database connections currently available.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of available connections is %value%.

3.1.2 Cached Statements Not Used (per minute)

This metric shows the number of statements per minute not satisfied by the statement cache.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The cache statements not used are %value% (per minute).

3.1.3 Cached Statements Used (%)

This metric shows the percentage of statements satisfied by the statement cache.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The cached statements used rate is %value%%%.

3.1.4 Cached Statements Used (per minute)

This metric shows the number of statements per minute satisfied by the statement cache.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The cache statements used are %value% (per minute).

3.1.5 Connection Pool Size

This metric shows the current count of JDBC connections in the JDBC connection pool.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connection pool size is %value%.

3.1.6 Connection Requests (per minute)

This metric shows the number of requests for a JDBC connection from this data source per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connection requests are %value% (per minute).

3.1.7 Connection Requests that Waited (per minute)

This metric shows the number of JDBC connection waits per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connections that waited are %value% (per minute).

3.1.8 Connection Requests Waiting

This metric shows the current number of JDBC connection requests waiting for a database connection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of connection requests waiting is %value%.

3.1.9 Connection Wait Successes (%)

This metric shows the percentage of requests waiting for a JDBC connection that successfully got a connection during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connection wait successes are %value%%%.

3.1.10 Connection Wait Successes (per minute)

This metric shows the number of JDBC connection wait successes per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connection wait successes are %value% (per minute).

3.1.11 Connections Created (per minute)

This metric shows the number of database connections created per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connections created are %value% (per minute).

3.1.12 Connections in Use

This metric shows the number of JDBC connections currently in use by applications.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of connections in use is %value%.

3.1.13 Statement Cache Size

This metric shows the number of prepared and callable JDBC statements currently cached in the connection pool.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The cache size is %value%.

3.1.14 Statements Added to Cache (per minute)

This metric shows the number of statements per minute added to the statement cache.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The statements added to cache are %value% (per minute).

3.1.15 Successful Connections (%)

This metric shows the percentage of requests that successfully returned JDBC connections.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The successful connection rate is %value%%%.

3.2 Application EJB Cache Metrics

This metric category describes the Application Enterprise JavaBeans (EJB) Cache metrics.

3.2.1 Bean Activations (per minute)

For the selected application, this metric shows the total number of EJB that have been activated since the server started.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The bean activations are %value% (per minute).

3.2.2 Cache Accesses (per minute)

This metric shows the number times per minute that an attempt was made to access the EJB cache.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The cache accesses is %value% (per minute).

3.2.3 Cache Hits (%)

This metric shows the percentage of cache accesses that completed successfully in the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The EJB cache hit rate is %value%%%.

3.2.4 Cache Misses (per minute)

This metric shows the average number of cache misses per minute for this EJB module.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The cache misses are %value% (per minute).

3.2.5 Cache Passivations (per minute)

This metric shows the total number of beans per minute that have been passivated.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The EJB Passivations are %value% (per minute).

3.2.6 Cached Beans

This metric shows the total number of EJBs currently active in the EJB cache.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of cached beans is %value%.

3.3 Application EJB Pool Metrics

This metric category described the Application EJB Pool metrics.

3.3.1 Available Beans

This metric shows the number of available beans.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of available beans is %value%.

3.3.2 Bean Accesses (per minute)

This metric shows the average number of pool accesses per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The bean accesses are %value% (per minute).

3.3.3 Bean Access Failures (per minute)

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The bean access failures are %value% (per minute).

This metric shows the percentage of pool accesses to the server that were successful.

3.3.4 Bean Destroys (per minute)

This metric shows the average number of EJB destroys per minute for the selected server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The bean destroys are %value% (per minute).

3.3.5 Beans in Use

This metric shows the number of EJB instances currently being used from the free pool.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of beans in use is %value%.

3.3.6 Successful Bean Accesses (%)

This metric shows the percentage of attempts to access the pool that were successful.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The successful bean access rate is %value%%%.

3.4 Application EJB Transaction Metrics

This metric category describes the Application EJB Transaction metrics.

3.4.1 Bean Transaction Commits (%)

This metric shows the percentage of EJB transactions that were committed.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The bean transaction commit rate is %value%%%.

3.4.2 Bean Transaction Commits (per minute)

This metric shows the EJB transaction commits per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The bean transaction commits are %value% (per minute).

3.4.3 Bean Transaction Rollbacks (per minute)

This metric shows the EJB transaction rollbacks per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The bean transaction rollbacks are %value% (per minute).

3.4.4 Bean Transaction Timeouts (per minute)

This metric shows the EJB transaction timeouts per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The bean transaction timeouts are %value% (per minute).

3.5 Application Message Driven EJB Metrics

This metric category describes the Application Message Driven EJB metrics.

3.5.1 MDB Messages (per minute)

This metric specifies the number of messages processed by message-driven beans (MDBs) per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The MDB messages are %value% (per minute).

3.5.2 MDB Suspensions (per minute)

This metric specifies the number of MDB JMS connection suspensions per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The MDB suspensions are %value% (per minute).

3.6 Application State Metrics

This metric category describes the Application State metric.

3.6.1 Application State

This metric displays the state of the selected application.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The application state is %value%.

3.7 Audit Operations

This metric category describes the metrics related to auditing operations for Oracle Access Manager.

3.7.1 Average Audit Latency (ms)

This metric specifies the average latency, in milliseconds, of the audit operations for this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Audit Operations Latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.7.2 Audit Operations per second

This metric specifies the audit throughput (audit operations per second) for this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Audit Operations Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.7.3 Server Name

This metric specifies the name of the server performing audit operations.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

3.8 Authentication

This metric category describes the metrics related to Oracle Access Manager authentication operations.

3.8.1 Average Authentication Latency (ms)

This metric specifies the average latency, in milliseconds, of the authentication requests handled by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authentication Latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.8.2 Authentication Requests per second

This metric specifies the rate of authentication request throughput (requests per second) for this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authentication Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.8.3 Authentication Success Rate (%)

This metric specifies the success to failure rate, as a percentage, for authorization requests handled by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authentication Success Rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.8.4 Server Name

This metric specifies the name of the OAM server handling the authentication request.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

3.9 Authorization

This metric category describes the metrics related to Oracle Access Manager authorization operations.

3.9.1 Average Authorization Latency (ms)

This metric specifies the average latency, in milliseconds, for authorization requests for this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.9.2 Authorization Requests per second

This metric specifies the authorization request throughput (requests per second) for this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.9.3 Authorization Success Rate (%)

This metric specifies the authorization request throughput (requests per second) for this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Success Rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.9.4 Server Name

This metric specifies the name of the server handling the authorization request.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

3.10 Connector Metrics

This metric category describes the Connector metrics.

3.10.1 Connection Requests Rejected (per minute)

This metric displays the total number of rejected connector requests per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of rejected connector connections is %value% (per minute).

3.10.2 Connection Requests Satisfied (per minute)

This metric displays the total number of satisfied connector connections per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of satisfied connector connections is %value% (per minute).

3.10.3 Connection Waiters

This metric displays the number of application requests waiting for a connection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of connector connection waiters is %value%.

3.10.4 Connections Closed (per minute)

This metric displays the number of physical database connections from this instance of the connection pool that are closed each minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of closed connector connections is %value% (per minute).

3.10.5 Connections Created (per minute)

This metric displays the number of physical database connections from this instance of the connection pool that are created each minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of created connector connections is %value% (per minute).

3.10.6 Connections Destroyed (per minute)

This metric displays the number of physical database connections from this instance of the connection pool that were destroyed each minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connector connection destroys are %value% (per minute).

3.10.7 Connections Destroyed by Shrinking (per minute)

This metric displays the number of physical database connections from this instance of the connection pool that were destroyed due to shrinking each minute

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connector connection destroys due to shrinking are %value% (per minute).

3.10.8 Connections Destroyed due to Error (per minute)

This metric displays the number of physical database connections from this instance of the connection pool that were destroyed due to errors each minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connector connection destroys due to error are %value% (per minute).

3.10.9 Connections Recycled (per minute)

This metric displays the number of physical database connections from this instance of the connection pool that were recycled each minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of recycled connector connections is %value% (per minute).

3.10.10 Free Connections

This metric displays the number of physical database connections from this instance of the connection pool that are available.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of free connector connections is %value%.

3.10.11 Open Connections

This metric displays the number of open physical database connections from this instance of the connection pool.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of open connector connections is %value%.

3.10.12 Unavailable Connections

This metric displays the number of connections that are currently unavailable to applications.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of unavailable connector connections for pool %name% is %value%.

3.11 Connector Connection Pool Metrics

This metric category describes the Connector Connection Pool metrics.

3.11.1 Connection Requests Rejected (per minute)

This metric displays the number of rejected connection requests to the connector connection pool.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of rejected connector connections for pool %name% is %value% (per minute).

3.11.2 Connection Requests Satisfied (per minute)

This metric displays the number of successful or satisified connection requests.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of satisfied connector connections for pool %name% is %value% (per minute).

3.11.3 Connection Waiters

This metric displays the number of application requests waiting for a connection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of connector connection waiters is %value%.

3.11.4 Connections Closed (per minute)

This metric displays the number of connections closed each minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of closed connector connections is %value% (per minute).

3.11.5 Connections Created (per minute)

This metric displays the number of connections created each minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of created connector connections is %value% (per minute).

3.11.6 Connections Destroyed (per minute)

This metric displays the number of connections destroyed each minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connector connection destroys are %value% (per minute).

3.11.7 Connections Destroyed by Shrinking (per minute)

This metric displays the number of connections destroyed due to shrinking each minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connector connection destroys due to shrinking are %value% (per minute).

3.11.8 Connections Destroyed due to Error (per minute)

This metric displays the number of connections destroyed due to errors each minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connector connection destroys due to error are %value% (per minute).

3.11.9 Connections Recycled (per minute)

This metric displays the number of connections recycled each minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of recycled connector connections for pool %name% is %value% (per minute).

3.11.10 Free Connections

This metric displays the number of available connections.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of free connector connections is %value%.

3.11.11 Open Connections

This metric displays the number of open connections.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of open connector connections is %value%.

3.11.12 Unavailable Connections

This metric displays the number of unavailable connections.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of unavailable connector connections for pool %name% is %value%.

3.12 Datasource Metrics

This metric category described the Datasource metrics.

3.12.1 Available Connections

For the selected data source, this metric shows the number of database connections currently available

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of available connections for datasource %name% is %value%.

3.12.2 Cached Statements not Used (per minute)

For the selected data source, this metric shows the number of statements per minute not satisfied by the statement cache

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The cache statements not used for datasource %name% are %value% (per minute).

3.12.3 Cached Statements Used (%)

For the selected data source, this metric shows the percentage of statements satisfied by the statement cache

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The cached statements used rate is %value%%%.

3.12.4 Cached Statements Used (per minute)

For the selected data source, this metric shows the number of statements per minute satisfied by the statement cache

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The cache statements used are %value% (per minute).

3.12.5 Connection Leaks (per minute)

For the selected data source, this metric shows the number of JDBC connection leaks per minute

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connection leaks for datasource %name% are %value% (per minute).

3.12.6 Connection Refresh Failures (per minute)

For the selected data source, this metric shows the number of failed JDBC connection refreshes per minute

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connection refresh failures for datasource %name% are %value% (per minute).

3.12.7 Connection Request Failures (per minute)

For the selected data source, this metric shows the number of failed JDBC connection requests per minute

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connection request failures for datasource %name% are %value% (per minute).

3.12.8 Connection Requests (per minute)

For the selected data source, this metric shows the number of requests for a JDBC connection from this data source per minute

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connection requests for datasource %name% are %value% (per minute).

3.12.9 Connection Requests that Waited (per minute)

For the selected data source, this metric shows the number of JDBC connection waits per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connections that waited for datasource %name% are %value% (per minute).

3.12.10 Connection Requests Waiting

For the selected data source, this metric shows the current number of JDBC connection requests waiting for a database connection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of connection requests waiting for datasource %name% is %value%.

3.12.11 Connection Wait Successes (%)

For the selected data source, this metric shows the percentage of requests waiting for a JDBC connection that successfully got a connection during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connection wait success rate for datasource %name% is %value%%%.

3.12.12 Connection Wait Successes (per minute)

For the selected data source, this metric shows the number of JDBC connection wait successes per minute

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connection wait successes for datasource %name% are %value% (per minute).

3.12.13 Connections Created (per minute)

For the selected data source, this metric shows the number of database connections created per minute

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connections created for datasource %name% are %value% (per minute).

3.12.14 Connections in Use

For the selected data source, this metric shows the number of JDBC connections currently in use by applications.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of connections in use for datasource %name% is %value%.

3.12.15 Failed Waiting Connection Requests (per minute)

For the selected data source, this metric shows the number of JDBC connection wait failures per minute

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The connection wait failures for datasource %name% are %value% (per minute).

3.12.16 Statements Added to Cache (per minute)

For the selected data source, this metric shows the number of statements per minute added to the statement cache.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The statements added to cache for datasource %name% are %value% (per minute).

3.12.17 Statements Discarded from Cache (per minute)

For the current data source, this metric shows the number of statements per minute discarded from the statement cache.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The statements discarded from the cache for datasource %name% are %value% (per minute).

3.12.18 Successful Connections (%)

For the selected data source, this metric shows the percentage of requests that successfully returned JDBC connections.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The successful connection rate for datasource %name% is %value%%%.

3.12.19 Unavailable Connections

For the selected data source, this metric shows the number of database connections that are currently unavailable (in use or being tested by the system).

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of unavailable connections for datasource %name% is %value%.

3.13 Datasource State Metric

This metric category describes state of the datasource.

3.13.1 State

This metric displays the state of the datasource.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The state of datasource %name% is %value%.

3.14 Deployment Module Metrics

This metric category describes the Deployment Module metrics.

3.14.1 Active Sessions

For the selected deployed module, this metric displays the number of active sessions.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of active sessions for web module %webModuleName% is %value%.

3.15 Deployment Application Level Work Manager Metrics

This metric category describes the Deployment Application Level Work Manager metrics.

3.15.1 Work Manager Pending Requests

For the selected server, this metric shows the number of work manager requests pending in the queue.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of work manager pending requests work manager %name% is %value%.

3.15.2 Work Manager Stuck Threads

For the selected server, this metric shows the number of work manager threads that are considered stuck on the basis of any stuck thread constraints.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of work manager stuck threads work manager %name% is %value%.

3.15.3 Work Manager Requests (per minute)

For the selected server, this metric shows the number of work manager requests processed per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The work manager requests work manager %name% are %value% (per minute).

3.16 Deployment Module Metrics By Application

This metric category describes the Deployment Module metrics by application.

3.16.1 Active Sessions

This metric displays the total number of active sessions for the deployed module.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of active sessions %value%.

3.17 Deployment Work Manager Metrics

This metric category describes the Deployment Work Manager metrics.

3.17.1 Work Manager Pending Requests

For the deployed module, this metric shows the number of work manager requests pending in the queue.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of work manager pending requests is %value%.

3.17.2 Work Manager Requests (per minute)

For the deployed module, this metric shows the number of work manager requests processed per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The work manager requests are %value% (per minute).

3.17.3 Work Manager Stuck Threads

For the deployed module, this metric shows the number of work manager threads that are considered stuck on the basis of any stuck thread constraints.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of work manager stuck threads is %value%.

3.18 EJB Cache Metrics

This metric category describes the Enterprise JavaBeans (EJB) Cache metrics.

3.18.1 Cached Beans

This metric shows the total number of EJBs currently active in the EJB cache.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of cached beans for EJB name %name%, EJB module %ejbModuleName% is %value%.

3.18.2 Cache Hits (%)

This metric displays the percentage of cache accesses that completed successfully during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The EJB cache hit rate for EJB name %name%, EJB module %ejbModuleName% is %value%%%.

3.18.3 Bean Activations (per minute)

This metric shows the total number of EJBs that have been activated since the server started.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The bean activations for EJB name %name%, EJB module %ejbModuleName% are %value% (per minute).

3.18.4 Cache Accesses (per minute)

This metric displays the number of cache access attempts per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The cache accesses for EJB name %name%, EJB module %ejbModuleName% is %value% (per minute).

3.18.5 Cache Misses (per minute)

This metric shows the average number of cache misses per minute for this EJB cache.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The cache misses for EJB name %name%, EJB module %ejbModuleName% are %value% (per minute).

3.18.6 Cache Passivations (per minute)

This metric shows the total number of beans per minute that have been passivated

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The EJB Passivations for EJB name %name%, EJB module %ejbModuleName% are %value% (per minute).

3.19 EJB Pool Metrics

This metric category descibes the EJB pool metrics.

3.19.1 Bean Accesses (per minute)

This metric shows how many times the EJB pool has been accessed per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The bean accesses for EJB %name%, EJB module %ejbModuleName% are %value% (per minute).

3.19.2 Bean Destroys (per minute)

This metric shows the average number of EJB destroys per minute for this EJB pool.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The bean destroys for EJB %name%, EJB module %ejbModuleName% are %value% (per minute).

3.19.3 Bean Access Failures (per minute)

This metric shows the average number of times per minute that a failed attempt was made to get an instance from the free pool.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The bean access failures for EJB %name%, EJB module %ejbModuleName% are %value% (per minute).

3.19.4 Beans in Use

This metric shows the number of EJB instances currently being used from the free pool.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of beans in use for EJB %name%, EJB module %ejbModuleName% is %value%.

3.19.5 Successful Bean Accesses (%)

This metric shows the percentage of EJB pool accesses that were successful.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The successful bean access rate for EJB %name%, EJB module %ejbModuleName% is %value%%%.

3.19.6 Available Beans

This metric shows the current number of available EJB instances in the free pool.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of available beans for EJB %name%, EJB module %ejbModuleName% is %value%.

3.20 EJB Transaction Metrics

This metric category describes the EJB Transaction metrics.

3.20.1 Bean Transaction Commits (%)

This metric shows the percentage of EJB transactions that were committed during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The bean transaction commit rate for EJB %name%, EJB module %ejbModuleName% is %value%%%.

3.20.2 Bean Transaction Commits (per minute)

This metric shows the EJB transaction commits per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of available beans for EJB %name%, EJB module %ejbModuleName% is %value%.

3.20.3 Bean Transaction Rollbacks (per minute)

This metric shows the EJB transaction rollbacks per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of available beans for EJB %name%, EJB module %ejbModuleName% is %value%.

3.20.4 Bean Transaction Timeouts (per minute)

This metric shows the EJB transaction timeouts per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of available beans for EJB %name%, EJB module %ejbModuleName% is %value%.

3.21 Identity Federation - IdP Partner Federated Single Sign-Ons

This metric category provides information about the Oracle Identity Federation metrics.

Oracle Identity Federation is a standalone, self-contained federation server that enables single sign-on and authentication in a multiple-domain identity network. Oracle Identity Federation supports multiple federated identity protocols.

An identity provider (IdP) is responsible for managing, authenticating, and asserting a set of identities within its set of federations. This is one of the three primary roles defined in the identity federation protocols supported by Oracle Identity Federation.

For more information about Oracle Identity Federation, see Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation.

3.21.1 Federated Single Sign-Ons (per second)

This metric displays the number of identity provider (IdP) partner single sign-ons during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

IdP Partner Federated Single Sign-Ons during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.21.2 Federated Single Sign-On Latency (ms)

This metric displays the amount of time (in ms) it took the single sign-ons to respond during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

IdP Partner Federated Single Sign-On Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.22 Identity Federation - Protocol Federated Single Sign-Ons

This metric category provides information about the Identity Federation - Protocol Federated Single Sign-Ons metrics, that is, federated single sign-on in an Identity Provider and Server Provider environment.

A service provider (SP) provides services to a Principal (a group of users such as a corporation, or a system entity whose identity can be authenticated) while relying on an identity provider to authenticate the Principal's identity. Service providers enter into partnerships with other service providers and identity providers with the goal of providing their common users with secure single sign-on between all parties of the federation.

3.22.1 IdP Federated Single Sign-Ons (per second)

This metric displays the number of federated single sign-ons in an identity provider environment per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

IdP Federated Single Sign-Ons during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.22.2 IdP Federated Single Sign-On Latency (ms)

This metric displays the amount of time (in ms) it took the single sign-ons in the identity provider environment to respond during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

IdP Federated Single Sign-On Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.22.3 SP Federated Single Sign-Ons (per second)

This metric displays the number of federated single sign-ons in the service provider environment per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

SP Federated Single Sign-Ons during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold�

3.22.4 SP Federated Single Sign-On Latency (ms)

This metric displays the amount of time (in ms) it took the single sign-ons in the service provider environment to respond during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

SP Federated Single Sign-On Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.23 Identity Federation - SP Partner Federated Single Sign-Ons

This metric category provides information about the Identity Federation metrics in a Service Provider environment.

3.23.1 Federated Single Sign-Ons (per second)

This metric displays the number of federated single sign-ons in the service provider environment per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

SP Partner Federated Single Sign-Ons during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.23.2 Federated Single Sign-On Latency (ms)

This metric displays the amount of time (in ms) it took the single sign-ons in the service provider environment to respond during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

SP Partner Federated Single Sign-On Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.24 Identity Federation - Total Federated Single Sign-Ons

This metric category provides information about the Identity Federation - Total Federated Single Sign-Ons metrics.

3.24.1 Total IdP Federated Single Sign-Ons (per second)

This metric displays the total number of federated single sign-ons in the identity provider environment during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

Total IdP Federated Single Sign-Ons during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.24.2 Total IdP Federated Single Sign-On Latency (ms)

This metric displays the total amount of time it took the single sign-ons to respond in the identity provider environment during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

Total IdP Federated Single Sign-On Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.24.3 Total SP Federated Single Sign-Ons (per second)

This metric displays the total number of federated single sign-ons in the service provider environment during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

Total SP Federated Single Sign-Ons during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.24.4 Total SP Federated Single Sign-On Latency (ms)

This metric displays the total amount of time it took the single sign-ons to respond in the service provider environment during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

Total SP Federated Single Sign-On Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.25 JEE Web Service Endpoint Metrics

3.25.1 JEE WS Endpoint - Avg Invocation Time per interval (ms)

This metric displays the average invocation time (ms) for the Java EE web service end point.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 30 Minutes

Not Defined

Not Defined

Average Invocation Time for endpoint in a five minute interval is %value%.

3.25.2 JEE WS Endpoint - Response Error Throughput (per minute)

This metric displays the number of response errors per minute for the Java EE web service end point.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 30 Minutes

Not Defined

Not Defined

Response Error throughput for endpoint in a five minute interval is %value%.

3.25.3 JEE WS Endpoint - Invocation Throughput (per minute)

This metric displays the number of invocations per minute for the Java EE web service end point.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 30 Minutes

Not Defined

Not Defined

Invocation throughput for endpoint in a five minute interval is %value%.

3.26 LDAP Operations

This metric category describes the metrics related to Oracle Access Manager user identity operations.

3.26.1 LDAP Operations per second

This metric specifies the rate per second for user or group related operations on the primary directory server repository. This value represents the aggregation of requests generated from this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

LDAP Operations Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.26.2 Average LDAP Operation Latency (ms)

This metric measures the average amount of time spent performing Identity Provider operations: authenticateUser() and isUserAssignedToGroup (), for example. It does not correspond to actual LDAP bind, search, or compare times.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

LDAP Operation Latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold .

3.26.3 LDAP Success Rate (%)

This metric measures the success to failure ratio for all Identity Provider component method calls. This might not correspond to the LDAP bind, search, or compare times, because failure can occur in the Identity Provider itself or the underlying User/Role API or at the JNDI layer and might never get down to actual LDAP server operations.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

LDAP Operations Success Rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.26.4 Server Name

This metric identifies the name of the server performing user identity operations.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

3.27 Log File Monitoring

This metric category provides information about the Log File Monitoring metric.

The Log File Monitoring metric allows the operator to monitor one or more log files for the occurrence of one or more perl patterns in the content. In addition, the operator can specify a perl pattern to be ignored for the log file. Periodic scanning will be performed against new content added since the last scan, lines matching the ignore pattern will be ignored first, then lines matching specified match patterns will result in one record being uploaded to the repository for each pattern. The user can set a threshold against the number of lines matching the given pattern. File rotation will be handled within the given file.

3.27.1 Log File Pattern Matched Line Count

This metric returns the actual content if the given file has been specifically registered for content uploading. Otherwise, it returns the count of lines that matched the pattern specified.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 60 Minutes

Not Defined

Not Defined

%log_file_message%. %sys_occurrence_count% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.28 Log Operations

This metric category describes the metrics related to logging operations for Oracle Access Manager.

3.28.1 Average Log Latency (ms)

This metric specifies the average latency, in milliseconds, of the logging operations for this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Log Operations Latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.28.2 Log Operations per second

This metric specifies the logging throughput (log operations per second) for this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Log Operations Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.28.3 Server Name

This metric specifies the name of the server performing the logging operations for this OAM instance.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

3.29 MDS Metrics

This metric category provides information about the Metadata Services (MDB) metrics.

3.29.1 IOs Per Document Get

This metric displays the average number of physical IOs per persistence-level document get. This is an indication of the efficiency of the document cache portion of the metadata cache for the application. Ideally it should be much less than 1.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The average number of physical IOs per Document Get is %value%.

3.29.2 IOs Per MO Content Get

This metric displays the average number of physical IOs per metadata object XML content retrieval. This is an indication of the efficiency of the metadata cache for the application. Ideally it should be much less than 1.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The average number of physical IOs per MO Content Get is %value%.

3.29.3 Metadata Object Get Processing Time (seconds)

This metric displays the average elapsed time in seconds to get a metadata object.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The average processing time of each Metadata Object Get is %value% seconds.

3.29.4 Metadata Update Processing Time (seconds)

This metric displays the average elapsed time in seconds taken to update a metadata object.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The average processing time of each Metadata Update is %value% seconds.

3.30 Message-Driven EJB Metrics

This metric category provides information about the Message-Driven EJB metrics.

3.30.1 MDB Messages (per minute)

This metric displays the number of messages processed by message-driven beans (MDBs) per minute during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The MDB messages for EJB %name%, EJB module %ejbModuleName% are %value% (per minute).

3.30.2 MDB Suspensions (per minute)

This metric shows the average number of MDB suspensions per minute during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The MDB suspensions for EJB %name%, EJB module %ejbModuleName% are %value% (per minute).

3.30.3 MDB Status

This metric displays the status of the MDB.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The MDB status for EJB %name%, EJB module %ejbModuleName% is %value%.

3.31 Mobile and Social - Internet Identity Providers

This metric category provides information about the Mobile and Social - Internet Identity Providers metics.

For more information about Oracle Access Management Mobile and Social, see Oracle Fusion Middleware Administrator's Guide for Oracle Access Management.

3.31.1 Authentications (per second)

This metric displays the number of authentications per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Authentications during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.32 Mobile and Social - JWT Tokens

This metric category provides information about the Mobile and Social - JWT Tokens metrics.

JWT authentication permits users running a web application from a desktop device to authenticate using the JSON Web Token format. JSON Web Token is a compact token format that is suitable for space-constrained environments such as HTTP Authorization headers. For more information, see Oracle Fusion Middleware Administrator's Guide for Oracle Access Management.

3.32.1 JWT Access Creation Tokens (per second)

This metric displays the number of JWT Access Tokens created per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT Access Creation Tokens during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.32.2 JWT Access Creation Token Latency (ms)

This metric displays the amount of time (in ms) required to process the JWT Access Tokens requests during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT Access Creation Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.32.3 JWT User Creation Tokens (per second)

This metric displays the number of JWT User Tokens created per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT Access Creation Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT User Creation Tokens during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.32.4 JWT User Creation Token Latency (ms)

This metric displays the amount of time (in ms) required to process the JWT User Token requests during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT Access Creation Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT User Creation Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.32.5 JWT Client Creation Tokens (per second)

This metric displays the number of JWT Client Tokens created per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT Access Creation Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT Client Creation Tokens during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.32.6 JWT Client Creation Token Latency (ms)

This metric displays the amount of time (in ms) required to process the JWT Client Token requests during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT Access Creation Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT Client Creation Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.32.7 JWT Get Tokens (per second)

This metric displays the number of JWT Get Tokens created per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT Access Creation Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT Get Tokens during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.32.8 JWT Get Token Latency (ms)

This metric displays the amount of time (in ms) required to process the JWT Get Token requests during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT Get Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.33 Mobile and Social - Local Logins and Registrations

This metric category provides information about the Mobile and Social - Local Logins and Registrations metrics.

For information about Oracle Access Management Mobile and Social, see Oracle Fusion Middleware Administrator's Guide for Oracle Access Management

3.33.1 Completed Local Logins (per second)

This metric displays the number of completed local logins per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Completed Local Logins during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.33.2 Failed Local Logins (per second)

This metric displays the number of failed local logins per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Failed Local Logins during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.33.3 Completed User Registrations (per second)

This metric displays the number of completed user registrations per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Completed User Registrations during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.33.4 Incomplete User Registrations(per second)

This metric displays the number of incomplete user registrations per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Incomplete User Registrations during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.34 Mobile and Social - Mobile JWT Tokens

This metric category provides information about the Mobile and Social - Mobile JWT Tokens metrics.

Mobile JWT permits users using mobile devices authenticate using the JSON Web Token format. For more information, see Oracle Fusion Middleware Administrator's Guide for Oracle Access Management.

3.34.1 JWT Access Creation Tokens (per second)

This metric displays the number of JWT Access Tokens created per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT Access Creation Tokens during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.34.2 JWT Access Creation Token Latency (ms)

This metric displays the amount of time (in ms) required to process the JWT Access Tokens during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT Access Creation Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.34.3 JWT User Creation Tokens (per second)

This metric displays the number of JWT User Tokens created per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT User Creation Tokens during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.34.4 JWT User Creation Token Latency (ms)

This metric displays the amount of time (in ms) required to process the JWT User Token requests during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT User Creation Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.34.5 JWT Client Creation Tokens (per second)

This metric displays the number of JWT Client Tokens created per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT Client Creation Tokens during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.34.6 JWT Client Creation Token Latency (ms)

This metric displays the amount of time (in ms) required to process the JWT Client Token requests during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT Client Creation Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.34.7 JWT Get Tokens (per second)

This metric displays the number of JWT Get Tokens created per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT Get Tokens during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.34.8 JWT Get Token Latency (ms)

This metric displays the amount of time (in ms) required to process the JWT Get Token requests during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

JWT Get Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.35 Mobile and Social - Mobile OAM Tokens

This metric category provides information about the Mobile and Social - Mobile OAM Tokens metrics.

Mobile Oracle Access Manager authentication permits users using mobile devices to authenticate using Oracle Access Manager. For more information, see Oracle Fusion Middleware Administrator's Guide for Oracle Access Management.

3.35.1 OAM Access Creation Tokens (per second)

This metric displays the number of OAM Access Tokens created per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

OAM Access Creation Tokens during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.35.2 OAM Access Creation Token Latency (ms)

This metric displays the amount of time (in ms) required to process the OAM Access Token requests during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

OAM Access Creation Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.35.3 OAM User Creation Tokens (per second)

This metric displays the number of OAM User Tokens created per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

OAM User Creation Tokens during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.35.4 OAM User Creation Token Latency (ms)

This metric displays the amount of time (in ms) required to process the OAM User Token requests during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

OAM User Creation Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.35.5 OAM Client Creation Tokens (per second)

This metric displays the number of OAM Client Tokens created per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

OAM Client Creation Tokens during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.35.6 OAM Client Creation Token Latency (ms)

This metric displays the amount of time (in ms) required to process the OAM Client Token requests during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

OAM Client Creation Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.35.7 OAM Get Tokens (per second)

This metric displays the number of OAM Get Tokens created per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

OAM Get Tokens during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.35.8 OAM Get Token Latency (ms)

This metric displays the amount of time (in ms) required to process the OAM Get Token requests during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

OAM Get Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.35.9 OAM Termination Tokens (per second)

This metric displays the number of OAM Termination Tokens created per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

OAM Termination Tokens during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.35.10 OAM Termination Token Latency (ms)

This metric displays the amount of time (in ms) required to process the OAM Termination Token requests during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

OAM Termination Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.36 Mobile and Social - OAM Tokens

This metric category provides information about the Mobile and Social - OAM Tokens metrics.

Oracle Access Manager (OAM) authentication permits users running a web application from a desktop device to authenticate using Access Manager. For more information, see Oracle Fusion Middleware Administrator's Guide for Oracle Access Management

3.36.1 OAM Creation Tokens (per second)

This metric displays the number of OAM Creation Tokens issued per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

OAM Creation Tokens during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.36.2 OAM Creation Token Latency (ms)

This metric displays the amount of time (in ms) required to process the OAM Creation Token requests during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

OAM Creation Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.36.3 OAM Get Tokens (per second)

This metric displays the number of OAM Get Tokens issued per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

OAM Get Tokens during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.36.4 OAM Get Token Latency (ms)

This metric displays the amount of time (in ms) required to process the OAM Get Token requests during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

OAM Get Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.36.5 OAM Termination Tokens (per second)

This metric displays the number of OAM Termination Tokens issued per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

OAM Termination Tokens during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.36.6 OAM Termination Token Latency (ms)

This metric displays the amount of time (in ms) required to process the OAM Termination Token requests during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

OAM Termination Token Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.37 Mobile and Social - User Profile Service - Group

This metric category provides information about the Mobile and Social - User Profile Service - Group metrics.

User Profile Service Provider allows Oracle Mobile and Social to query and update an Identity Service Provider using Mobile (REST) Services calls. For more information, see Oracle Fusion Middleware Administrator's Guide for Oracle Access Management

3.37.1 Create Group Operations (per second)

This metric displays how group profiles were created per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Create Group Operations during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.37.2 Create Group Operation Latency (ms)

This metric displays the amount of time (in ms) required to process the Create a Group operation during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Create Group Operation Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.37.3 Read Group Operations (per second)

This metric displays the number of group profiles retrieved per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Read Group Operations during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.37.4 Read Group Operation Latency (ms)

This metric displays the amount of time (in ms) required to process the Read a Group operation during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Read Group Operation Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.37.5 Delete Group Operations (per second)

This metric displays the number of group profiles deleted per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Delete Group Operations during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.37.6 Delete Group Operation Latency (ms)

This metric displays the amount of time (in ms) required to process the Delete a Group operation during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Delete Group Operation Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.37.7 Update Group Operations (per second)

This metric displays the number of group profiles updated per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Update Group Operations during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.37.8 Update Group Operation Latency (ms)

This metric displays the amount of time (in ms) required to process the Update a Group operation during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Update Group Operation Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.37.9 Search Group Operations (per second)

This metric displays the number of searches performed per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Search Group Operations during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.37.10 Search Group Operation Latency (ms)

This metric displays the amount of time (in ms) it took to process the search operation.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Search Group Operation Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.38 Mobile and Social - User Profile Service - People

This metric category provides information about the Mobile and Social - User Profile Service - People metrics.

User Profile Service Provider allows Oracle Mobile and Social to query and update an Identity Service Provider using Mobile (REST) Services calls. The User Profile Services can access and update User records located in a Directory store. For more information, see Oracle Fusion Middleware Administrator's Guide for Oracle Access Management

3.38.1 Create People Operations (per second)

This metric displays how many People records were created per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Create People Operations during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.38.2 Create People Operation Latency (ms)

This metric displays the amount of time (in ms) required to process the Create People operation.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Create People Operation Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.38.3 Read People Operations (per second)

This metric displays how many People records were retrieved per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Read People Operations during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.38.4 Read People Operation Latency (ms)

This metric displays the amount of time (in ms) required to process the Read People operation.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Read People Operation Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.38.5 Delete People Operations (per second)

This metric displays how many People records were deleted per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Delete People Operations during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.38.6 Delete People Operation Latency (ms)

This metric displays the amount of time (in ms) required to process the Delete People operation.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Delete People Operation Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.38.7 Update People Operations (per second)

This metric displays how many People records were updated per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Update People Operations during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.38.8 Update People Operation Latency (ms)

This metric displays the amount of time (in ms) required to process the Update People operation.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Update People Operation Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.38.9 Search People Operations (per second)

This metric displays how many People records were searched per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Search People Operations during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.38.10 Search People Operation Latency (ms)

This metric displays the amount of time (in ms) required to process the Search People operation.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Search People Operation Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.39 Mobile and Social - User Profile Service - Relationship

This metric category provides information about the Mobile and Social - User Profile Service - Relationship metrics.

Relationships can be used to add, delete, read, and search a user with respect to a group. For more information, see Oracle Fusion Middleware Administrator's Guide for Oracle Access Management.

3.39.1 Create Relationship Operations (per second)

This metric displays the number of users assigned to a group during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Create Relationship Operations during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.39.2 Create Relationship Operation Latency (ms)

This metric displays the amount of time (in ms) required to process the Create Relationship operation.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Create Relationship Operation Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.39.3 Read Relationship Operations (per second)

This metric displays the number of relationship profiles that were retrieved.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Read Relationship Operations during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.39.4 Read Relationship Operation Latency (ms)

This metric displays the amount of time (in ms) required to process the Read Relationship operation.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Read Relationship Operation Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.39.5 Delete Relationship Operations (per second)

This metric displays the number of relationship profiles that were deleted during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Delete Relationship Operations during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.39.6 Delete Relationship Operation Latency (ms)

This metric displays the amount of time (in ms) required to process the Delete Relationship operation

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Delete Relationship Operation Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.39.7 Search Relationship Operations (per second)

This metric displays how many Relationship profiles were searched per second during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Search Relationship Operations during the last collection interval %value% (per second) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.39.8 Search Relationship Operation Latency (ms)

This metric displays the amount of time (in ms) required to process the Search Relationship operation.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

Search Relationship Operation Latency during the last collection interval %value% (ms) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.40 Module EJB Cache Metrics

This metric category provides information about the Module EJB Cache metrics.

3.40.1 Cached Beans

This metric shows the total number of beans currently in the EJB cache.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

The number of cached beans for EJB module %ejbModuleName% is %value%.

3.40.2 Cache Hits (%)

This metric shows the percentage of cache accesses that completed successfully.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

The EJB cache hit rate for EJB module %ejbModuleName% is %value%%%.

3.40.3 Bean Activations (per minute)

This metric shows the average number of beans per minute that have been activated from the EJB home during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

The bean activations for EJB module %ejbModuleName% are %value% (per minute).

3.40.4 Cache Accesses (per minute)

This metric shows the number times per minute that an attempt was made to access the EJB cache during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

The cache accesses for EJB module %ejbModuleName% is %value% (per minute).

3.40.5 Cache Misses (per minute)

This metric shows the average number of cache misses per minute for this EJB module during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

The cache misses for EJB module %ejbModuleName% are %value% (per minute).

3.40.6 Cache Passivations (per minute)

This metric displays the total number of passivated beans per minutue during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR2 (11.1.2)

Every 15 Minutes

Not Defined

Not Defined

The EJB Passivations for EJB module %ejbModuleName% are %value% (per minute).

3.41 Module EJB Transaction Metrics

This metric category describes the Module EJB Transaction metrics.

3.41.1 Bean Transaction Commits (%)

This metric shows the percentage of EJB transactions that were committed during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The bean transaction commit rate for EJB module %ejbModuleName% is %value%%%.

3.41.2 Bean Transaction Commits (per minute)

This metric shows the EJB transaction commits per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The bean transaction commits for EJB module %ejbModuleName% are %value% (per minute).

3.41.3 Bean Transaction Rollbacks (per minute)

This metric shows the EJB transaction rollbacks per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The bean transaction rollbacks for EJB module %ejbModuleName% are %value% (per minute).

3.41.4 Bean Transaction Timeouts (per minute)

This metric shows the EJB transaction timeouts per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The bean transaction timeouts for EJB module %ejbModuleName% are %value% (per minute).

3.42 Module Message Driven EJB Metrics

3.42.1 MDB Messages (per minute)

This metric specifies the number of messages processed by message-driven beans (MDBs) per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The MDB messages for EJB module %ejbModuleName% are %value% (per minute).

3.42.2 MDB Suspensions (per minute)

This metric specifies the number of MDB JMS connection suspensions per minute.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The MDB suspensions for EJB module %ejbModuleName% are %value% (per minute).

3.43 Number of Authentications

This metric category describes the Number of Authentications metrics.

3.43.1 Number Of Invalid Credential Errors Against The LDAP User Identity Store

This metric displays the number of invalid credential errors against the LDAP user identity store.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

Invalid Credential Errors during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.43.2 Number of LDAP Time Out Errors In The Last Collection

This metric displays the number of LDAP timeout errors during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

User not found Errors during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.43.3 Number of User Not Found Errors In The Last Collection

This metric displays the number of user not found errors during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

LDAP Time Out Errors during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.44 Number of Authorizations

This metric category provides information about the Number of Authorizations metrics.

3.44.1 Number of Failed Authorizations in the last collection

This metric displays the number of failed authorizations during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

Failed Authorizations during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.44.2 Number of SSO Session Creation Failures

This metric displays the number of SSO session creation failures.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

Failed SSO Session Creations during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.45 OAM Application Clients

This metric category describes the metrics related to Oracle Access Manager application domains.

3.45.1 Average Application Authentication Latency (ms)

This metric specifies the average latency, in milliseconds, for authorization operations in an application domain.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authentication Latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.45.2 Application Authentication Requests per second

This metric specifies the rate of authentication requests processed, per second, in an application domain.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authentication Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.45.3 Application Authentication Success Rate (%)

This metric specifies the success to failure ratio for authorization operations in an application domain.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authentication Success Rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.45.4 Average Application Authorization Latency (ms)

This metric specifies the average latency, in milliseconds, for authorization requests in an application domain.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.45.5 Application Authorization Requests per second

This metric specifies the rate of authorization requests, per second, for an application domain.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.45.6 Application Authorization Success Rate (%)

This metric specifies the success to failure ratio, as a percentage, for authorization operations in an application domain.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Success Rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.46 OAM 10g Client

This metric category describes the metrics related to Oracle Access Manager operations in support of an OAM 10g Agent.

3.46.1 OAM Client Average Authentication Latency (ms)

This metric specifies the average latency, in milliseconds, of the authentication requests coming from an OAM 10g Agent.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

3.46.2 OAM Client Authentication Requests per second

This metric specifies the authentication throughput (requests per second) coming from a OAM 10g Agent.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

3.46.3 OAM Client Authentication Success Rate (%)

This metric specifies the success to failure rate, as a percentage, for authentication requests coming from an OAM 10g Agent.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

3.46.4 OAM Client Average Authorization Latency (ms)

This metric specifies the average latency, in milliseconds, for authorization requests coming from an OAM 10g Agent.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.46.5 OAM Client Authorization Requests per second

This metric specifies the authorization throughput (requests per second) coming from an OAM 10g Agent.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.46.6 OAM Client Authorization Success Rate (%)

This metric specifies the success to failure rate, as a percentage, for authorization requests coming from an OAM 10g Agent.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Success Rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.47 OAM Proxy

This metric category describes the OAM Proxy metrics.

3.47.1 Proxy Failed Authentications in Last Collection

This metric displays the number of proxy failed authentications during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Success Rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.47.2 Proxy Failed Authorizations in Last Collection

This metric displays the number of proxy failed authorizations during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Success Rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.47.3 Proxy Failed Resource Protected in Last Collection

This metric displays the number of proxy failed resources protected during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Success Rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.48 Oracle SSO 10g Client

This metric category describes the metrics related to Oracle Access Manager operations in support of an OSSO 10g agent.

3.48.1 OSSO Client Average Authentication Latency (ms)

This metric specifies the average latency, in milliseconds, of authentication requests coming from an OSSO 10g agent.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authentication Latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.48.2 OSSO Client Authentication Requests per second

This metric specifies the authentication throughput (requests per second) coming from an OSSO 10g Agent.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authentication Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.48.3 OSSO Client Authentication Success Rate (%)

This metric specifies the success to failure ratio, as a percentage, for authentication requests coming from an OSSO 10g Agent.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authentication Success Rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.49 Oracle Web Service Endpoint Metrics

This metric category describes the Oracle Web Service Endpoint metrics.

3.49.1 Oracle WS Endpoint - Avg Invocation Time per interval(sec)

This metric specifies the average invocation time for an Oracle Web Service end point for a 5 minute interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 30 Minutes

Not Defined

Not Defined

Average Invocation Time for endpoint in a five minute interval is %value%.

3.49.2 Oracle WS Endpoint - Fault Throughput(per minute)

This metric specifies the number of faults per minute for an Oracle Web Service end point for a 5 minute interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 30 Minutes

Not Defined

Not Defined

Fault throughput for endpoint in a five minute interval %value%.

3.49.3 Oracle WS Endpoint - Invocation Throughput(per minute)

This metric specifies the number of invocations per minute for an Oracle Web Service end point for a 5 minute interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 30 Minutes

Not Defined

Not Defined

Invocation throughput endpoint in a five minute interval %value%.

3.50 Resource Utilization

This metric category describes the Resource Utilization metrics.

3.50.1 CPU Utilization (%)

This metric displays the percentage of CPU that is being used by Oracle Access Manager.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 300 Seconds

Not Defined

Not Defined

The CPU utilization is greater than %value%

3.50.2 Memory Utilization (%)

This metric displays the percentage of memory that is being used by Oracle Access Manager.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 300 Seconds

Not Defined

Not Defined

The Memory utilization is greater than %value%

3.51 Response

Response metrics represent the availability of the selected OAM instance.

3.51.1 UpDown Status

This metric shows the availability of this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every Minute

Not Defined

0

The Oracle Access Manager is down.

3.52 RESTful Service Application Metrics

This metric category provides information about the RESTful Service Application metrics.

3.52.1 RESTful Service Invocation Throughput (per minute)

For this application, this metric displays the number of RESTful service invocations per minute during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 30 Minutes

Not Defined

Not Defined

The RESTful service invocations are %value% (per minute).

3.52.2 RESTful Service Error Count Throughput (per minute)

For this application, this metric displays the number of RESTful service errors per minute during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 30 Minutes

Not Defined

Not Defined

The RESTful service error counts are %value% (per minute).

3.52.3 RESTful Service Execution Time Average (seconds)

For this application, this metric displays the average time (in seconds) to process a RESTful service during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 30 Minutes

Not Defined

Not Defined

The RESTful service execution time average is %value% (seconds).

3.53 RESTful Service Method Metrics

This metric category provides information about the RESTful Service Method metrics.

3.53.1 RESTful Service Invocation Throughput (per minute)

This metric displays the number of RESTful service invocations per minute during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 30 Minutes

Not Defined

Not Defined

The RESTful service invocations are %value% (per minute).

3.54 RESTful Service Resource Metrics

This metric category provides information about the RESTful Service Resource metrics.

3.54.1 RESTful Service Invocation Throughput (per minute)

This metric displays the number of RESTful service invocations per minute during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 30 Minutes

Not Defined

Not Defined

The RESTful service invocations are %value% (per minute).

3.55 Security Token Service - Token Generation Operations

This metric category provides information about the Security Token Service - Token Generation Operations metrics.

3.55.1 Issuance Latency (ms)

This metric specifies the average latency of security token creation or generation for this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Token issue creation latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.55.2 Tokens Issued

This metric specifies the total number of security tokens that were created or generated by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Token creations during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.55.3 Token Issuances per second

This metric specifies the throughput of the security token creation or generation (tokens per second) by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Token creation throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.56 Security Token Service - Token Validation Operations

This metric category describes the metrics pertaining to core (primitive) security token validation operations for this OAM instance.

3.56.1 Number of Tokens Validated

This metric specifies the total number of security tokens that were validated by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Token validations during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.56.2 Token Validations per second

This metric specifies the throughput of security token validation (tokens per second) by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Token validation throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.56.3 Token Validation Latency (ms)

This metric specifies the average latency of security token validation (in milliseconds) by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Token issue validation latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.57 Security Token Service - Partners

This metric category describes the metrics pertaining to partner security token validation operations for this OAM instance

3.57.1 Tokens Issued

This metric specifies the total count of security token issuance requests received from a partner by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Partner token requests during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.57.2 Issuance Latency (ms)

This metric specifies the average latency of processing security token issuance requests received from a partner by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Partner token issue latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.57.3 Token Issuances per second

This metric specifies the throughput of processing security token issuance requests received from a partner (requests per second) by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Partner token issue request throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.57.4 Issuance Success Rate (%)

This metric specifies the success to failure ratio, as a percentage, for security token issuance requests received from a partner by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Partner token request issuance success rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.57.5 Number of Tokens Validated

This metric specifies the total number of security token validation requests received from a partner by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Partner token validation requests during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.57.6 Token Validation Latency (ms)

This metric specifies the average latency of processing security token validation requests from a partner by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Partner token validation latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.57.7 Token Validations per second

This metric specifies the throughput of the processing security token validation requests from a partner by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Partner token validation request throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.57.8 Validation Success Rate (%)

The metric specifies the success to failure ratio, as a percentage, for security token validation requests from a partner by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Partner token validation success rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

3.58 Security Token Service - Token Requests

This metric category describes the metrics related to Oracle Access Manager security tokens for this OAM instance.

3.58.1 Issuance Latency (ms)

This metric specifies the latency of the security token issuance request processing (in milliseconds) for this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Token issue request latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.58.2 Tokens Issued

This metric specifies the total number of security token issuance requests processed by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Token issue requests during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.58.3 Token Issuances per second

This metric specifies the throughput of the security token issuance (requests per second) by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Token issue request throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.58.4 Issuance Success Rate (%)

This metric specifies the success to failure ratio, as a percentage, for security token issuance requests by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Token issue request success rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.58.5 Token Validation Latency (ms)

This metric specifies the average latency of the security token validation request processing (in milliseconds) by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Token validation request latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.58.6 Number of Tokens Validated

This metric specifies the total number of security token validation requests processed by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Token validation requests during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.58.7 Token Validations per second

This metric specifies the throughput of the security token validation request processing (in milliseconds) by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Token validation request throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.58.8 Validation Success Rate (%)

This metric specifies the success to failure ratio, as a percentage, for security token validation request processing by this OAM instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

11gR1 (11.1.1.4), 11gR2 (11.1.2)

Every 5 Minutes

Not Defined

Not Defined

Token validation request success rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

3.59 Servlet/JSP Metrics

This metric category provides information about the Servlet/JSP metrics.

3.59.1 Request Processing Time (ms)

This metric shows the average time consumed to execute servlets and JSPs during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The request processing time for servlet/jsp %name%, web module %webModuleName% is %value% ms.

3.59.2 Requests (per minute)

This metric shows the rate at which servlets and JSPs are being invoked during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The requests processed for servlet/jsp %name%, web module %webModuleName% are %value% (per minute).

3.59.3 Reloads (per minute)

This metric shows the average number of reloads of the selected servlet or JSP per minute during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The reloads for servlet/jsp %name%, web module %webModuleName% are %value% (per minute).

3.60 Servlet/JSP Metrics By Application

This metric category provides information about the Servlet/JSP Metrics By Application metrics.

3.60.1 Request Processing Time (ms)

This metric shows the average time consumed to execute servlets and JSPs for this application during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The request processing time is %value% ms.

3.60.2 Requests (per minute)

This metric shows the rate at which servlets and JSPs are being invoked for this application during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The requests processed are %value% (per minute).

3.60.3 Reloads (per minute)

This metric shows the average number of reloads of the selected servlet or JSP per minute for this application during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The reloads are %value% (per minute).

3.61 Servlet/JSP Metrics By Module

This metric category provides information about the Servlet/JSP Metrics By Module metrics.

3.61.1 Request Processing Time (ms)

This metric shows the average time consumed to execute servlets and JSPs for this module during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The reloads are %value% (per minute).

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The reloads are %value% (per minute).

3.61.2 Requests (per minute)

This metric shows the rate at which servlets and JSPs are being invoked for this module during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The reloads are %value% (per minute).

3.61.3 Reloads (per minute)

This metric shows the average number of reloads of the selected servlet or JSP per minute for this module during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The reloads are %value% (per minute).

3.62 Webgate Status

This metric category provides information about the status of the WebGate. A WebGate is a Web server plug-in that is shipped out-of-the-box with Oracle Access Manager.

3.62.1 Webgate Status

This metric monitors if the WebGate is up and running.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

0

%webgatename% is Down.

4 Oracle Access Management Cluster

Oracle Enterprise Manager can be used to manage Oracle Access Management metrics that show the performance for Oracle Access Manager 11g servers and OAM server clusters.

4.1 OAM Applications Domains (Aggregated)

Metrics for OAM application domains in the cluster.

4.1.1 Application Authentication Latency (ms)

This metric specifies the average latency, in milliseconds, for authentication requests processed in this application domain for all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

>

Not Defined

Not Defined

Authentication Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.1.2 Application Authentication Requests per second

This metric specifies the authentication throughput (requests per second) in this application domain for OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

>

Not Defined

Not Defined

Authentication Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.1.3 Application Authentication Success Rate (%)

This metric specifies the success to failure rate for authentication operations in this application domain for all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

>

Not Defined

Not Defined

Authentication Success Failure Ratio during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.1.4 Application Authorization Latency (ms)

This metric specifies the average latency, in milliseconds, for authorization operations in this application domain for all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.1.5 Application Authorization Requests per second

This metric specifies the authorization throughput (requests per second) in this application domain for all OAM instances in this cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.1.6 Application Authorization Success Rate (%)

This metric specifies the success to failure ratio, as a percentage, for authorization requests in this application domain for all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Success Failure Ratio during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.2 OAM 10g Aggregates

Metrics for all OAM 10g agents related to OAM Instances in the cluster.

4.2.1 OAM Client Average Authentication Latency (ms)

This metric specifies the average latency, in milliseconds, for authentication requests coming from this OAM 10g Webgate for all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.2.2 OAM Client Authentication Requests per second

This metric specifies the rate of authentication requests (per second) coming from this OAM 10g Webgate for all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.2.3 OAM Client Authentication Success Rate (%)

This metric specifies the success to failure ratio, as a percentage, for authentication requests coming from this OAM 10g webgate for all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Success Failure Ratio during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.2.4 OAM Client Average Authorization Latency (ms)

This metric specifies the average latency, in milliseconds, for authorization requests coming from this OAM 10g Webgate for all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.2.5 OAM Client Authorization Requests per second

This metric specifies the throughput of authorization requests (requests per second) coming from this OAM 10g Webgate for all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.2.6 OAM Client Authorization Success Rate (%)

This metric specifies the success to failure ratio, as a percentage, for authorization requests coming from this OAM 10g Webgate for all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Success Failure Ratio during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.3 OAM 10g Throughput (Aggregated)

Metrics for OAM 10g agents related to OAM Instances in the cluster.

4.3.1 OAM Client Authentications per second

This metric specifies the rate of authentication requests (per second) coming from this OAM 10g Webgate for all OAM instances in the cluster.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

4.3.2 OAM Client Authorizations per second

This metric specifies the throughput of authorization requests (requests per second) coming from this OAM 10g Webgate for all OAM instances in the cluster.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

4.4 OSSO 10g (Aggregated)

Metrics related to OSSO 10g Agents across the OAM cluster.

4.4.1 OSSO Client Average Authentication Latency (ms)

This metric specifies the average latency, in milliseconds, for authentication requests coming from this OSSO 10g agent for OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authentication Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.4.2 OSSO Client Authentication Requests per second

This metric specifies the throughput of authentication requests (requests per second) coming from this OSSO 10g agent for OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authentication Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.4.3 Authentication Success Rate (%)

This metric specifies the success to failure ratio, as a percentage, for authentication requests coming from this OSSO 10g agent for all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authentication Success Failure Ratio during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.5 OSSO 10g Throughput (Aggregated)

Metrics for OSSO agents communicating with OAM instances in the cluster.

4.5.1 OSSO Client Operations per second

This metric specifies the rate of authentication throughput (requests per second) coming from this OAM 10g Webgate for all OAM instances in the cluster.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

4.6 Audit Operations (Aggregated)

Metrics related to auditing operations for Oracle Access Manager servers in the cluster.

4.6.1 Average Audit Latency (ms)

This metric specifies the average latency, in milliseconds, of the audit operations for all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Audit Operations Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.6.2 Audit Operations per second

This metric specifies the rate of audit operation (per second) for all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Audit Operations Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.7 Audit Operations Throughput (Aggregated)

Metrics related to auditing operations for Oracle Access Manager across the cluster.

4.7.1 Operations per second

This metric specifies the audit throughput (audit operations per second) for all OAM instances in the cluster.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

4.8 Authentication Aggregates

Metrics for aggregated authentication operations with Oracle Access Manager.

4.8.1 Average Authentication Latency (ms)

This metric specifies the average latency, in milliseconds, for authentication requests handled by all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authentication Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.8.2 Authentication Requests per second

This metric specifies the authentication throughput (requests per second) for all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authentication Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.8.3 Authentication Success Rate (%)

This metric specifies the success to failure ratio, as a percentage, for authentication requests handled by all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authentication Success Failure Ratio during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.9 Authentications Throughput (Aggregated)

Metrics representing aggregated authentication throughput for requests handled by all OAM instances in the cluster.

4.9.1 Authentication Requests per second

This metric specifies the rate of authentication request throughput (requests per second) for all OAM instances in the cluster.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

4.10 Authorizations (Aggregated)

Metrics related to authorization operations performed by Oracle Access Manager instances in the cluster.

4.10.1 Average Authorization Latency (ms)

This metric specifies the average latency, in milliseconds, for authorization requests. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.10.2 Authorization Requests per second

This metric specifies the rate of authorization request throughput (requests per second) for all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.10.3 Authorization Success Rate (%)

This metric specifies the success to failure ratio, as a percentage, for authorization requests. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Authorization Success Failure Ratio during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.11 Authorizations Throughput (Aggregated)

Metrics related to authorization operations aggregated across all OAM instances in the cluster.

4.11.1 Authorization Requests per second

This metric specifies the authorization request throughput (requests per seconds) handled by all OAM instances in the cluster.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

4.12 Core Token Generation Operations

Metrics pertaining to core token operations in the cluster.

4.12.1 Number of Tokens Issued

This metric specifies the total number of security tokens created or generated. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Token creations during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.12.2 Tokens Issued per second

This metric specifies the average latency of security token creation or generation. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Token creation throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.12.3 Token Issuance Latency (ms)

This metric specifies the average latency of security token creation or generation. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Token issue creation latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.13 Core Token Validation Operations

Metrics related to core token validation in the cluster.

4.13.1 Custom Tokens Validated

This metric specifies the total number of security tokens validated. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Token validations during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.13.2 Tokens Validated per second

This metric specifies the throughput (tokens per second) of the security token validation processing. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Token validation throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.13.3 Token Validation Latency (ms)

This metric specifies the average latency, in milliseconds, of the security token validation processing. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Token issue validation latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.14 Log Operations (Aggregated)

Metrics related to logging operations for Oracle Access Manager instances within the cluster.

4.14.1 Average Latency (ms)

This metric specifies the average latency, in milliseconds, of the logging operations for all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Log Operations Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.14.2 Log Operations per second

This metric specifies the logging operations throughput (per second) for all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Log Operations Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.15 Log Operations Throughput (Aggregated)

Metrics related to logging operations for Oracle Access Manager.

4.15.1 Log Operations per second

This metric specifies logging throughput (logging operations per second). This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

4.16 Token Service Clients

Metrics pertaining to Token Service partners for all OAM Instances in the cluster.

4.16.1 Token Issuance Latency (ms)

This metric specifies the average latency of security token issuance requests for a partner. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Partner token issue latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.16.2 Tokens Issued

This metric specifies the total number of requests from a partner. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Partner token requests during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.16.3 Tokens Issued per second

This metric specifies the throughput (requests per second) of security token issuance requests from a partner. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Partner token issue request throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.16.4 Token Issuance Success Rate (%)

This metric specifies the success to failure ratio, as a percentage, for security token issuance requests from a partner. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Partner token request issuance success rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.16.5 Requester

This metric specifies the name of a requester partner. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

4.16.6 Token Validation Success Rate (%)

This metric specifies the success to failure ratio, as a percentage, for security token validation requests from a partner. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Partner token validation request success rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.16.7 Token Validation Latency (ms)

This metric specifies the average latency of processing security token validation requests from a partner. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Partner token validation request latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.16.8 Tokens Validated

This metric specifies the total number of security token validation requests from a partner. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Partner token validation requests during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.16.9 Token Validations per second

This metric specifies the throughput (requests per second) of security token validation requests from a partner. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Partner token validation request throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.17 Response

Response metrics represent the availability of the selected instance.

4.17.1 Status

This metric specifies the availability of this OAM server cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 1 Minute

Not Defined

0

The Oracle Access Manager instance is down

4.18 Token Issuances

Metrics related to security token issuance requests aggregated across all OAM instances in the cluster.

4.18.1 Token Issuance Latency (ms)

This metric specifies the average latency of the security token issuance request processing. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Token issue request latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.18.2 Tokens Issued

This metric specifies the total number of security token issuance requests. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Token issue requests during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.18.3 Tokens Issued per second

This metric specifies the throughput (requests per second) of the security token issuance request processing. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Token issue request throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.18.4 Issuance Success Rate (%)

This metric specifies the success to failure ratio, as a percentage, for security token issuance requests. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Token issue request success rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.18.5 Validation Latency (ms)

This metric specifies the average latency of the security token validation request processing. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Token validation request latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.18.6 Tokens Validated

This metric specifies the total number of security token validation requests. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Token validation requests during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.18.7 Validations per second

This metric specifies the throughput (requests per second) of the security token validation request processing. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Token validation request throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.18.8 Validation Success Rate (%)

This metric specifies the success to failure ratio, as a percentage, for security token validation requests. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Token validation request success rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.19 LDAP Operations (Aggregated)

Metrics for all LDAP operations for all OAM instances in the cluster.

4.19.1 LDAP_Operations per second

This metric measures the average number of Identity Provider operations, per second, that are called by various OAM components (Authentication Engine, Authorization Engine, Remote Registration, and so on) for all OAM instances in the cluster. It does not correspond to actual LDAP bind, search, or compare operation counts.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

LDAP Operations Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.19.2 Operation Name

This metric represents the hostname of the server hosting the roll up of operations between the user identity store and OAM Servers in the cluster.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

4.19.3 Average Latency (ms)

This metric measures the average amount of time spent in Identity Provider operations (for example, authenticateUser() and isUserAssignedToGroup ()) for all OAM instances in the cluster. It does not correspond to actual LDAP bind, search, or compare times. This value has been aggregated across all OAM instances in the cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

LDAP Operation Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.19.4 LDAP Operations Success Rate (%)

This metric measures the success to failure ratio for all Identity Provider component method calls for all OAM instances in the cluster. This may not correspond to the LDAP bind, search, or compare times, since failure can occur in the Identity Provider itself or the underlying User/Role API or at the JNDI layer and might never get down to actual LDAP server operations.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

LDAP Operations Success Failure Ratio during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

4.20 LDAP Operations Throughput (Aggregated)

Metrics for LDAP operations measure the average number of Identity Provider operations, per second, that are called by various OAM components (Authentication Engine, Authorization Engine, Remote Registration, and so on). It does not correspond to actual LDAP bind, search, or compare operation counts.

4.20.1 LDAP Operations per second

This metric measures the average number of Identity Provider operations, per second, that are called by various OAM components (Authentication Engine, Authorization Engine, Remote Registration, and so on) for all OAM instances in the cluster. It does not correspond to actual LDAP bind, search, or compare operation counts.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

5 Oracle Adaptive Access Manager

This chapter describes the Oracle Enterprise Manager can be used to manage Oracle Adaptive Access Manager metrics that show the performance for Oracle Adaptive Access Manager 11g servers and OAAM server clusters.

5.1 Datasource Metrics

This category of metrics provides information about the connection metrics.

5.1.1 Available Connections

For the selected datasource, this metric shows the number of database connections currently available (not in use).

5.1.2 Connections Created (per minute)

This metrics shows the average number of database connections created for this data source per minute in the last 5 minutes.

5.1.3 Connections in Use

This metric shows the number of data source connections that are currently in use by applications.

5.1.4 Connection Leaks (per minute)

For the selected datasource, this metric shows the average number of JDBC connection leaks per minute over the last 5 minutes. A leaked connection is a connection that was reserved from the data source but was not returned to the data source when the connect was closed.

5.1.5 Connection Pool Size

This metrics shows the average number of database connections created for this datasource per minute in the last 5 minutes.

5.1.6 Connection Refresh Failures (per minute)

This metric shows the average number of times per minute that the datasource attempted to refresh a database connection and failed over the past five minutes.

5.1.7 Connection Request Failures (per minute)

For the selected datasource, this metric shows the number of failed JDBC connection requests per minute, averaged over the past five minutes.

5.1.8 Connection Requests (per minute)

This metric shows the average number of requests for a connection from this datasource per minute over the last 5 minutes.

5.1.9 Successful Connections (%)

This metric shows the percentage of requests that successfully returned connections for this datasource over the last 5 minutes.

5.1.10 Unavailable Connections

This metric shows the number of database connections that are currently unavailable (in use or being tested by the system) in this instance of the datasource.

5.1.11 Connection Requests Waiting

For the selected datasource, this metric shows the number of JDBC connection wait successes per minute, averaged over the past five minutes. A wait success is a request for a connection from this datasource that had to wait before getting a connection and eventually succeeded in getting a connection.

5.1.12 Failed Waiting Connection Requests (per minute)

For the current data source, this metric shows the average number of connection wait requests that failed per minute over the past five minutes. A connection wait request is a request for a database connection that had to wait before getting a connection. Connection wait requests can fail for a variety of reasons, including waiting for longer than the value of the ConnectionReserveTimeoutSeconds property.

5.1.13 Connection Requests that Waited (per minute)

For the selected datasource, this metric shows the average number of connection wait requests per minute in the last 5 minutes. A connection wait request is a request for a connection that had to wait before getting a connection. This metric includes those that eventually got a connection and those that did not get a connection.

5.1.14 Connection Wait Successes (%)

For the current datasource, this metric shows the percentage of connection wait requests that successfully got a database connection during the last 5 minutes. A connection wait request is a request for a connection that had to wait before getting a connection. This metric includes those that eventually got a connection and those that did not get a connection.

5.1.15 Connection Wait Successes (per minute)

For the selected datasource, this metric shows the number of JDBC connection wait successes per minute, averaged over the past five minutes. A wait success is a request for a connection from this data source that had to wait before getting a connection and eventually succeeded in getting a connection.

5.2 Datasource - State

This metric shows the current state of the datasource.

5.2.1 Statements Added to Cache (per minute)

This metric shows the number of statements per minute that were added to the statement cache for this data source in the last 5 minutes.

5.2.2 Statements Discarded from Cache (per minute)

This metric shows the average number of statements per minute that were discarded from the cache over the past five minutes. Each connection in the connection pool has its own cache of statements. This number is the sum of the number of statements that were discarded from the caches for all connections in the connection pool.

5.2.3 Cached Statements not Used (per minute)

For the selected data source, this metric shows the number of statements per minute not satisfied by the statement cache, averaged over the past five minutes.

5.2.4 Cached Statements Used (%)

This metric shows the percentage of statements satisfied by the statement cache during the last 5 minutes. Each connection in the connection pool has its own cache of statements.

5.2.5 Cached Statements Used (per minute)

This metric shows the average number of statements per minute satisfied by the data source statement cache in the last 5 minutes. Each connection in the connection pool has its own cache of statements.

5.2.6 Statement Cache Size

For the current data source, this metric shows the number of prepared and callable JDBC statements currently cached in the connection pool. Each JDBC connection in the connection pool has its own cache of statements. This number is the sum of the number of statements in the caches for all connections in the connection pool.

5.3 EJB Module Metrics

These metrics provide information about the EJB home over the last 5 minutes.

5.3.1 Cached Beans

This metric shows the total number of beans from this EJB Home that are currently in the EJB cache.

5.3.2 Bean Activations (per minute)

This metric shows the average number of beans per minute that have been activated from the EJB home over the last 5 minutes.

5.3.3 Cache Hits (%)

This metric shows the percentage of cache accesses that completed successfully in the last 5 minutes.

5.3.4 Cache Misses (per minute)

This metric shows the average number of cache misses per minute for this EJB module in the last 5 minutes.

5.3.5 Bean Accesses (per minute)

For the current EJB module, this metric shows how many times the EJB pool has been accessed per minute. This is averaged over the last 5 minutes.

5.3.6 Bean Access Successes (%)

This metric shows the percentage of EJB pool accesses that were successful in the last 5 minutes.

5.3.7 Free Bean Instances

This metric shows the current number of available EJB instances in the free pool.

5.3.8 Bean Destroys (per minute)

This metric shows the average number of EJB destroys per minute for this EJB module over the last 5 minutes.

5.3.9 Bean Access Failures (per minute)

This metric shows the average number of times per minute that a failed attempt was made to get an instance from the free pool. This value is averaged over the past five minutes. An attempt to get a bean from the pool will fail if there are no available instances in the pool.

5.3.10 Beans in Use

This metric shows the number of EJB instances currently being used from the free pool.

5.3.11 Bean Transaction Commits (per minute)

This metric shows the average number of EJB transaction commits per minute for this EJB Module over the last 5 minutes.

5.3.12 Bean Transaction Rollbacks (per minute)

This metric shows the average number of EJB transaction rollbacks per minute for this EJB module over the last 5 minutes.

5.3.13 Bean Transaction Timeouts (per minute)

This metric shows the average number of EJB transaction timeouts per minute for this EJB module over the last 5 minutes.

5.4 EJB Transaction Metrics

These metrics show the transaction information for this EJB over the last 5 minutes.

5.4.1 Bean Transaction Commits (%)

This metric shows the EJB transaction commits per minute, averaged over the past five minutes.

5.4.2 Bean Transaction Commits (per minute)

This metric shows the EJB transaction commits per minute, averaged over the past five minutes.

5.4.3 Bean Transaction Rollbacks (per minute)

This metric shows the EJB transaction rollbacks per minute, averaged over the past five minutes.

5.4.4 Bean Transaction Timeouts (per minute)

This metric shows the average number of EJB transaction timeouts per minute for the EJB module over the last 5 minutes.

5.5 Overview Metrics

These metrics provide data on how the servlets and JSPs, EJBs, and Oracle WebLogic Server Work Manager for the selected application are currently performing.

5.5.1 Cached Beans

This metric shows the total number of EJBs currently active in the EJB cache.

5.5.2 Cache Accesses (per minute)

This metric shows the average number of EJB cache access attempts per minute on the selected server in the last 5 minutes.

5.5.3 Bean Activations (per minute)

This metric shows the average number of Enterprise Java Beans activated per minute over the last 5 minutes.

5.5.4 Cache Hits (%)

This metrics indicates the percentage of cache accesses that completed successfully in the last 5 minutes.

5.5.5 Cache Misses (per minute)

This metric shows the number of EJB cache misses per minute in the last 5 minutes.

5.5.6 Bean Accesses (per minute)

This metrics shows the average number of Pool accesses per minute for the selected server in the last 5 minutes.

5.5.7 Bean Successes (%)

For the selected server, this metric displays the percentage of EJB pool accesses that were successful in the last 5 minutes.

5.5.8 Free Bean Instances

For the selected server, this metric indicates the current number of available Java bean instances in the free pool.

5.5.9 Bean Destroys (per minute)

This metric shows the average number of EJB destroys per minute for the selected server in the last 5 minutes.

5.5.10 Bean Access Failures (per minute)

This metric shows the percentage of pool accesses to the server that were successful in the last 5 minutes.

5.5.11 Beans in Use

This metric shows the number of EJB instances currently being used from the free pool.

5.5.12 Bean Transaction Commits (%)

For the selected server, this metric identifies the EJB transaction commits per minute for the last 5 minutes.

5.5.13 Bean Transaction Commits (per minute)

For the selected server, this metric identifies the EJB transaction commits per minute for the last 5 minutes.

5.5.14 Bean Transaction Rollbacks (per minute)

For the selected server, this metric shows the number of transactions rolled back per minute, averaged over the past five minutes.

5.5.15 Bean Transaction Timeouts (per minute)

This metric shows the EJB transaction timeouts per minute for the last 5 minutes on the selected server.

5.5.16 MDB Messages (per minute)

For the selected server, this metric specifies the number of messages processed by message-driven beans (MDBs) per minute in the last 5 minutes.

5.5.17 Requests (per minute)

This metric shows the number of requests processed per minute during the last 5 minutes on the selected server. If the request handling throughput is very low, either there is no activity on the server or a problem exists which prevents the server from processing requests.

5.5.18 Request Processing Time (ms)

This metric shows the average time (in milliseconds) spent to process a request during the last interval. The interval is the period specified as the collection frequency for this metric.

5.5.19 Active Sessions

The number of active sessions for the selected OAAM server.

5.5.20 Work Manager Pending Requests

For the selected server, this metric shows the number of work manager requests pending in the queue.

5.5.21 Work Manager Requests (per minute)

This metric shows the number of work manager requests processed per minute in the last 5 minutes on the selected server.

5.6 Servlet/JSP Metrics

These metrics provide information about the selected servlet or JSP per minute over the last 5 minutes.

5.6.1 Reloads (per minute)

This metric shows the average number of reloads of the selected servlet or JSP per minute over the last 5 minutes.

5.6.2 Requests (per minute)

For the selected server, this metric shows the average number of servlet and/or JSP invocations per minute, averaged over the past five minutes.

5.6.3 Request Processing Time (ms)

For the selected server, the average amount of time spent executing servlets and/or JSPs in the last 5 minutes (milliseconds).

5.7 Web Module Metrics

These metrics provide information for the selected web module.

5.7.1 Requests (per minute)

This metric shows the average number of servlet and JSP invocations per minute for this Web module in the last 5 minutes.

5.7.2 Request Processing Time (ms)

This metric shows the average amount of time (in milliseconds) spent executing servlets and/or JSPs in this Web module for the last 5 minutes.

5.7.3 Active Sessions

This metric shows the number of active sessions for this web module.

5.8 Login Metrics Summary

This category of metrics provides status and performance data related to OAAM server login requests.

5.8.1 Percentage of Blocked Logins during the Last 5 Minute Collection Interval

This metric represents the percentage of login requests that are blocked by OAAM during the last 5 minute collection interval. Importance of this metric: This metric is used to give some indication of the percentage of login requests that were blocked. Login requests are usually blocked if OAAM policies detect unusual or fraudulent behavior.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If there is a high percentage of blocked login requests, review the rules and policies that are resulting in the BLOCK action. Check to see if BLOCK is the appropriate action.

5.8.2 Number of Logins Blocked during the Last 5 Minute Collection Interval

This metric shows the number of login requests blocked by OAAM during the last 5 minute collection interval. Login requests are usually blocked if OAAM policies detect unusual or fraudulent behavior. Importance of this metric: This metric is used to give some indication of how many login requests are blocked. Login requests are usually blocked if OAAM policies detect unusual or fraudulent behavior.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when value is out of bound: If there are too many blocked login requests, review the rules and policies that are resulting in the BLOCK action. Check to see if BLOCK is the appropriate action for the situation.

5.8.3 Percentage of Challenged Logins during the Last 5 Minute Collection Interval

This metric represents the percentage of login requests that were presented with challenge questions after authentication during the last 5 minute collection interval. Importance of this metric: This metric is used to give some indication of the percentage of login requests that were presented with challenge questions as a second factor authentication. A very high rate of this value indicates that login requests are occurring in a suspicious or risky environment.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If there are too many login requests that are being challenged, review the rules and policies that are resulting in the CHALLENGE action. Check to see if CHALLENGE is the appropriate action.

5.8.4 Number of Logins Challenged during the Last 5 Minute Collection Interval

This metric shows the number of login requests that were presented with challenge questions after authentication. Importance of this metric: This metric is used to give some indication of how many login requests were presented with challenge questions as a second factor authentication. A very high rate of this value indicates that login requests are occurring in a suspicious/risky environment.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when this value is out of bound: If there are too many login requests that are being challenged, review the rules and policies that are resulting in the CHALLENGE action. Check to see if CHALLENGE is the appropriate action for the situation.

5.8.5 Percentage of Failed Logins during the Last 5 Minute Collection Interval

This metric shows the percentage of login requests that failed during the last 5 minute collection interval. Importance of this metric: This metric is used to give some indication of the percentage of login requests that have failed. A failed login request usually implies that authentication was not successful. A very high rate of failed login requests when compared with total login requests may indicate suspicious activity.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: Usually this percentage should be low. If most of the logins are failures then there might be suspicious activity. Consider further investigation of the device and location of the failed login requests.

Check the server logs to make sure the authentication subsystem is working and there are no errors from the authentication subsystem.

5.8.6 Number of Failed Logins per Sec since the Server Startup

This metric shows the number of failed login requests per second since server startup. Importance of this metric: A failed login request usually implies that authentication was not successful. Usually the rate of failed logins should be low. A very high rate of failed login requests when compared with the total number of login requests may indicate suspicious activity.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when value is out of bound: Usually this count should be low. If most of the logins are failures, there might be suspicious activity. Consider further investigation into the device and location of the failed login requests. Check the server logs to make sure the authentication subsystem is working and that there are no errors from the authentication subsystem.

5.8.7 Number of Logins Failed during the Last 5 Minute Collection Interval

This metric shows the number of failed logins during the last collection interval. Importance of this metric: A failed login request usually implies that authentication was not successful. A very high rate of failed login requests when compared with the total number of login requests implies suspicious activity.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when value is out of bound: Usually this count should be low. If most of the logins are failures, there might be suspicious activity. Consider further investigation into the device and location of the failed login requests. Check the server logs to make sure the authentication subsystem is working and that there are no errors from it.

5.8.8 Percentage of Successful Logins during the Last 5 Minute Collection Interval

This metric shows the percentage of login requests that were successful. Importance of this metric: Usually most login requests are successful in normal scenarios. Very low rates of successful login requests when compared with total login requests indicate suspicious activity.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If the percentage of successful logins is very low, consider further investigation into the device and location of the failed login requests.

5.8.9 Number of Successful Logins per Sec Since the Server Startup

This metric represents the number of successful login requests per second for the selected OAAM server since server startup. Importance of this metric: This metric is used to give some indication of how many login requests were successful. Usually most login requests are successful in normal scenarios. A very low rate of successful login requests when compared with total login requests may indicate suspicious activity.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: Usually most logins are successful unless there is suspicious activity. If the number of successful logins is very low when compared to the total number of logins, consider further investigation into the device and location of the failed login requests.

5.8.10 Number of Successful Logins during the Last 5 Minute Collection Interval

This metric shows the number of successful login requests during the last 5 minute collection interval. Importance of this metric: This metric is used to give some indication of how many login requests were successful. Usually most login requests are successful in normal scenarios. Very low rates of successful login requests when compared with total login requests may indicate suspicious activity.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: Usually most logins are successful unless there is suspicious activity. If the number of successful logins is very low when compared to the total number of logins, consider further investigation into the device and location of the failed login requests.

5.8.11 Number of Total Logins Attempted during the Last 5 Minute Collection Interval

This metric shows the total number of login requests during the last 5 minute collection interval. Importance of this metric: This metric is used to give some indication of the login requests activity.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when this value is out of bound:

- If the logins count is very high, but does not impact system performance, no action is necessary.

- If the login count is very high and impacts performance, consider creating a cluster of OAAM servers so that the load can be shared across multiple servers.

- When the login count is too high, look at the failed login count and see if there is any correlation. If most of the logins are failures, there might be suspicious activity. Consider further investigation into the device and location of the failed login requests.

5.9 Policy Execution Summary

These metrics provide statistics and performance information about policy execution. The time spent to process policies includes:

1. Time taken to execute a given policy. This metric value includes the time taken to execute ALL the rules associated to a policy.

2. Time to process the trigger combinations, rule results, and alerts.

5.9.1 Average Execution Time for All Policies since Server Startup (ms)

This metric shows the average time (in milliseconds) spent to process all policies since server startup.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

5.9.2 Total Number of Policies Processed

This metric captures the total number of policies that completed processing.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

5.9.3 Total Number of Policies Processed since Last Sample

This metric captures the total number of policies processed at the end of the sampling interval.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

5.9.4 Maximum Time Taken by Any Policy since Server Startup (ms)

This metric captures the maximum time spent for any policy to complete processing since server startup (ms).

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

5.9.5 Minimum Time Taken by Any Policy Since Server Startup (ms)

This metric shows the minimum time spent for any policy to complete processing since server startup (ms).

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

5.9.6 Time Taken for Servicing All Policies Since Server Startup (ms)

This metric shows the total time (in milliseconds) spent processing all policies associated with a checkpoint since server startup.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

5.10 Response

This category of metrics indicates whether the target OAAM Server is available.

5.10.1 UpDown Status

This metric indicates the status of the OAAM Server. A value of one (1) indicates that the application is up and running. A value of zero (0) indicates that the application is down.

5.11 Rule Execution Summary

The category of metrics that pertain to rule execution.

5.11.1 Average Execution Time for All Requests Since Server Startup (ms)

This metric shows the average time (in milliseconds) spent processing all rules associated with a policy since server startup.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If the average time to process all rules associated with the policy is high, check to see if there are too many rules in the policy. If there are, consider splitting them into different policies. Check to see if expensive rules exist in the policy. If they do, consider optimizing the underlying SQL queries or optimizing and tuning the database.

5.11.2 Total Number of Requests Completed

This metric captures the total number of rules processed.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If the total number of rules processed is low, check to see if there are too many rules in the policy. If there are, consider splitting them into different policies. Also check to see if expensive rules exist in the policy. If they do, consider optimizing the underlying SQL queries or optimizing and tuning the database.

5.11.3 Total Number of Requests Completed Since Last Sample

This metric captures the total number of rules processed since the last sample.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If the total number of rules processed since the last sample is low, check to see if there are too many rules in the policy. If there are, consider splitting them into different policies. Check to see if expensive rules exist in the policy. If they do, consider optimizing the underlying SQL queries or optimizing and tuning the database.

5.11.4 Maximum Time Taken by Any Request since Server Startup (ms)

This metric shows the maximum time (in milliseconds) spent processing any request since the server started.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If the value of the metric is high, consider optimizing the underlying SQL queries or optimizing/tuning database.

5.11.5 Minimum Time Taken by Any Request Since Server Startup (ms)

This metric shows the minimum time (in milliseconds) spent processing any request since server startup.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If the value of the metric is high, consider optimizing the underlying SQL queries or optimizing/tuning database.

5.11.6 Time Taken for Servicing All Requests Since Server Startup (ms)

This metric shows the total time (in milliseconds) spent processing all rules associated with a policy since server startup.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: A high value could be attributed to either too many rules associated to a policy or expensive rules. If there are too many rules, consider splitting them into different policies. If there are expensive rules, consider optimizing the underlying SQL queries or optimizing/tuning database.

5.12 Checkpoint Execution Summary

This metric presents a summary of the time spent to execute all the policies in a checkpoint.

5.12.1 Average Checkpoint Processing Time for All Requests Since Server Startup (ms)

This metric shows the average time (in milliseconds) spent processing all policies associated with a checkpoint since the server started. Usually one or more policies are associated to a checkpoint. This metric value includes the value from the metric "Policy Execution."

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If the metric value is high, perform the following steps:

1. Narrow down the cause to Rules Execution or Policy Execution.

2. Check to see if any SQL queries are taking too long to execute and appropriately tune and optimize the database.

For the Rule Execution metric: A high value could be attributed to either too many rules associated to a policy or more expensive rules. If the value for the time taken to process rules associated with a policy is a high value, check to see if there are too many rules in the policy. If there are, consider splitting them into different policies. Check to see if expensive rules exist in the policy. If they do, consider optimizing the underlying SQL queries or optimizing and tuning the database.

For the Policy Execution metric: If the value for the time taken to process the policy is high, check to see if trigger combinations exist in the policy. If they do, consider not using trigger combinations. Check to see if nested policies exist in the policy. Review them and consider alternatives.

5.12.2 Total Number of Checkpoints Completed

This metric captures the total number of checkpoints executed.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If the number of checkpoints executed is low, perform the following steps:

1. Narrow down the cause to Rules Execution or Policy Execution.

2. Check to see if any SQL queries are taking too long to execute and appropriately tune and optimize the database.

For the Rule Execution metric: A high value could be attributed to either too many rules associated to a policy or more expensive rules. If the value for the time taken to process rules associated with a policy is a high value, check to see if there are many rules in the policy. If there are, consider splitting them into different policies. Check to see if expensive rules exist in the policy. If they do, consider optimizing the underlying SQL queries or optimizing and tuning the database.

For the Policy Execution metric: If the value for the time taken to process the policy is high, check to see if trigger combinations exist in the policy. If they do, consider not using trigger combinations. Check to see if nested policies exist in the policy. Review them and consider alternatives.

5.12.3 Total Number of Checkpoints Completed Since Last Sample

This metric captures the total number of checkpoints where all associated policies were processed since the last sample.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If the number of checkpoints executed is low, perform the following steps:

1. Narrow down the cause to Rules Execution or Policy Execution.

2. Check to see if any SQL queries are taking too long to execute and appropriately tune and optimize the database.

For the Rule Execution metric: A high value could be attributed to either too many rules associated to a policy or more expensive rules. If the value for the time taken to process rules associated with a policy is a high value, check to see if there are many rules in the policy. If there are, consider splitting them into different policies. Check to see if expensive rules exist in the policy. If they do, consider optimizing the underlying SQL queries or optimizing and tuning the database.

For the Policy Execution metric: If the value for the time taken to process the policy is high, check to see if trigger combinations exist in the policy. If they do, consider not using trigger combinations. Check to see if nested policies exist in the policy. Review them and consider alternatives.

5.12.4 Maximum Time Taken by Any CheckPoint Since Server Startup (ms)

This metric shows the maximum time (in milliseconds) spent processing policies associated with any checkpoint since the server started.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If the number of checkpoints executed is low, perform the following steps:

1. Narrow down the cause to Rules Execution or Policy Execution.

2. Check to see if any SQL queries are taking too long to execute and appropriately tune and optimize the database.

For the Rule Execution metric: A high value could be attributed to either too many rules associated to a policy or more expensive rules. If the value for the time taken to process rules associated with a policy is a high value, check to see if there are many rules in the policy. If there are, consider splitting them into different policies. Check to see if expensive rules exist in the policy. If they do, consider optimizing the underlying SQL queries or optimizing and tuning the database.

For the Policy Execution metric: If the value for the time taken to process the policy is high, check to see if trigger combinations exist in the policy. If they do, consider not using trigger combinations. Check to see if nested policies exist in the policy. Review them and consider alternatives.

5.12.5 Minimum Time Taken by Any Checkpoint Since Server Startup (ms)

This metric shows the minimum time (in milliseconds) spent processing any checkpoint since the server started.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If the number of checkpoints executed is low, perform the following steps:

1. Narrow down the cause to Rules Execution or Policy Execution.

2. Check to see if any SQL queries are taking too long to execute and appropriately tune and optimize the database.

For the Rule Execution metric: A high value could be attributed to either too many rules associated to a policy or more expensive rules. If the value for the time taken to process rules associated with a policy is a high value, check to see if there are many rules in the policy. If there are, consider splitting them into different policies. Check to see if expensive rules exist in the policy. If they do, consider optimizing the underlying SQL queries or optimizing and tuning the database.

For the Policy Execution metric: If the value for the time taken to process the policy is high, check to see if trigger combinations exist in the policy. If they do, consider not using trigger combinations. Check to see if nested policies exist in the policy. Review them and consider alternatives.

5.12.6 Time Taken for Servicing All Checkpoint Since Server Startup (ms)

This metric shows the total time (in milliseconds) spent processing all checkpoints since the server started.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If the number of checkpoints executed is low, perform the following steps:

1. Narrow down the cause to Rules Execution or Policy Execution.

2. Check to see if any SQL queries are taking too long to execute and appropriately tune and optimize the database.

For the Rule Execution metric: A high value could be attributed to either too many rules associated to a policy or more expensive rules. If the value for the time taken to process rules associated with a policy is a high value, check to see if there are many rules in the policy. If there are, consider splitting them into different policies. Check to see if expensive rules exist in the policy. If they do, consider optimizing the underlying SQL queries or optimizing and tuning the database.

For the Policy Execution metric: If the value for the time taken to process the policy is high, check to see if trigger combinations exist in the policy. If they do, consider not using trigger combinations. Check to see if nested policies exist in the policy. Review them and consider alternatives.

5.13 Update Authorization Status Summary

This category of metrics provides information related to updates in user authorization status.

5.13.1 Average Execution Time for All Requests Since Server Startup (ms)

This metric shows the average time (in milliseconds) spent executing the updateAuthStatus() API call since the server started.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If the metric value is high, you may want to investigate this metric in more detail. Check to see if the database is performing optimally and if SQL queries are taking too long to execute. If query execution consumes significant time, consider adding relevant indexes or tuning the database and/or purging and archiving old, obsolete data from various OAAM tables.

For information about setting up archive and purge procedures, see the archive and purge appendix in Oracle Fusion Middleware Administrator's Guide for Oracle Adaptive Access Manager.

5.13.2 Total Number of Requests Completed

This metric shows the total time (in milliseconds) spent for the updateAuthStatus() API call to complete since server startup. This value indicates the total time taken for the API Call updateAuthStatus to complete. This API is called to update the authentication status of the user request.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If the metric value is high, you may want to investigate this metric in more detail. Check to see if the database is performing optimally and if SQL queries are taking too long to execute. If query execution consumes significant time, consider adding relevant indexes or tuning the database and/or purging and archiving old, obsolete data from various OAAM tables.

For information about setting up archive and purge procedures, see the archive and purge appendix in Oracle Fusion Middleware Administrator's Guide for Oracle Adaptive Access Manager.

5.13.3 Total Number of Requests Completed Since Last Sample

This metric captures the total number of updateAuthStatus() API calls since the last sample.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

5.13.4 Maximum Time Taken by Any Request Since Server Startup (ms)

This metric shows the maximum time (in milliseconds) spent executing any updateAuthStatus() API call since the server started. This API is called to update the authentication status of the user request.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If the metric value is high, you may want to investigate this metric in more detail. Check to see if the database is performing optimally and if SQL queries are taking too long to execute. If query execution consumes significant time, consider adding relevant indexes or tuning the database and/or purging and archiving old, obsolete data from various OAAM tables.

For information about setting up archive and purge procedures, see the archive and purge appendix in Oracle Fusion Middleware Administrator's Guide for Oracle Adaptive Access Manager.

5.13.5 Minimum Time Taken by Any Request Since Server Startup (ms)

This metric shows the minimum time (in milliseconds) spent to execute the updateAuthStatus() API call since the server started. This updateAuthStatus() API is called to update the authentication status of the user request.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If the metric value is high, you may want to investigate this metric in more detail. Check to see if the database is performing optimally and if SQL queries are taking too long to execute. If query execution consumes significant time, consider adding relevant indexes or tuning the database and/or purging and archiving old, obsolete data from various OAAM tables.

For information about setting up archive and purge procedures, see the archive and purge appendix in Oracle Fusion Middleware Administrator's Guide for Oracle Adaptive Access Manager.

5.13.6 Time Taken for Servicing All Requests Since Server Startup (ms)

This metric shows the total time (in milliseconds) spent to execute all updateAuthStatus() API calls since the server started. This updateAuthStatus() API is called to update the authentication status of the user request.

The following table shows how often the metric's value is collected

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Action when the value is out of bound: If the metric value is high, you may want to investigate this metric in more detail. Check to see if the database is performing optimally and if SQL queries are taking too long to execute. If query execution consumes significant time, consider adding relevant indexes or tuning the database and/or purging and archiving old, obsolete data from various OAAM tables.

For information about setting up archive and purge procedures, see the archive and purge appendix in Oracle Fusion Middleware Administrator's Guide for Oracle Adaptive Access Manager.

5.14 Update Log Summary

This category of metrics provides information concerning the updateLog API call. This API call captures the userId, IP Address and other details of the user request.

5.14.1 Average Execution Time for All Requests Since Server Startup (ms)

This metric shows the average execution time (in milliseconds) for the API call updateLog() since server startup. updateLog() is the data collection API that captures the user ID, IP address and other details of the user request.

User Action

Action when the value is out of bound: If the metric value is high, you may want to investigate this metric in more detail. Check to see if the database is performing optimally and if the queries on VCRYPT_TRACKER_USERNODE_LOGS are taking too long to execute. If query execution consumes significant time, consider adding relevant indexes or tuning the database and/or purging and archiving old, obsolete data from various OAAM tables.

For information about setting up archive and purge procedures, see the archive and purge appendix in Oracle Fusion Middleware Administrator's Guide for Oracle Adaptive Access Manager.

5.14.2 Total Number of Requests Completed

This metric captures the total number of times the "updateLog()" API Call was executed.

5.14.3 Total Number of Requests Completed Since Last Sample

This metric captures the total number of times the updateLog API call was executed since the last sample. updateLog() is the data collection API that captures the user ID, IP address and other details of the user request.

5.14.4 Maximum Time Taken by Any Request Since Server Startup (ms)

This metric shows the maximum time (in milliseconds) spent executing any updateLog() API call since server startup. updateLog() is the data collection API that captures the user ID, IP address and other details of the user request.

User Action

Action when the value is out of bound: If the metric value is high, you may want to investigate this metric in more detail. Check to see if the database is performing optimally and if the queries on VCRYPT_TRACKER_USERNODE_LOGS are taking too long to execute. If query execution consumes significant time, consider adding relevant indexes or tuning the database and/or purging and archiving old, obsolete data from various OAAM tables.

For information about setting up archive and purge procedures, see the archive and purge appendix in Oracle Fusion Middleware Administrator's Guide for Oracle Adaptive Access Manager.

5.14.5 Minimum Time Taken by Any Request Since Server Startup (ms)

This metric shows the minimum execution time (in milliseconds) for any updateLog API call since server startup. updateLog() is the data collection API that captures the user ID, IP address and other details of the user request.

User Action

Action when the value is out of bound: If the metric value is high, you may want to investigate this metric in more detail. Check to see if the database is performing optimally and if the queries on VCRYPT_TRACKER_USERNODE_LOGS are taking too long to execute. If query execution consumes significant time, consider adding relevant indexes or tuning the database and/or purging and archiving old, obsolete data from various OAAM tables.

For information about setting up archive and purge procedures, see the archive and purge appendix in Oracle Fusion Middleware Administrator's Guide for Oracle Adaptive Access Manager.

5.14.6 Time Taken for Servicing All Requests Since Server Startup (ms)

This metric shows the cumulative amount of time (in milliseconds) that was spent executing updateLog() API calls. updateLog() is the data collection API that captures the user ID, IP address and other details of the user request.

User Action

Action when the value is out of bound: If the metric value is high, you may want to investigate this metric in more detail. Check to see if the database is performing optimally and if the queries on VCRYPT_TRACKER_USERNODE_LOGS are taking too long to execute. If query execution consumes significant time, consider adding relevant indexes or tuning the database and/or purging and archiving old, obsolete data from various OAAM tables.

For information about setting up archive and purge procedures, see the archive and purge appendix in Oracle Fusion Middleware Administrator's Guide for Oracle Adaptive Access Manager.

6 Oracle Adaptive Access Manager Cluster

This chapter describes the Oracle Adaptive Access Manager Cluster metrics. An OAAM cluster is a group of servers working together with OAAM services to provide support for failover, load balancing, and scalability.

6.1 Oracle Adaptive Access Manager Datastore Information

This category of metrics provides information on the statuses of all the OAAM server instances in the OAAM cluster.

6.1.1 JDBC URL

This metric provides information about the database connections of the OAAM server instances in the OAAM cluster.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

6.2 Login Metrics Summary

This category of metrics represents the aggregate number of logins to the OAAM servers in the cluster on which OAAM is running.

6.2.1 Blocked Logins Rate (%)

This metric represents the aggregate percentage of login requests to the OAAM servers in the OAAM cluster that were blocked.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 6-1 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

>

Not Defined

Not Defined

-

Blocked Logins %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

6.2.2 Blocked Logins

This metric represents the aggregate number of login requests to the OAAM servers in the OAAM cluster that were blocked by OAAM during the last five minute interval.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 6-2 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins %value% is below warning (%warning_threshold%) or critical (%critical_threshold%) threshold

6.2.3 Challenged Logins Rate (%)

This metric represents the aggregate percentage of login requests to the OAAM servers in the OAAM cluster that were presented with challenge questions.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 6-3 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

>

Not Defined

Not Defined

-

Logins Challenged (%) %value% is above warning (%warning_threshold%) or critical (%critical_threshold%) threshold

6.2.4 Challenged Logins

This metric represents the aggregate number of login requests to the OAAM servers in the OAAM cluster that were presented with challenge questions as a second factor authentication.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 6-4 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

>

Not Defined

Not Defined

-

Challenged Logins%value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

6.2.5 Failed Logins Rate (%)

This metric represents the aggregate percentage of login requests to the OAAM servers in the OAAM cluster that have failed.

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 6-5 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

>

Not Defined

Not Defined

-

Failed Login Rate (%) %value% is above warning (%warning_threshold%) or critical (%critical_threshold%) threshold

6.2.6 Failed Logins

This metric represents the aggregate number of failed login requests to the OAAM servers in the OAAM cluster in the last 5-minute collection interval.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 6-6 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

>

Not Defined

Not Defined

-

Failed Logins %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

6.2.7 Successful Logins Rate (%)

This metric specifies the aggregate percentage of login requests to the OAAM servers in the OAAM cluster that were successful.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 6-7 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

>

Not Defined

Not Defined

-

Successful Login Rate (%) %value% is below warning (%warning_threshold%) or critical (%critical_threshold%) threshold

6.2.8 Successful Logins

This metric represents the aggregate number of login requests to the OAAM servers in the OAAM cluster that were successful in the last 5-minute interval. Most login requests are successful in normal scenarios. Very low rates of successful login requests when compared with total login requests imply suspicious activity.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 6-8 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins %value% is below warning (%warning_threshold%) or critical (%critical_threshold%) threshold

6.2.9 Total Logins Attempted

This metric represents the aggregate total number of login requests to the OAAM servers in the OAAM cluster during the last 5-minute collection interval.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 6-9 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

>

Not Defined

Not Defined

-

Total Logins Attempted %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

6.3 Login Metrics Rate Summary

This category of metrics represents the status and performance of the logins to the OAAM servers in the OAAM cluster.

6.3.1 Failed Logins per second

This metric represents the aggregate number of failed login requests per second to the OAAM servers in the OAAM cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 6-10 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

>

Not Defined

Not Defined

-

++

Failed Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

6.3.2 Successful Logins per second

This metric represents the aggregate number of successful login requests per second for the OAAM servers in the OAAM cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 6-11 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

6.4 Response

This category of metrics represents the status and performance of the OAAM servers in the OAAM cluster.

6.4.1 Status

This metric represents the current status of the OAAM Servers in the OAAM cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 6-12 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

=

0

The Oracle Adaptive Access Manager cluster instance is down

7 Oracle Identity Manager

This chapter describes the Oracle Identity Manager metrics.

7.1 Oracle Adaptive Metrics

This category of metrics provides information on Adapter metrics.

7.1.1 Adapter Name

The name of the adapter.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 600 Seconds

7.1.2 Average Adapter Execution Time (ms)

The average time in milliseconds to execute an adapter in the last five minutes.

The following table shows how often the metric's value is collected.

Table 7-1 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

Average Adapter Execution Time (ms) %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

7.1.3 Completed Adapter Executions

The total number of completed adapter executions in the last five minutes.

The following table shows how often the metric's value is collected.

Table 7-2 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

Completed Adapter Executions %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold..

7.1.4 Maximum Adapter Execution Time (ms)

The maximum time in milliseconds to execute an adapter in the last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 600 Seconds

7.1.5 Minimum Adapter Execution Time (ms)

The minimum time in milliseconds to execute an adapter in the last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 600 Seconds

7.2 Datasource Metrics

This section provides details on the datasource metrics.

7.2.1 Datasource - Available Connections

This metric shows the number of database connections currently available (not in use) for this data source.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-3 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

<

Not Defined

Not Defined

-

The number of available connections for datasource %name% is %value%.

7.2.2 Datasource - Connections Created (per minute)

This metrics shows the average number of database connections created for this data source per minute in the last five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-4 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The connections created for datasource %name% are %value% (per minute).

7.2.3 Datasource - Connections in Use

This metric shows the number of data source connections that are currently in use by applications.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-5 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The number of connections in use for datasource %name% is %value%.

7.2.4 Datasource - Connection Leaks (per minute)

For the selected data source, this metric shows the average number of JDBC connection leaks per minute over the last 5 minutes. A leaked connection is a connection that was reserved from the data source but was not returned to the data source when the connect was closed.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-6 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The connection leaks for datasource %name% are %value% (per minute).

7.2.5 Datasource - Connection Pool Size

This metric shows the current number of JDBC connections in the connection pool in the selected data source.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-7 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The connection pool size is %value%.

7.2.6 Datasource - Connection Refresh Failures (per minute)

This metric shows the average number of times per minute that the data source attempted to refresh a database connection and failed over the past five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-8 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The connection refresh failures for datasource %name% are %value% (per minute).

7.2.7 Datasource - Connection Request Failures (per minute)

This metric shows the average number of failed connection requests per minute in the last five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-9 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The connection request failures for datasource %name% are %value% (per minute).

7.2.8 Datasource - Connection Requests (per minute)

This metric shows the average number of requests for a connection from this data source per minute over the last five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-10 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The connection requests for datasource %name% are %value% (per minute).

7.2.9 Datasource - Successful Connections (%)

This metric shows the percentage of requests that successfully returned connections for this data source over the last five minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-11 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

<

Not Defined

Not Defined

-

The successful connection rate for datasource %name% is %value%%%.

7.2.10 Datasource - Unavailable Connections

This metric shows the number of database connections that are currently unavailable (in use or being tested by the system) in this instance of the data source.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-12 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The number of unavailable connections for datasource %name% is %value%.

7.2.11 Datasource - Connection Requests Waiting

This metric shows the current number of connection wait requests for this data source. A connection wait request is a request that had to wait for a database connection.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-13 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The number of connection requests waiting for datasource %name% is %value%.

7.2.12 Datasource - Failed Waiting Connection Requests (per minute)

For the current data source, this metric shows the average number of connection wait requests that failed per minute over the past five minutes. A connection wait request is a request for a database connection that had to wait before getting a connection. Connection wait requests can fail for a variety of reasons, including waiting for longer than the value of the ConnectionReserveTimeoutSeconds property.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-14 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The connection wait failures for datasource %name% are %value% (per minute).

7.2.13 Datasource - Connection Requests that Waited (per minute)

For the selected data source, this metric shows the average number of connection wait requests per minute in the last 5 minutes. A connection wait request is a request for a connection that had to wait before getting a connection. This metric includes those that eventually got a connection and those that did not get a connection.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-15 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The connections that waited for datasource %name% are %value% (per minute).

7.2.14 Datasource - Connection Wait Successes (%)

For the current data source, this metric shows the percentage of connection wait requests that successfully got a database connection during the last 5 minutes. A connection wait request is a request for a connection that had to wait before getting a connection. This metric includes those that eventually got a connection and those that did not get a connection.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-16 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

<

Not Defined

Not Defined

-

The connection wait success rate for datasource %name% is %value%%%.

7.2.15 Datasource - Connection Wait Successes (per minute)

For this data source, this metric shows the average number of connection wait requests that succeeded per minute over the last 5 minutes. A connection wait request succeeds when it eventually gets a database connection.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-17 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The connection wait successes for datasource %name% are %value% (per minute).

7.2.16 Datasource - State

The current state of the data source. Possible states are: * Running - the data source is enabled (deployed and not suspended). This is the normal state of the data source. * Suspended - the data source has been manually disabled. * Shutdown - the data source is shutdown and all database connections have been closed. * Overloaded - all resources in pool are in use. * Unhealthy - all connections are unavailable (not because they are in use). This state occurs if the database server is unavailable when the data source is created (creation retry must be enabled) or if all connections have failed connection tests (on creation, on reserve, or periodic testing). * Unknown - the data source state is unknown

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-18 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

=!

Not Defined

Not Defined

-

The state of datasource %name% is %value%.

7.2.17 Datasource - Statements Added to Cache (per minute)

This metric shows the number of statements per minute that were added to the statement cache for this data source in the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-19 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The statements added to cache are %value% (per minute).

7.2.18 Datasource - Statements Discarded from Cache (per minute)

This metric shows the average number of statements per minute that were discarded from the cache over the past five minutes. Each connection in the connection pool has its own cache of statements. This number is the sum of the number of statements that were discarded from the caches for all connections in the connection pool.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-20 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The statements discarded from the cache for datasource %name% are %value% (per minute).

7.2.19 Datasource - Cached Statements not Used (per minute)

This metric shows the average number of statements per minute not satisfied by the statement cache in the last 5 minutes. Each connection in the connection pool has its own cache of statements.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-21 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The cache statements not used for datasource %name% are %value% (per minute).

7.2.20 Datasource - Cached Statements Used (%)

This metric shows the percentage of statements satisfied by the statement cache during the last 5 minutes. Each connection in the connection pool has its own cache of statements.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-22 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

<

Not Defined

Not Defined

-

The cached statements used rate is %value%%%.

7.2.21 Datasource - Cached Statements Used (per minute)

This metric shows the average number of statements per minute satisfied by the data source statement cache in the last 5 minutes. Each connection in the connection pool has its own cache of statements.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-23 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The cache statements used are %value% (per minute).

7.2.22 Datasource - Statement Cache Size

This metric shows the number of prepared and callable statements currently cached in the statement. Each connection in the connection pool has its own cache of statements. This number is the sum of the number of statements in the caches for all connections in the connection pool.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-24 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The cache size is %value%.

7.3 EJB Module Metrics

This section provides details on the EJB module metrics.

7.3.1 Cached Beans

This metric shows the total number of beans from this EJB Home that are currently in the EJB cache.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-25 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The number of cached beans for EJB module %ejbModuleName% is %value%.

7.3.2 Bean Activations (per minute)

This metric shows the average number of beans per minute that have been activated from the EJB home over the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-26 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The bean activations for EJB module %ejbModuleName% are %value% (per minute).

7.3.3 Cache Hits (%)

This metric shows the percentage of cache accesses that completed successfully in the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-27 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

<

Not Defined

Not Defined

-

The EJB cache hit rate for EJB module %ejbModuleName% is %value%%%.

7.3.4 Cache Misses (per minute)

This metric shows the average number of cache misses per minute for this EJB module in the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-28 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The cache misses for EJB module %ejbModuleName% are %value% (per minute).

7.3.5 Bean Accesses (per minute)

This metric shows the average EJB pool accesses per minute over the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-29 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The bean accesses for EJB module %ejbModuleName% are %value% (per minute).

7.3.6 Bean Access Successes (%)

This metric shows the percentage of EJB pool accesses that were successful in the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-30 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

<

Not Defined

Not Defined

-

The successful bean access rate for EJB module %ejbModuleName% is %value%%%.

7.3.7 Free Bean Instances

This metric shows the current number of available EJB instances in the free pool.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-31 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

<

Not Defined

Not Defined

-

The number of available beans for EJB module %ejbModuleName% is %value%.

7.3.8 Bean Destroys (per minute)

This metric shows the average number of EJB destroys per minute for this EJB module over the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-32 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The bean destroys for EJB module %ejbModuleName% are %value% (per minute).

7.3.9 Bean Access Failures (per minute)

This metric shows the average number of times per minute that a failed attempt was made to get an instance from the free pool. This value is averaged over the past five minutes. An Attempt to get a bean from the pool will fail if there are no available instances in the pool.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-33 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The bean access failures for EJB module %ejbModuleName% are %value% (per minute).

7.3.10 Beans in Use

This metric shows the number of EJB instances currently being used from the free pool.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-34 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The number of beans in use for EJB module %ejbModuleName% is %value%.

7.3.11 Bean Transaction Commits (per minute)

This metric shows the average number of EJB transaction commits per minute for this EJB Module over the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-35 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The bean transaction commits for EJB module %ejbModuleName% are %value% (per minute).

7.3.12 Bean Transaction Rollbacks (per minute)

This metric shows the average number of EJB transaction rollbacks per minute for this EJB module over the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-36 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

<

Not Defined

Not Defined

-

The bean transaction rollbacks for EJB module %ejbModuleName% are %value% (per minute).

7.3.13 Bean Destroys (per minute)

This metric shows the average number of EJB destroys per minute for this EJB module over the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-37 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

<

Not Defined

Not Defined

-

The bean destroys for EJB module %ejbModuleName% are %value% (per minute).

7.4 EJB Transaction Metrics

This section provides details on the EJB transaction metrics.

7.4.1 Bean Transaction Commits (%)

This metric shows the percentage of EJB transactions that were committed for the select EJB over the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-38 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

<

Not Defined

Not Defined

-

The bean transaction commit rate for EJB %name%, EJB module %ejbModuleName% is %value%%%.

7.4.2 Bean Transaction Commits (per minute)

This metric shows the average number of EJB transaction commits per minute for this EJB over the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-39 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The bean transaction commits for EJB %name%, EJB module %ejbModuleName% are %value% (per minute).

7.4.3 Bean Transaction Rollbacks (per minute)

This metric shows the average number of transaction rollbacks per minute for this EJB over the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-40 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The bean transaction rollbacks for EJB %name%, EJB module %ejbModuleName% are %value% (per minute).

7.4.4 Bean Transaction Timeouts (per minute)

This metrics shows the average number of transaction timeouts per minute for this EJB over the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-41 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

The bean transaction timeouts for EJB %name%, EJB module %ejbModuleName% are %value% (per minute).

7.5 Overview Metrics

This section provides details on the overview metrics.

7.5.1 Cached Beans

This metrics shows the total number of EJBs currently active in the EJB cache.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-42 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

>

Not Defined

Not Defined

-

++

Failed Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.2 Cache Accesses (per minute)

This metric shows the average number of EJB cache access attempts per minute for this application in the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-43 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.3 Bean Activations (per minute)

This metric shows the average number of Enterprise Java Beans that have been activated per minute over the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-44 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.4 Cache Hits (%)

This metrics indicates the percentage of cache accesses that completed successfully in the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-45 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.5 Cache Misses (per minute)

This metric shows the average number of EJB cache misses per minute in this application in the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-46 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.6 Bean Accesses (per minute)

This metric shows the average EJB pool accesses per minute over the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-47 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.7 Bean Successes (%)

This metric shows the percentage of EJB pool accesses that were successful for this application in the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-48 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.8 Free Bean Instances

This metric shows the current number of available EJB instances in the free pool.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-49 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.9 Bean Destroys (per minute)

This metric shows the average number of EJB destroys per minute for this application in the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-50 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.10 Bean Access Failures (per minute)

This metric shows the average number of failed pool accesses per minute for this application in the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-51 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.11 Beans in Use

This metric shows the number of EJB instances currently being used from the free pool.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-52 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.12 Bean Transaction Commits (%)

This metric shows the percentage of EJB transactions that were committed for this application during the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-53 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.13 Bean Transaction Commits (per minute)

This metric shows the average number of EJB transaction commits per minute for this application in the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-54 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.14 Bean Transaction Rollbacks (per minute)

This metric shows the average number of EJB transaction rollbacks per minute for this EJB module over the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-55 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.15 Bean Transaction Timeouts (per minute)

This metric shows the average number of EJB transaction timeouts per minute for this EJB module over the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-56 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.16 MDB Messages (per minute)

This metric shows the average number of messages processed by Message Driven Beans (MDBs) per minute for this application in the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-57 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.17 Requests (per minute)

This metrics shows the average number of servlet and/or JSP invocations per minute in this application in the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-58 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.18 Request Processing Time (ms)

This metric displays the average amount of time (in milliseconds) spent executing servlets and/or JSPs in this application in the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-59 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.19 Active Sessions

This metric shows the number of active sessions for this application.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-60 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.20 Work Manager Pending Requests

This metric shows the number of Work Manager requests waiting in the queue.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-61 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.5.21 Work Manager Requests (per minute)

This metric shows the average number of Work Manager requests processed per minute for this application over the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-62 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

<

Not Defined

Not Defined

-

Successful Logins per second %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

7.6 Servlet/JSP Metrics

This category of metrics provides information on Servlet/JSP metrics.

7.6.1 Reloads (per minute)

This metric shows the average number of reloads of the selected servlet or JSP per minute over the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-63 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 15 Minutes

After Every Sample

>

Not Defined

Not Defined

-

The reloads for servlet/jsp %name%, web module %webModuleName% are %value% (per minute).

7.6.2 Requests (per minute)

This metrics shows the average number of invocations of the selected servlet or JSP per minute over the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-64 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 15 Minutes

After Every Sample

>

Not Defined

Not Defined

-

The requests processed for servlet/jsp %name%, web module %webModuleName% are %value% (per minute).

7.6.3 Request Processing Time (ms)

This metric shows the average amount of time (in milliseconds) that was spent executing the selected servlet or JSP over the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-65 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 15 Minutes

After Every Sample

>

Not Defined

Not Defined

-

The request processing time for servlet/jsp %name%, web module %webModuleName% is %value% ms.

7.7 Web Module Metrics

This category of metrics provides information on web module metrics.

7.7.1 Requests (per minute)

This metric shows the average number of servlet and JSP invocations per minute for this Web module in the last 5 minutes.

7.7.2 Request Processing Time (ms)

This metric shows the average amount of time (in milliseconds) spent executing servlets and/or JSPs in this Web module for the last 5 minutes.

7.7.3 Active Sessions

This metric shows the number of active sessions for this web module.

7.8 Events Handler

This category of metrics provides information on events handler metrics.

7.8.1 Average Events Execution Time (ms)

The average time in milliseconds to process an event handler in the last 5 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-66 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 15 Minutes

After Every Sample

>

Not Defined

Not Defined

-

Average Events Execution Time (ms) %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

7.8.2 Completed Events Executions

The total number of completed event handler executions in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-67 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

Completed Events Executions %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

7.8.3 Maximum Events Execution Time (ms)

The maximum time in milliseconds to process an event handler in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

7.8.4 Minimum Events Execution Time (ms)

The minimum time in milliseconds to process an event handler in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

7.9 Java JEE Web Service Endpoints

This category of metrics provides information on Java JEE Web Service Endpoint metrics.

7.9.1 Dispatch Time Total

This metric shows the total amount of dispatch time since the Web service was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

7.9.2 Execution Time Total

This metrics represents the total time that the Web service port has spent executing since the Web service was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

7.9.3 Invocation Count

This metric represents the total number of invocations for the selected Web services port since the Web service was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

7.9.4 Response Count

This metric shows the total number of responses since the Web service was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

7.9.5 Response Error Count

This number provides the total number of response errors since the Web service was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

7.9.6 Response Time Total

This metric represents the total response time of this Web services port since the Web service was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

7.10 JMS Queue

This category of metrics provides information on JMS Queue metrics.

7.10.1 Average Processing Time (ms)

The average time in milliseconds to process a JMS message in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

7.10.2 Number of Processed Messages

The total number of processed JMS messages in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

7.10.3 Maximum Processing Time (ms)

The maximum time in milliseconds to process a JMS message in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

7.10.4 Minimum processing Time (ms)

The minimum time in milliseconds to process a JMS message in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

7.11 MDS Metrics

This category of metrics provides information on MDS metrics.

7.11.1 Metadata Object Gets Per Second

The number of metadata object gets per second.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

User Action

High values may occur for a heavily used or complex application. No action needs to be taken unless application performance is perceived to be too slow, in which case it might be advisable to increase the hardware resources available to the application.

7.11.2 Metadata Object Get Processing Time (seconds)

The average elapsed time in seconds to get a metadata object.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

User Action

This value should be considerably less than 1 second. If the value is greater than about 0.01, check the cache efficiency metrics (IOs Per Metadata Object Get and IOs Per MO Content Get), and increase the MDS cache size if those metrics indicate a problem. If those metrics are normal, the CPU may be overloaded, meaning the application may need more hardware resources, especially if performance is perceived to be slow.

7.11.3 IOs Per Document Get

The average number of physical IOs per persistence-level document get. This is an indication of the efficiency of the document cache portion of the metadata cache for the application. Ideally it should be much less than 1.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

User Action

If the value is close to or more than 1, this could indicate that the MDS cache for the application is too small. Try increasing the size of the MDS cache to see if it reduces the value of this statistic.

7.11.4 IOs Per MO Content Get

The average number of physical IOs per metadata object XML content retrieval. This is an indication of the efficiency of the metadata cache for the application. Ideally it should be much less than 1.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

User Action

If the value is close to or more than 1, this could indicate that the MDS cache for the application is too small. Try increasing the size of the MDS cache to see if it reduces the value of this statistic.

7.11.5 IOs Per Metadata Object Get

The average number of physical IOs per metadata object get. This is an indication of the efficiency of the metadata cache for the application. Ideally it should be much less than one.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

User Action

If the value is close to or more than 1, this could indicate that the MDS cache for the application is too small. Try increasing the size of the MDS cache to see if it reduces the value of this statistic.

7.11.6 Metadata Updates Per Second

The average number of metadata objects updated per second.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

User Action

If the value of this metric is significant compared to the number of HTTP requests serviced per second, it means many users are creating or updating customizations or personalizations using the page composer or, more likely, via inherent changes. In this case, if application performance is perceived be slow, it might be wise to reduce the number of these updates by configuring the application to use a different ADF change manager (so the changes are saved in memory only, not to disk).

7.11.7 Metadata Update Processing Time (seconds)

The average elapsed time in seconds taken to update a metadata object.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

User Action

If the value of this metric exceeds about 1 second the MDS repository database may need tuning. If the "Metadata Updates Per Second" metric is also high, steps may need to be taken to reduce the number of updates (see user action for that metric).

7.12 Executions and Messages

This category of metrics provides information on executions and messages metrics.

7.12.1 Total Adapter Executions

The total number of all adapter executions in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

7.12.2 Total Events Handler Executions

The total number of all event handler executions in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

7.12.3 Total JMS Messages

The total number of all processed JMS messages in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

7.13 SPML Web Services

This category of metrics provides information on SPML Web service metrics.

7.13.1 Average Response Time (ms)

The average time in milliseconds taken to respond to SPML requests in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

7.13.2 Incoming Calls

The total number of SPML calls made in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

7.14 Response

This category of metrics represents the status and performance of the OAAM servers in the OAAM cluster.

7.14.1 Status

This metric represents the current status of the OAAM Servers in the OAAM cluster.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 7-68 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 300 Seconds

After Every Sample

=

0

The Oracle Adaptive Access Manager cluster instance is down

8 Oracle BI Instance

An Oracle BI Instance target is comprised of all Oracle Business Intelligence system components (such as Oracle BI Server, Oracle BI Presentation Services, and Oracle BI Scheduler) in a given Oracle Business Intelligence installation. You can use Fusion Middleware Control to monitor and manage these processes.

8.1 Oracle BI PS Requests Rate

This category shows metrics related to the rate at which requests are being processed by the given Oracle BI Presentation Services component.

8.1.1 Active Sessions

The number of active Presentation Services sessions.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.1.2 Bad Requests

The total number of bad requests.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.1.3 Completed Requests

The total number of requests completed.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.1.4 Completed Requests/sec

The number of requests completed each second.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.1.5 Current Requests

The current number of requests being processed.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.1.6 Failed Requests

The total number of failed requests.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.1.7 GET Requests Throughput

The number of GET requests completed each second.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.1.8 GET Requests

The total number of GET requests completed.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.1.9 GET/POST Requests Throughput

The number of GET/POST requests completed each second.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.1.10 GET/POST Requests

The total number of GET/POST requests completed.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.1.11 Long Requests

The total number of long running requests.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.1.12 Peak Requests

The peak number of requests concurrently being processed.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.1.13 POST Requests Throughput

The number of POST requests completed each second.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.1.14 POST Requests

The total number of POST requests completed.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.1.15 SOAP Requests Throughput

The number of SOAP requests completed each second.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.1.16 SOAP Requests

The total number of SOAP requests completed.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.2 Oracle BI PS Aggregation

This category shows performance information and metrics related to requests processed across all Oracle BI Presentation Services components in the BI cluster.

8.2.1 Active sessions

The number of active sessions for all Oracle BI Presentation Services components in the BI cluster.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.2.2 Completed Requests/sec

The number of requests completed each second for all Oracle BI Presentation Services components in the BI cluster.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.2.3 Current Requests

The current number of requests being processed across all Oracle BI Presentation Services components in the BI cluster.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.2.4 Failed Requests

The total number of failed requests across all Oracle BI Presentation Services components in the BI cluster.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.2.5 GET/POST Throughput

The number of GET/POST requests completed each second for all Oracle BI Presentation Services components in the BI cluster.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.2.6 SOAP Throughput

The number of SOAP requests completed each second for all Oracle BI Presentation Services components in the BI cluster.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.3 Oracle BI Aggregation

This category shows performance information and metrics for all Oracle BI Server components in the BI cluster.

8.3.1 Avg Query Elapsed Time

The average elapsed time, in seconds, for queries that completed during the sampling interval, for all Oracle BI Servers across the BI cluster. This metric includes both successful and failed queries.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.3.2 Queries/sec

The number of queries completed each second by all Oracle BI Servers across the BI cluster during the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.3.3 Total sessions

The total number of sessions that connected clients to all Oracle BI Servers across the BI cluster during the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.4 Oracle BI Data Cache

This category shows performance information about the Oracle BI Server query cache.

8.4.1 Hit Ratio as %

The percentage of hits for the Oracle BI data cache during the sampling period.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.4.2 Hits/sec

The number of times each second that a query was satisfied from the data cache during the sampling period.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.4.3 Qualified queries misses / second

The number of times each second a qualified query was not satisfied from the data cache during the sampling period.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.4.4 Unqualified queries misses / second

The number of times each second an unqualified query occurred. An unqualified query is a query that did not qualify to hit the cache.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5 Oracle BI DB Connection Pool

This category provides information about the database connection pools used by Oracle Business Intelligence.

8.5.1 Accumulated Opened Connections

The total number of connections that were opened for this connection pool. New connections can be opened as fresh connections, when a connection times out, or when there is a problem with the connection.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.2 Accumulated Requests

The total number of requests that have been submitted to the given database connection pool.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.3 Accumulated Stolen Connections

The total number of connections that were closed and reopened with a different logon. It includes connections that were closed at the end of processing the previous request.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.4 Average Queued Requests

The average number of requests that had to wait in queue for a connection to become available, since the server was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.5 Average Queued Time (ms)

The average number of milliseconds that a request waited in queue before a connection became available, since the server was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.6 Avg. Opened Connections/sec

The average number of connections that were opened since the server was started. New connections can be opened as fresh connections, when a connection times out, or when there is a problem with the connection.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.7 Avg. Request/sec

The average number of requests per second that have been submitted to the given database connection pool since the server was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.8 Avg. Stolen Connections/sec

The average number of connections that were closed and reopened with a different logon since the server was started. It includes connections that were closed at the end of processing the previous request.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.9 Capacity

The maximum number of connections that the given database connection pool allows.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.10 Current Busy Connection Count

The current number of connections assigned to process a query in the given database connection pool.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.11 Current Connection Count

The current number of open connections in the thread pool.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.12 Current Queued Requests

The number of requests that are currently queued, waiting for a connection to become available.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.13 Current Queued Time (ms)

The number of milliseconds that the request that is next in line for processing has waited in queue.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.14 Lowest Queued Requests

The smallest number of requests that have been in queue since the server was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.15 Lowest Queued Time (ms)

The smallest number of milliseconds that a request has had to wait in queue since the server was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.16 Peak Busy Connection Count

The maximum number of connections assigned to process a query during the lifetime of the given database connection pool.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.17 Peak Connection Count

The maximum of number of open connections during the lifetime of the thread pool.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.18 Peak Queued Requests

The peak number of requests that have been in queue since the server was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.19 Peak Queued Time (ms)

The peak number of milliseconds that a request has had to wait in queue since the server was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.20 Producer ID of the Oldest Queued Request

The Producer ID of the oldest queued request in the given database connection pool. The oldest queued request will be the next request to obtain a database connection. The request may have to wait for a thread before obtaining the connection.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.5.21 Request ID of the Oldest Queued Request

The Request ID of the oldest queued request in the given database connection pool. The oldest queued request will be the next request to obtain a database connection. The request may have to wait for a thread before obtaining the connection.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6 Oracle BI General

This category shows performance information and metrics for the given Oracle BI Server.

8.6.1 Active Execute Requests

The number of execute requests active within the Oracle BI Server at the end of the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.2 Active Fetch Requests

The number of fetch requests active within the Oracle BI Server at the end of the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.3 Active File Handles

The number of open file handles that are servicing client requests or physical execution requests at the end of the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.4 Active Initblock Executions

The number of initialization block requests active within the Oracle BI Server at the end of the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.5 Active Logins

The number of active logins within the Oracle BI Server at the end of the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.6 Active Prepare Requests

The number of query prepare requests active within the Oracle BI Server at the end of the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.7 Avg. Failed Logins Elapsed Time

The average elapsed time, in seconds, for failed logins that completed during the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.8 Avg. Initblock Executions Elapsed Time

The average elapsed time, in seconds, for the execution of initialization blocks that completed during the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.9 Avg. query elapsed time

The average elapsed time, in seconds, for queries that completed during the sampling interval. This metric includes both successful and failed queries.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.10 Avg. Succeeded Logins Elapsed Time

The average elapsed time, in seconds, for successful logins that completed during the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.11 Busy File Handles

The number of file handles currently being written to or being read from.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.12 File Handle Waiters

The number of objects waiting for a file handle to become available.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.13 Free File Handles

The number of available file handles in the file handle pool.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.14 Max. Initblock Execution Elapsed Time

The maximum time, in seconds, for the execution of a single initialization block for each login request that completed during the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.15 Max File Handles

The peak number of concurrently running file handles since the server was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.16 New Execute Requests

The number of new execute requests received by the Oracle BI Server during the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.17 New Fetch Requests

The number of new fetch requests received by the Oracle BI Server during the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.18 New Initblock Executions

The total number of new initialization block requests received by the Oracle BI Server during the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.19 New Logins

The total number of new login requests received by the Oracle BI Server during the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.20 New Prepare Requests

The number of new query prepare requests received by the Oracle BI Server during the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.21 New Requests

The total number of new requests received by the Oracle BI Server during the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.22 Queries/sec

The number of queries completed per second by the Oracle BI Server during the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.23 Succeeded Initblock Execution Ratio as %

The percentage of initialization block requests that succeeded during the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.24 Succeeded Logins Ratio as %

The percentage of logins that succeeded during the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.6.25 Total sessions

The total number of sessions that connected clients to the Oracle BI Server during the sampling interval.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

8.7 Oracle BI Generic Cache

This metric category provides information about internal Oracle BI Server caches, including:

- Star_ColumnAggrInfo_Cache

- Star_DrillDownInfo_Cache

- Star_DrillDownQuery_Cache

- Star_LDAP_Cache

- Star_Plan_Cache

- Star_RowWiseInit_Cache

8.7.1 Average hits / second

The average number of hits each second for the specified cache object during the sampling interval.

8.7.2 Average misses / second

The average number of misses each second for the specified cache object during the sampling interval.

8.7.3 Average new entries / second

The average number of entries added each second to the specified cache object during the sampling interval.

8.7.4 Average replacements / second

The average number of entries deleted each second from the specified cache object during the sampling interval.

8.7.5 Average requests / second

The average number of requests each second against the specified cache object during the sampling interval.

8.7.6 Capacity

The total capacity of the specified cache object.

8.7.7 Total requests

The total number of requests during the sampling interval against the specified cache object.

8.7.8 Utilization ratio as %

The percentage of the specified cache object in use.

8.8 Oracle BI LDAP Authentication

This category shows performance information and metrics for LDAP requests. Only legacy custom LDAP server requests are included.

8.8.1 Active LDAP Requests

The number of active LDAP authentication requests received by the Oracle BI Server during the sampling interval.

8.8.2 Avg. Failed LDAP Requests Elapsed Time

The average elapsed time, in seconds, for failed LDAP authentication requests received by the Oracle BI Server during the sampling interval.

8.8.3 Avg. Succeeded LDAP Requests Elapsed Time

The average elapsed time, in seconds, for successful LDAP authentication requests received by the Oracle BI Server during the sampling interval.

8.8.4 LDAP Requests Cache Hit Ratio as %

The percentage of LDAP authentication requests that successfully hit the LDAP cache during the sampling period.

8.8.5 New Impersonated LDAP Requests

The total number of new impersonated LDAP authentication requests received by the Oracle BI Server during the sampling interval.

8.8.6 New LDAP Requests

The total number of new LDAP authentication requests received by the Oracle BI Server during the sampling interval.

8.8.7 Succeeded LDAP Requests Ratio as %

The percentage of LDAP authentication requests that succeeded during the sampling interval.

8.9 Oracle BI Physical DB

This category shows performance information and metrics for all physical databases that are being used as data sources for Oracle Business Intelligence.

8.9.1 Active Executes

The number of outstanding executes that remain at the given physical database at the end of the sampling interval.

8.9.2 Active Fetches

The number of outstanding fetches that remain at the given physical database at the end of the sampling interval.

8.9.3 Active Prepares

The number of outstanding prepares that remain at the given physical database at the end of the sampling interval.

8.9.4 Avg. query request response time

The average time, in seconds, that it takes for the given physical database to respond to a query request during the sampling interval.

8.9.5 Failed Queries/sec

The number of queries that failed each second in the given physical database during the sampling interval.

8.9.6 KiloBytes/sec

The number of kilobytes retrieved each second from the given physical database during the sampling interval. This metric includes both completed and failed queries.

8.9.7 New Executes

The number of executes sent to the given physical database during the sampling interval.

8.9.8 New Fetches

The number of fetches sent to the given physical database during the sampling interval.

8.9.9 New Prepares

The number of prepares sent to the given physical database during the sampling interval.

8.9.10 Queries/sec

The number of queries completed each second by the given physical database during the sampling interval.

8.9.11 Rows/sec

The number of rows retrieved each second from the given physical database during the sampling interval. This metric includes both completed and failed queries.

8.10 Oracle BI PS Caches

This category provides information about caches within Oracle BI Presentation Services.

8.10.1 Cache Hits

The number of requests satisfied by the cache.

8.10.2 Cache Misses

The number of requests not satisfied by the cache.

8.10.3 Cache Stale

The number of requests satisfied by the cache, but stale.

8.10.4 Cleanups

The number of cleanup passes that have finished.

8.10.5 Current Entries

The current number of entries in this cache.

8.10.6 Peak Entries

The peak number of entries in this cache.

8.11 Oracle BI PS Catalog Access

This category provides information related to Oracle BI Presentation Catalog access.

8.11.1 Attribute Retrievals

The number of item attributes retrieved.

8.11.2 Create Folders

The number of folders created.

8.11.3 Create Links

The number of links created.

8.11.4 Delete Items

The number of items deleted.

8.11.5 Read Objects

The number of objects read.

8.11.6 Searches

The number of searches performed.

8.11.7 Write Objects

The number of objects written.

8.11.8 Write Objects Successfully

The number of successful writes.

8.12 Oracle BI PS Catalog Attribute Cache

This category provides information related to the Oracle BI Presentation Catalog attribute cache. The attribute cache maintains information in memory about recently accessed items in the Oracle BI Presentation Catalog.

8.12.1 Cache Hits

The total number of requests satisfied by the attribute cache.

8.12.2 Cache Misses

The total number of requests not satisfied by the attribute cache.

8.12.3 Cache Stale Misses

The total number of requests that missed cache because the cache entry had expired.

8.12.4 Current Cache Entries

The current number of entries in the attribute cache.

8.12.5 Peak Cache Entries

The peak number of entries in the attribute cache.

8.13 Oracle BI PS Chart Engine

This category provides information related to the Oracle BI Presentation Services chart engine and cache. The chart cache maintains recently accessed charts on disk for instantaneous response.

8.13.1 Cache Hits

The total number of chart requests retrieved from the chart cache.

8.13.2 Charts Submitted/sec

The number of charts submitted for creation each second. This does not include chart requests satisfied by the chart cache.

8.13.3 Current Cached Charts

The current number of entries in the chart cache. This includes finished, queued, and running charts in the cache.

8.13.4 Current Charts Queued

The current number of charts waiting in queue for processing.

8.13.5 Current Running Charts

The number of charts that are currently being processed. This does not include charts waiting in queue for processing.

8.13.6 Peak Cached Charts

The peak number of entries in the chart cache.

8.13.7 Peak Charts Queued

The peak number of charts concurrently waiting in queue for processing.

8.13.8 Peak Running Charts

The peak number of charts being concurrently processed.

8.13.9 Total Charts Rejected

The total number of chart requests rejected because the maximum allowed queued number of charts was reached.

8.13.10 Total Charts Submitted

The total number of charts submitted for creation. This does not include chart requests satisfied by the chart cache.

8.14 Oracle BI PS Connection Pool

This category provides information related to connections established from Oracle BI Presentation Services to the Oracle BI Server.

8.14.1 Current Authentications

The current number of Oracle BI Server connections in the process of being authenticated and established.

8.14.2 Current Open Connections

The current number of open Oracle BI Server connections.

8.14.3 New Connections/sec

The number of Oracle BI Server connections established each second.

8.14.4 Peak Authentications

The peak number of Oracle BI Server connections being concurrently authenticated and established.

8.14.5 Peak Open Connections

The peak number of open Oracle BI Server connections.

8.14.6 Total Connections

The total number of Oracle BI Server connections established.

8.14.7 Total Failed

The total number of Oracle BI Server connection requests that failed to be established. This metric includes requests rejected because too many connections were in the process of being established.

8.14.8 Total Rejected

The total number of Oracle BI Server connection requests rejected because too many connections were in the process of being established.

8.15 Oracle BI PS DirectorySearches

This category provides information related to Oracle BI Presentation Services directory searches.

8.15.1 Total Search Start Requests

The total number of requests to start searching a directory.

8.15.2 Total Search Stop Requests

The total number of requests to stop searching a directory.

8.15.3 Total Searches Started

The total number of directory searches started.

8.15.4 Total Searches Stopped

The total number of directory searches stopped.

8.16 Oracle BI PS DXE

This category provides information related to the Oracle BI Presentation Data Exchange Engine (DXE).

8.16.1 Total Actual Aggregate Queries Compiled

The total number of queries compiled as Aggregate type.

8.16.2 Total Actual Cube Queries Compiled

The total number of queries compiled as Cube type.

8.16.3 Total Actual Expression Queries Compiled

The total number of queries compiled as Expression type.

8.16.4 Total Actual Presort Cube Queries Compiled

The total number of queries compiled as Presort Cube type.

8.16.5 Total Actual Presort Table Queries Compiled

The total number of queries compiled as Presort Table type.

8.16.6 Total Actual Regular Queries Compiled

The total number of queries compiled as Regular type.

8.16.7 Total Actual Union Queries Compiled

The total number of queries compiled as Union type.

8.16.8 Total Input Aggregate Query Requests

The total number of requests to process Aggregate type queries.

8.16.9 Total Input Cube Query Requests

The total number of requests to process Cube type queries.

8.16.10 Total Input Regular Query Requests

The total number of requests to process Regular type queries.

8.16.11 Total Input Union Query Requests

The total number of requests to process Union type queries.

8.16.12 Total Order By Requests

The total number of queries that requested Order By.

8.16.13 Total Order By Requests Optimized Away

The total number of queries with Order By requests that were optimized away.

8.16.14 Total Query Requests

The total number of requests to process queries.

8.17 Oracle BI PS File Accesses

This category provides information related to file access within Oracle BI Presentation Services.

8.17.1 Current Open Files

The current number of open files.

8.17.2 Peak Open File

The peak number of open files.

8.17.3 Total Files

The total number of files that have been opened.

8.17.4 Total Files/sec

The number of files that have been opened each second.

8.18 Oracle BI PS HTTP Socket Pool

This category provides information related to Oracle BI Presentation Services HTTP 1.1 socket usage.

8.18.1 Total Closed At Reuse

The total number of sockets that were reported closed by the TCP layer when an attempt was made to reuse them.

8.18.2 Total Closed Exception

The total number of sockets closed because of an exception.

8.18.3 Total Closed First Read

The total number of sockets closed at first read (in other words, after the request was sent). These closed sockets have the potential to cause repeated delivery at the HTTP server.

8.18.4 Total Closed HTTP

The total number of sockets closed because the HTTP protocol requested explicit closure.

8.18.5 Total Closed Outstanding

The total number of sockets that could not be reused because their response was not fully consumed.

8.18.6 Total Closed Timedout

The total number of sockets closed because they reached the timeout specified in the Keep-Alive response header from the HTTP server.

8.18.7 Total Closed Unknown

The total number of sockets that were closed for no known reason.

8.18.8 Total Endpoints

The total number of distinct HTTP servers that are, or have been, the target of HTTP requests.

8.18.9 Total New sockets

The total number of sockets created.

8.18.10 Total Reused

The total number of socket requests satisfied by reusing an existing socket.

8.19 Oracle BI PS JavaHost Proxy Requests

This category provides information about the JavaHost proxy requests, used for PDF, charts, and so on.

8.19.1 Requests to Generate Briefing Books

The current number of requests to generate Briefing Books.

8.19.2 Requests to Generate PDFs

The current number of requests to generate PDFs.

8.19.3 Requests to Generate Powerpoints

The current number of requests to generate a Powerpoint presentation.

8.20 Oracle BI PS Metadata

This category provides information related to metadata retrieved by Oracle BI Presentation Services from the Oracle BI Server.

8.20.1 Current Subject Areas

The current number of subject areas loaded in memory.

8.20.2 Peak Subject Areas

The peak number of subject areas loaded in memory.

8.20.3 Subject Area Loads/sec

The number of subject areas loaded each second.

8.20.4 Total Subject Area Loads

The total number of subject areas loaded.

8.21 Oracle BI PS Query Cache

This category provides information about the Oracle BI Presentation Services cache for Oracle BI Server queries.

8.21.1 Cache Clean Ups/sec

The number of query cache cleanup jobs run each second.

8.21.2 Cache Hits/sec

The number of cache hits each second.

8.21.3 Canceled Queries/sec

The number of queries each second that have been returned as canceled by the Oracle BI Server.

8.21.4 Current Cache Entries

The current number of entries in the Presentation Services query cache.

8.21.5 Current Query Preps

The number of query preparations currently being executed against the Oracle BI Server.

8.21.6 Current Query Preps Cache Size

The current number of entries in the query preparation cache.

8.21.7 Current Queued Immediate Queries

The number of immediate queries that are currently queued waiting for execution against the Oracle BI Server. Immediate queries bypass the Presentation Services query cache.

8.21.8 Current Queued Queries

The number of queries that are currently queued waiting for execution against the Oracle BI Server.

8.21.9 Current Running Immediate Queries

The number of immediate queries that are currently being executed against the Oracle BI Server. Immediate queries bypass the Presentation Services query cache.

8.21.10 Current Running Queries

The number of queries that are currently being executed against the Oracle BI Server.

8.21.11 Errored Queries/sec

The number of queries each second that have failed to execute against the Oracle BI Server.

8.21.12 New Queries/sec

The number of new queries that have been attempted each second.

8.21.13 Peak Cache Entries

The peak number of entries concurrently in the Presentation Services query cache.

8.21.14 Peak Query Preps

The peak number of concurrent query preparations being executed against the Oracle BI Server.

8.21.15 Peak Query Preps Cache Size

The peak number of entries in the query preparation cache.

8.21.16 Peak Queued Immediate Queries

The peak number of immediate queries concurrently queued waiting for execution. Immediate queries bypass the Presentation Services query cache.

8.21.17 Peak Queued Queries

The peak number of queries concurrently queued waiting for execution.

8.21.18 Peak Running Immediate Queries

The peak number of concurrently running immediate queries against the Oracle BI Server. Immediate queries bypass the Presentation Services query cache.

8.21.19 Peak Running Queries

The peak number of concurrently running queries against the Oracle BI Server.

8.21.20 Proactive Cache Clean Ups/sec

The number of times each second the query cache has been proactively cleaned up due to limited resources, or because the allowed limits of the cache were exceeded.

8.21.21 Query Piggybacks/sec

The number of queries each second that have 'piggybacked' off of an equivalent running query.

8.21.22 Query Preps Errors/sec

The number of query preparations that failed each second.

8.21.23 Query Preps/sec

The number of query preparations each second.

8.21.24 Successful Queries/sec

The number of queries each second that have been returned by the Oracle BI Server without error.

8.21.25 Total Cache Clean Ups

The number of query cache cleanup jobs that have been run.

8.21.26 Total Cache Hits

The total number of cache hits.

8.21.27 Total Canceled Queries

The total number of queries that have been returned as canceled by the Oracle BI Server.

8.21.28 Total Errored Queries

The total number of queries that have failed to execute against the Oracle BI Server.

8.21.29 Total Proactive Cache Clean Ups

The number of times the query cache has been proactively cleaned up due to limited resources, or because the allowed limits of the cache were exceeded.

8.21.30 Total Query Attempts

The total number of queries that have been attempted.

8.21.31 Total Query Piggybacks

The total number of queries that have 'piggybacked' off of an equivalent running query.

8.21.32 Total Query Prep Cache Hits

The total number of query preparations resolved by the cache.

8.21.33 Total Query Prep Cache Misses

The total number of query preparations resolved by the Oracle BI Server.

8.21.34 Total Query Preps

The total number of query preparations.

8.21.35 Total Query Preps Errors

The total number of query preparations that failed.

8.21.36 Total Successful Queries

The total number of queries that have been returned by the Oracle BI Server without error.

8.22 Oracle BI PS Request Processor

This category shows performance information related to requests processed by Oracle BI Presentation Services.

8.22.1 Bad Requests

The total number of bad requests.

8.22.2 Completed Requests

The total number of requests completed.

8.22.3 Completed Requests/sec

The number of requests completed each second.

8.22.4 Current Requests

The current number of requests being processed.

8.22.5 Failed Requests

The total number of failed requests.

8.22.6 GET Requests

The total number of GET requests completed.

8.22.7 Long Requests

The total number of long running requests.

8.22.8 Peak Requests

The peak number of requests concurrently being processed.

8.22.9 POST Requests

The total number of POST requests completed.

8.22.10 SOAP Requests

The total number of SOAP requests completed.

8.23 Oracle BI PS Sessions

This category provides information about Oracle BI Presentation Services sessions. A session can be a browser or an Intelligent Agent session.

8.23.1 Active Sessions

The number of active Presentation Services sessions.

8.23.2 Current Embryonic Sessions

The number of current embryonic sessions. An embryonic session is a session that has not yet logged in, or in other words, a session that is still at the login page.

8.23.3 Current Sessions

The number of current Presentation Services sessions.

8.23.4 Failed Logins/sec

The number of failed logins each second.

8.23.5 New Logins/sec

The number of new logins each second.

8.23.6 New Sessions/sec

The number of new sessions each second.

8.23.7 Peak Active Sessions

The peak number of concurrent active sessions.

8.23.8 Peak Embryonic Sessions

The peak number of embryonic sessions.

8.23.9 Peak Logged In

The peak number of concurrent browser sessions logged in.

8.23.10 Peak Sessions

The peak number of concurrent sessions.

8.23.11 Sessions Logged In

The current number of browser sessions that are logged in.

8.23.12 Total Failed Logins

The total number of failed logins.

8.23.13 Total Lifetime Sessions

The total number of sessions created since the Oracle BI Presentation Services server was started.

8.23.14 Total Logins

The total number of successful logins.

8.24 Oracle BI PS Sockets

This category provides information related to Oracle BI Presentation Services sockets.

8.24.1 Total Close Requests

The total number of requests to close sockets.

8.24.2 Total Closed

The total number of sockets closed.

8.24.3 Total Open Requests

The total number of requests to open sockets.

8.24.4 Total Opened

The total number of sockets opened.

8.25 Oracle BI PS Thread Pools

This category provides information about thread pools within Oracle BI Presentation Services. A thread pool is responsible for executing jobs of a specific type.

8.25.1 Current Jobs Queued

The number of jobs currently waiting in queue for processing by this thread pool.

8.25.2 Current Jobs Running

The number of jobs currently being processed by this thread pool.

8.25.3 Current Threads

The number of threads currently in this thread pool.

8.25.4 Peak Jobs Queued

The peak number of concurrent jobs waiting in queue for processing by this thread pool.

8.25.5 Peak Jobs Running

The peak number of concurrent jobs being processed by this thread pool.

8.25.6 Peak Threads

The peak number of concurrent threads in this thread pool.

8.25.7 Total Jobs Completed

The total number of jobs that were completed by this thread pool. This metric does not include jobs that ended prematurely or unexpectedly.

8.25.8 Total Jobs Submitted

The total number of jobs submitted for processing by this thread pool.

8.25.9 Total Jobs Unfinished

The total number of jobs that ended prematurely or unexpectedly during processing.

8.26 Oracle BI PS Threads

This category provides information related to Oracle BI Presentation Services threads.

8.26.1 Total Close Requests

The total number of requests to destroy a thread.

8.26.2 Total Closed

The total number of threads destroyed.

8.26.3 Total Created

The total number of threads created.

8.26.4 Total Open Requests

The total number of requests to create a thread.

8.27 Oracle BI PS User Population Searches

This category provides performance information related to all searches made using the User Population Manager.

8.27.1 UserPopulationAPI.SearchByGUID

The number of user population searches by GUID.

8.27.2 UserPopulationAPI.SearchByName

The number of user population searches by user name.

8.27.3 UserPopulationAPI.SearchByPattern

The number of user population searches by pattern.

8.28 Oracle BI PS XML Document Caches

This category provides information related to the Oracle BI Presentation Services XML document caches.

8.28.1 Current Disk Entries

The current number of cache entries stored on disk.

8.28.2 Current Disk Usage (KB)

The current disk usage of the cache in kilobytes.

8.28.3 Current Memory Entries

The current number of cache entries in memory.

8.28.4 Disk Added (KB)

The amount of disk space added in kilobytes since the server was started.

8.28.5 Disk Cache Hits

The number of cache requests satisfied from disk.

8.28.6 Disk Cache Misses

The number of cache requests that were not satisfied from disk.

8.28.7 Disk Deleted (KB)

The amount of disk space deleted in kilobytes since the server was started.

8.28.8 Invalid Requests

The total number of cache requests that were invalid. Typically, invalid cache requests contain an invalid cache key.

8.28.9 Memory Cache Hits

The number of cache requests satisfied in memory.

8.28.10 Peak Memory Entries

The peak number of cache entries concurrently in memory.

8.28.11 Total Memory Entries

The total number of cache entries in memory since the server was started.

8.29 Oracle BI PS XML Validator

This category provides information related to XML validations within Oracle BI Presentation Services.

8.29.1 Current Validations

The current number of XML validations.

8.29.2 Current Validators in Pool

The current number of XML validators.

8.29.3 Peak Validations

The peak number of concurrent XML validations.

8.29.4 Peak Validators in Pool

The peak number of XML validators.

8.29.5 Total Validations

The total number of XML instances validated.

8.29.6 Validations/sec

The number of XML instances validated each second.

8.30 Oracle BI Thread Pool

This category provides performance information about the Oracle BI Server thread pools. Note that the requests measured by these metrics are internal server requests, not user queries.

8.30.1 Accumulated Requests

The total number of requests serviced by the Oracle BI Server thread pools since the server was started.

8.30.2 Average Execution Time (ms)

The average number of milliseconds that it took for a request to be processed.

8.30.3 Average Queued Requests

The average number of requests waiting for a thread to become available.

8.30.4 Average Queued Time (ms)

The average number of milliseconds that a request waited for a thread to become available.

8.30.5 Avg. Request/sec

The average number of requests that were processed each second by the Oracle BI Server.

8.30.6 Capacity

The maximum allowed number of threads in the Oracle BI Server thread pools.

8.30.7 Current Busy Thread Count

The number of threads currently in use.

8.30.8 Current Execution Time (ms)

The number of milliseconds that it took for the most recent request to be processed.

8.30.9 Current Queued Requests

The number of requests currently waiting for a thread to become available.

8.30.10 Current Queued Time (ms)

The number of milliseconds that the request that is next in line for processing has waited in queue.

8.30.11 Current Thread Count

The total number of threads currently in the Oracle BI Server thread pools.

8.30.12 Lowest Execution Time (ms)

The smallest number of milliseconds that it has taken to process a request since the server was started.

8.30.13 Lowest Queued Requests

The smallest number of requests that have been in queue since the server was started.

8.30.14 Lowest Queued Time (ms)

The smallest number of milliseconds that a request has had to wait in queue.

8.30.15 Maximum Stack Size (bytes)

The peak stack size used by the set of active threads, in bytes.

8.30.16 Peak Busy Thread Count

The peak number of concurrently active threads.

8.30.17 Peak Execution Time (ms)

The peak number of milliseconds that it took for a request to be processed.

8.30.18 Peak Queued Requests

The peak number of requests that have been in queue since the server was started.

8.30.19 Peak Queued Time (ms)

The peak number of milliseconds that a request has had to wait in queue.

8.30.20 Peak Thread Count

The peak number of threads in the Oracle BI Server thread pools.

8.31 Weblogic BI Metrics By Server

This category shows performance information for each Web application deployed on a given Oracle WebLogic Server. You can display the metrics in this category to compare with other values.

8.31.1 Weblogic BI Action Framework Metrics

This category shows average performance information for Action Framework requests across the Oracle WebLogic Server cluster.

8.31.2 Requests (per minute)

The average number of servlet and/or JSP invocations per minute for Action Framework requests across the Oracle WebLogic Server cluster, in the last 5 minutes.

8.31.3 Request Processing Time (ms)

The average time (in milliseconds) it took for the cluster to process an Action Framework request during the last interval. The interval is the period of time specified as the collection frequency for this metric.

8.32 Weblogic BI Analytics Metrics

This category shows total/average performance information for all managed servers across the Oracle WebLogic Server cluster.

8.32.1 Requests (per minute)

The average number of servlet and/or JSP invocations per minute for the BI Analytics Web application across the Oracle WebLogic Server cluster, in the last 5 minutes.

8.32.2 Request Processing Time (ms)

The average time (in milliseconds) it took for the cluster to process a BI Analytics request during the last interval. The interval is the period of time specified as the collection frequency for this metric.

8.32.3 Active Sessions

The total number of active sessions for the BI Analytics Web application across the Oracle WebLogic Server cluster.

8.33 Weblogic BI SOA Metrics

This category shows average performance information for Web services requests across the Oracle WebLogic Server cluster.

8.33.1 Requests (per minute)

The average number of servlet and/or JSP invocations per minute for Web services requests across the Oracle WebLogic Server cluster, in the last 5 minutes.

8.33.2 Request Processing Time (ms)

The average time (in milliseconds) it took for the cluster to process a Web services request during the last interval. The interval is the period of time specified as the collection frequency for this metric.

8.34 Weblogic Server Metrics

This category shows performance information for the given Oracle WebLogic Server. You can display the metrics in this category to compare with other values.

8.34.1 CPU Usage Percentage

The percentage of the CPU that is being used by the Oracle WebLogic Server. As traffic increases, CPU utilization increases.

8.34.2 Heap Used (MB)

The amount of heap space (total program memory) used, in megabytes, by the Oracle WebLogic Server.

8.34.3 Requests (per minute)

The average number of servlet and/or JSP invocations per minute for the Oracle WebLogic Server in the last 5 minutes.

8.34.4 Request Processing Time (ms)

The average time (in milliseconds) it took for the Oracle WebLogic Server to process a request during the last interval. The interval is the period of time specified as the collection frequency for this metric.

8.34.5 Active Sessions

The number of active sessions for the Oracle WebLogic Server.

9 Glassfish Metrics

This chapter describes the Glassfish metrics.

9.1 EJB Cache Metrics by Server

This metric category provides information on EJB cache metrics by server.

9.1.1 Cache Hits (per minute)

This metric shows how many times per minute user requests on this server found a bean in the EJB cache.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The number of EJB cache hits is %value% (per minute).

9.1.2 Cache Misses (per minute)

This metric shows how many times per minute user requests on this server didn't find a bean in the EJB cache.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The number of EJB cache misses is %value% (per minute).

9.1.3 Cache Access Attempts (per minute)

This metric shows how many times per minute user requests on this server have attempted to access the EJB Cache.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The number of EJB cache access attempts is %value% (per minute).

9.1.4 Cache Hits (%)

This metric shows the percentage of user requests on this server that found a bean in the EJB cache.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The EJB cache hit rate is %value%%%.

9.2 EJB Pool Metrics By Server

This metric category provides information on the EJB Pool Metrics by Server.

9.2.1 Beans in Pool

This metric shows the number of EJBs deployed to this server that are currently in the associated pool, providing information about how the pool is changing.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The number of beans in pool is %value%."

9.2.2 Threads Waiting

This metric shows the number of threads waiting for free beans, giving an indication of possible congestion of requests.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The number of threads waiting for free beans is %value%.

9.3 JMS Connection Pool Metrics by Server

This metric category provides information on JMS connection pool metrics by server.

9.3.1 Connections in Use

This metric shows the number of JMS connections currently in use on this server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The number of JMS connections in use is %value%.

9.3.2 Connections Pending

This metric shows the number of JMS connection requests in the queues on this server that are waiting to be serviced.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The number of JMS connections pending is %value%."

9.3.3 Connections Acquired (per minute)

This metric shows how many times per minute a logical connection was acquired from a JMS connection pool on this server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The number of JMS connections acquired is %value% (per minute)."

9.4 JTA Metrics

This metric category provides information on JTA metrics.

9.4.1 Active JTA Transactions

This metric shows the number of transactions currently active on this server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The number of active JTA transactions is %value%.

9.4.2 Committed JTA Transactions (per minute)

This metric shows the number of transactions per minute that have been committed on this server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The committed transactions are %value% (per minute).

9.4.3 JTA Transaction Rollbacks (per minute)

This metric shows the number of transactions per minute that have been rolled back on this server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The transaction rollbacks are %value% (per minute).

9.5 JVM Metrics

This metric category provides information on JVM metrics.

9.5.1 Heap Usage (MB)

This metric shows the heap memory in megabytes used by the Java Virtual machine.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The heap usage is %value% MB."

9.5.2 Java Vendor

This metric shows the name of the Java Virtual Machine vendor.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

9.5.3 Java Version

This metric shows the version of the Java Virtual Machine.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

9.5.4 CPU Usage (%)

This metric shows the percentage of CPU time used by the Java Virtual machine.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The CPU usage is %value%%%.

9.5.5 Heap Usage (%)

This metric shows the percentage of heap memory used by the Java Virtual machine.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The heap usage is %value%%%."

9.6 JVM Class Loading

This metric category provides information about the JVM class loading metric.

9.6.1 JVM Class Loading - Classes Currently Loaded

This metric tracks and raises an alert when the number of classes currently loaded exceeds the defined thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The number of classes currently loaded is %value%.

9.7 JVM Compilation Metrics

This metric category provides information about JVM compilation metrics.

9.7.1 JVM Compilation - Compilation Time (since startup) (ms)

For the selected Java Virtual Machine (JVM), this metric shows the total time spent by the JVM in compilation. The value of the metric is in milliseconds and shows the time spent in compilation since the JVM was last started.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

9.8 JVM Garbage Collectors Metrics

This metric category provides information about JVM garbage collectors metrics.

9.8.1 Garbage Collector - Invocations (per min)

This metric is the number of times the garbage collector was invoked per minute during the last metric collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The invocations for garbage collector %Name% are %value% (per minute).

9.8.2 Garbage Collector - Invocation Time (ms)

This metric shows the average time ( in millisecs) spent per invocation of the garbage collector during the last metric collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The invocation time for garbage collector %Name% is %value% ms.

9.8.3 Garbage Collector - Old Heap Percent Free after GC (%)

This metric tracks and raises an alert when the percentage of the old heap free space after garbage collection is less than the percentage defined in the thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

Percent of old heap free after GC for garbage collector %Name% is %value%%%.

9.8.4 Garbage Collector - Old Heap size after GC (MB)

This metric tracks the size (in MB) of the old heap free space after garbage collection.

Target Version

Collection Frequency

All versions

Every 15 Minutes

9.8.5 Garbage Collector - Percent Time spent (%)

This metric tracks and raises an alert when the percentage of time that the garbage collector spends in garbage collection exceeds the percentage defined in the thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The percentage of time garbage collector %Name% has spent in Garbage Collection is %value% (%).

9.9 JVM Memory Pools Metrics

This metric category provides information about JVM memory pools metrics.

9.9.1 Name

This metric shows the name of the JVM memory pool.

Target Version

Collection Frequency

All versions

Every 15 Minutes

9.9.2 Type

This metric shows the type of the JVM memory pool.

Target Version

Collection Frequency

All versions

Every 15 Minutes

9.9.3 Memory Pool - Current Usage (MB)

This metric shows the current memory usage (in megabytes) of the selected Java Virtual Machine (JVM).

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The memory usage for pool %Name% is %value% MB.

9.10 JVM Memory Usage Metrics

This metric category provides information about the JVM memory usage metrics.

9.10.1 JVM Memory - Heap Memory Usage (MB)

This metric shows the total heap memory (in megabytes) currently in use by the selected Java Virtual Machine (JVM).

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The heap memory usage is %value% MB.

9.10.2 JVM Memory - Non-Heap Memory Usage (MB)

This metric shows the total non-heap memory (in megabytes) currently in use by the selected Java Virtual Machine (JVM).

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The heap memory usage is %value% MB.

9.10.3 JVM Memory - Objects Pending Finalization

This metric shows the number of objects pending finalization in the selected Java Virtual Machine (JVM).

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The number of objects pending finalization is %value%.

9.11 JVM Runtime Metrics

This metric category provides information about the JVM runtime metrics.

9.11.1 VM Name

This metric shows the name of the selected Java Virtual Machine (JVM).

Target Version

Collection Frequency

10gR3, 11g, 12c

Every 15 Minutes

9.11.2 VM Version

This metric shows the version number of the selected Java Virtual Machine (JVM).

Target Version

Collection Frequency

10gR3, 11g, 12c

Every 15 Minutes

9.12 JVM Threads

This metric category provides information about JVM threads metrics.

9.12.1 JVM Threads - Active Daemon Threads

This metric shows the current number of active daemon threads in the selected Java Virtual Machine (JVM).

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The number of objects pending finalization is %value%.

9.12.2 JVM Threads - Deadlocked Threads

This metric shows the current number of deadlocked threads in the selected Java Virtual Machine (JVM).

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The number of objects pending finalization is %value%.

9.12.3 JVM Threads - Peak Threads

This metric shows the maximum (peak) number of threads started in this Java Virtual Machine (JVM) since the JVM was started.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The number of objects pending finalization is %value%.

9.12.4 JVM Threads - Active Threads

This metric shows the current number of active threads in the selected Java Virtual Machine (JVM).

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The number of objects pending finalization is %value%.

9.13 Module Metrics by Server

This metric category provides information on module metrics by server.

9.13.1 Active Sessions

This metric shows the number of sessions currently active on the server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The number of active sessions is %value%."

9.14 Response

This metric category provides information on the Response metrics.

9.14.1 Status

This metric shows the status of the server as an integer. A value of "1" is up, and a value of "0" is down.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every Minute

Not Defined

0

MESSAGE="The GlassFish Server is down"
CLEAR_MESSAGE="The GlassFish Server is up"

9.15 Server Metrics

This metric category provides information on server metrics.

9.15.1 State

This metric shows the current state of the server as an integer. Possible values are as follows:

- public static final int STARTING_STATE = 0;

- public static final int RUNNING_STATE = 1;

- public static final int STOPPING_STATE = 2;

- public static final int STOPPED_STATE = 3;

- public static final int FAILED_STATE = 4;

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The server state is %value%.

9.15.2 Start Time

This metric shows the time when the server was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

9.16 Server Datasource Metrics

This metric category provides information on server datasource metrics.

9.16.1 Connections in Use

This metric shows the number of datasource connections currently in use by applications running on this server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The number of connections in use is %value%.

9.16.2 Connections Created (per minute)

This metric shows the number of physical datasource connections created per minute by the pools on this server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The connections created are %value% (per minute).

9.16.3 Connections Acquired (per minute)

This metric shows the number of logical datasource connections acquired per minute from the pools on this server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The connections acquired are %value% (per minute).

9.17 Server Servlet Metrics

This metric category provides information on server servlet metrics.

9.17.1 Request Processing Time (ms)

This metric shows the average amount of time in milliseconds it took to process a servlet request on this server, since the last collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The request processing time is %value% ms

9.17.2 Requests (per minute)

This metric shows the number of servlet requests processed per minute on this server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Not Defined

Not Defined

The requests processed is %value% (per minute).

10 Oracle Essbase Server Metrics

This chapter describes the Oracle Essbase server metrics.

10.1 Server Information

This category of metrics shows the number of current users and applications on the Essbase server.

10.1.1 Connected Users

This metric shows the number of users connected to the Essbase server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

10.1.2 Running Apps

This metric shows the number of Essbase applications running on the Essbase server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

10.1.3 Unaccessed Apps

This metric shows the number of available Essbase applications that are not running on the Essbase server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

10.1.4 Response (ms)

This metric shows the time required, in milliseconds, for the Essbase server to respond to requests.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

10.2 Resource Usage

This category of metrics shows the resource usage of the Essbase server.

10.2.1 CPU Usage (%)

This metric shows the percentage of CPU being used by the Essbase server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

10.2.2 Memory Usage (MB)

This metric shows the amount of physical memory, in megabytes, being used by the Essbase server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

10.2.3 Memory Usage (%)

This metric shows the percentage of physical memory being used by the Essbase server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

10.3 Response

This category of metrics shows the status and performance of the Essbase server.

10.3.1 Response - Status

This metric shows whether the Essbase server is responding to requests.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

11 Oracle Essbase Applications

These metrics show the performance of Oracle Essbase applications.

11.1 Application Information

This category of metrics shows the resource usage of applications running on the Oracle Essbase server.

11.1.1 Response (ms)

This metric shows the time required, in milliseconds, for the Oracle Essbase application to respond to requests.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

11.1.2 Memory Usage (MB)

This metric shows the amount of physical memory, in megabytes, being used by the Oracle Essbase application.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

11.1.3 Threads

This metric shows the number of independent processes currently in use within the Oracle Essbase application.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

11.2 Response

This category of metrics shows the status and performance of Oracle Essbase applications.

11.2.1 Response - Status

This metric shows whether the Oracle Essbase application is responding.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

12 Oracle Coherence Cache

All Oracle Coherence entities are monitored from a central MBean (JMX) server or central Management Node. All metrics source are Coherence MBeans and Java platform MBeans. Sample Coherence MBean reference available from the "Coherence MBean Reference" appendix in the Oracle Coherence Management Guide:

http://docs.oracle.com/cd/E24290_01/coh.371/e22842/appendix_mbean.htm

General Metric Naming Conventions:

- Total {Metric Name} - Absolute Total value as returned by MBean server. Typically this is since node start or since statistics were last reset. For example, Cache Usage > Total Gets metric for a Oracle Coherence Node target is the total number of gets on a cache since node start or statistics reset.

- Total {Metric Name} Per Minute - Rate computed on Absolute Total value as discussed in "Per Minute metric computation"

- Aggregate {Metric Name} - Aggregated value across multiple entities. For example Cache Usage > Aggregate Gets for a Oracle Coherence Cache target is the aggregate number of gets for a cache across all nodes that supports this cache

- Aggregate {Metric Name} Per Minute - Rate computed on Aggregate value as discussed in "Per Minute metric computation"

- Metric names without Total/Aggregate - These are either STRING metrics or instantaneous values as returned by MBean server. They may be aggregated across entities where applicable.

12.1 Response

This metric category shows the time required, in milliseconds, for the server to respond to requests.

12.1.1 Cache Status

This metric displays the coherence cache status.

Target Version

Collection Frequency

All Versions

Every 60 Seconds

12.2 Aggregate Storage Manager Metrics

This metric category provides information about the Aggregate Storage Manager metrics.

12.2.1 Aggregate Events Dispatched

This metric displays the total number of events dispatched by the Storage Manager.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate events dispatched by Storage Manager is %value%

12.2.2 Aggregate Events Dispatched Per Minute

This metric displays the number of events dispatched per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate events dispatched per minute by Storage Manager is %value%.

12.2.3 Aggregate Evictions

This metric displays the number of evictions from the backing map managed by this Storage Manager.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate evictions by Storage Manager is %value%.

12.2.4 Aggregate Evictions Per Minute

This metric displays the number of evictions from the backing map per minute

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate evictions per minute by Storage Manager is %value%.

12.2.5 Aggregate Inserts

This metric displays the number of inserts into the backing map managed by this Storage Manager.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate inserts into backing map is %value%.

12.2.6 Aggregate Inserts Per Minute

This metric displays the number of inserts into backing map per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate inserts per minute into backing map is %value%.

12.2.7 Aggregate Listener Filters

This metric displays the number of filter-based listeners currently registered with the Storage Manager.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate listener filters registered by Storage Manager is %value%.

12.2.8 Aggregate Listener Keys

This metric displays the number of key-based listeners currently registered with the Storage Manager.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate listener keys registered with Storage Manager is %value%.

12.2.9 Aggregate Locks Granted

This metric displays the number of locks currently granted for the portion of the partitioned cache managed by the Storage Manager.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate locks granted by Storage Manager is %value%

12.2.10 Aggregate Locks Pending

This metric displays the number of pending lock requests for the portion of the partitioned cache managed by the Storage Manager.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate locks pending in Storage Manager is %value%.

12.2.11 Aggregate Removes

This metric displays the number of removes from the backing map caused by operations such as clear, remove or invoke.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate removes from backing map is %value%.

12.2.12 Aggregate Removes Per Minute

This metric displays the number of removes from backing map per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate removes per minute from backing map is %value%.

12.3 Aggregate Cache Usage Metrics (Coherence version 3.4)

This metric category provides information about the Aggregate Cache Usage metrics.

12.3.1 Aggregate Puts

This metric displays the aggregate number of puts.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Puts in cache is %value%.

12.3.2 Aggregate Puts Per Minute

This metric displays the number of puts per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Puts per minute in cache is %value%.

12.3.3 Aggregate Puts Time (ms) Per Minute

This metric displays the total number of ms spent on put() operations per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Puts Time (ms) per minute is %value%.

12.3.4 Aggregate Gets

This metric displays the aggregate number of gets.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Gets in cache is %value%.

12.3.5 Aggregate Gets Per Minute

This metric displays the number of gets per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Gets per minute in cache is %value%.

12.3.6 Aggregate Gets Time (ms) Per Minute

This metric displays the total number of ms spent on get() operations per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Gets Time (ms) per minute is %value%

12.3.7 Aggregate Hits

This metric displays the rough number of cache hits. A cache hit is a read operation invocation for which an entry exists in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Hits is %value%

12.3.8 Aggregate Hits Per Minute

This metric displays the rough number of cache hits per minute. A cache hit is a read operation invocation for which an entry exists in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Hits per minute is %value%

12.3.9 Aggregate Hits Time (ms) Per Minute

This metric displays the total number of ms per minute for the get() operations for which an entry existed in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Hits Time (ms) per minute is %value%

12.3.10 Aggregate Misses

This metric displays the rough number of cache misses. A cache miss is a read operation for which no entry exists in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Misses is %value%.

12.3.11 Aggregate Misses Per Minute

This metric displays the rough number of cache misses per minute. A cache miss is a read operation for which no entry exists in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Misses per minute is %value%.

12.3.12 Aggregate Misses Time (ms) Per Minute

This metric displays the total number of ms per minute for the get() operations for which no entry existed in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Misses Time (ms) per minute is %value%

12.3.13 Aggregate Writes

This metric displays the total number of storage writes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Writes is %value%

12.3.14 Aggregate Writes Per Minute

This metric displays the total number of storage writes per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Writes per minute is %value%.

12.3.15 Aggregate Write Time (ms) Per Minute

This metric displays the cumulative time spent on storage writes per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Write Time (ms) per minute is %value%.

12.3.16 Aggregate Reads

This metric displays the total number of reads.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Reads is %value%.

12.3.17 Aggregate Reads Per Minute

This metric displays the total number of reads per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Reads per minute is %value%.

12.3.18 Aggregate Read Time (ms) Per Minute

This metric displays the cumulative time spent on reads per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Read Time (ms) per minute is %value%.

12.3.19 Aggregate Failures Per Minute

This metric displays the total number of storage failures per minute (load, store and erase operations).

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Failures per minute is %value%.

12.3.20 Aggregate Queue Size

This metric displays the size of the write-behind queue.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Queue Size is %value%.

12.3.21 Hit Probability

This metric displays the rough probability that the next invocation is a hit.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Cache Hit Probability is %value%.

12.3.22 Hits to Gets Ratio (%)

This metric displays the percentage ratio of cache hits to get() operation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Cache Hits to Gets Ratio is %value%.

12.3.23 Average Time Per Get (ms)

This metric displays the average number of ms per get() invocation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per cache Get (ms) is %value%.

12.3.24 Average Time Per Get-Hit (ms)

This metric displays the average number of ms per get() invocation that is a hit.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per cache Get-Hit (ms) is %value%

12.3.25 Average Time Per Get-Miss (ms)

This metric displays the average number of ms per get() invocation that is a miss.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per cache Get-Miss (ms) is %value%.

12.3.26 Average Time Per Put (ms)

This metric displays the average number of ms per put() invocation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per cache Put (ms) is %value%.

12.3.27 Average Time Per Read (ms)

This metric displays the average time (in ms) spent per read operation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per cache Read (ms) is %value%.

12.3.28 Average Time Per Write (ms)

This metric displays the average time (in ms) spent per write operation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per cache Write (ms) is %value%.

12.4 Aggregate Cache Usage Metrics (Coherence version 3.4.2 - 3.7.1)

This metric category provides information about the aggregate cache usage metrics for Coherence versions 3.4.2 - 3.7.1.

12.4.1 Aggregate Puts

This metric displays the aggregate number of puts.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Puts in cache is %value%.

12.4.2 Aggregate Puts Per Minute

This metric displays the number of puts per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Puts per minute in cache is %value%.

12.4.3 Aggregate Puts Time (ms) Per Minute

This metric displays the total number of ms spent on put() operations per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Puts Time (ms) per minute is %value%.

12.4.4 Aggregate Gets

This metric displays the aggregate number of gets.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Gets in cache is %value%.

12.4.5 Aggregate Gets Per Minute

This metric displays the number of gets per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Gets per minute in cache is %value%.

12.4.6 Aggregate Gets Time (ms) Per Minute

This metric displays the total number of ms spent on get() operations per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Gets Time (ms) per minute is %value%

12.4.7 Aggregate Hits

This metric displays the rough number of cache hits. A cache hit is a read operation invocation for which an entry exists in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Hits is %value%

12.4.8 Aggregate Hits Per Minute

This metric displays the rough number of cache hits per minute. A cache hit is a read operation invocation for which an entry exists in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Hits per minute is %value%

12.4.9 Aggregate Hits Time (ms) Per Minute

This metric displays the total number of ms per minute for the get() operations for which an entry existed in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Hits Time (ms) per minute is %value%

12.4.10 Aggregate Misses

This metric displays the rough number of cache misses. A cache miss is a read operation for which no entry exists in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Misses is %value%.

12.4.11 Aggregate Misses Per Minute

This metric displays the rough number of cache misses per minute. A cache miss is a read operation for which no entry exists in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Misses Time (ms) per minute is %value%

12.4.12 Aggregate Misses Time (ms) Per Minute

This metric displays the total number of ms per minute for the get() operations for which no entry existed in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Misses Time (ms) per minute is %value%

12.4.13 Aggregate Writes

This metric displays the total number of storage writes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Writes is %value%

12.4.14 Aggregate Writes Per Minute

This metric displays the total number of storage writes per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Writes per minute is %value%.

12.4.15 Aggregate Write Time (ms) Per Minute

This metric displays the cumulative time spent on storage writes per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Write Time (ms) per minute is %value%.

12.4.16 Aggregate Reads

This metric displays the total number of reads.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Reads is %value%.

12.4.17 Aggregate Reads Per Minute

This metric displays the total number of reads per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Reads per minute is %value%.

12.4.18 Aggregate Read Time (ms) Per Minute

This metric displays the cumulative time spent on reads per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Read Time (ms) per minute is %value%.

12.4.19 Aggregate Failures Per Minute

This metric displays the total number of storage failures per minute (load, store, and erase operations).

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Failures per minute is %value%.

12.4.20 Aggregate Queue Size

This metric displays the size of the write-behind queue.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Queue Size is %value%.

12.4.21 Aggregate Prunes

This metric displays the total number of prunes. A prune operation occurs every time the cache reaches its high watermark.

12.4.22 Aggregate Prunes Per Minute

This metric displays the number of prune operations per minute. A prune operation occurs every time the cache reaches its high watermark.

12.4.23 Aggregate Prune Time (ms) Per Minute

This metric displays the total number of ms for the prune operations per minute.

12.4.24 Hit Probability

This metric displays the rough probability that the next invocation is a hit.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Cache Hit Probability is %value%.

12.4.25 Hits to Gets Ratio (%)

This metric displays the percentage ratio of cache hits to get() operation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Cache Hits to Gets Ratio is %value%.

12.4.26 Average Time Per Get (ms)

This metric displays the average number of ms per get() invocation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per cache Get (ms) is %value%.

12.4.27 Average Time Per Get-Hit (ms)

This metric displays the average number of ms per get() invocation that is a hit.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per cache Get-Hit (ms) is %value%

12.4.28 Average Time Per Get-Miss (ms)

This metric displays the average number of ms per get() invocation that is a miss.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per cache Get-Miss (ms) is %value%.

12.4.29 Average Time Per Put (ms)

This metric displays the average number of ms per put() invocation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per cache Put (ms) is %value%.

12.4.30 Average Time Per Read (ms)

This metric displays the average time (in ms) spent per read operation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per cache Read (ms) is %value%.

12.4.31 Average Time Per Write (ms)

This metric displays the average time (in ms) spent per write operation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per cache Write (ms) is %value%.

12.5 Aggregate Cache Size Metrics

This metric category provides information about the Aggregate Cache Size metrics.

12.5.1 Aggregate Units

This metric displays the size of the cache measured in units.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate cache Units is %value%.

12.5.2 Unit Factor

This metric displays the factor by which the Units, LowUnits, and HighUnits properties are adjusted.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

12.5.3 Aggregate Cache Objects

This metric displays the number of objects in the cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Cache Objects is %value%

12.5.4 Aggregate Memory Usage in Bytes (assuming BINARY Calculator)

This metric displays the number of bytes consumed by the objects in the cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Memory Usage is %value% bytes.

12.5.5 Aggregate Memory Usage in MB (assuming BINARY Calculator)

This metric displays the MB consumed by the objects in the cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Memory Usage is %value% MB

12.5.6 Average Object Size in Bytes

This metric displays the average memory consumed by each object in bytes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Object Size is %value% bytes.

12.6 Aggregate Query Optimization Metrics (Coherence version 3.7)

This metric category provides information about the Aggregate Query Optimization metrics.

12.6.1 Maximum Query Duration (ms)

This metric displays the number of milliseconds of the longest running query.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Maximum Query Duration (ms) is %value%.

12.6.2 Aggregate Non Optimized Queries Executed Per Minute

This metric displays the total number of parallel queries that could not be resolved per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Non Optimized Queries Executed Per Minute is %value%.

12.6.3 Average Non Optimized Query Execution Time (ms)

This metric displays the average duration, in milliseconds, for non-optimized query execution.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Non Optimized Query Execution Time (ms) is %value%.

12.6.4 Aggregate Non Optimized Query Time (ms) Per Minute

This metric displays the total execution time, in milliseconds for queries that could not be resolved per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Non Optimized Query Time (ms) Per Minute is %value%.

12.6.5 Aggregate Optimized Queries Executed Per Minute

This metric displays the total number of parallel queries that were fully resolved using indexes per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Optimized Queries Executed Per Minute is %value%.

12.6.6 Average Optimized Query Execution Time (ms)

This metric displays the average duration, in milliseconds, for optimized query execution.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Optimized Query Execution Time (ms) is %value%.

12.6.7 Aggregate Optimized Query Time (ms) Per Minute

This metric displays the total execution time, in milliseconds for queries that were fully resolved using indexes per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Optimized Query Time (ms) Per Minute is %value%.

12.7 Aggregate Query Optimization Metrics (Coherence version 3.7.1)

This metric category provides information about the Aggregate Query Optimization metrics.

12.7.1 Maximum Query Duration (ms)

This metric displays the number of milliseconds of the longest running query.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Maximum Query Duration (ms) is %value%.

12.7.2 Aggregate Non Optimized Queries Executed Per Minute

This metric displays the total number of parallel queries that could not be resolved per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Non Optimized Queries Executed Per Minute is %value%.

12.7.3 Average Non Optimized Query Execution Time (ms)

This metric displays the average duration, in milliseconds, for non-optimized query execution.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Non Optimized Query Execution Time (ms) is %value%.

12.7.4 Aggregate Non Optimized Query Time (ms) Per Minute

This metric displays the total execution time, in milliseconds for queries that could not be resolved per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Non Optimized Query Time (ms) Per Minute is %value%.

12.7.5 Aggregate Optimized Queries Executed Per Minute

This metric displays the total number of parallel queries that were fully resolved using indexes per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Optimized Queries Executed Per Minute is %value%.

12.7.6 Average Optimized Query Execution Time (ms)

This metric displays the average duration, in milliseconds, for optimized query execution.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Optimized Query Execution Time (ms) is %value%.

12.7.7 Aggregate Optimized Query Time (ms) Per Minute

This metric displays the total execution time, in milliseconds for queries that were fully resolved using indexes per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Optimized Query Time (ms) Per Minute is %value%.

12.7.8 Aggregate Query Contentions Per Minute

This metric displays the aggregate number of times a query had to be reevaluated per minute due to concurrent updates.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Query Contentions Per Minute is %value%

13 Oracle Coherence Cluster

All Oracle Coherence entities are monitored from a central MBean (JMX) server or central Management Node. All metrics source are Coherence MBeans and Java platform MBeans. Sample Coherence MBean reference available from the "Coherence MBean Reference" appendix in the Oracle Coherence Management Guide:

http://docs.oracle.com/cd/E24290_01/coh.371/e22842/appendix_mbean.htm

General Metric Naming Conventions:

- Total {Metric Name} - Absolute Total value as returned by MBean server. Typically this is since node start or since statistics were last reset. For example, Cache Usage > Total Gets metric for a Oracle Coherence Node target is the total number of gets on a cache since node start or statistics reset.

- Total {Metric Name} Per Minute - Rate computed on Absolute Total value as discussed in "Per Minute metric computation"

- Aggregate {Metric Name} - Aggregated value across multiple entities. For example Cache Usage > Aggregate Gets for a Oracle Coherence Cache target is the aggregate number of gets for a cache across all nodes that supports this cache

- Aggregate {Metric Name} Per Minute - Rate computed on Aggregate value as discussed in "Per Minute metric computation"

- Metric names without Total/Aggregate - These are either STRING metrics or instantaneous values as returned by MBean server. They may be aggregated across entities where applicable.

13.1 Response

This metric category shows the time required, in milliseconds, for the server to respond to requests.

13.1.1 Cluster Status

This metric displays the current status of coherence cluster.

Target Version

Collection Frequency

All Versions

Every 60 Seconds

13.2 Nodes Replenish and Entity Discovery Alert Metric

This metric category provides information about the Nodes Replenish and Entity Discovery Alert metrics.

13.2.1 Cluster Size Change (For Node Process Replenish)

This metric displays the change in cluster size used to automatically replenish nodes.

Target Version

Collection Frequency

All Versions

Every 60 Seconds

13.2.2 Cluster Size Change (For Node Entity Addition)

This metric displays the change in cluster size used to automatically discover new nodes in Enterprise Manager.

Target Version

Collection Frequency

All Versions

Every 60 Seconds

13.3 Departed Coherence Cluster Members

This metric category provides information about the Departed Coherence Cluster Members metrics.

13.3.1 Recently Departed Members

This metric displays the cluster node member information for recently departed nodes.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

13.4 Aggregate Node Metrics

This metric category provides information about the Aggregate Node metrics.

13.4.1 Number of Nodes

This metric displays the total number of cluster member nodes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Cluster size is %value%

13.4.2 Number of Nodes Departed

This metric displays the number of recently departed Coherence cluster node members.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

%value% nodes departed Coherence cluster

13.4.3 Average Publisher Success Rate (%)

This metric displays the ratio of the number of packets successfully delivered to the total number of sent packets.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Publisher success rate is %value%

13.4.4 Average Receiver Success Rate (%)

This metric displays the ratio of the number of packets successfully acknowledged to the total number of received packets.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Receiver success rate is %value%

13.4.5 Aggregate Memory Consumed (MB)

This metric displays the aggregate memory (MB) used by coherence cluster.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Current aggregate memory consumption is %value% MB

13.4.6 Aggregate Memory Available (MB)

This metric displays the aggregate memory available (MB).

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Current aggregate memory available is %value% MB

13.4.7 Aggregate Send Success Rate Per Minute (%)

This metric displays the send success rate % computed per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Send Success Rate is %value% per minute

13.4.8 Aggregate Receive Success Rate Per Minute (%)

This metric displays the receive success rate % computed per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Aggregate Receive Success Rate is %value% per minute

13.5 Aggregate Cache Metrics

This metric category provides information about the Aggregate Cache metrics.

Note:
By default, collection for this metric category is disabled.

13.5.1 Number of Caches

This metric displays the total number of caches.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

13.5.2 Aggregate Number of Cache Objects

This metric displays the total number of objects in all cache nodes in a cluster.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate cache objects in cluster is %value%

13.6 Aggregate Service Storage Enabled Nodes Alert Metric

This metric category provides information about the Aggregate Service Storage Enabled Nodes Alert metrics.

13.6.1 Coherence Service Name

This metric displays the name of the coherence service.

Target Version

Collection Frequency

All Versions

Every 60 Seconds

13.6.2 Storage Enabled Nodes

This metric displays the total number of storage enabled cluster node members running this service.

Target Version

Collection Frequency

All Versions

Every 60 Seconds

13.6.3 Storage Enabled Nodes Size Change (To Replenish Storage Nodes)

This metric displays the change in Storage Enabled Nodes Size alert metric used to replenish storage nodes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 60 Seconds

After Every 5th Collection

-1

-5

%value% storage nodes departed Coherence cluster

13.7 Aggregate Service Requests and Tasks

This metric category provides information about the Aggregate Service Requests and Tasks metrics.

13.7.1 Service Name

This metric displays the name of the Coherence service.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

13.7.2 Aggregate Requests Per Minute

This metric displays the total number of synchronous requests issued by the service per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Requests per minute is %value%

13.7.3 Aggregate Pending Requests

This metric displays the aggregate number of pending synchronous requests issued by the service.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Pending Requests is %value%

13.7.4 Maximum Pending Request Time (ms)

This metric displays the duration (in ms) of the oldest pending synchronous request issued by the service.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Maximum Pending Request Time (ms) is %value%

13.7.5 Aggregate Timed-Out Requests Per Minute

This metric displays the number of timed-out requests per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Timed-out Requests per minute is %value%

13.7.6 Aggregate Tasks Executed Per Minute

This metric displays the number of executed tasks per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Tasks Executed per minute is %value%

13.7.7 Aggregate Tasks Backlog

This metric displays the aggregate size of backlog queue that holds tasks scheduled to be executed.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Tasks Backlog is %value%

13.7.8 Aggregate Timed-Out Tasks Per Minute

This metric displays the aggregate number of timed-out tasks per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Timed-out Tasks per minute is %value%

13.7.9 Aggregate Hung Tasks

This metric displays the aggregate number of currently executing hung tasks.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Hung Tasks is %value%

13.7.10 Average Request Duration (ms)

This metric displays the average duration (in ms) of a synchronous request issued by the service.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Average Request Duration (ms) is %value%

13.7.11 Maximum Request Duration (ms)

This metric displays the maximum duration (in ms) of a synchronous request issues by the service.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Maximum Request Duration (ms) is %value%

13.7.12 Average Task Duration (ms)

This metric displays the average duration (in ms) of an individual task execution.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Average Task Duration (ms) is %value%

13.7.13 Maximum Hung Task Duration (ms)

This metric displays the longest currently executing hung task duration in ms.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Maximum Hung Task Duration (ms) is %value%

13.7.14 Maximum Task Backlog

This metric displays the maximum size of the backlog queue.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Maximum Task Backlog is %value%

13.7.15 Number of Nodes

This metric displays the total number of cluster node members running this service.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

13.7.16 Storage Enabled Nodes

This metric displays the total number of storage enabled cluster node members running this service.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

13.8 Aggregate Service Partitions and Threads

This metric category provides information about the Aggregate Service Partitions and Threads metrics.

13.8.1 Coherence Service Name

This metric displays the name of the Coherence service.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

13.8.2 Aggregate Partitions Endangered

This metric displays the total number of partitions that are not currently backed up across all nodes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Default Management Agent upload frequency

Not Defined

Not Defined

Aggregate Partitions Endangered is %value%

13.8.3 Aggregate Partitions Unbalanced

This metric displays the total number of primary and backup partitions which remain to be transferred.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Default Management Agent upload frequency

Not Defined

Not Defined

Aggregate Partitions Unbalanced is %value%

13.8.4 Aggregate Partitions Vulnerable

This metric displays the total number of partitions that are backed up on the same computer where the primary partition owner resides.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Default Management Agent upload frequency

Not Defined

Not Defined

Aggregate Partitions Vulnerable is %value%

13.8.5 Aggregate Abandoned Threads

This metric displays the aggregate number of abandoned threads from the service thread pool.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Default Management Agent upload frequency

Not Defined

Not Defined

Aggregate Abandoned Threads is %value%

13.8.6 Average Active Threads

This metric displays the average number of active threads in the service thread pool.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Default Management Agent upload frequency

Not Defined

Not Defined

Average Active Threads is %value%

13.8.7 Aggregate Idle Threads

This metric displays the aggregate number of currently idle threads in the service thread pool.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Default Management Agent upload frequency

Not Defined

Not Defined

Aggregate Idle Threads is %value%

13.8.8 Aggregate Threads

This metric displays the aggregated number of threads in the service thread pool.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

Default Management Agent upload frequency

Not Defined

Not Defined

Aggregate Threads is %value%

13.9 Aggregate Transaction Manager Metrics

This metric category provides information about the Aggregate Transaction Manager metrics.

13.9.1 Service Name

This metric displays the name of the Coherence service.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

13.9.2 Aggregate Commit Time (ms) Per Minute

This metric displays the cumulative time (in ms) spent during commit phase computed per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Commit Time (ms) per minute is %value%

13.9.3 Aggregate Timeout Time (ms) Per Minute

This metric displays the transaction time out value in ms computed per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Timeout Time (ms) per minute is %value%

13.9.4 Aggregate Active Transactions Per Minute

This metric displays the aggregate number of currently active transactions per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Active Transactions per minute is %value%

13.9.5 Aggregate Transactions Committed Per Minute

This metric displays the aggregate number of transactions that have been committed by the Transaction Manager per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Transactions Committed per minute is %value%

13.9.6 Aggregate Transactions Recovered Per Minute

This metric displays the aggregate number of transactions that have been recovered by the Transaction Manager per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Transactions Recovered per minute is %value%

13.9.7 Aggregate Transactions Rolled Back Per Minute

This metric displays the aggregate number of transactions that have been rolled back by the Transaction Manager per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Transactions Rolled back per minute is %value%

13.9.8 Aggregate Transaction Duration (ms) Per Minute

This metric displays the cumulative time (in ms) spent on active transaction computed per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Transaction Duration (ms) per minute is %value%

13.10 Aggregate HTTP Session (Web) Metrics (Coherence version 3.4.2 – 3.5)

This metric category provides information about the Aggregate HTTP Session (Web) metrics.

13.10.1 Web Application ID

This metric displays the HTTP Session (Aggregate) - Web Application ID.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

13.10.2 Aggregate Attributes in Local Session

This metric displays the total number of non-distributed session attributes stored in the local session attribute cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Attributes in Local Session cache is %value%

13.10.3 Aggregate Sessions in Local Session Cache

This metric displays the total number of non-distributed sessions stored in the local session cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Sessions in Local Session cache is %value%

13.10.4 Aggregate Session Cache Updates Per Minute

This metric displays the total updates of session object stored in the session storage clustered cache per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Session cache Updates per minute is %value%

13.10.5 Aggregate Overflow Cache Updates Per Minute

This metric displays the total updates to session attributes stored in the "overflow" clustered cache per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Overflow cache Updates per minute is %value%

13.11 Aggregate HTTP Session (Web) Metrics (Coherence version 3.6 – 3.7.1)

This metric category provides information about the Aggregate HTTP Session (Web) metrics (Coherence version 3.6 - 3.7.1).

13.11.1 Web Application ID

This metric displays the HTTP Session (Aggregate) - Web Application ID.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

13.11.2 Aggregate Attributes in Local Session cache

This metric displays the total number of non-distributed session attributes stored in the local session attribute cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Attributes in Local Session cache is %value%

13.11.3 Aggregate Sessions in Local Session Cache

This metric displays the total number of non-distributed sessions stored in the local session cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Sessions in Local Session cache is %value%

13.11.4 Aggregate Session Cache Updates Per Minute

This metric displays the total updates of session object stored in the session storage clustered cache per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Session cache Updates per minute is %value%

13.11.5 Aggregate Overflow Cache Updates Per Minute

This metric displays the total updates to session attributes stored in the "overflow" clustered cache per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Overflow cache Updates per minute is %value%

13.11.6 Average Reap Duration (ms)

This metric displays the average reap duration.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Average Reap Duration (ms) is %value%

13.11.7 Average Reaped Sessions

This metric displays the average number of reaped sessions in a reap cycle.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Average Reaped Sessions is %value%

13.12 Aggregate Weblogic HTTP Session (Web) Metrics

This metric category provides information about the Aggregate Weblogic HTTP Session (Web) metrics.

13.12.1 Web Application ID

This metric displays the HTTP Session (Aggregate) - Web Application ID.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

13.12.2 Aggregate Attributes in Local Session cache

This metric displays the total number of non-distributed session attributes stored in the local session attribute cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Attributes in Local Session cache is %value%

13.12.3 Aggregate Sessions in Local Session Cache

This metric displays the total number of non-distributed session attributes stored in the local session attribute cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Sessions in Local Session cache is %value%

13.12.4 Aggregate Session Cache Updates Per Minute

This metric displays the total updates of session object stored in the session storage clustered cache per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Session cache Updates per minute is %value%

13.12.5 Aggregate Overflow Cache Updates Per Minute

This metric displays the total updates to session attributes stored in the "overflow" clustered cache per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Aggregate Overflow cache Updates per minute is %value%

13.12.6 Average Reap Duration (ms)

This metric displays the average reap duration.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Average Reap Duration (ms) is %value%

13.12.7 Average Reaped Sessions

This metric displays the average number of reaped sessions in a reap cycle.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Average Reaped Sessions is %value%

13.13 Cache Entities Discovery Alert Metric

This metric category describes the Cache Entities Discovery Alert metric.

Note:
By default, collection for this metric category is disabled.

13.13.1 Change in Number of Caches

This metric displays the change in the number of caches used to automatically discover new caches in Enterprise Manager.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

N/A

Not Defined

Not Defined

%value% new caches added to Cluster

14 Oracle Coherence Node

All Oracle Coherence entities are monitored from a central MBean (JMX) server or central Management Node. All metrics source are Coherence MBeans and Java platform MBeans. Sample Coherence MBean reference available from the "Coherence MBean Reference" appendix in the Oracle Coherence Management Guide:

http://docs.oracle.com/cd/E24290_01/coh.371/e22842/appendix_mbean.htm

General Metric Naming Conventions:

- Total {Metric Name} - Absolute Total value as returned by MBean server. Typically this is since node start or since statistics were last reset. For example, Cache Usage > Total Gets metric for a Oracle Coherence Node target is the total number of gets on a cache since node start or statistics reset.

- Total {Metric Name} Per Minute - Rate computed on Absolute Total value as discussed in "Per Minute metric computation"

- Aggregate {Metric Name} - Aggregated value across multiple entities. For example Cache Usage > Aggregate Gets for a Oracle Coherence Cache target is the aggregate number of gets for a cache across all nodes that supports this cache

- Aggregate {Metric Name} Per Minute - Rate computed on Aggregate value as discussed in "Per Minute metric computation"

- Metric names without Total/Aggregate - These are either STRING metrics or instantaneous values as returned by MBean server. They may be aggregated across entities where applicable.

14.1 Response

This metric category shows the time required, in milliseconds, for the server to respond to requests.

14.1.1 Node Status

This metric displays the coherence node status

Target Version

Collection Frequency

All Versions

Every 1 Minute

14.2 Storage Manager

This metric category provides information about the Store Manager metrics.

14.2.1 Total Events Dispatched

This metric displays the total number of events dispatched by the Storage Manager.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Events Dispatched is %value%

14.2.2 Total Events Dispatched Per Minute

This metric displays the number of events dispatched per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Events Dispatched per minute is %value%

14.2.3 Total Evictions

This metric displays the number of evictions from the backing map managed by this Storage Manager.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Evictions is %value%

14.2.4 Total Inserts

This metric displays the number of inserts into the backing map managed by this Storage Manager.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Inserts is %value%

14.2.5 Total Inserts Per Minute

This metric displays the number of inserts per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Inserts per minute is %value%

14.2.6 Listener Filters

This metric displays the number of filter-based listeners currently registered with the Storage Manager.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Listener Filters is %value%

14.2.7 Listener Keys

This metric displays the number of key-based listeners currently registered with the Storage Manager.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Listener Keys is %value%

14.2.8 Total Listener Registrations

This metric displays the total number of listener registration requests processed by the Storage Manager.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Listener Registrations is %value%

14.2.9 Locks Granted

This metric displays the number of locks currently granted for the portion of the partitioned cache managed by the Storage Manager.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Locks Granted is %value%

14.2.10 Total Removes

This metric displays the number of removes from the backing map caused by operations such as clear, remove, or invoke.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Removes is %value%

14.2.11 Total Removes Per Minute

This metric displays the number of removes per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Removes per minute is %value%

14.3 Cache Usage (Coherence version 3.4)

This metric category provides information about the cache usage for Coherence version 3.4.

14.3.1 Total Puts

This metric displays thetotal number of puts.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Puts is %value%

14.3.2 Total Puts Per Minute

This metric displays the number of puts per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Puts per minute is %value%

14.3.3 Total Puts Time (ms) Per Minute

This metric displays the total number of ms spent on put() operations per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Puts Time (ms) per minute is %value%

14.3.4 Total Gets

This metric displays the total number of gets.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Gets is %value%

14.3.5 Total Gets Per Minute

This metric displays the number of gets per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Gets per minute is %value%

14.3.6 Total Gets Time (ms) Per Minute

This metric displays the total number of ms spent on get() operations per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Gets Time (ms) per minute is %value%

14.3.7 Total Hits

This metric displays the rough number of cache hits. A cache hit is a read operation invocation for which an entry exists in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Hits is %value%

14.3.8 Total Hits Per Minute

This metric displays the rough number of cache hits per minute. A cache hit is a read operation invocation for which an entry exists in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Hits per minute is %value%

14.3.9 Total Hits Time (ms) Per Minute

This metric displays the total number of ms per minute for the get() operations for which an entry existed in this map

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Hits Time (ms) is %value%

14.3.10 Total Misses

This metric displays the rough number of cache misses. A cache miss is a read operation for which no entry exists in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Misses is %value%

14.3.11 Total Misses Per Minute

This metric displays the rough number of cache misses per minute. A cache miss is a read operation for which no entry exists in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Misses per minute is %value%

14.3.12 Total Misses Time (ms) Per Minute

This metric displays the total number of ms per minute for the get() operations for which no entry existed in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Misses Time (ms) is %value%

14.3.13 Total Writes

This metric displays the total number of storage writes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Writes is %value%

14.3.14 Total Writes Per Minute

This metric displays the total number of storage writes per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Writes per minute is %value%

14.3.15 Total Writes Time (ms) Per Minute

This metric displays the cumulative time spent on storage writes per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Writes Time (ms) is %value%

14.3.16 Total Reads

This metric displays the total number of reads.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Reads is %value%

14.3.17 Total Reads Per Minute

This metric displays the total number of reads per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Reads per minute is %value%

14.3.18 Total Reads Time (ms) Per Minute

This metric displays the cumulative time spent on reads per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Reads Time (ms) per minute is %value%

14.3.19 Total Failures Per Minute

This metric displays the total number of storage failures per minute (load, store and erase operations).

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Failures per minute is %value%

14.3.20 Queue Size

This metric displays the size of the write-behind queue.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Queue Size is %value%

14.3.21 Hit Probability

This metric displays the rough probability that the next invocation is a hit.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Hit Probability is %value%

14.3.22 Hits to Gets Ratio (%)

This metric displays the percentage ratio of cache hits to get() operation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Hits to Gets Ratio is %value%

14.3.23 Average Time Per Get (ms)

This metric displays the average number of ms per get() invocation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per Get (ms) is %value%

14.3.24 Average Time Per Get-Hit (ms)

This metric displays the average number of ms per get() invocation that is a hit.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per Get-Hit (ms) is %value%

14.3.25 Average Time Per Get-Miss (ms)

This metric displays the average number of ms per get() invocation that is a miss.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per Get-Miss (ms) is %value%

14.3.26 Average Time Per Put (ms)

This metric displays the average number of ms per put() invocation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per Put (ms) is %value%

14.3.27 Average Time Per Read (ms)

This metric displays the average time (in ms) spent per read operation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per Read (ms) is %value%

14.3.28 Average Time Per Write (ms)

This metric displays the average time (in ms) spent per write operation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per Write (ms) is %value%

14.4 Cache Usage (Coherence version 3.4.2 - 3.7.1)

This metric category provides information about the cache usage metrics for Coherence version 3.4.2 - 3.7.1.

14.4.1 Total Puts

This metric displays the total number of puts.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Puts is %value%

14.4.2 Total Puts Per Minute

This metric displays the number of puts per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Puts per minute is %value%

14.4.3 Total Puts Time (ms) Per Minute

This metric displays the total number of ms spent on put() operations per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Puts Time (ms) per minute is %value%

14.4.4 Total Gets

This metric displays the total number of gets.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Gets is %value%

14.4.5 Total Gets Per Minute

This metric displays the number of gets per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Gets per minute is %value%

14.4.6 Total Gets Time (ms) Per Minute

This metric displays the total number of ms spent on get() operations per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Gets Time (ms) per minute is %value%

14.4.7 Total Hits

This metric displays the rough number of cache hits. A cache hit is a read operation invocation for which an entry exists in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Hits is %value%

14.4.8 Total Hits Per Minute

This metric displays the rough number of cache hits per minute. A cache hit is a read operation invocation for which an entry exists in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Hits per minute is %value%

14.4.9 Total Hits Time (ms) Per Minute

This metric displays the total number of ms per minute for the get() operations for which an entry existed in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Hits Time (ms) is %value%

14.4.10 Total Misses

This metric displays the rough number of cache misses. A cache miss is a read operation for which no entry exists in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Misses is %value%

14.4.11 Total Misses Per Minute

This metric displays the rough number of cache misses per minute. A cache miss is a read operation for which no entry exists in this map.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Misses per minute is %value%

14.4.12 Total Misses Time (ms) Per Minute

This metric displays the total number of ms per minute for the get() operations for which no entry existed in this map

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Misses Time (ms) is %value%

14.4.13 Total Writes

This metric displays the total number of storage writes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Writes is %value%

14.4.14 Total Writes Per Minute

This metric displays the total number of storage writes per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Writes per minute is %value%

14.4.15 Total Writes Time (ms) Per Minute

This metric displays the cumulative time spent on storage writes per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Writes Time (ms) is %value%

14.4.16 Total Reads

This metric displays the total number of reads.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Reads is %value%

14.4.17 Total Reads Per Minute

This metric displays the total number of reads per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Reads per minute is %value%

14.4.18 Total Reads Time (ms) Per Minute

This metric displays the cumulative time spent on reads per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Reads Time (ms) per minute is %value%

14.4.19 Total Failures Per Minute

This metric displays the total number of storage failures per minute (load, store and erase operations).

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Failures per minute is %value%

14.4.20 Queue Size

This metric displays the size of the write-behind queue.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Queue Size is %value%

14.4.21 Total Prunes

This metric displays the total number of prunes. A prune operation occurs every time the cache reaches its high watermark.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Prunes is %value%

14.4.22 Total Prunes Per Minute

This metric displays the number of prune operations per minute. A prune operation occurs every time the cache reaches its high watermark.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Prunes per minute is %value%

14.4.23 Total Prune Time (ms) Per Minute

This metric displays the total number of ms for the prune operations per minute

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Prunes Time (ms) per minute is %value%

14.4.24 Hit Probability

This metric displays the rough probability that the next invocation is a hit Hits to Gets Ratio (%).

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Hit Probability is %value%

14.4.25 Hits to Gets Ratio (%)

This metric displays the percentage ratio of cache hits to get() operation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Hits to Gets Ratio is %value%

14.4.26 Average Time Per Get (ms)

This metric displays the average number of ms per get() invocation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per Get (ms) is %value%

14.4.27 Average Time Per Get-Hit (ms)

This metric displays the average number of ms per get() invocation that is a hit.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per Get-Hit (ms) is %value%

14.4.28 Average Time Per Get-Miss (ms)

This metric displays the average number of ms per get() invocation that is a miss.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per Get-Miss (ms) is %value%

14.4.29 Average Time Per Put (ms)

This metric displays the average number of ms per put() invocation Average Time Per Read (ms).

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per Put (ms) is %value%

14.4.30 Average Time Per Read (ms)

This metric displays the average time (in ms) spent per read operation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per Read (ms) is %value%

14.4.31 Average Time Per Write (ms)

This metric displays the average time (in ms) spent per write operation.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Time per Write (ms) is %value%

14.5 Cache Size

This metric category provides information about the Coherence node cache size.

14.5.1 Cache Name

This metric displays the name of the Coherence cache.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

14.5.2 Service Name

This metric displays the name of the Coherence service cache tier.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

14.5.3 Cache Tier

This metric displays the two tier Coherence cache consisting of front and back tiers.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

14.5.4 Cache Loader

This metric displays the Coherence cache loader.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

14.5.5 Units

This metric displays the size of the cache measured in units.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

14.5.6 Unit Factor

This metric displays the factor by which the Units, LowUnits and HighUnits properties are adjusted.

Target Version

Collection Frequency

All Versions

Every 5 minutes

14.5.7 Cache Objects

This metric displays the number of objects in the cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Cache Objects is %value%

14.6 Query Optimization (Coherence version 3.7)

This metric category provides information about the query optimization for Coherence version 3.7.

14.6.1 Cache Name

This metric displays the name of the Coherence cache.

Target Version

Collection Frequency

All Versions

Every 5 minutes

14.6.2 Service Name

This metric displays the name of the Coherence service.

Target Version

Collection Frequency

All Versions

Every 5 minutes

14.6.3 Max Query Description

This metric displays a description of the query with the longest duration.

Target Version

Collection Frequency

All Versions

Every 5 minutes

14.6.4 Max Query Duration (ms)

This metric displays the number of milliseconds of the longest running query.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Non Optimized Query Execution Time is %value% (ms)

14.6.5 Total Non Optimized Queries Executed Per Minute

This metric displays the total number of parallel queries that could not be resolved per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Non Optimized Queries are %value% per minute

14.6.6 Average Non Optimized Query Execution Time (ms)

This metric displays the average duration, in milliseconds, for non-optimized query execution.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Non Optimized Query Execution Time is %value% (ms)

14.6.7 Total Non Optimized Query Time (ms) Per Minute

This metric displays the total execution time, in milliseconds for queries that could not be resolved per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Non Optimized Query Execution Time is %value% (ms) per minute

14.6.8 Total Optimized Queries Executed Per Minute

This metric displays the total number of parallel queries that were fully resolved using indexes per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Optimized Queries are %value% per minute

14.6.9 Average Optimized Query Execution Time (ms)

This metric displays the average duration, in milliseconds, for optimized query execution.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Optimized Query Execution Time is %value% (ms)

14.6.10 Total Optimized Query Time (ms) Per Minute

This metric displays the total execution time, in milliseconds for queries that were fully resolved using indexes per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Optimized Query Execution Time is %value% (ms) per minute

14.7 Service Requests and Tasks

This metric category provides information about the service requests and tasks associated with Oracle Coherence Node.

14.7.1 Service Name

This metric displays the service name.

Target Version

Collection Frequency

All Versions

Every 5 minutes

14.7.2 Service Name Backups For Cache Storage

This metric displays the number of backups for every cache storage.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Backups for Cache Storage is %value%

14.7.3 Total Requests Per Minute

This metric displays the number of requests per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Service Requests per minute is %value%

14.7.4 Pending Requests

This metric displays the number of pending requests.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Pending Requests is %value%

14.7.5 Pending Duration (ms)

This metric displays the duration of pending requests in ms.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Pending Duration (ms) is %value%

14.7.6 Total Timed-Out Requests Per Minute

This metric displays the number of request timeouts per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Timed-out Requests per minute is %value%

14.7.7 Total Tasks Executed Per Minute

This metric displays the number of tasks executed per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Tasks Executed per minute is %value%

14.7.8 Total Tasks Backlog

This metric displays the size of backlog queue.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Tasks Backlog is %value%

14.7.9 Total Tasks Timed-Out Per Minute

This metric displays the number of timed-out tasks per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Tasks Timed-out per minute is %value%

14.7.10 Total Hung Tasks Per Minute

This metric displays the number of hung tasks.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Hung Tasks per minute is %value%

14.7.11 Average Request Duration (ms)

This metric displays the average duration (in ms) of a synchronous request issued by the service.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Service Request Duration (ms) is %value%

14.7.12 Maximum Request Duration (ms)

This metric displays the maximum duration (in ms) of a synchronous request issues by the service.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Maximum Request Duration (ms) is %value%

14.7.13 Storage Enabled Nodes

This metric displays the total number of cluster node members running this service.

Target Version

Collection Frequency

All Versions

Every 5 minutes

14.7.14 Average Task Duration (ms)

This metric displays the average duration (in ms) of an individual task execution.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Task Duration (ms) is %value%

14.7.15 Maximum Hung Task Duration (ms)

This metric displays the longest currently executing hung task duration in ms.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Maximum Hung Task Duration (ms) is %value%

14.7.16 HA Numeric Status

This metric displays the service status represented as number:

- 1 - MACHINE-SAFE

- 2 - NODE-SAFE

- 3 - ENDANGERED

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

High Availability Status Numeric value is %value%

14.7.17 Maximum Task Backlog

This metric displays the maximum size of the backlog queue.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Maximum Task Backlog is %value%

14.7.18 Running

This metric specifies whether the service is running.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Optimized Query Execution Time is %value% (ms) per minute

14.7.19 HA Status

This metric displays the High Availability (HA) status for this service.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

ENDANGERED

High Availability Status is %value%

14.7.20 HA Numeric Status

This metric displays the Service Status represented as number:

1 - MACHINE-SAFE, 2 - NODE-SAFE, and 3 - ENDANGERED.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

High Availability Status Numeric value is %value%

14.8 Service Partitions and Threads

This metric category provides information about the Oracle Coherence Node service partition and threads metrics.

14.8.1 Service Name

This metric displays the service name.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.8.2 Owned Partitions Backup

This metric displays the number of partitions that this node member backs up.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Owned Partitions Backup is %value%

14.8.3 Owned Partitions Primary

This metric displays the number of partitions that this node member owns.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Owned Partitions Primary is %value%

14.8.4 Partitions Endangered

This metric displays the total number of partitions that are not currently backed up.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Partitions Endangered is %value%

14.8.5 Partitions Unbalanced

This metric displays the total number of primary and backup partitions which remain to be transferred.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Partitions Unbalanced is %value%

14.8.6 Partitions Vulnerable

This metric displays the total number of partitions that are backed up on the same computer where the primary partition owner resides.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Partitions Vulnerable is %value%

14.8.7 Average Active Threads

This metric displays the average number of active threads in the service thread pool.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Average Active Threads is %value%

14.8.8 Idle Threads

This metric displays the number of currently idle threads in the service thread pool.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Idle Threads is %value%

14.8.9 Threads

This metric displays the number of threads in the service thread pool.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Threads count is %value%

14.8.10 Threads Abandoned Per Minute

This metric displays the number of threads abandoned per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Threads Abandoned per minute is %value%

14.9 Heap Memory Usage

This metric category provides information about the Oracle Coherence Node heap memory usage metrics.

14.9.1 Heap Memory Initialized (bytes)

This metric displays the number of heap bytes initialized.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Memory Pool Heap Memory Initialized (bytes) is %value%

14.9.2 Heap Memory Max (bytes)

This metric displays the maximum number of bytes used since start of the JVM.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.9.3 Heap Memory Used (bytes)

This metric displays the bytes used by the JVM.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Memory Pool Heap Memory Used (bytes) is %value%

14.10 Garbage Collector

This metric category provides information about the Oracle Coherence Node garbage collector metrics.

14.10.1 Name

This metric displays the Garbage Collector name.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.10.2 Total Garbage Collections

This metric displays the total items garbage collected.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Garbage Collections is %value%

14.10.3 Total Garbage Collections Per Minute

This metric displays the items of garbage collected per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Garbage Collections per minute is %value%

14.10.4 Total Garbage Collection Time (ms)

This metric displays the time taken to garbage collect items.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Garbage Collection Time (ms) is %value%

14.10.5 Total Collection Time (ms) Per Minute

This metric displays the garbage collection time per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Collection Time (ms) per minute is %value%

14.10.6 Garbage Collector Start Time (ms)

This metric displays the start time for a garbage collection.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.10.7 Garbage Collector End Time (ms)

This metric displays the end time for a garbage collection.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.11 Garbage Collector Before GC

This metric category provides information about the Garbage Collector Before GC metrics.

14.11.1 Name

This metric displays the garbage collector name.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.11.2 Memory Usage Key Before GC

This metric displays the garbage collector key of memory usage before garbage collection.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.11.3 Memory Usage Key Before GC (bytes)

This metric displays the amount of memory currently used (bytes).

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Memory Used Before GC (bytes) is %value%

14.12 Garbage Collector After GC

This metric category provides information about the Garbage Collector After GC metrics.

14.12.1 Name

This metric displays the garbage collector name.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.12.2 Memory Usage Key After GC

This metric displays the garbage collector key of memory usage after garbage collection.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.12.3 Memory Used After GC (bytes)

This metric displays the amount of memory currently used (bytes).

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Memory Used After GC (bytes) is %value%

14.13 Memory Pool

This metric category provides information about the Memory Pool metrics.

14.13.1 Memory Pool Name

This metric displays the memory pool name.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.13.2 Memory Pool Heap Memory Initialized (bytes)

This metric displays the number of heap bytes initialized.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Heap Memory Initialized (bytes) is %value%

14.13.3 Memory Pool Heap Memory Max (bytes)

This metric displays the maximum number of bytes used since the start of the JVM.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.13.4 Memory Pool Heap Memory Used (bytes)

This metric displays the bytes used by the JVM.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Heap Memory Used (bytes) is %value%

14.14 Node Process and Operating System

This metric category provides information about the Node Process and Operating Storm metrics.

Note:
By default, collection for this metric category is disabled.

14.14.1 Free Physical Memory Size (MB)

This metric displays the amount of free RAM available to the Operating System.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

<

Not Defined

Not Defined

Free Physical Memory Size (MB) is %value%

14.14.2 Free Swap Space Size (MB)

This metric displays the amount of free swap space available to the Operating System.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

>

Not Defined

Not Defined

Free Swap Space Size (MB) is %value%

14.14.3 Open File Descriptors

This metric displays the number of open file descriptors.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Open File Descriptors is %value%

14.14.4 Total Process CPU Time (ms)

This metric displays the total amount of CPU time that the JVM has consumed since it was started.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Process CPU Time (ms) is %value%

14.15 Node Process CPU Usage

This metric category provides information about the node process CPU usage.

14.15.1 CPU Usage (%)

This metric provides the percentage of CPU usage in the last interval.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

The CPU Usage is %value%%%

14.16 Network Health Details

This metric category provides information about the metrics associated with Network Health Details.

14.16.1 Publisher Success Rate (%)

This metric displays the publisher success rate is a ratio of the number of packets successfully delivered to the total number of sent packets.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Publisher Success Rate is %value%

14.16.2 Receiver Success Rate (%)

This metric displays the receiver success rate is a ratio of the number of packets successfully acknowledged to the total number of received packets.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Receiver Success Rate is %value%

14.16.3 Total Packets Sent

This metric displays the total number of packets sent since last statistics reset.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Packets Sent is %value%

14.16.4 Total Packets Sent Per Minute

This metric displays the number of packets sent per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Packets Sent per minute is %value%

14.16.5 Total Packets Resent

This metric displays the total number of packets resent since last statistics reset.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Packets Resent is %value%

14.16.6 Total Packets Resent Per Minute

This metric displays the number of packets resent per minute. A packet is resent if there is no ACK received within a timeout period.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Packets Resent per minute is %value%

14.16.7 Send Success Rate Per Minute (%)

This metric displays the send success rate % computed per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Send Success Rate per minute is %value%

14.16.8 Total Packets Repeated

This metric displays the total number of duplicate packets received since last statistics reset.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Packets Repeated is %value%

14.16.9 Total Packets Repeated Per Minute

This metric displays the number of duplicate packets received per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Packets Repeated per minute is %value%

14.16.10 Total Packets Received

This metric displays the total number of packets received per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Packets Received is %value%

14.16.11 Total Packets Received Per Minute

This metric displays the number of packets received per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Packets Received per minute is %value%

14.16.12 Receive Success Rate Per Minute (%)

This metric displays the percentage of receive success rate computed per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Receive Success Rate per minute is %value%

14.17 Node Performance Details

This metric category provides information about the metrics associated with the Node Performance Details.

14.17.1 Packet Delivery Efficiency

This metric displays the efficiency of packet loss detection and retransmission.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Packet Delivery Efficiency is %value%

14.17.2 Total Packets Bundled Per Minute

This metric displays the total number of packets which were bundled before transmission per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Packets Bundled per minute is %value%

14.17.3 Total Packets Resent Per Minute

This metric displays the number of packets resent too early per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Packets Resent per minute is %value%

14.17.4 Total Packets Resent Excess Per Minute

This metric displays the total number of packet retransmissions which were later proven unnecessary.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Packets Resent Excess per minute is %value%

14.17.5 Send Queue Size

This metric displays the number of packets currently scheduled for delivery.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Send Queue Size is %value%

14.17.6 Total TCP Ring Failures Per Minute

This metric displays the number of recovered TcpRing disconnects per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total TCP Ring Failures per minute is %value%

14.17.7 Weakest Channel

This metric displays the ID of the cluster member to which this member is having the most difficulty communicating.

Target Version

Collection Frequency

All Versions

Every 5 minutes

14.17.8 Node Memory Available (MB)

This metric displays the total amount of memory in the JVM available for new objects in MB.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Node Memory Available (MB) is %value%

14.17.9 Node Memory Used (MB)

This metric displays the amount of JVM memory in MB consumed by new objects.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Node Memory Used (MB) is %value%

14.18 Aggregate Node Performance for All Caches

This metric category provides information about the Aggregate Node Performance for All Caches metrics.

14.18.1 Aggregate Gets

This metric displays the total number of get() operations on this node for all caches.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Node Aggregate Gets is %value%

14.18.2 Aggregate Puts

This metric displays the total number of put() operations on this node for all caches.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Node Aggregate Puts is %value%

14.18.3 Aggregate Puts Per Minute

This metric displays the total Put() operations on this node for all caches per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Node aggregate Puts per minute is %value%

14.18.4 Aggregate Gets Per Minute

This metric displays the total get() operations on this node for all caches per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Node aggregate Gets per minute is %value%

14.19 Flash Journal

This metric category provides information about the Flash Journal metrics.

14.19.1 Journal Files

This metric displays the number of journal files that are currently in use.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Journal Files in use are %value%

14.19.2 Journal Binary Stores

This metric displays the number of active JournalBinaryStore objects that are using this journal.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Binary Store is %value%

14.19.3 Total Data Size (bytes)

This metric displays the amount of data, in bytes, that are currently stored for this journal.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Data stored in Journal is %value% Bytes

14.19.4 Total File Size (bytes)

This metric displays the total size of all journal files for this journal.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total File Space Used is %value% Bytes

14.19.5 Journal Backlog

This metric displays the number of serialized values that have yet to be persisted.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Backlog is %value%

14.19.6 Backlog Size (bytes)

This metric displays the maximum size, bytes, of the backlog. The backlog is amount of serialized values that has yet to be persisted.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Backlog Size is %value% Bytes

14.19.7 Total Pool Size (bytes)

This metric displays the total size, in bytes, of all available buffers in the pool.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total size available in all buffers is %value% Bytes

14.20 RAM Journal

This metric category provides information about the RAM Journal metrics.

14.20.1 Journal Files

This metric displays the number of journal files that are currently in use.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Journal Files in use are %value%

14.20.2 Journal Binary Stores

This metric displays the number of active JournalBinaryStore objects that are using this journal.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Binary Store is %value%

14.20.3 Total Data Size (bytes)

This metric displays the amount of data, in bytes, that are currently stored for this journal, in bytes, that are currently stored for this journal.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Data stored in Journal is %value% Bytes

14.20.4 Total File Size (bytes)

This metric displays the total size of all journal files for this journal.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total File Space Used is %value% Bytes

14.21 Connection Details

This metric category provides information about the Connection Details metrics.

14.21.1 Service Name

This metric displays the name of the Coherence service.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.21.2 Connection UUID

This metric displays the UUID of the Coherence connection.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.21.3 Connection Time (ms)

This metric displays the time duration (in ms) that the client has been connected.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Connection Time (ms) is %value%

14.21.4 Outgoing Queue Backlog (bytes)

This metric displays the backlog (in bytes) of the outgoing queue.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Outgoing Queue Backlog (bytes) is %value%

14.21.5 Outgoing Message Queue Backlog

This metric displays the backlog of the outgoing message queue.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Outgoing Message Queue Backlog is %value%

14.21.6 Total Bytes Received Per Minute

This metric displays the number of bytes received per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Bytes Received per minute is %value%

14.21.7 Total Bytes Sent Per Minute

This metric displays the number of bytes sent per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Bytes Sent per minute is %value%

14.21.8 Total Messages Received Per Minute

This metric displays the number of messages received per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Messages Received per minute is %value%

14.21.9 Total Messages Sent Per Minute

This metric displays the number of messages sent per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Messages Sent per minute is %value%

14.22 Proxy (Connection Manager) Details

This metric category provides information about the Proxy (Connection Manager) Details metrics.

14.22.1 Service Name

This metric displays the name of the Coherence service.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.22.2 Connections

This metric displays the number of connections to the proxy service.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Connections value is %value%

14.22.3 Outgoing Backlog (bytes)

This metric displays the number of bytes queued to be sent by the proxy service.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Outgoing Backlog (bytes) is %value%

14.22.4 Outgoing Messages Backlog

This metric displays the number of messages queued by the proxy service.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Outgoing Messages Backlog is %value%

14.22.5 Total Bytes Sent Per Minute

This metric displays the number of bytes sent by the proxy service per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Bytes Sent per minute is %value%

14.22.6 Total Bytes Received Per Minute

This metric displays the number of bytes received by the proxy host per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Bytes Received per minute is %value%

14.22.7 Total Messages Sent Per Minute

This metric displays the number of messages sent by the proxy host per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Messages Sent per minute is %value%

14.22.8 Total Messages Received Per Minute

This metric displays the number of messages received by the proxy host per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Messages Received per minute is %value%

14.23 Transaction Manager

This metric category provides information about the Transaction Manager metrics.

14.23.1 Service Name

This metric displays the name of the Coherence service.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.23.2 Total Commit Duration (ms) Per Minute

This metric displays the cumulative time (in ms) spent during commit phase computed per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Commit Duration (ms) per minute is %value%

14.23.3 Timeout Duration (ms) Per Minute

This metric displays the transaction time out value in ms computed per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Timeout Duration (ms) per minute is %value%

14.23.4 Total Active Transactions Per Minute

This metric displays the number of currently active transactions per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Active Transactions per minute is %value%

14.23.5 Total Committed Transactions Per Minute

This metric displays the number of transactions that have been committed by the Transaction Manager per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Committed Transaction per minute is %value%

14.23.6 Total Recovered Transactions Per Minute

This metric displays the number of transactions that have been recovered by the Transaction Manager per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Recovered Transactions per minute is %value%

14.23.7 Total Rolled Back Transactions Per Minute

This metric displays the number of transactions that have been rolled back by the Transaction Manager per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Rolled back Transactions per minute is %value%

14.23.8 Total Transaction Duration (ms) Per Minute

This metric displays the cumulative time (in ms) spent on active transactions computed per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Transaction Duration (ms) per minute is %value%

14.24 Messaging

This metric category provides information about the Messaging metrics.

Note:
By default, collection for this metric category is disabled.

14.24.1 Destination

This metric displays the coherence messaging description.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.24.2 Destination ID

This metric displays the coherence messaging description ID.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.24.3 Subscription

This metric displays the coherence messaging subscription.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.24.4 Subscription ID

This metric displays the coherence messaging subscription ID.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.24.5 Total Messages Acknowledged

This metric displays the number of messages acknowledged.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Messages Acknowledged is %value%

14.24.6 Total Messages Received

This metric displays the number of messages received.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Total Messages Received is %value%

14.25 Publishing Service

This metric category provides information about the Publishing Service metrics.

Note:
By default, collection for this metric category is disabled.

14.25.1 Publisher ID

This metric displays the publisher ID.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.25.2 Cache Name

This metric displays the name of the coherence cache.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.25.3 Publisher Name

This metric displays the name of the Publisher.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.25.4 Consecutive Publishing Failures Per Minute

This metric displays the consecutive publishing failures by the Publishing Service per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Consecutive Publishing Failures per minute is %value%

14.25.5 Last Publishing Duration

This metric displays the last publishing duration.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Last Publishing Duration is %value%

14.25.6 Maximum Publishing Duration

This metric displays the maximum publishing duration.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Maximum Publishing Duration is %value%

14.25.7 Minimum Publishing Duration

This metric displays the minimum publishing duration.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Minimum Publishing Duration is %value%

14.25.8 Publish Count Per Minute

This metric displays the publish count per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Publish Count per minute is %value%

14.25.9 Replicated Entries Per Minute

This metric displays the number of entries replicated per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Replicated Entries per minute is %value%

14.25.10 Replication Entry Candidates Per Minute

This metric displays the number of replication entry candidates per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Replication Entry Candidates per minute is %value%

14.25.11 Publishing Service State

This metric displays the state of the Publishing Service.

Target Version

Collection Frequency

All Versions

Every 15 minutes

14.25.12 Publishing Duration Per Minute

This metric displays the total publishing duration per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Collection

Not Defined

Not Defined

Publishing Duration per minute is %value%

14.26 HTTP Session (Web) Metrics (Coherence version 3.4.2 – 3.5)

This metric category provides information about the HTTP Session (Web) metrics for Coherence versions 3.4.2 to 3.5.

14.26.1 Web Application ID

This metric displays the HTTP Session Per Node - Web Application ID.

Target Version

Collection Frequency

All Versions

Every 5 minutes

14.26.2 Attributes in Local Session Cache

This metric displays the number of nondistributed session attributes stored in the local session attribute cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Attributes in Local Session cache is %value%

14.26.3 Sessions in Local Session Cache

This metric displays the number of nondistributed sessions stored in the local session cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Sessions in Local Session cache is %value%

14.26.4 Average Size for Attribute Overflows (bytes)

This metric displays the average size (in bytes) of the session attributes stored in the "overflow" clustered cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Size for Attribute Overflows (bytes) is %value%

14.26.5 Maximum Size for Attribute Overflow (bytes)

This metric displays the maximum size (in bytes) of a session attribute stored in the "overflow" clustered cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Maximum Size for Attribute Overflow (bytes) is %value%

14.26.6 Total Overflow Cache Updates Per Minute

This metric displays the updates to session attributes stored in the "overflow" clustered cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Overflow Cache Updates per minute is %value%

14.26.7 Session Average Lifetime (seconds)

This metric displays the average lifetime (in seconds) of session objects invalidated.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Session Average Lifetime (seconds) is %value%

14.26.8 Session Average Size (bytes)

This metric displays the average size (in bytes) of session objects placed in the session storage clustered cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Session Average Size (bytes) is %value%

14.26.9 Session Maximum Size (bytes)

This metric displays the maximum size (in bytes) of a session object placed in the session storage clustered cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Session Maximum Size (bytes) is %value%

14.26.10 Session Minimum Size (bytes)

This metric displays the minimum size (in bytes) of a session object placed in the session storage clustered cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Session Minimum Size (bytes) is %value%

14.26.11 Number of Sticky Sessions

This metric displays the number of session objects that are pinned to this instance of the web application.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Number of Sticky Sessions is %value%

14.26.12 Total Session Updates Per Minute

This metric displays the updates of session object stored in the session storage clustered cache per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Session Updates per minute is %value%

14.27 HTTP Session (Web) Metrics (Coherence version 3.6 – 3.7.1)

This metric category provides information about the HTTP Session (Web) metrics for Coherence versions 3.6 to 3.7.1.

14.27.1 Web Application ID

This metric displays the HTTP Session Per Node - Web Application ID.

Target Version

Collection Frequency

All Versions

Every 5 minutes

14.27.2 Attributes in Local Session Cache

This metric displays the number of nondistributed session attributes stored in the local session attribute cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Attributes in Local Session cache is %value%

14.27.3 Sessions in Local Session Cache

This metric displays the number of nondistributed sessions stored in the local session cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Sessions in Local Session cache is %value%

14.27.4 Average Size for Attribute Overflows (bytes)

This metric displays the average size (in bytes) of the session attributes stored in the "overflow" clustered cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Size for Attribute Overflows (bytes) is %value%

14.27.5 Maximum Size for Attribute Overflow (bytes)

This metric displays the maximum size (in bytes) of a session attribute stored in the "overflow" clustered cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Maximum Size for Attribute Overflow (bytes) is %value%

14.27.6 Total Overflow Cache Updates Per Minute

This metric displays the updates to session attributes stored in the "overflow" clustered cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Overflow Cache Updates per minute is %value%

14.27.7 Session Average Lifetime (seconds)

This metric displays the average lifetime (in seconds) of session objects invalidated.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Session Average Lifetime (seconds) is %value%

14.27.8 Session Average Size (bytes)

This metric displays the average size (in bytes) of session objects placed in the session storage clustered cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Session Average Size (bytes) is %value%

14.27.9 Session Maximum Size (bytes)

This metric displays the maximum size (in bytes) of a session object placed in the session storage clustered cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Session Maximum Size (bytes) is %value%

14.27.10 Session Minimum Size (bytes)

This metric displays the minimum size (in bytes) of a session object placed in the session storage clustered cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Session Minimum Size (bytes) is %value%

14.27.11 Number of Sticky Sessions

This metric displays the number of session objects that are pinned to this instance of the web application.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Number of Sticky Sessions is %value%

14.27.12 Total Session Updates Per Minute

This metric displays the updates of session object stored in the session storage clustered cache per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Session Updates per minute is %value%

14.27.13 Average Reap Duration (ms)

This metric displays the average reap duration in milliseconds.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Reap Duration (ms) is %value%

14.27.14 Maximum Reap Duration (ms)

This metric displays the maximum reap duration in milliseconds.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Maximum Reap Duration (ms) is %value%

14.27.15 Last Reap Duration (ms)

This metric displays the time in ms it took for the last reap cycle to finish.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Last Reap Duration (ms) is %value%

14.27.16 Average Reaped Sessions

This metric displays the average number of reaped sessions in a reap cycle.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Reaped Sessions is %value%

14.27.17 Maximum Reaped Sessions

This metric displays the maximum number of sessions reaped in a reap cycle.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Maximum Reaped Sessions is %value%

14.27.18 Sessions Reaped in Last Reap Cycle

This metric displays the number of expired sessions that were reaped in the last reap cycle.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Sessions Reaped in Last Reap Cycle is %value%

14.27.19 Total Reaped Sessions

This metric displays the number of expired sessions that has been reaped.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Reaped Sessions is %value%

14.27.20 Last Reap Cycle

This metric displays the start time for the last reap cycle.

Target Version

Collection Frequency

All Versions

Every 5 minutes

14.27.21 Next Reap Cycle

This metric displays the time for the next reap cycle.

Target Version

Collection Frequency

All Versions

Every 5 minutes

14.28 Weblogic HTTP Session (Web) Metrics

This metric category provides information about the Weblogic HTTP Session (Web) metrics.

14.28.1 Web Application ID

This metric displays the HTTP Session Per Node - Web Application ID.

Target Version

Collection Frequency

All Versions

Every 5 minutes

14.28.2 Attributes in Local Session Cache

This metric displays the number of nondistributed session attributes stored in the local session attribute cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Attributes in Local Session cache is %value%

14.28.3 Sessions in Local Session Cache

This metric displays the number of nondistributed sessions stored in the local session cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Sessions in Local Session cache is %value%

14.28.4 Average Size for Attribute Overflows (bytes)

This metric displays the average size (in bytes) of the session attributes stored in the "overflow" clustered cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Size for Attribute Overflows (bytes) is %value%

14.28.5 Maximum Size for Attribute Overflow (bytes)

This metric displays the maximum size (in bytes) of a session attribute stored in the "overflow" clustered cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Maximum Size for Attribute Overflow (bytes) is %value%

14.28.6 Total Overflow Cache Updates Per Minute

This metric displays the updates to session attributes stored in the "overflow" clustered cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Overflow Cache Updates per minute is %value%

14.28.7 Session Average Lifetime (seconds)

This metric displays the average lifetime (in seconds) of session objects invalidated.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Session Average Lifetime (seconds) is %value%

14.28.8 Session Average Size (bytes)

This metric displays the average size (in bytes) of session objects placed in the session storage clustered cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Session Average Size (bytes) is %value%

14.28.9 Session Maximum Size (bytes)

This metric displays the maximum size (in bytes) of a session object placed in the session storage clustered cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Session Maximum Size (bytes) is %value%

14.28.10 Session Minimum Size (bytes)

This metric displays the minimum size (in bytes) of a session object placed in the session storage clustered cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Session Minimum Size (bytes) is %value%

14.28.11 Number of Sticky Sessions

This metric displays the number of session objects that are pinned to this instance of the web application.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Number of Sticky Sessions is %value%

14.28.12 Total Session Updates Per Minute

This metric displays the updates of session object stored in the session storage clustered cache per minute.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Session Updates per minute is %value%

14.28.13 Average Reap Duration (ms)

This metric displays the average reap duration in milliseconds.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Reap Duration (ms) is %value%

14.28.14 Maximum Reap Duration (ms)

This metric displays the maximum reap duration in milliseconds.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Maximum Reap Duration (ms) is %value%

14.28.15 Last Reap Duration (ms)

This metric displays the time in ms it took for the last reap cycle to finish.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Last Reap Duration (ms) is %value%

14.28.16 Average Reaped Sessions

This metric displays the average number of reaped sessions in a reap cycle.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Average Reaped Sessions is %value%

14.28.17 Maximum Reaped Sessions

This metric displays the maximum number of sessions reaped in a reap cycle.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Maximum Reaped Sessions is %value%

14.28.18 Sessions Reaped in Last Reap Cycle

This metric displays the number of expired sessions that were reaped in the last reap cycle.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Sessions Reaped in Last Reap Cycle is %value%

14.28.19 Total Reaped Sessions

This metric displays the number of expired sessions that has been reaped.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3rd Collection

Not Defined

Not Defined

Total Reaped Sessions is %value%

14.28.20 Last Reap Cycle

This metric displays the start time for the last reap cycle.

Target Version

Collection Frequency

All Versions

Every 5 minutes

14.28.21 Next Reap Cycle

This metric displays the time for the next reap cycle.

Target Version

Collection Frequency

All Versions

Every 5 minutes

15 Oracle HTTP Server

This chapter describes Oracle HTTP Server (OHS) metrics.

Note:
This book uses the following terminology when referring to the different versions and implementations of Oracle HTTP Server (OHS):

- Managed OHS 10g: Oracle HTTP server associated with an Oracle WebLogic Server domain

- Managed OHS 11g: Oracle HTTP server associated with an Oracle WebLogic Server domain

- Standalone OHS 11g: Oracle HTTP Server in standalone mode (not associated with an Oracle WebLogic Server domain)

- Managed OHS 12c: Oracle HTTP Server in an Oracle WebLogic Server domain (often referred to as a colocated HTTP server). In this configuration, Oracle HTTP Server is managed through the Oracle WebLogic Server.

- Standalone OHS 12c: Oracle HTTP Server in a standalone domain. In this configuration, Oracle HTTP Server is managed independently of Oracle WebLogic Server.

For more information about the different implementations of OHS, see the Oracle Fusion Middleware documentation relevant to your release.

http://www.oracle.com/technetwork/documentation/

15.1 mod_oc4j Destination Metrics

This metric category provides details about the failed requests routed by mod_oc4j to a particular OC4J Instance.

15.1.1 Percentage of Requests that Were Failures

This metric shows the percentage of the total number of requests routed by mod_oc4j to this particular OC4J instance that were failed requests.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

Every 5 Minutes

Not Defined

Not Defined

The percentage of requests that resulted in failures is %value%%%

15.2 mod_oc4j General Metrics

This metric category displays charts that show the count of requests to OC4J instances, and the percentage of requests that failed and resulted in internal errors.

15.2.1 Percentage of Requests Resulted in Internal Errors

This metric shows the percentage of total number of requests routed for all the Mount Points that resulted in internal errors.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

Every 5 Minutes

Not Defined

Not Defined

Heap Usage is %value%MB

15.2.2 Percentage of Requests that Were Failures

This metric shows the percentage of total number of requests routed for all the mount points that were failed requests.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

Every 5 Minutes

1

1.5

The percentage of requests that resulted in failures is %value%%%

15.3 mod_oc4j MountPt Metrics

This metric category provides details about the successful and failed requests routed by mod_oc4j for a particular mount point. The metrics table shows details such as the OC4J instances to which the requests were routed and the path for the OC4J Mount directive in the mod_oc4j.conf file.

15.3.1 Percentage of Requests that Were Failures

This metric shows the percentage of total number of requests routed by mod_oc4j for this particular mount point that were failed requests.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

Every 30 Minutes

1

1.5

The percentage of requests that resulted in failures is %value%%%

15.4 modplsql_HTTPResponseCodes Metrics

This metric category provides information about the count or percentage of various types of response codes since Oracle HTTP Server was last restarted.

15.4.1 400sPercentage

This metric shows the count of unsuccessful mod_plsql requests returning a 400 HTTP response code.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Managed OHS10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

Every 5 Minutes

Not Defined

Not Defined

HTTP 400 response codes are %value% %%

15.4.2 500sPercentage

This metric shows the count of unsuccessful mod_plsql requests returning a 500 HTTP response code.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

Every 5 Minutes

Not Defined

Not Defined

HTTP 500 response codes are %value% %%

15.5 OHS Module Metrics

This metric category contains metrics about Oracle HTTP Server modules.

15.5.1 Request Handling Throughput, for a Module (requests per second)

This rate metric specifies the number of requests handled per second by this module during the last interval. The interval is the period of time specified as the collection frequency for this metric. This metric helps you determine the frequency of requests currently being served by the module. If the request handling throughput is very low, either there is no activity on the Web server for the module, or there is something else going on that is preventing the module from processing requests.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS Standalone OHS 12c (12.1.2)

Every 5 Minutes

15.5.2 Request Handling Time, for a Module (seconds)

This metric specifies the average time (in seconds) it took the module to handle a request during the last interval. The interval is the period of time specified as the collection frequency of this module.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

15.5.3 Total Handled Requests for a Module

This metric specifies the total number of requests handled by this module during the collection interval.

Target Version

Collection Frequency

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

15.6 OHS Process Metrics

This metric category provides metrics about Oracle HTTP Server processes.

15.6.1 Heap Usage (MB)

This metric shows the amount of heap space (total program memory) used by Oracle HTTP Server's parent process.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

Every 5 Minutes

Not Defined

Not Defined

Heap Usage is %value%MB

15.7 OHS Response Code Metrics

This metric category includes metrics about the amount of Oracle HTTP Server response codes since the Oracle HTTP Server was last restarted.

15.7.1 HTTP 4xx Errors Throughput

This metric shows the number of HTTP 4xx errors per second returned by Oracle HTTP Server during the last successful collection interval. This value is the number of 4xx errors returned by the server in the last interval divided by the interval time (in seconds).

Target Version

Collection Frequency

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 15 Minutes

15.7.2 HTTP 4xx Errors

This metric shows the number of HTTP 4xx errors returned by Oracle HTTP Server during the last successful collection interval.

Target Version

Collection Frequency

Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

Every 15 Minutes

15.7.3 HTTP 5xx Errors Throughput

This metric specifies the number of HTTP 5xx errors per second returned by Oracle HTTP Server during the last successful collection interval. This value is the number of 5xx errors returned by the server in the last interval divided by the interval time (in seconds.

Target Version

Collection Frequency

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 15 Minutes

15.7.4 HTTP 5xx errors

This metric specifies the number of HTTP 5xx errors returned by Oracle HTTP Server during the last successful collection interval.

Target Version

Collection Frequency

Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

Every 15 Minutes

15.8 OHS Server Metrics

This metric category displays information about the Oracle HTTP Server.

15.8.1 Active HTTP Connections

This metric shows the number of open HTTP connections.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

Not Defined

Not Defined

The number of active connections is %value%

15.8.2 Active HTTP Requests

This metric specifies the number of requests currently being serviced.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

Not Defined

Not Defined

The number of active requests is %value%

15.8.3 Busy Processes

This metric specifies the number of child servers that are busy.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

15.8.4 Busy Threads

This metric shows the number of Oracle HTTP Server threads that are servicing requests currently.

Target Version

Collection Frequency

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

15.8.5 Busy Threads (%)

This metric shows the percentage of Oracle HTTP Server threads that are servicing requests currently.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

85

90

The percentage of processes that are busy handling requests is %value%%%

15.8.6 Connection Duration (seconds)

This metric shows the average time (in seconds) a connection was open during the last interval. The interval is the period of time specified as the collection frequency for this metric. A connection remains open until all of the requests that it is handling have been completed.

Target Version

Collection Frequency

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

15.8.7 Error Rate (%)

This metric specifies the percentage of requests that encountered errors during the last interval. The interval is the period of time specified as the collection frequency for this metric.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

1

1.5

The percentage of requests that resulted in errors is %value%%%

User Action

Use Log Viewer to examine the errors in this Oracle HTTP Server's error log file. From the Oracle Enterprise Manager Cloud Control console, right-click the Oracle HTTP Server target name, select Logs, then View Log Messages.

For more information about log messages, see the Oracle Enterprise Manager Cloud Control Administrator's Guide.

15.8.8 Idle Threads

This metric specifies the number of Oracle HTTP Server threads that are not servicing requests.

Target Version

Collection Frequency

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

15.8.9 Idle Processes

This metric specifies the number of processes that are not handling any requests.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

15.8.10 Number of Threads

This metric specifies the total number of Oracle HTTP Server threads.

Target Version

Collection Frequency

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

15.8.11 Percentage of Busy Processes

This metric shows the percentage of Oracle HTTP Server child processes that are currently servicing requests.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

85

90

The percentage of processes that are busy handling requests is %value%%%

User Action

To tune the percentage of Oracle HTTP Server child processes that are currently servicing requests, you can change the values for the MaxClients, MinSpareServers, and MaxSpareServers directives. You can change the values of the MaxClients, MinSpareServers and MaxSpareServers directives on the Oracle HTTP Server Performance Directives Configuration page in the Oracle Enterprise Manager Fusion Middleware Control Console. For more information about the MaxClients, MinSpareServers, and MaxSpareServers directives, go to the Apache HTTP Server Documentation section of the Apache web site, then navigate to the Directives information.

http://www.apache.org

15.8.12 Request Processing Time (milliseconds)

This metric shows the average time (in milliseconds) it took to process a request during the last interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Collection Frequency

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

15.8.13 Request Processing Time (seconds)

This metric shows the average time it took to process a request during the last interval. The interval is the period of time specified as the collection frequency for this metric.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1))

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

Not Defined

Not Defined

The average processing time for a request is %value% seconds

15.8.14 Request Throughput (requests per second)

This rate metric specifies the number of requests per second serviced during the last interval. The interval is the period of time specified as the collection frequency for this metric. This metric specifies how much of a load this Oracle HTTP Server is handling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

15.8.15 Response Data Processed (KB per response)

This metric specifies the average size of a response (in KB) during the last interval. The interval is the period of time specified as the collection frequency for this metric.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

Not Defined

Not Defined

The average size of a request is %value%KB

15.8.16 Response Data Throughput (KB per second)

This metric specifies the amount of response data (in KB/seconds) processed by Oracle HTTP Server during the last interval. The interval is the period of time specified as the collection frequency for this metric.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

15.9 OHS Virtual Host Metrics

This metric category provides virtual host information.

15.9.1 Active Requests for a Virtual Host

This metric specifies the total number of active requests currently being processed by the virtual host.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

135

140

The number of active requests for virtual host %name% is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Name" object.

If warning or critical threshold values are currently set for any "Name" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Name" object, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

15.9.2 Request Processing Time for a Virtual Host (seconds)

This metric shows the average amount of time it took the virtual host to process one request during the last interval. The interval is the period of time specified as the collection frequency for this metric.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

Not Defined

Not Defined

The average processing time for a request for virtual host %name% is %value% seconds

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Name" object.

If warning or critical threshold values are currently set for any "Name" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Name" object, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

15.9.3 Request Throughput for a Virtual Host (requests per second)

This rate metric specifies the number of requests per second serviced by the virtual host during the last interval. The interval is the period of time specified as the collection frequency for this metric. This metric specifies how much of a load this virtual host is handling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

15.9.4 Response Data Processed For a Virtual Host (KB per response)

This metric specifies the average size of a response (in KB) during the last interval. The interval is the period of time specified as the collection frequency for this metric.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1))

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

Not Defined

Not Defined

The average size of a request for virtual host %name% is %value%KB

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Name" object.

If warning or critical threshold values are currently set for any "Name" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Name" object, use the Edit Thresholds page.

15.9.5 Response Data Throughput For a Virtual Host (KB per second)

This metric specifies the amount of response data (in KB/second) processed by the virtual host during the last interval. The interval is the period of time specified as the collection frequency for this metric.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

15.9.6 Virtual Host Type

This metrics provides the type of virtual host, which can be IP_DEFAULT, NAME_DEFAULT, IP_BASED, or NAME_BASED.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

15.10 Oracle HTTP Server General Metrics

This metric category provides general Oracle HTTP Server metrics.

15.10.1 Start Time (ms since Epoch)

This metric shows the start time of the Oracle HTTP Server.

Target Version

Collection Frequency

Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

Every 5 Minutes

15.11 Resource Usage

This metric category provides information about CPU and memory usage.

15.11.1 CPU Idle Time (%)

This metric shows the percentage of time the CPU has been idle on the host.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

Every 5 Minutes

15.11.2 CPU Usage (%)

This metric shows the percentage of CPU used by the Oracle HTTP server.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

Not Defined

Not Defined

CPU Utilization is %value%%%

15.11.3 Free Memory (%)

This metric shows the percentage of current free memory on the host that has Oracle HTTP Server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

Every 5 Minutes

15.11.4 Free Memory (MB)

This metric shows current free memory on the host that has an Oracle HTTP Server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

Every 5 Minutes

15.11.5 Memory Usage (%)

This metric shows the current percentage of physical memory used by the component.

The following table shows how often the metric's value is collected.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

80

90

Memory Utilization is %value%%%

15.11.6 Memory Usage (MB)

This metric shows the current physical memory used by Oracle HTTP Server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 5 Minutes

15.11.7 Other CPU Usage (%)

This metric shows the percentage of CPU used by host processes other than Oracle HTTP Server. If you are having problems with CPU usage on the Oracle HTTP server host computer, this metric can help you determine whether or not Oracle HTTP server is causing the problem.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

Every 5 Minutes

User Action

Navigate to the host Home page in the Fusion Middleware Control and review the top processes to see if you can identify which processes are consuming the most CPU. Or, navigate to the host Performance page in the Cloud Control and view the processes that are consuming the most CPU.

15.11.8 Other Memory Usage (%)

This metric specifies the percentage of other memory usage on the computer. It includes all the memory except for Oracle HTTP Server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

Every 5 Minutes

15.11.9 Other Memory Usage (MB)

This metric shows current host memory used by processes other than Oracle HTTP Server. If you are having problems with CPU usage on the Oracle HTTP Server host computer, this metric can help you determine whether or not Oracle HTTP Server is causing this problem.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

Every 5 Minutes

User Action

Navigate to the host Home page in the Fusion Middleware Control and review the top processes to see if you can identify which processes are consuming the most memory. Or, navigate to the host Performance page in the Cloud Control and view the processes that are consuming the most memory.

15.11.10 Start Time (ms since Epoch)

This metric shows the start time of Oracle HTTP Server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

Every 5 Minutes

15.11.11 Total Memory (MB)

Amount of physical memory (in MB) for the host where Oracle HTTP Server is running.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

Every 5 Minutes

15.12 Response

This metric category provides metrics that give availability information about Oracle HTTP Server.

15.12.1 Response - Status

This metric indicates whether or not Oracle HTTP Server is up or down. A status of 1 means the server is up, and a status of 2 means the server is down.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every Minute

Not Defined

0

The Oracle HTTP Server instance is down

User Action

If the Oracle HTTP Server instance is down, start it from the Home page for Oracle HTTP Server in the Oracle Enterprise Manager Cloud Control console.

15.13 Virtual Host Summary

This metric category provides a summary of the virtual hosts.

Note:
By default, this metric category is disabled.

15.13.1 Number of Virtual Hosts

This metric shows the number of monitored virtual hosts.

The following table shows how often the metric's value is collected, when metric collection is enabled.

Target Version

Collection Frequency

- Managed OHS 10gR1 (10.1.2.x), 10gR3 (10.1.3.x)

- Managed OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Managed OHS 12c (12.1.2.x)

- Standalone OHS 11g (11.1.1.7, 11.1.1.6, 11.1.1.5, 11.1.1.4, 11.1.1.3, 11.1.1.2, 11.1.1.1)

- Standalone OHS 12c (12.1.2)

Every 60 Minutes

16 Apache Tomcat Metrics

Oracle Enterprise Manager can be used to manage Apache Tomcat. You can use the All Metrics page for an Apache Tomcat target to view the metrics that are being monitored for that target by Oracle Management Agent.

The Apache Tomcat metrics provide for each metric the following information:

- Description

- Metric summary. The metric summary can include some or all of the following: target version, evaluation frequency, collection frequency, upload frequency, operator, default warning threshold, default critical threshold, consecutive number of occurrences preceding notification, and alert text.

- Multiple Thresholds (where applicable)

16.1 All Applications

This metric category contains aggregated performance metrics spanning all the applications deloyed to the Apache Tomcat container.

16.1.1 All Applications - Rejected Sessions

This metric shows the number of sessions rejected by all the applications running on the Apache Tomcat container since last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.1.2 All Applications - Sessions Created

This metric shows the number of sessions created by all the applications running on the Apache Tomcat container since the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.1.3 All Applications - Total Active Sessions

This metric shows the number of active sessions of all the applications running on the Apache Tomcat container.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.2 All Applications JSP Monitor Metrics

This metric category contains aggregated performance metrics spanning all the JavaServer Pages (JSPs) deployed to the Apache Tomcat container.

16.2.1 All Applications - JSP Access

This metric shows the number of times JSPs were accessed on all the applications since last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.2.2 All Applications - JSP Reload

This metric shows the number of times JSPs were reloaded on all the applications since last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.3 All Global Request Processors Metrics

This metric category contains aggregated performance metrics spanning all the Global Request Processors deployed to the Apache Tomcat container.

16.3.1 All Global Request Processors - Total Bytes Received

This metric shows the bytes received by all the request processors running on the Apache Tomcat container since last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.3.2 All Global Request Processors - Total Errors

This metric shows the error count on all the request processors running on the Apache Tomcat container since last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.3.3 All Global Request Processors - Total Requests

This metric shows the request count on all the request processors running on the Apache Tomcat container since last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.3.4 All Global Request Processors -Total Bytes Sent

This metric shows the bytes sent by all the request processors running on the Apache Tomcat container since last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.4 Application Cache Metrics

This metric category contains the usage details of the application cache of the Apache Tomcat container.

16.4.1 Cache Access Count

This metric shows the number of times the cache was accessed since last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.4.2 Cache Hit Count

This metric shows the number of times the cache was hit since last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.5 Applications Metrics

This metric category contains the metrics for each application deployed to the container.

16.5.1 Active Session Since Last Collection

This metric shows the number of active sessions created since the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.5.2 Average Processing Time (ms)

This metric shows the average time taken (in milliseconds) for processing a request.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.5.3 Processing Time Since last collection (ms)

This metric shows the processing time (in milliseconds) since the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.5.4 Rejected Sessions Since Last collection

This metric shows the number of sessions rejected since the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.5.5 Request Count Since Last Collection

This metric shows the number of requests served since the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.5.6 Sessions Created Since Last Collection

This metric shows the number of new sessions created since the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.5.7 Total Active Sessions

This metric shows the total number of active sessions since startup.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.5.8 Total Processing Time (ms)

This metric shows the total processing time (in milliseconds) since startup.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.5.9 Total Rejected Sessions

This metric shows the total number of rejected sessions since startup.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.5.10 Total Request Count

This metric shows the total number of requests served since startup.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.5.11 Total Sessions Since Startup

This metric shows the total number of sessions created since startup.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.6 DataSource Metrics

This metric category contains the attributes of all the data sources configured for the Apache Tomcat container.

16.6.1 Active Datasource Connections

This metric shows the number of active connections to the data source.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.6.2 Idle Datasource Connections

This metric shows the number of idle connections to the data source.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.7 Global Request Processor Metrics

This metric category contains the attributes of each Global Request Processor configured on the Apache Tomcat container.

16.7.1 Average Request Processing Time (ms)

This metric shows the average time taken (in milliseconds) for processing a request by the global request processor.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.7.2 Bytes Received Since Last Collection

This metric shows the number of bytes received by each request processor since the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.7.3 Bytes Sent Since Last Collection

This metric shows the number of bytes sent by each request processor since the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.7.4 Errors Since Last Collection

This metric shows the error count of each request processor since the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.7.5 Request Processing Time (ms)

This metric shows the request processing time (in milliseconds) of each global request processor.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.7.6 Requests Since Last Collection

This metric shows the number of requests served by each request processor since the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.8 JSP Monitor Metrics

This metric category contains the usage details of JSPs.

16.8.1 JSP Access

This metric shows the number of times JSPs were accessed since during the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.8.2 JSP Reload

This metric shows the number of times JSPs were reloaded since the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.9 JVM

This metric category provides information about Java Virtual Machine (JVM) usage.

16.9.1 Server CPU Usage (%)

This metric shows the server CPU percentage usage during the last collection interval.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 15 minutes

16.10 JVM Garbage Collector

This metric category provides information about JVM Garbage Collectors.

16.10.1 Name

This metric shows the name of the JVM garbage collector.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 15 minutes

16.10.2 Garbage Collector - Duration of last Garbage Collection (ms)

This metric indicates the number of milliseconds that the JVM pent on the last garbage collection ended during the last collection interval.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 15 minutes

16.10.3 Garbage Collector - Invocation Time (ms)

This metric indicates the number of milliseconds that the JVM has spent on all garbage collection runs during last collection interval.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 15 minutes

16.10.4 Garbage Collector - Invocation Rate (per min)

This metric indicates the rate at which the garbage collections happened during the last collection interval.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 15 minutes

16.10.5 Garbage Collector - Percentage Time spent (elapsed)

This metric indicates the percentage of time that the JVM has spent on all garbage collections during last collection interval.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 15 minutes

16.11 JVM Heap Memory Pool after GC

This metric category provides information about the JVM Heap Memory Pool memory usage metrics after garbage collection.

16.11.1 JVM Garbage Collector - Name

This metric displays the name of the garbage collector.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 15 minutes

16.11.2 Memory Pool

This metric displays the name of the memory pool.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 15 minutes

16.11.3 Memory usage after GC (MB)

This metric displays the amount of memory used by the memory pool after the garbage collection (MB).

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 15 minutes

16.11.4 Percentage Memory usage after GC (%)

This metric displays the percentage memory usage of the memory pool after garbage collection (%).

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 15 minutes

16.12 JVM Memory Pools

This metric provides information about the metrics for memory usage in the JVM memory pools.

16.12.1 Name

This metric displays the name of the JVM memory pool.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 15 minutes

16.12.2 Memory Pool - Type

This metric displays the type of the JVM memory pool.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 15 minutes

16.12.3 Memory Pool - Current Usage (MB)

This metric displays the amount of memory currently used in the JVM memory pool.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 15 minutes

16.12.4 Memory Pool - Percentage Usage (%)

This metric displays the current memory usage percentage with respect to the maximum memory available in the memory pool (%).

16.12.5 Memory Pool - Peak Usage (MB)

This metric displays the peak memory usage by the Memory Pool since the JVM started.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 15 minutes

16.13 JVM Threads

This metric category provides information about the JVM Threads metrics.

16.13.1 JVM Threads - Active Threads

This metric displays the number of active threads running in the JVM.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 15 minutes

16.13.2 JVM Threads - Peak Threads

This metric displays the maximum number of active threads running at any time in the JVM.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 15 minutes

16.13.3 JVM Threads - Active Daemon Threads

This metric displays the number of Daemon threads running in the JVM.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 15 minutes

16.13.4 JVM Threads - Threads created (per min)

This metric displays the number of JVM Threads started during the last collection interval (per minute).

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 15 minutes

16.14 Memory

This metric category provides information about memory usage metrics.

16.14.1 JVM Heap Memory Usage (MB)

This metric displays the amount of memory (in MB) used in the heap.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.14.2 JVM Total Heap Memory Usage (MB)

This metric displays the maximum amount (in MB) of heap memory available for the JVM.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.14.3 JVM Non-Heap Memory Usage (MB)

This metric displays the amount of memory (in MB) being used in the non-heap.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.14.4 JVM Total Non-Heap Memory Usage (MB)

This metric displays the maximum amount of non-heap memory (in MB) available for the JVM.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.14.5 JVM Heap Memory Usage (%)

This metric displays the current heap memory percentage with respect to the maximum heap memory available.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.14.6 JVM Non-Heap Memory Usage (%)

This metric displays the current non-heap memory percentage with respect to the maximum non-heap memory available.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.14.7 JVM Objects Pending Finalization

This metric displays the number of objects waiting to be finalized in the memory.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.15 Memory Usage

This metric category gives information about the memory load on the Apache Tomcat container.

16.15.1 Heap Memory Usage (MB)

This metric shows the heap memory usage (in MB) of the server.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.15.2 Non Heap Memory Usage (MB)

This metric shows the nonheap memory usage (in MB) of the server.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.16 Response Metrics

This metric category shows the status of the Apache Tomcat container.

16.16.1 Status

This metric shows the status of the Apache Tomcat container - whether up or down.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.17 Servlets Metrics

This metric category contains attributes of each servlet loaded on the Apache Tomcat container.

16.17.1 Average Processing Time (ms)

This metric shows the average processing time (in milliseconds) since the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.17.2 Maximum Servlet Request Processing Time (ms)

This metric shows the maximum time taken (in milliseconds) for processing a request by the servlet.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.17.3 Number Of Errors Since Startup

This metric shows the number of erroneous requests received by the servlet since startup.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.17.4 Number Of Requests Since Startup

This metric shows the number of requests received by the servlet since startup.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.17.5 Number Of Servlet Errors Since Last Collection

This metric shows the number of erroneous requests received by the servlet since the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.17.6 Processing Time Since Last Collection

This metric shows the time taken for processing all the requests since the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.17.7 Requests Count Since Last Collection

This metric shows the number of requests served by the servlet since the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.17.8 Total Servlet Request Processing Time (ms)

This metric shows the total time taken (in milliseconds) for processing all the requests by the servlet.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.18 Session Manager Metrics

This metric category contains the statistics of the sessions managed by the Apache Tomcat container.

16.18.1 Active Sessions Since Startup

This metric shows the active number of sessions of each application since startup.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Real-time only

16.18.2 Rejected Sessions Since Startup

This metric shows the number of sessions rejected by each application since startup.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Real-time only

16.18.3 Application Name

This metric shows the name of the deployed application.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Real-time only

16.18.4 Sessions Created Since Startup

This metric shows the number of new sessions created since startup.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Real-time only

16.18.5 Sessions Created Since Last Collection

This metric shows the number of sessions created since the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Real-time only

16.18.6 Active Sessions Since Last Collection

This metric shows the number of active sessions since the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Real-time only

16.18.7 Rejected Sessions Since Last Collection

This metric shows the number of sessions rejected since the last collection.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Real-time only

16.19 Thread Pools Metrics

This metric category contains statistics on various thread pools used by the Apache Tomcat container.

16.19.1 Busy Threads

This metric shows the number of busy threads on the Apache Tomcat container.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

16.19.2 Threads

This metric shows the number of threads created on the Apache Tomcat container.

Target Version

Collection Frequency

Apache Tomcat 7.x and earlier

Every 5 minutes

17 Java EE Application

This chapter describes metrics for Java EE applications deployed to Oracle WebLogic Server.

17.1 ADFC Taskflow Metrics

This metric category describes metrics concerning ADFc (ADF Controller)

17.1.1 Total Active Taskflows

The count of active task flows in an ADF application since the application was run. This metric records the number of times that a task flow has been the active task flow for a user.

For example, if the user goes from task flow A to task flow B and then exits back to A, then task flow A will have been active two times and task flow B active once. Therefore the total active count would be three.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.1.2 Active Taskflows

This metric represents the number of currently active ADF task flows.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.1.3 Active throughput

The rate at which task flows are processed since the data was last collected.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.1.4 Active Taskflows

The number of active task flows processed since the last time metric data was collected.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.1.5 Total Entered Taskflows

This metric displays the number of task flows entered at the current time.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.1.6 Entered Taskflows

This metric records the number of times a task flow has been entered. Exiting back into a task flow from a called task flow is not the same as entering it. For example, if the user goes from task flow A to task flow B and then exits back to A, the total would be two, one entry for each into A and B.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.1.7 Invoke Taskflows

This metric records the number of times the task flow has been called by a task flow call activity.

Not every task flow is initiated by a task flow call activity. In most cases, this is probably going to be the same as number of entered task flows, but not all the time.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.1.8 Invoked Taskflows completed

The number of invoked task flows that have been completed at the current time.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.1.9 Taskflow Invoke time

The average time taken over the past five minutes to invoke ADF taskflows.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.1.10 Average Time

The average time to process task flows since the data was last collected.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.1.11 Maximum Time

The maximum time taken to process task flows since the data was last collected.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.1.12 Minimum Time

The minimum time taken to process the task flow since the data was last collected.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.2 Module Removals

The number of Application Module instances removed at the current time.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.3 Pool Checkouts

The number of free Application Module instances checked out at the current time.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.4 Average Creation time(ms)

The average creation time for an ApplicationModule instance since the data was last collected.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.5 Free Instances

The number of free Application Module instances at the current time.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.6 Maximum Creation Time (ms)

The maximum creation time for an Application Module instance since the data was last collected.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.7 Request Count

The number of main Application Module instances since the last request.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.8 Available Instances in last 5 Minutes

For the selected ApplicationModule, the count of available ApplicationModule instances in the pool over the past five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.9 Available Instances in last 1 min

For the selected ApplicationModule, the count of available ApplicationModule instances in the pool over the past one minute.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.10 Unavailable Instances in last 5 Minutes

For the selected ApplicationModule, the number of unavailable ApplicationModule instances in the pool over the past five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.11 Unavailable Instances in last 1 Minute

For the selected ApplicationModule, the count of unavailable ApplicationModule instances in the pool over the past one minute.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.12 Activations

The name of the ApplicationModule to which the following metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.13 Pool check Ins

The number of ApplicationModule instances checked into the ApplicationModule pool since the data was last collected.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.14 Pool Check Outs

The number of ApplicationModule instances checked out of the ApplicationModule pool since the data was last collected.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.15 Pool Check Out Failures

The number of ApplicationModule instance check out failures of the ApplicationModule pool since the data was last collected.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.16 Referenced Modules Reused

This metric provides details on the referenced modules used

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.17 Unreferenced Modules Recycled

This metric provides details on the unreferenced modules recycled.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.18 Datasource Metrics

This category provides information about datasource metrics.

17.18.1 Datasource - Available Connections

For the selected data source, this metric shows the number of database connections currently available (not in use).

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

<

Not Defined

Not Defined

The number of available connections for datasource %name%, application %appName% is %value%.

17.18.2 Datasource - Connections Created (per minute)

For the selected data source, this metric shows the number of database connections created per minute, averaged over the past five minutes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

The connections created for datasource %name%, application %appName% are %value% (per minute).

17.18.3 Datasource - Connections in Use

For the selected data source, this metric shows the number of JDBC connections currently in use by applications.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

The number of connections in use for datasource %name%, application %appName% is %value%.

17.18.4 Datasource - Connection Leaks (per minute)

For the selected data source, this metric shows the number of JDBC connection leaks per minute, averaged over the past five minutes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

The connection leaks for datasource %name%, application %appName% are %value% (per minute).

17.18.5 Datasource - Connection Pool Size

For the current data source, this metric shows the current count of JDBC connections in the JDBC connection pool.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

The number of connections in the connection pool for datasource %name%, application %appName% is %value%.

17.18.6 Datasource - Connection Refresh Failures (per minute)

For the selected data source, this metric shows the number of failed JDBC connection refreshes per minute, averaged over the past five minutes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

The connection refresh failures for datasource %name%, application %appName% are %value% (per minute)..

17.18.7 Datasource - Connection Request Failures (per minute)

For the selected data source, this metric shows the number of failed JDBC connection requests per minute, averaged over the past five minutes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

The connection request failures for datasource %name%, application %appName% are %value% (per minute).

17.18.8 Datasource - Connection Requests (per minute)

For the selected data source, this metric shows the number of requests for a JDBC connection from this data source per minute, averaged over the past five minutes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

The connection requests for datasource %name%, application %appName% are %value% (per minute).

17.18.9 Datasource - Successful Connections (%)

For the selected data source, this metric shows the percentage of requests that successfully returned JDBC connections during the last five minutes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

<

Not Defined

Not Defined

The successful connection rate for datasource %name%, application %appName% is %value%%%..

17.18.10 Datasource - Unavailable Connections

For the selected data source, this metric shows the number of database connections that are currently unavailable (in use or being tested by the system).

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

The number of unavailable connections for datasource %name%, application %appName% is %value%..

17.18.11 Datasource - Connection Requests Waiting

For the selected data source, this metric shows the current number of JDBC connection requests waiting for a database connection.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

The number of connection requests waiting for datasource %name%, application %appName% is %value%..

17.18.12 Datasource - Failed Waiting Connection Requests (per minute)

For the selected data source, this metric shows the number of JDBC connection wait failures per minute, averaged over the past five minutes.

A wait failure is a request for a connection from this data source that had to wait before getting a connection and eventually failed to get a connection. Waiting connection requests can fail for a variety of reasons, including waiting for longer than the ConnectionReserveTimeoutSecond.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

The connection wait failures for datasource %name%, application %appName% are %value% (per minute).

17.18.13 Datasource - Connection Requests that Waited (per minute)

For the selected data source, this metric shows the number of JDBC connection waits per minute, averaged over the past five minutes.

A JDBC connection wait is a request for a connection from this data source that had to wait before getting a connection, including those that eventually got a connection and those that did not get a connection

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

The connections that waited for datasource %name%, application %appName% are %value% (per minute).

17.18.14 Datasource - Connection Wait Successes (%)

For the selected data source, this metric shows the percentage of requests waiting for a JDBC connection that successfully got a connection during the last five minutes.

A JDBC connection wait is a request for a connection from this data source that had to wait before getting a connection, including those that eventually got a connection and those that did not get a connection

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

<

Not Defined

Not Defined

The connection wait success rate for datasource %name%, application %appName% is %value%%%.

17.18.15 Datasource - Connection Wait Successes (per minute)

For the selected data source, this metric shows the number of JDBC connection wait successes per minute, averaged over the past five minutes.

A wait success is a request for a connection from this data source that had to wait before getting a connection and eventually succeeded in getting a connection.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

The connection wait successes for datasource %name%, application %appName% are %value% (per minute).

17.18.16 Datasource - State

For the selected data source, this metric shows the current state of the data source. Possible states are:

- Running - the data source is enabled (deployed and not suspended). This is the normal state of the data source.

- Suspended - the data source has been manually disabled.

- Shutdown - the data source is shutdown and all database connections have been closed.

- Overloaded - all resources in pool are in use.

- Unhealthy - all connections are unavailable (not because they are in use). This state occurs if the database server is unavailable when the data source is created (creation retry must be enabled) or if all connections have failed connection tests (on creation, on reserve, or periodic testing).

- Unknown - the data source state is unknown

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

!=

Not Defined

Not Defined

The state of datasource %name%, application %appName% is %value%..

17.18.17 Datasource - Statements Added to Cache (per minute)

For the selected data source, this metric shows the number of statements per minute added to the statement cache, averaged over the past five minutes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

<

Not Defined

Not Defined

The statements added to cache for datasource %name%, application %appName% are %value% (per minute).

17.18.18 Datasource - Statements Discarded from Cache (per minute)

For the current data source, this metric shows the number of statements per minute discarded from the statement cache, averaged over the past five minutes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

<

Not Defined

Not Defined

The statements discarded from the cache for datasource %name%, application %appName% are %value% (per minute).

17.18.19 Datasource - Cached Statements not Used (per minute)

For the selected data source, this metric shows the number of statements per minute not satisfied by the statement cache, averaged over the past five minutes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

The cache statements not used for datasource %name%, application %appName% are %value% (per minute)..

17.18.20 Datasource - Cached Statements Used (%)

For the selected data source, this metric shows the percentage of statements satisfied by the statement cache during the last five minutes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

<

Not Defined

Not Defined

The number of available connections for datasource %name%, application %appName% is %value%.

17.18.21 Datasource - Cached Statements Used (per minute)

For the selected data source, this metric shows the number of statements per minute satisfied by the statement cache, averaged over the past five minutes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

<

Not Defined

Not Defined

The cached statements used rate for datasource %name%, application %appName% is %value%%%.

17.18.22 Datasource - Statement Cache Size

For the current data source, this metric shows the number of prepared and callable JDBC statements currently cached in the connection pool.

Each JDBC connection in the connection pool has its own cache of statements. This number is the sum of the number of statements in the caches for all connections in the connection pool.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

The size of the statement cache for datasource %name%, application %appName% is %value%.

17.19 EJB Module Metrics

This category provides information about EJB module metrics.

17.19.1 EJB Module - Cached Beans

This metric shows the total number of beans from this EJB Home that are currently in the EJB cache.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.19.2 EJB Module - Bean Activations (per minute)

This metric shows the average number of beans per minute that have been activated from the EJB home over the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.19.3 EJB Module - Cache Hits (%)

This metric shows the percentage of cache accesses that completed successfully in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.19.4 EJB Module - Cache Misses (per minute)

This metric shows the average number of cache misses per minute for this EJB module in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.19.5 EJB Module - Bean Accesses (per minute)

This metric shows the average EJB pool accesses per minute over the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.19.6 EJB Module - Bean Access Successes (%)

This metric shows the percentage of EJB pool accesses that were successful in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.19.7 EJB Module - Free Bean Instances

This metric shows the current number of available EJB instances in the free pool.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.19.8 EJB Module - Bean Destroys (per minute)

This metric shows the average number of EJB destroys per minute for this EJB module over the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.19.9 EJB Module - Bean Access Failures (per minute)

This metric shows the average number of times per minute that a failed attempt was made to get an instance from the free pool. This value is averaged over the past five minutes.

An Attempt to get a bean from the pool will fail if there are no available instances in the pool.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.19.10 EJB Module - Beans In Use

This metric shows the number of EJB instances currently being used from the free pool.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.19.11 EJB Module - Bean Transaction Commits (per minute)

This metric shows the average number of EJB transaction commits per minute for this EJB Module over the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.19.12 EJB Module - Bean Transaction Rollbacks (per minute)

This metric shows the average number of EJB transaction rollbacks per minute for this EJB module over the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.19.13 EJB Module - Bean Transaction Timeouts (per minute)

This metric shows the average number of EJB transaction timeouts per minute for this EJB module over the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.20 EJB Transaction Metrics

This category provides information about EJB transaction metrics.

17.20.1 EJB Transaction - Bean Transaction Commits (%)

This metric shows the percentage of EJB transactions that were committed during the last five minutes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

<

Not Defined

Not Defined

The bean transaction commit rate is %value%%%.

17.20.2 EJB Transaction - Bean Transaction Commits (per minute)

This metric shows the EJB transaction commits per minute, averaged over the past five minutes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

The bean transaction commits are %value% (per minute).

17.20.3 EJB Transaction - Bean Transaction Rollbacks (per minute)

This metric shows the EJB transaction rollbacks per minute, averaged over the past five minutes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

The bean transaction rollbacks are %value% (per minute).

17.20.4 EJB Transaction - Bean Transaction Timeouts (per minute)

This metric shows the EJB transaction timeouts per minute, averaged over the past five minutes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

The bean transaction timeouts are %value% (per minute).

17.21 Overview Metrics

This category provides information about the EJB overview metrics.

17.21.1 Cached Beans

This metric shows the total number of EJBs currently active in the EJB cache.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.2 Cache Accesses (per minute)

This metric shows the average number of EJB cache access attempts per minute for this application in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.3 Bean Activations (per minute)

This metric shows the average number of Enterprise Java Beans that have been activated per minute over the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.4 Cache Hits (%)

This metrics indicates the percentage of cache accesses that completed successfully in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.5 Cache Misses (per minute)

This metric shows the average number of EJB cache misses per minute in this application in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.6 Bean Accesses (per minute)

This metrics shows the average number of Pool accesses per minute for this application in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.7 Bean Successes (%)

This metric shows the percentage of EJB pool accesses that were successful for this application in the last 5 minutes.

This metric provides details on the unreferenced modules recycled.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.8 Free Bean Instances

This metric shows the current number of available EJB instances in the free pool.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.9 Bean Destroys (per minute)

This metric shows the average number of EJB destroys per minute for this application in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.10 Bean Access Failures (per minute)

This metric shows the average number of failed pool accesses per minute for this application in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.11 Beans In Use

This metric shows the number of EJB instances currently being used from the free pool.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.12 Bean Transaction Commits (%)

This metric shows the percentage of EJB transactions that were committed for this application during the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.13 Bean Transaction Commits (per minute)

This metric shows the average number of EJB transaction commits per minute for this application in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.14 Bean Transaction Rollbacks (per minute)

This metric shows the average number of EJB transaction rollbacks per minute for this application over the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.15 Bean Transaction Timeouts (per minute)

This metric shows the average number of EJB transaction timeouts per minute for this application over the past 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.16 MDB Messages (per minute)

This metric shows the average number of messages processed by Message Driven Beans (MDBs) per minute for this application in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.17 Requests (per minute)

This metrics shows the average number of servlet and/or JSP invocations per minute in this application in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.18 Request Processing Time (ms)

This metric displays the average amount of time (in milliseconds) spent executing servlets and/or JSPs in this application in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.19 Active Sessions

This metric shows the number of active sessions for this application.

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.20 Work Manager Pending Requests

This metric shows the number of Work Manager requests waiting in the queue.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.21.21 Work Manager Requests (per minute)

This metric shows the average number of Work Manager requests processed per minute for this application over the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.22 Servlet/JSP Metrics

This category provides information about servlet/JSP metrics.

17.22.1 Servlet/JSP - Reloads (per minute)

This metric shows the average number of reloads of the selected servlet or JSP per minute over the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.22.2 Servlet/JSP - Requests (per minute)

This metric shows the average number of invocations of the selected servlet or JSP per minute over the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.22.3 Servlet/JSP - Request Processing Time (ms)

This metric shows the average amount of time (in milliseconds) that was spent executing the selected servlet or JSP over the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.23 Status Metrics

This category provides information about status metrics.

17.23.1 Server Name

This metric shows the name of the current WebLogic server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.23.2 State

This metric shows the current state of the application.

This metric specifies whether this application version is the currently active version. An application can be the only version currently deployed, or it can have more than one version currently deployed, using the side-by-side deployment feature.

If more than one version is deployed, only one version can be active.

Values for this metric can be:

- INACTIVE - it has not been activated yet, or that there is more than one version of the application deployed (using side-by-side deployment) and this one is retiring.

- ACTIVE_ADMIN - the currently active version for administrative channel requests.

- ACTIVE state the currently active version for normal (non-administrative) channel requests.

This metric provides details on the unreferenced modules recycled.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.24 Web Module Metrics

This category provides information about Web module metrics.

17.24.1 Web Module - Requests (per minute)

This metric shows the average number of servlet and JSP invocations per minute for this Web module in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.24.2 Web Module - Request Processing Time (ms)

This metric shows the average amount of time (in milliseconds) spent executing servlets and/or JSPs in this Web module for the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.24.3 Web Module - Active Sessions

This metric shows the number of active sessions for this web module.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

17.25 MDS Metrics

Metrics concerning MDS (Metadata Services)

17.25.1 Metadata Object Gets Per Second

The number of metadata object gets per second.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

High values (100s or 1000s or more) may occur for a heavily used and/or complex application. No action needs to be taken unless application performance is perceived to be too slow, in which case it might be advisable to increase the hardware resources available to the application.

17.25.2 Metadata Object Get Processing Time (seconds)

The average elapsed time in seconds to get a metadata object.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3 Samples

>

Not Defined

Not Defined

The average processing time of each Metadata Object Get is %value% seconds.

User Action

This value should be considerably less than 1 second. If the value is greater than about 0.01, check the cache efficiency metrics (IOs Per Metadata Object Get and IOs Per MO Content Get), and increase the MDS cache size if those metrics indicate a problem. If those metrics are normal, the CPU may be overloaded, meaning the application may need more hardware resources, especially if performance is perceived to be slow.

17.25.3 IOs Per Document Get

The average number of physical IOs per persistence-level document get. This is an indication of the efficiency of the document cache portion of the metadata cache for the application. Ideally it should be much less than 1.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3 Samples

>

Not Defined

Not Defined

The average number of physical IOs per Document Get is %value%.

User Action

If the value is close to or more than 1, this could indicate that the MDS cache for the application is too small. Try increasing the size of the MDS cache to see if it reduces the value of this statistic.

17.25.4 IOs Per MO Content Get

The average number of physical IOs per metadata object XML content retrieval. This is an indication of the efficiency of the metadata cache for the application. Ideally it should be much less than 1.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3 Samples

>

Not Defined

Not Defined

The average number of physical IOs per MO Content Get is %value%.

User Action

If the value is close to or more than 1, this could indicate that the MDS cache for the application is too small. Try increasing the size of the MDS cache to see if it reduces the value of this statistic.

17.25.5 IOs Per Metadata Object Get

The average number of physical IOs per metadata object get. This is an indication of the efficiency of the metadata cache for the application. Ideally it should be much less than one.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3 Samples

>

Not Defined

Not Defined

The average number of physical IOs per Metadata Object Get is %value%.

User Action

If the value is close to or more than 1, this could indicate that the metadata cache for the application is too small. Try increasing the size of the MDS cache to see if it reduces the value of this statistic.

17.25.6 Metadata Updates Per Second

The average number of metadata objects updated per second.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

If the value of this metric is significant compared to the number of HTTP requests serviced per second, it means many users are creating or updating customizations or personalizations using the page composer or, more likely, via inherent changes. In this case, if application performance is perceived be slow, it might be wise to reduce the number of these updates by configuring the application to use a different ADF change manager (so the changes are saved in memory only, not to disk).

No user action.

17.25.7 Metadata Update Processing Time (seconds)

The average elapsed time in seconds taken to update a metadata object.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3 Samples

>

Not Defined

Not Defined

The average processing time of each Metadata Update is %value% seconds.

User Action

If the value of this metric exceeds about 1 second the MDS repository database may need tuning. If the "Metadata Updates Per Second" metric is also high, steps may need to be taken to reduce the number of updates (see user action for that metric).

17.25.8 Response

This category provides information about response metrics

17.25.9 UpDown Status

The up or down status of the application. A value of one (1) indicates that the application is up and running; a value of zero (0) indicates that the application is down.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every Minute

After Every 60 Samples

=

Not Defined

0

The J2EE Application is down

18 Oracle Service Bus

This chapter describes Oracle Service Bus (OSB) metrics.

Oracle Service Bus is a proven market-leading Enterprise Service Bus (ESB) built from the ground up for Service-Oriented Architecture (SOA) lifecycle management that provides foundation capabilities for service discovery and intermediation, rapid service provisioning and deployment, and governance. This service-infrastructure software adheres to the SOA principles of building coarse grained, loosely coupled, and standards-based services, creating neutral container in which business functions may connect service consumers and back-end business services, regardless of underlying infrastructure.

Built to meet exacting standards for reliability, availability, scalability, and performance, Oracle Service Bus uniquely combines the integration capabilities of an ESB with operational service management, into a single enterprise-class software product, with a layered functional architecture.

You can use the All Metrics page of this target to view the metrics that have been collected for this target by Oracle Management Agent.

18.1 Flow Component Resource Details Metrics

This category provides information about the resource type FLOW_COMPONENT.

18.1.1 Average Response Time (Flow Component)

This metric shows the average response time of the resource type (FLOW_COMPONENT) since last collection (75 minutes).

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

Average response time since last collection is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects.

If warning or critical threshold values are currently set for any unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.1.2 Open Instance Count (FLOW_COMPONENT)

This metric shows the open instance count of the resource type (FLOW_COMPONENT) since last collection (75 minutes).

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

Number of opened instances since last collection is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects.

If warning or critical threshold values are currently set for any unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.1.3 Error Instance Count (Flow Component)

This metric shows the error instance count of the resource type (FLOW_COMPONENT) since last collection (75 minutes).

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

Number of faulted instances since last collection is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects.

If warning or critical threshold values are currently set for any unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.2 End Point URI Resource Details Metrics

This category provides information about the resource type URI.

18.2.1 Average Response Time (End Point URI)

This metric shows the average response time of the resource type (URI) since last collection (75 minutes).

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

Average response time since last collection is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects.

If warning or critical threshold values are currently set for any unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.2.2 Open Instance Count (End Point URI)

This metric shows the open instance count of the resource type(URI) since last collection (75 minutes).

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

Number of opened instances since last collection is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects.

If warning or critical threshold values are currently set for any unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects, use the Edit Thresholds page. See "Editing Metrics"for information on accessing the Edit Thresholds page.

18.2.3 Error Instance Count (End Point URI)

This metric shows the error instance count of the resource type (URI) since last collection (75 minutes).

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

Number of faulted instances since last collection is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects.

If warning or critical threshold values are currently set for any unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.3 End Point Operation Resource Details Metrics

This category provides information about the resource type WEBSERVICE_OPERATION.

18.3.1 Average Response Time (End Point Operation)

This metric shows the average response time of the resource type (WEBSERVICE_OPERATION) since last collection (75 minutes).

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

Average response time since last collection is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects.

If warning or critical threshold values are currently set for any unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.3.2 Open Instance Count (End Point Operation)

This metric shows the open instance count of the resource type (WEBSERVICE_OPERATION) since last collection (75 minutes).

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

Number of opened instances since last collection is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects.

If warning or critical threshold values are currently set for any unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.3.3 Error Instance Count (End Point Operation)

This metric shows the error instance count of the resource type (WEBSERVICE_OPERATION) since last collection (75 minutes).

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

Number of faulted instances since last collection is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects.

If warning or critical threshold values are currently set for any unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Service ID", "Service Type", "Resource Name", and "Resource Type" objects, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.4 OSB Service Details Metrics

This category provides metrics related to Oracle Service Bus services. The information is collected every 24 hours.

18.4.1 Contains Sensitive Details

This metric indicates whether or not the service handles sensitive data.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

18.4.2 Created User

This metric shows the name of the user who created the service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

18.4.3 Created Time

This metric shows the time when the service was created.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

18.4.4 End Point URI

This metric shows the end point URI of the service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

18.4.5 Last Modified User

This metric shows the name of the user who last modified the service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

18.4.6 Last Modified Time

This metric shows the time when the service was last modified.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

18.4.7 Protocol

This metric shows the protocol of the service it operates on.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

18.4.8 Status

This metric shows the status of the service. The status can be either Up or Down.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

18.4.9 Version

This metric shows the version of Oracle Service Bus.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 24 Hours

18.5 OSB Service Metrics

This category provides metrics related to proxy services and business services running on Oracle Service Bus.

18.5.1 Average Response Time

This metric shows the average time taken by the service to respond since last collection. The information is collected every 75 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.5.2 Total Average Response Time

This metric shows the total average time taken by the service to respond since the time the server was restarted.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.5.3 Open Instance Count

This metric shows the number of open instances of the service since last collection. The information is collected every 75 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.5.4 Total Open Instance Count

This metric shows the total number of messages handled by this service since the time the server was restarted.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Service ID" object.

If warning or critical threshold values are currently set for any "Service ID" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Service ID" object, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.5.5 Error Instance Count

This metric shows the number of errored instances for the service since last collection. The information is collected every 75 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.5.6 Total Error Instance Count

This metric shows the total number of error instances occurred on this service since the time the server was restarted.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.5.7 Failure Rate

This metric shows the failure rate of messages since last collection.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.5.8 Maximum Response Time

This metric shows the maximum time taken by this service to respond since the time the server was restarted.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.5.9 Minimum Response Time

This metric shows the minimum time taken by this service to respond since the time the server was restarted.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.5.10 Service Name

This metric shows the name of the proxy or business service running on Oracle Service Bus.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.5.11 Path

This metric shows the current path to the project and resource directory hierarchy in the configuration.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.5.12 Project Name

This metric shows the name of the project associated with Oracle Service Bus.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.5.13 Service Type

This metric shows the type of service running on Oracle Service Bus. The service type can be Proxy or Business.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.5.14 WebService Security Violation Instance Count

This metric shows the number of web service security violation caused by the service since last collection. The information is collected every 75 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.5.15 Total WebService Security Violation Instance Count

This metric shows the total number of web service security violations caused by the service since the time the server was restarted.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.6 OSB Proxy Service Metrics

This category provides metrics related to proxy services and business services running on Oracle Service Bus.

18.6.1 Average Response Time

This metric shows the average time taken by the service to respond since last collection. The information is collected every 75 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

Average response time since last collection is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Service ID" object.

If warning or critical threshold values are currently set for any "Service ID" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Service ID" object, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.6.2 Total Average Response Time

This metric shows the total average time taken by the service to respond since the time the server was restarted.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.6.3 Open Instance Count

This metric shows the number of open instances of the service since last collection. The information is collected every 75 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

Number of opened instances since last collection is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Service ID" object.

If warning or critical threshold values are currently set for any "Service ID" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Service ID" object, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.6.4 Total Open Instance Count

This metric shows the total number of messages handled by this service since the time the server was restarted.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.6.5 Error Instance Count

This metric shows the number of errored instances for the service since last collection. The information is collected every 75 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

Number of faulted instances since last collection is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Service ID" object.

If warning or critical threshold values are currently set for any "Service ID" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Service ID" object, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.6.6 Total Error Instance Count

This metric shows the total number of error instances occurred on this service since the time the server was restarted.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.6.7 Failure Rate

This metric shows the failure rate of messages since last collection.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

Failure Rate since last collection is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Service ID" object.

If warning or critical threshold values are currently set for any "Service ID" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Service ID" object, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.6.8 Maximum Response Time

This metric shows the maximum time taken by this service to respond since the time the server was restarted.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.6.9 Minimum Response Time

This metric shows the minimum time taken by this service to respond since the time the server was restarted.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.6.10 Service Name

This metric shows the name of the proxy or business service running on Oracle Service Bus.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.6.11 Path

This metric shows the current path to the project and resource directory hierarchy in the configuration.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.6.12 Project Name

This metric shows the name of the project associated with Oracle Service Bus.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.6.13 Service Type

This metric shows the type of service running on Oracle Service Bus. The service type can be Proxy or Business.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.6.14 WebService Security Violation Instance Count

This metric shows the number of web service security violation caused by the service since last collection. The information is collected every 75 minutes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

Total number of webservice security violation instances are %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Service ID" object.

If warning or critical threshold values are currently set for any "Service ID" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Service ID" object, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.6.15 Total WebService Security Violation Instance Count

This metric shows the total number of web service security violations caused by the service since the time the server was restarted.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.7 OSB Service Dependency Metrics

This category provide metrics related to the services that are dependent on a particular service.

18.7.1 Dependent Service ID

This metric shows the ID of the service that is dependent on this particular service.

18.8 Response

This category provides status metrics for Oracle Service Bus.

18.8.1 Status

This metric shows the current status of Oracle Service Bus. The status can be either Up or Down.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 1 Minute

Not Defined

0

OSB target status is down.

18.9 SLA Alert Metrics

This category provides information about the SLA alerts generated in the OSB console.

18.9.1 Service Name

This metric shows the name of the service (Proxy/Business).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.9.2 Project Name

This metric shows the name of the project.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.9.3 SLA Severity Critical Alerts (per min)

This metric shows the number of SLA severity alerts since last collection.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

The OSB Severity critical alerts are %value% (per minute)

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Service ID" object.

If warning or critical threshold values are currently set for any "Service ID" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Service ID" object, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.9.4 Total SLA Severity Critical Alerts

This metric shows the total number of SLA severity alerts since the time the server restarted(Severity Level - critical).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.9.5 SLA Severity Fatal Alerts (per min)

This metric shows the number of SLA severity alerts since last collection.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

The OSB Severity fatal alerts are %value% (per minute)

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Service ID" object.

If warning or critical threshold values are currently set for any "Service ID" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Service ID" object, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.9.6 Total SLA Severity Fatal Alerts

This metric shows the total number of SLA severity alerts since the time the server was restarted (Severity Level - fatal).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.9.7 SLA Severity Major Alerts (per min)

This metric shows the number of SLA severity alerts since last collection.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

The OSB Severity major alerts are %value% (per minute)

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Service ID" object.

If warning or critical threshold values are currently set for any "Service ID" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Service ID" object, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.9.8 Total SLA Severity Major Alerts

This metric shows the total number of SLA severity alerts since the time the server was restarted (Severity Level - Major).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.9.9 SLA Severity Minor Alerts (per min)

This metric shows the number of SLA severity alerts since last collection.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

The OSB Severity minor alerts are %value% (per minute).

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Service ID" object.

If warning or critical threshold values are currently set for any "Service ID" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Service ID" object, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.9.10 Total SLA Severity Minor Alerts

This metric shows the total number of SLA severity alerts since the time the server was restarted(Severity Level - Minor).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.9.11 SLA Severity Warning Alerts (per min)

This metric shows the number of SLA severity alerts since last collection.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 75 Minutes

Not Defined

Not Defined

The OSB Severity warning alerts are %value% (per minute).

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Service ID" object.

If warning or critical threshold values are currently set for any "Service ID" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Service ID" object, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

18.9.12 Total SLA Severity Warning Alerts

This metric shows the total number of SLA severity alerts since the time the server was restarted(Severity Level - Warnings).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

18.9.13 Service Type

This metric shows the type of service either Proxy or Business.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

19 Oracle SOA Infra

This chapter describes Oracle SOA Infra metrics.

Note:
Metrics related to throughput and instances are shown with a delay of 15 minutes from the time of invocation.

19.1 B2B Active Entities Metrics

This category provides information about B2B active entities metrics.

19.1.1 Number of Active Agreements

This metric shows the number of active agreements.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.1.2 Number of Active Documents

This metric shows the number of active documents.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.1.3 Number of Active Trading Partners

This metric shows the number of active trading partners.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.2 B2B Document Metrics Table

This category provides information about B2B Document Metrics Table metrics.

19.2.1 Number of Inbound Messages

This metric shows the number of inbound messages.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.2.2 Number of inbound message faults

This metric shows the number of inbound message faults.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.2.3 Inbound Message Size (KB)

This metric shows the inbound message size.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.2.4 Inbound Messages processing time

This metric shows the processing time for inbound messages.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.2.5 B2B Document Name

This metric shows the B2B document name.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.2.6 Number of Outbound Messages

This metric shows the number of outbound messages.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.2.7 Number of outbound message faults

This metric shows the number of outbound message faults.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.2.8 Outbound Message Size (KB)

This metric shows the outbound message size.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.2.9 Outbound Messages processing time

This metric shows the processing time for outbound messages.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.3 B2B Inbound Endpoint Metrics

This category provides information about B2B Inbound Endpoint metrics.

19.3.1 B2B Inbound Endpoint Status

This metric shows the status of the B2B inbound endpoint.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.4 B2B Outbound Endpoint Metrics

This category provides information about B2B Outbound Endpoint metrics.

19.4.1 B2B Outbound Endpoint Status

This metric shows the status of the B2B outbound endpoint.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.5 B2B Trading Partner Metrics

This category provides information about B2B Trading Partner metrics.

19.5.1 Number of inbound messages

This metric shows the number of inbound messages for B2B trading partners.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.5.2 Number of inbound message faults

This metric shows the number of inbound message faults for B2B trading partners.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.5.3 Inbound Message Size (KB)

This metric shows the inbound size of messages for B2B trading partners.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.5.4 Processing time of Inbound Messages

This metric shows the processing time of inbound messages for B2B trading partners.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.5.5 Trading partner name

This metric shows the name of the trading partner.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.5.6 Number of outbound messages

This metric shows the number of outbound messages for B2B trading partners.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.5.7 Number of outbound message faults

This metric shows the number of outbound message faults for B2B trading partners.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.5.8 Outbound Message Size (KB)

This metric shows the outbound size of messages for B2B trading partners.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.5.9 Processing time of outbound messages

This metric shows the processing time of outbound messages for B2B trading partners.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.6 BPEL Engine Requests Rate Metric Table

Displays the BPEL Engine request related metrics

19.6.1 Active request throughput in the last 5 minutes

This metric shows the active request throughput in the last five minutes in the BPEL service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.6.2 Last active request value

This metric shows the value for the last active request in the BPEL service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.6.3 Scheduled request throughput in the last 5 minutes

This metric shows the scheduled request throughput for the last five minutes in the BPEL service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.6.4 Last scheduled request value

This metric shows the value for the last scheduled request in the BPEL service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.7 Business Rules Engine Cache Metrics Table

Displays the business rules service engine cache metrics.

19.7.1 Total Access Count since server startup

This metric shows the total access count since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.7.2 Last value of access count

This metric shows the last value of the access count in the business rules service engine cache.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.7.3 Total Count since server startup

This metric shows the total count of objects in the cache since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.7.4 Last value of total count

This metric shows the last value of the total count.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.8 Business Rule Engine Request Breakdown Rate Metric Table

Displays the path of a message/request within the service engine.

19.8.1 Request count since server startup

This metric shows the count of objects in the cache since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.8.2 Throughput of requests in the last 5 minutes

This metric shows the request message throughput in the last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.8.3 Last value of request

This metric shows the value of the last request message.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.8.4 Average request processing time

This metric shows the average request processing time for messages.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.8.5 Number of completed requests

This metric shows the number of completed instances.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.8.6 Response

Shows if the SOA server is available or not.

19.8.7 UpDown Status

This metric shows the current status of the SOA server. A value of 1 indicates the server is running. A value of 0 indicates the server is down.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every Minute

After Every 60 Samples

=

Not Defined

0

1

The SOA Infrastructure instance is down

19.9 SOA Infrastructure Bindings Rate Metric Table

Shows metrics of the SOA Bindings.

19.9.1 Active request throughput in the last 5 minutes

This metric shows the active request throughput in the last five minutes in the binding component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.9.2 Number of faults since server startup

This metric shows the number of faults in the binding component since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.9.3 Average request processing time

This metric shows the average request processing time for the binding component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.9.4 Total number of processed requests since server startup

This metric shows the total number of processed requests since server startup in the binding component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.10 SOA Composite Bindings/References Rate Metric

This category provides information about SOA composite bindings/references rate metrics.

19.10.1 Total number of faults since server start

This metric shows the total number of faults since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.10.2 Throughput of faults in the last 5 minutes

This metric shows the throughput for faults in the last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.10.3 Average Incoming Messages Processing Time

This metric shows the average processing time for incoming messages.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.10.4 Total completed incoming messages since server start

This metric shows total number of completed incoming messages since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.10.5 Incoming messages throughput in the last 5 minutes

This metric shows the throughput for incoming messages in the last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.10.6 Total Incoming Messages Processing Time

This metric shows the total processing time for incoming messages.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.10.7 Total Incoming Message processing time

This metric shows the total processing time for incoming message.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.10.8 Total number of incoming messages since server start

This metric shows the total number of incoming messages since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.10.9 Incoming message throughput in the last 5 minutes

This metric shows the throughput for incoming messages in the last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.10.10 Average Outbound Messages Processing Time

This metric shows the average processing time for outbound messages.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.10.11 Total completed outgoing messages since server start

This metric shows the total number of completed, outgoing messages since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.10.12 Outbound messages throughput in the last 5 minutes

This metric shows the throughput for outbound messages in the last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.10.13 Total Outbound Messages Processing Time since server start

This metric shows the total processing time for outbound messages since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.10.14 Total Outbound Message processing time

This metric shows the total processing time for outbound messages.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.10.15 Total number of outgoing messages since server start

This metric shows the total number of outgoing messages since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.10.16 Outbound message events throughput in the last 5 minutes

This metric shows the throughout for outbound message events in the last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11 BPEL Dispatcher Rate Metric Table

Displays throughput metrics related to the BPEL dispatcher.

19.11.1 Total number of messages processed per thread since server startup

This metric shows the total number of messages processed per thread in the BPEL dispatcher since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.2 Throughput of total messages in the last 5 minutes

This metric shows the total message throughput in the BPEL dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.3 Last value of total message

This metric shows the last value of all messages in the BPEL dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.4 Throughput of average thread allocation time in the last 5 minutes

This metric shows the throughput for the average thread allocation time in the last five minutes in the BPEL dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.5 Last value of average thread allocation time

This metric shows the last value of average thread allocation time in the BPEL dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.6 Throughput of average thread lifetime in the last 5 minutes

This metric shows the throughput for the lifetime of the average thread in the last five minutes in the BPEL dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.7 Last value of average thread lifetime

This metric shows the last value for the lifetime of the average thread in the BPEL dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.8 Throughput of maximum threads in the last 5 minutes

This metric shows the throughput for maximum threads in the last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.9 Last value of maximum thread

This metric shows the last value for the maximum thread in the BPEL dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.10 Throughput of minimum threads in the last 5 minutes

This metric shows the throughput for minimum threads in the last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.11 Last value of minimum thread

This metric shows the last value for the minimum thread in the BPEL dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.12 Number of active threads since server startup

This metric shows the number of active threads since server startup in the BPEL dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.13 Throughput of thread count in the last 5 minutes

This metric shows the thread count throughput in the last five minutes in the BPEL dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.14 Last value of thread count

This metric shows the last thread count value in the BPEL dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.15 Number of thread highs since server startup

This metric shows the number of high thread levels in the BPEL dispatcher since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.16 Throughput of thread high in the last 5 minutes

This metric shows high levels of thread throughput in the last five minutes in the BPEL dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.17 Last value of thread high

This metric shows the last high value of the thread in the BPEL dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.18 Number of pending threads since server startup

This metric shows the number of pending threads in the BPEL dispatcher since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.19 Throughput of pending threads in the last 5 minutes

This metric shows the throughput for pending threads in the last five minutes in the BPEL dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.20 Last value of pending thread

This metric shows the last value of the pending thread in the BPEL dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.21 Total number of threads since server startup

This metric shows the total number of threads in the BPEL dispatcher since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.22 Throughput of total threads in the last 5 minutes

This metric shows the throughput for all threads in the last five minutes in the BPEL dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.11.23 Last value of total thread metric

This metric shows the last value for the total thread metric in the BPEL dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.12 BPMN Dispatcher Rate Metric Table

Throughput of total messages in the last 5 minutes.

19.12.1 Last value of maximum thread

This metric shows the last value for the maximum thread in the BPMN dispatcher

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.12.2 Number of active threads since server startup

This metric shows the number of active threads since server startup in the BPMN dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.12.3 Throughput of thread count in the last 5 minutes

This metric shows the thread count throughput in the last five minutes in the BPMN dispatcher.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.13 SOA Mediator Engine Cache

This category provides information about SOA Mediator Engine Cache metrics.

19.13.1 Last value of metadata cache

This metric shows the last value of the metadata cache in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.13.2 Last value of transformation cache

This metric shows the last value of transformation cache in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.13.3 SOA Mediator Engine Requests

This metric shows the callback requests in the mediator service engine

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.13.4 Callback Requests

This metric shows the callback requests in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.13.5 Delay Requests

This metric shows the delayed requests in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.13.6 Dequeue Requests

This metric shows the dequeued requests in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.13.7 Timeout Requests

This metric shows the timed out requests in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14 SOA Mediator Engine Request Breakdown Rate Metric Table

Displays the path taken by a request in the Mediator Service Engine and the time spent

19.14.1 enqueue-phase.active

This metric shows the active enqueued phases in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.2 Avg Enqueue Time (ms)

This metric shows the average time spent on enqueuing in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.3 Enqueued

This metric shows the completed enqueuing phases in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.4 Throughput of Enqueue phase

This metric shows the throughput for enqueuing in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.5 Total Enqueue Time (ms)

This metric shows the total enqueuing time in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.6 invoke-phase.active

This metric shows the active invocations in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.7 Avg Invoke Time (ms)

This metric shows the average invocation time in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.8 Invoked

This metric shows the completed invocations in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.9 Throughput of Invoke phase

This metric shows the throughput for invocations in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.10 Total Invoke Time (ms)

This metric shows the total invocation time in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.11 invokeOneway-phase.active

This metric shows the active one-way invocations in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.12 Avg Oneway Invoke Processing Time (ms)

This metric shows the average processing time for one-way invocations in milliseconds in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.13 Oneway Invocations

This metric shows the completed one-way invocations in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.14 Throughput of Oneway Invocations

This metric shows the throughput for one-way invocations in the mediator service component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.15 Total Oneway Invocation Time (ms)

This metric shows the total time for one-way invocations in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.16 publish-phase.active

This metric shows the active publishing phases in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.17 Avg Publication Time (ms)

This metric shows the average publication times in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.18 Publications

This metric shows the completed publishing phases in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.19 Throughput of Publication phase

This metric shows the throughput for publications in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.20 Total Publication Time (ms)

This metric shows the total publication times in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.21 transformation-phase.active

This metric shows the active transformation phases in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.22 Avg Transformation Time (ms)

This metric shows the average time for transformations in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.23 Transformations

This metric shows the completed transformations in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.24 Throughput of Transformations

This metric shows the throughput for transformations in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.14.25 Total Transformation Time (ms)

This metric shows the total time for transformations in the mediator service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15 SOA Infra Mesh

Displays the SOA server mesh metrics

19.15.1 Number of active messages in the mesh

This metric displays the number of active messages in the SOA server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15.2 Total number of messages in the mesh since server startup

This metric shows the total number of messages in the SOA server since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15.3 Number of faulted messages in the mesh

This metric displays the number of faulted messages in the SOA server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15.4 Throughput of messages in the mesh in the last 5 minutes

This metric displays the throughput for messages in the SOA server in the last 5 minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15.5 SOA Infra Mesh Message Count Table

This metric shows the soa infra mesh message count.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15.6 Total number of messages in the mesh since server startup

This metric shows the total number of messages in the service infrastructure since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15.7 Mesh Name

This metric shows service infrastructure performance.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15.8 Throughput of faulted asynchronous messages in the last 5 minutes

This metric shows the throughput for faulted asynchronous messages in the last five minutes in the SOA server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15.9 Number of active asynchronous messages

This metric shows the number of active, asynchronous messages in the SOA server at this time.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15.10 Average processing time of asynchronous messages

This metric shows the average processing time for asynchronous messages in the SOA server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15.11 Number of completed asynchronous messages

This metric shows the number of completed asynchronous messages in the SOA server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15.12 Throughput of asynchronous messages in the last 5 minutes

This metric shows the throughput for asynchronous messages in the last five minutes in the SOA server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15.13 Total processing time of asynchronous messages

This metric shows the total processing time for asynchronous messages in the SOA server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15.14 Throughput of faulted synchronous messages in the last 5 minutes

This metric shows the throughput for faulted, synchronous messages in the last five minutes in the SOA server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15.15 Number of active synchronous messages

This metric shows the number of active, synchronous messages in the SOA server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15.16 Average processing time of synchronous messages

This metric shows the average processing time for synchronous messages in the SOA server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15.17 Number of completed synchronous messages

This metric displays the number of completed, synchronous messages in the SOA server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15.18 Throughput of synchronous messages in the last 5 minutes

This metric displays the throughput for synchronous messages in the last five minutes in the SOA server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.15.19 Total processing time of synchronous messages

This metric shows the total processing time for synchronous messages in the SOA server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16 SOA Message Processing Rate Metric Table

Displays the metrics related to message processing in the service engines

19.16.1 Total number of active requests since server startup

This metric shows the total number of active requests since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.2 Throughput of the active requests in the last 5 minutes

This metric shows message processing details in the service engines.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.3 Last value of active request

This metric shows the last value of the active request.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.4 Total number of BPEL messages since startup

This metric shows the total number of BPEL messages since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.5 Engine Name

This metric shows the BPEL service engine name.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.6 Total number of decision service messages since startup

This metric shows the total number of decision service messages since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.7 Engine Name

This metric shows the decision service engine name.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.8 Number of faults since server startup

This metric shows the number of faults occurring since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.9 Throughput of faulted requests in the last 5 minutes

This metric shows the throughput of faulted requests in the last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.10 Rate of processing faulted requests

This metric shows the processing rate for faulted requests.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.11 Total number of mediator messages since startup

This metric shows the total number of mediator messages since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.12 Engine Name

This metric shows the mediator service engine name.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.13 Total number of messages since server startup

This metric shows the total number of messages since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.14 Total number of asynchronous requests since server startup

This metric shows the total number of asynchronous requests since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.15 Throughput of asynchronous invocations in the last 5 minutes

This metric shows the throughput of asynchronous invocations in the last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.16 Rate of processing asynchronous invocations

This metric shows processing rate for asynchronous invocations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.17 Average asynchronous message processing time since server startup

This metric shows the average processing time for asynchronous messages since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.18 Total number of synchronous requests since server startup

This metric shows the total number of synchronous requests since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.19 Synchronous invocations throughput in the last 5 minutes

This metric shows the throughput for synchronous invocations in the last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.20 Rate of processing synchronous invocations

This metric shows the processing rate for synchronous invocations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.21 Average synchronous message processing time since server startup

This metric shows the average processing time for synchronous messages since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.22 Total number of workflow messages since startup

This metric shows the total number of human workflow messages since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.16.23 Engine Name

This metric shows the human workflow service engine name.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.17 Total Composite Instances

Shows the instance metrics of composites deployed on the SOA server

19.17.1 Total number of instances since server startup

This metric shows the total number of composite instances created since server startup. This count spans across composites deployed on the SOA server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.17.2 Domain Name

This metric shows the instance metrics of composites deployed on the SOA server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.18 Total Composite Faults

Displays the metrics of the composite faults

19.18.1 Total number of faults since server startup

This metric shows the total number of faults across all composite instances since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

19.19 Workflow Request Breakdown Rate Metrics

Shows the various services used by the Workflow Service Engine and their usage metrics.

19.19.1 Number of invocations since server startup

This metric shows the total number of invocations in the human workflow service engine since server startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.19.2 Service Name

This metric shows the name of the internal service used by the human workflow service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.19.3 Number of active requests

This metric shows the number of active requests in the human workflow service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.19.4 Average request processing time

This metric shows the average request processing time in the human workflow service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

19.19.5 Number of completed requests

This metric shows the total number of completed requests in the human workflow service engine.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

20 SOA Composite

This chapter describes Oracle SOA Composite metrics.

20.1 SOA Composite B2B Inbound Metrics

Displays the metrics for the Composite B2B Inbound messages.

20.1.1 InBound Message Count

This metric displays the number of inbound messages in B2B trading partners.

20.1.2 Inbound Messages Faults

This metric displays the number of faults in inbound messages in the B2B binding.

20.1.3 Inbound Messages Size

This metric displays the inbound message size in the B2B binding.

20.1.4 Inbound Message Processing Time

This metric displays the time taken to process inbound messages by the B2B binding.

20.1.5 ServerName

This metric shows the name of the server for inbound messages in B2B trading partners.

20.1.6 Total Outbound Messages Count

This metric displays the total number of outbound messages in the B2B binding.

20.2 SOA Composite B2B Outbound Metrics

Displays the B2B outbound message metrics.

20.2.1 Name

This metric displays the name

20.2.2 OutBound Message Count

This metric displays the number of outbound messages in the B2B binding.

20.2.3 Outbound Messages Faults

This metric displays the number of faults in outbound messages in the B2B binding.

20.2.4 Outbound Messages Size

This metric displays the size of outbound messages in the B2B binding.

20.2.5 Outbound Message Processing Time

This metric displays the processing time for outbound messages in the B2B binding.

20.2.6 ServerName

This metric shows the name of the server for B2B outbound messages.

20.2.7 Total Outbound Messages Count

This metric displays the total number of outbound messages in the B2B binding.

20.3 BPEL Activity Time Distribution

Shows the information related to the BPEL activity-time distribution.

20.3.1 Average Execution Time (ms)

This metric shows the average time it took for this BPEL activity to execute.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.3.2 Activity Count

This metric shows the number of times this BPEL activity has been invoked.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.3.3 Activity Name

This metric shows the name of the BPEL activity whose data is being shown.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.3.4 Server Name

This metric shows the name of the J2EE container in which the SOA composite application is deployed.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.4 SOA Composite - Response Metrics

Indicates whether the SOA composite application is available to accept requests.

20.4.1 Status

This metric shows the current state of the SOA composite application. A value of 1 indicates the application is available and a value of 0 indicates the application is not available.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every Minute

After Every 60 Samples

=

Not Defined

0

The J2EE Application is down

20.5 SOA Composite Bindings/References Rate Metric

Displays metrics about the SOA bindings.

20.5.1 Total number of faults since server start

This metric shows the total number of faulted messages in the binding.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.5.2 Average Incoming Messages Processing Time

This metric shows the average processing time of incoming messages in the binding.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.5.3 Total number of incoming messages since server start

This metric shows the total number of incoming messages in the binding.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.5.4 Incoming message throughput in last 5 minutes

This metric shows the throughput for inbound messages in the binding.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.5.5 Average Outbound Messages Processing Time

This metric shows the average processing time of outbound messages in the binding.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.5.6 Total number of outgoing messages since server start

This metric shows the total number of outbound messages in the binding.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.5.7 Outbound message throughput in last 5 minutes

This metric shows the throughput for outbound messages in the binding.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.6 SOA Component References

Shows the metrics of the SOA component references.

20.6.1 Average Message Processing Time (secs) since server start up

This metric shows the average time taken by the reference to respond to invocations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.6.2 Number of Faults

This metric shows the number of faults encountered when this reference was invoked.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.6.3 Number of Messages

This metric shows the number of times that this reference has been invoked by the SOA component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.6.4 Average Message Processing Time (secs) in last 5 mins

This metric shows the total time taken by the reference to respond to an invocation.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.6.5 Reference Name

This metric shows the SOA component whose reference is being shown.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.6.6 Component References

This metric shows the SOA component reference name.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.6.7 Component Type

This metric indicates that the current type is a component whose references are being listed.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.7 SOA Component Rollup Metric

Shows all SOA component throughput metrics.

20.7.1 Business faults throughput in the last 5 minutes

This metric shows the throughput for messages with business faults in this SOA component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.7.2 Number of active faulted instances

This metric shows the number of active, faulted messages in this SOA component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.7.3 Average processing time for faulted instances

This metric shows the average time spent processing faulted messages in this SOA component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.7.4 Number of faulted instances

This metric shows the number of faulted messages in this SOA component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.7.5 Throughput of faulted instances in the last 5 minutes

This metric shows the throughput for faulted messages in this SOA component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.7.6 Total time spent on processing faulted instances

This metric shows the time spent processing faulted messages in this SOA component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.7.7 Total average faulted processing time

This metric shows the total time spent processing faulted messages in this SOA component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.7.8 Instance throughput in the last 5 minutes

This metric shows the throughput for incoming messages in the SOA component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.7.9 Server Name

This metric shows the SOA component throughput for the server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.7.10 Number of active successful instances

This metric shows the number of successful, active messages in this SOA component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.7.11 Average processing time for successful instances

This metric shows the average time spent processing successful messages in this SOA component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.7.12 Number of successful instances

This metric shows the number of successfully completed messages in this SOA component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.7.13 Throughput of successful instances in the last 5 minutes

This metric shows the throughput for successful messages in this SOA component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.7.14 Total time spent on processing successful instances

This metric shows the time spent processing successful messages in this SOA component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.7.15 Total average successful processing time

This metric shows the total time spent processing successful messages.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.7.16 System faults throughput in the last 5 minutes

This metric shows the throughput for messages with system faults in this SOA component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.7.17 Total faults throughput in the last 5 minutes

This metric shows the throughput for all faulted messages in this SOA component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.8 SOA Composite - Rate Metrics

Displays the throughput metrics for a SOA composite.

20.8.1 Instance throughput in the last 5 minutes

This metric shows the total throughput for the composite instances.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.8.2 Asynchronous message event throughput in the last 5 minutes

This metric shows the throughput for asynchronous messages.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.8.3 Average asynchronous message Processing time

This metric shows the average processing time of asynchronous messages in the SOA composite.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.8.4 Asynchronous messages throughput in the last 5 minutes

This metric shows the throughput of asynchronous messages in this SOA composite.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.8.5 Total asynchronous message processing time

This metric shows the total processing time of asynchronous messages in the SOA composite.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.8.6 Synchronous message event throughput in the last 5 minutes

This metric displays the throughput for requests to the SOA composite.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.8.7 Average synchronous message processing time

This metric shows the average processing time of synchronous messages in this SOA composite.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.8.8 Synchronous messages throughput in the last 5 minutes

This metric shows the throughput for all synchronous messages to this composite.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.8.9 Total synchronous message processing time

This metric shows the total processing time of synchronous messages for this SOA composite.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.8.10 Server Name

This metric shows the name of the server on which the SOA composite application revision is deployed.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9 Mediator Case

Displays metrics about the mediator case.

20.9.1 Average processing time of invocations

This metric shows the average processing time of invocations in the mediator component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9.2 Invocation throughput in the last 5 minutes

This metric shows the throughput for messages in the mediator case.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9.3 Total processing time for invocations

This metric shows the total processing time of invocations in the mediator component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9.4 Failed filtered messages throughput in the last 5 minutes

This metric shows the throughput for the failed, filtered message in the mediator case.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9.5 Average processing time of faulted cases

This metric shows the average processing time of faulted cases in the mediator component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9.6 Number of faulted cases

This metric shows the number of faulted cases in this mediator component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9.7 Faulted case throughput in the last 5 minutes

This metric shows the throughput of faulted cases in this mediator component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9.8 Total processing time for faulted cases

This metric shows the total processing time for faulted cases in the mediator component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9.9 Filtered messages throughput in the last 5 minutes

This metric shows the throughput for the filtered messages of the mediator case.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9.10 Invocation Count throughput in the last 5 minutes

This metric shows the throughput for the invocation count of the mediator case.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9.11 Component Type

This metric shows the component type, which in this case is always mediator.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9.12 Composite Label

This metric shows the label of the SOA composite.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9.13 Case Target

This metric shows the case target of the mediator.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9.14 Mediator Flow

This metric shows the state of the mediator flow.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9.15 Flow Type

This metric shows the flow type of the mediator component case.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9.16 Average processing time of successful cases

This metric shows the average processing time of successful cases.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9.17 Number of successful cases

This metric shows the number of successful cases in this mediator component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9.18 Successful case throughput in the last 5 minutes

This metric shows the throughput for successful cases in this mediator component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.9.19 Total processing time for successful cases

This metric shows the total processing time for successful cases in this mediator component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.10 Mediator Flow Metric

Displays metrics about the Mediator component's flow.

20.10.1 Deferred message count throughput in last 5 minutes

This metric shows the throughput for the deferred message count in the mediator component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.10.2 Failed filter case throughput in last 5 minutes

This metric shows the throughput for the failed filter case in the mediator component.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.10.3 Average faulted instance processing time

This metric shows the average time spent processing faulted messages.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.10.4 Faulted instances throughput in last 5 minutes

This metric shows the throughput for faulted messages.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.10.5 Total faulted instance processing time

This metric shows the total time spent processing faulted messages.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.10.6 Instance throughput in last 5 minutes

This metric shows the throughput for the mediator instances.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.10.7 Component Type

This metric shows the component type, which in this case is always mediator.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.10.8 Composite Label

This metric shows the SOA composite label in which the mediator component is packaged.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.10.9 Flow Type

This metric shows the flow type for the mediator.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.10.10 Average successful instance processing time

This metric shows the average time spent processing successful messages.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.10.11 Successful instances throughput in last 5 minutes

This metric shows the successful instance processing time.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.10.12 Total successful instance processing time

This metric shows the total time spent processing successful messages.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

20.11 Total Composite Instances

Displays metrics about the total composite instances.

20.11.1 Total number of composite instances since server startup

This is the number of composite instances since server startup

20.11.2 Domain Name

The domain name

20.12 Total Composite Faults

Displays metrics about total composite faults.

20.12.1 Total number of faults since server startup

This is the number of faults recorded since server startup.

20.13 Reference Binding Rollup

This provides details on the references exposed by the composite

20.13.1 Average Incoming Messages Processing Time

This metric shows the average incoming messages processing time.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.2 Average Incoming Messages Processing Time (ms)

This metric shows the average incoming messages processing time in milliseconds.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.3 Average Outbound Messages Processing Time

This metric shows the average outbound messages processing time.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.4 Average Outbound Messages Processing Time (ms)

This metric shows the average outbound messages processing time in milliseconds.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.5 Binding - Error rate

This metric shows the binding error rate.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.6 Composite Revision

This metric shows the revision of the composite.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.7 Composite Name

This metric shows the composite name.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.8 Domain Name

This metric shows the domain name.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.9 End Point URL

This metric shows the end point URL.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.10 Incoming message throughput in last 5 minutes

This metric shows the incoming message throughput in last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.11 Incoming message throughput in last 5 minutes (sec)

This metric shows the incoming message throughput in last five minutes, expressed in seconds.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.12 Outbound message throughput in last 5 minutes

This metric shows the outbound message throughput in the last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.13 Outbound message throughput in last 5 minutes (sec)

This metric shows the outbound message throughput in the last five minutes, expressed in seconds.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.14 Reference Name

This metric shows the reference name.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.15 Reference Type

This metric shows the reference type.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.16 Total number of faults since last collection

This metric shows the total number of faults since last collection.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.17 Total number of faults since startup

This metric shows the total number of faults since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.18 Total number of incoming messages Since Last Collection

This metric shows the total number of incoming messages since last collection.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.19 Total number of incoming messages since startup

This metric shows the total number of incoming messages since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.20 Total number of outgoing messages since last collection

This metric shows the total number of outgoing messages since last collection.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.21 Total number of outgoing messages since startup

This metric shows the total number of outgoing messages since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.22 WSDL Port

This metric shows the WSDL port.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.13.23 WSDL URL of the service

This metric shows the WSDL URL of the service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14 Service Binding Rollup

This provides details on the services exposed by the composite.

20.14.1 Average Incoming Messages Processing Time

This metric shows the average incoming messages processing time.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.2 Average Incoming Messages Processing Time (ms)

This metric shows the average incoming messages processing time in milliseconds.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.3 Average Outbound Messages Processing Time

This metric shows the average outbound messages processing time.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.4 Average Outbound Messages Processing Time (ms)

This metric shows the average outbound messages processing time in milliseconds.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.5 Binding - Error rate

This metric shows the binding error rate.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.6 Composite Revision

This metric shows the revision of the composite.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.7 Composite Name

This metric shows the composite name.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.8 Domain Name

This metric shows the domain name.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.9 End Point URL

This metric shows the end point URL.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.10 Incoming message throughput in last 5 minutes

This metric shows the incoming message throughput in last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.11 Incoming message throughput in last 5 minutes (sec)

This metric shows the incoming message throughput in last five minutes, expressed in seconds.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.12 Outbound message throughput in last 5 minutes

This metric shows the outbound message throughput in the last five minutes.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.13 Outbound message throughput in last 5 minutes (sec)

This metric shows the outbound message throughput in the last five minutes, expressed in seconds.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.14 Reference Name

This metric shows the reference name.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.15 Reference Type

This metric shows the reference type.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.16 Total number of faults since last collection

This metric shows the total number of faults since last collection.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.17 Total number of faults since startup

This metric shows the total number of faults since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.18 Total number of incoming messages Since Last Collection

This metric shows the total number of incoming messages since last collection.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.19 Total number of incoming messages since startup

This metric shows the total number of incoming messages since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.20 Total number of outgoing messages since last collection

This metric shows the total number of outgoing messages since last collection.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.21 Total number of outgoing messages since startup

This metric shows the total number of outgoing messages since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.22 WSDL Port

This metric shows the WSDL port.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

20.14.23 WSDL URL of the service

This metric shows the WSDL URL of the service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

21 Forms

This chapter describes Oracle Forms metrics.

21.1 Forms Resource Usage

This metric measures the resources consumed by all the Forms sessions.

21.1.1 CPU Usage (%)

This metric specifies the percentage CPU usage of all the Forms sessions.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 10.3.1

Every 5 Minutes

80

90

cpu.component is %value% and has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

User Action

Navigate to the host Home page in the Fusion Middleware Control and review the top processes to see if you can identify which processes are consuming the most CPU. Or, navigate to the host Performance page in the Fusion Middleware Control and view the processes that are consuming the most CPU and take appropriate action.

21.1.2 Total CPU Time (millisec)

This metric specifies the total CPU Time (in millisec) consumed by all the Forms sessions.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

Release 10.3.1

Every 5 Minutes

User Action

No user action required.

21.1.3 instname.value

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

Release 10.3.1

Every 5 Minutes

User Action

No user action required.

21.1.4 Total Private Memory (KB)

This metric measures the total memory (in KB) consumed by all the Forms sessions. This is not the actual private memory on Linux but the Resident Set Size (RSS). RSS is the number of pages the process has in physical memory, minus three for administrative purposes.

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 10.3.1

Every 5 Minutes

80

90

Total Private Memory is %value%%% and has crossed warning (%warning_threshold%%%) or critical (%critical_threshold%%%) threshold.

User Action

Navigate to the host Home page in the Fusion Middleware Control and review the top processes to see if you can identify which processes are consuming the most Memory. Or, navigate to the host Performance page in the Fusion Middleware Control and view the processes that are consuming the most Memory and take appropriate action.

21.2 JVM Controllers

The JVM Controllers category provides information about all the JVM controllers.

21.2.1 JVM CPU Usage (%)

This metric specifies the percentage of CPU Usage consumed by the JVM Controller including child JVM processes.

User Action

Navigate to the host Home page in the Fusion Middleware Control and review the top processes to see if you can identify which processes are consuming the most CPU. Or, navigate to the host Performance page in the Fusion Middleware Control and view the processes that are consuming the most CPU.

21.2.2 CPU Time (millisec)

This metric specifies the CPU Time (in millisec) consumed by the JVM Controller process including child JVM processes.

21.2.3 Number of JVMs running for this JVM Controller

This metric specifies the number of JVMs running for this JVM Controller.

21.2.4 JVM Private Memory (KB)

This metric specifies the Private Memory (in KB) consumed by the JVM Controller including child JVM processes. This is not the actual private memory on Linux but the Resident Set Size (RSS). RSS is the number of pages the process has in physical memory, minus three for administrative purposes.

21.2.5 UP Time (millisec)

This metric specifies the UP Time (in millisec) of the JVM Controller.

21.3 Number Of Sessions

The number of sessions category provides information about all the sessions.

21.3.1 Number Of Sessions

This metric measures the total number of Forms sessions of all Forms application deployments deployed in various WebLogic Server instances.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

Release 10.3.1

Every 5 Minutes

21.4 Response

The Response category provides information about the default Forms application deployment 'formsapp' in WebLogic Server WLS_FORMS

21.4.1 instname.value

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 10.3.1

Every 1 Minute

500

1000

The Forms Listener response time is unacceptable.

21.4.2 Status

This metric shows the status of the Forms Application 'formsapp' running inside WebLogic Server WLS_FORMS. By default, this metric has a critical threshold of 0 indicating that the Forms Servlet is unreachable and therefore Forms instance is not accessible. A critical alert is generated when the metric value reaches the critical threshold value once. It is recommended that this threshold is set at the default value.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 1 Minute

Not Defined

0

The Forms instance is not accessible.

The value of this metric is obtained by measuring the availability of the Forms application.

The current value of this metric can also be seen from the Deployments table on the Forms Home Page.

User Action

Check whether the WLS_FORMS instance has been started and if so that the application formsapp.ear has been deployed successfully.

21.5 Average Servlet Response Time

Average response time (in millisec) of Forms Servlet.

21.5.1 Average Response Time (millisec)

This metric measure the average response time.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 10.3.1

Every 5 Minutes

500

1000

The Forms Listener response time is unacceptable.

21.5.2 instname.value

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

Release 10.3.1

Every 5 Minutes

22 Portal

This chapter describes Oracle Portal metrics.

Note:
The current Enterprise Manager release does not support Oracle 10g Portal metrics.

22.1 Portlets (All)

This category provides information about portlets metrics.

22.1.1 Cache Hit (%)

This metric specifies the rate of cache hits.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

22.1.2 Average Time (ms)

This metric specifies the average time.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

22.1.3 Requests (per minute)

This metric specifies the rate per minute of requests to the Portal.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

22.1.4 Availability (%)

The percentage availability.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

22.1.5 Producer Type

The producer type

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

22.2 Portlets (Top 5)

This category provides information about portlets (Top 5) metrics.

22.2.1 Cache Hit (%)

The cache hit percentage

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

22.2.2 Average Time (ms)

This is the average time in milliseconds

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

22.2.3 Requests (per minute)

This is the number of requests recorded per minute.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

22.2.4 Availability (%)

The percentage availability

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

22.2.5 Producer Type

The producer type

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

22.3 Producers (All)

This category provides information about producers metrics.

22.3.1 Cache Hit (%)

This metric specifies the rate of cache hits from a producer.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to assess the cache hit ratio for a producer.

22.3.2 Average Time (ms)

This metric specifies the average time in executing portlet calls for a producer.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to assess the response times of a producer. If response time is out-of-bound, then assess average response times of individual portlets. Consider caching options and scaling out to optimize performance.

22.3.3 Requests (per minute)

This metric specifies the rate of requests per minute that are getting serviced from a producer.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to assess the load on the producer.

22.3.4 Availability (%)

This metric measures the availability of a producer, and measures the percent of requests that got an HTTP-2xx response from a producer.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to assess the availability of a producer. If this number is out-of-bounds, check the producer instance for availability and check for network connectivity from the Portal middle-tier to the producer.

22.3.5 Producer Type

The producer type

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

22.4 Producers (Top 5)

This category provides information about producers (Top 5) metrics.

22.4.1 Cache Hit (%)

The cache hit percentage.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

22.4.2 Average Time (ms)

The average time in milliseconds

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

22.4.3 Requests (per minute)

The number of requests per minute

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

22.4.4 Availability (%)

The percentage availability

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

22.4.5 Producer Type

The producer type

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

22.5 Portal Cache

This category provides information about portal cache metrics.

22.5.1 Average Expire Hit Time (ms)

This metric specifies the average time for cache hits in the Portal cache for content that uses "Expires-based caching".

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to assess the caching statistics of the pages/content. See "Using Caching with PL/SQL Based Web Applications" section in the Oracle® Fusion Middleware User's Guide for mod_plsql in OTN.

22.5.2 Expire Hit (%)

This metric specifies the percentage of requests that resulted in successful cache hits, for content that does "Expiry-based caching".

Use this metric to assess the caching statistics of the pages/content. See "Using Caching with PL/SQL Based Web Applications" section in the Oracle® Fusion Middleware User's Guide for mod_plsql in OTN.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to assess the caching statistics of your pages/content. See "Using Caching with PL/SQL Based Web Applications" section in the Oracle® Fusion Middleware User's Guide for mod_plsql in OTN.

22.5.3 Average New Time (ms)

This metric specifies the average time for cache misses in the Portal cache for content that is newly created in the cache.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to assess the caching statistics of your pages/content. See "Using Caching with PL/SQL Based Web Applications" section in the Oracle® Fusion Middleware User's Guide for mod_plsql in OTN.

22.5.4 New (%)

This metric specifies the percentage of requests for which new content was generated and cached. New content was generated because there were cache misses due to content not being in the Portal Cache.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to assess the caching statistics of your pages/content.

22.5.5 Average Ping Hit Time (ms)

This metric specifies the average time for cache hits in the Portal cache for content that uses "Ping-based caching".

Use this metric to assess the caching statistics of your pages/content.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to assess the caching statistics of the pages/content. See "Using Caching with PL/SQL Based Web Applications" section in the Oracle® Fusion Middleware User's Guide for mod_plsql in OTN.

22.5.6 Ping Hit (%)

This metric specifies the percentage of requests that resulted in successful cache hits for content that requires ping checks.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to assess the caching statistics of your pages/content.

22.5.7 Requests (per minute)

This metric specifies the rate per minute of requests to the Portal Cache.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to assess the rate of requests to the Portal Cache.

22.5.8 Average Stale Time (ms)

This metric specifies the average time for cache misses in the Portal cache for content that is stale and requires re-generation.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to assess the caching statistics of the pages/content. See "Using Caching with PL/SQL Based Web Applications" section in the Oracle® Fusion Middleware User's Guide for mod_plsql in OTN.

22.5.9 Stale (%)

This metric specifies the percentage of requests that resulted in cache misses because the content cached in the Portal Cache was not the latest.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to assess the caching statistics of your pages or content and to understand how frequently cached content is becoming stale due to content editing. See "Using Caching with PL/SQL Based Web Applications" section in the Oracle® Fusion Middleware User's Guide for mod_plsql in OTN.

22.6 Database Connection Pool Statistics

This category provides information about database connection pool statistics.

22.6.1 Average Fetch Time (ms)

This metric provides the average time spent by Portal in acquiring a database connection - either by creating a fresh connection to the database or by acquiring a connection from the connection pool.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

If the average time is high:

- Look at the connection pool hit ratio and make sure it is not out-of-bounds.

- Look at the time taken to create new connections to the database, and at your database settings.

- Check the network and database connection.

22.6.2 Requests (per minute)

This metric provides the rate of incoming requests that require a database connection

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Tune the database sessions based on the number of concurrent requests that require a database connection.

22.6.3 Hit (%)

This metric indicates the effectiveness of the Portal connection pool by measuring the percentage of Portal database connection pool hit rate.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

If this value is low, check the:

- setting for the PlsqlMaxRequestsPerSession connection pooling parameter. If the setting for this parameter is too low, the pooled connection may be discarded based on the property setting.

- "Database Repository Response Code Statistics" metrics to see if there are too many error responses. Some database error responses may cause a pooled connection to be discarded.

- database logs to find out if there are any server side crashes.

22.6.4 New (%)

This metric indicates the effectiveness of the Portal connection pool by measuring the percentage rate of creating new database connections in Portal.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

If this value is low, check the:

- setting for the PlsqlMaxRequestsPerSession connection pooling parameter. If the setting for this parameter is too low, the pooled connection may be discarded based on the property setting.

- "Database Repository Response Code Statistics" metrics to see if there are too many error responses. Some database error responses may cause a pooled connection to be discarded.

- database logs to find out if there are any server side crashes.

22.6.5 Stale (%)

This metric indicates the effectiveness of the Portal connection pool by providing the percentage rate of discarding pooled database connections.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

If this value is low, check the:

- setting for the PlsqlMaxRequestsPerSession connection pooling parameter. If the setting for this parameter is too low, the pooled connection may be discarded based on the property setting.

- "Database Repository Response Code Statistics" metrics to see if there are too many error responses. Some database error responses may cause a pooled connection to be discarded.

- database logs to find out if there are any server side crashes.

22.7 Database Repository Response Code Statistics

This category provides information about database repository response code statistic metrics.

22.7.1 Responses (per minute)

This metric provides the rate per minute for generating a HTTP response code, and is a measure of how frequently a particular HTTP response code is generated.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this value along with the "Average Response Time" value to assess the number of requests that are generating a particular HTTP response code and to assess the total time spent on it. For example, charting some of the typical failure codes like HTTP-404, HTTP-500, HTTP-503 and so on enables the assessment of the failure rate.

22.7.2 Average Processing Time (ms)

This metric provides the average response time for generating a response code.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this value along with the "Responses (per minute)" value to assess the time taken in generating a response. If the average response time is not within bounds, or if the total time taken in generating a response code is high, investigate further to find out why. For example, if the time taken to get a response from the database is consistently high, then it is possible that the database is under too much load or it is not performing too well because of some SQL*queries. SQL*Profiling and SQL*Trace maybe enabled to help identify the issue.

22.8 Page Engine Statistics

This category provides information about page engine statistic metrics.

22.8.1 Average Queue Wait Time (ms)

This metric provides the average time all internal PPE requests spent in the PPE internal request queue.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

If the average time is high, analyze why existing PPE threads are not being released to take on work from the PPE internal queue. Assess the page caching options and analyze the performance of system and network resources. Consider tweaking the number of the PPE fetcher threads or having a new container. Make sure that increasing the number of threads does not impact performance.

22.8.2 Average Page Processing Time (ms)

This metric specifies the average time taken to generate the pages and also retrieve the page metadata.

If the average time is high, use the Portal diagnostic logs to find out the cause of any failures. Average time may be high due to any of the following reasons:

- Poorly performing portlet

- Sudden increase in the load

- Database performance issues

- Network or database connectivity issues

22.8.3 Pages (per minute)

This metric specifies the rate of pages per minute generated by the Parallel Page Engine

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

If this value is out-of-bounds, identify the key pages in the site and enable better caching options. See "Improving Page Performance" chapter in "User's Guide for Oracle Portal" document in OTN for performance tuning information.

22.8.4 Average Page Metadata Fetch Time (ms)

This metric specifies the average time taken to retrieve the page metadata.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

If the average time is high, review the page metadata caching options for the pages and enable more caching at various levels.

22.8.5 Page Metadata Fetches (per minute)

This metric specifies the page metadata throughput per-minute.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

If this value is out-of-bounds, identify the key pages for the site and enable better caching. See "Improving Page Performance" chapter in "User's Guide for Oracle Portal" document in OTN for performance tuning information.

22.8.6 Average Page Metadata Wait Time (ms)

This metric specifies the average time spent in the PPE internal request queue waiting for page metadata.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

This value maybe high because the system is under heavy load. The value may also be high because the requests are waiting for the PPE request threads to become available. In this case, use the "poolSize" configuration setting to increase the size of the thread pool. Default pool size is 25.

22.8.7 Queue Timeouts (per minute)

This metric specifies the rate per minute of the number of requests for Portal data that have timed out in the PPE internal request queue.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

If this value is out-of-bounds, use the diagnostic logs to get details on specific page or content requests that are timing out. Analyze the log details to identify any pattern for the timeout. Some common reasons for timeout are listed below.

- Timeout is encountered around peak load times. This maybe because the system is not setup to take the load, the pages/content are not responsive enough to meet the performance criteria, or the pages/contents are not optimized for best performance by enabling caching.

- Timeout is always for a particular portlet or set of portlets. Evaluate the backend producer and its load and response characteristics.

- Same page times out most of the times. This typically is indicative of some attributes of the page. Analyze the page and its contents, and optimize caching. See "Improving Page Performance" chapter in "User's Guide for Oracle Portal" document in OTN for performance tuning information.

- Timeouts may occur because of performance blocks in resources like the CPU/memory/resources of the instances such as the middle-tier, database, producer nodes and so on. Monitor these resources for such blocks.

- Timeout may occur while connecting to the remote nodes or there maybe delays due to network connectivity issues.

- Timeout may occur due to improper system and network configuration.

If all aspects of the system and network are setup properly, consider increasing the number of fetcher threads in the PPE or adding another node in the cluster. However, this option should be done only if other components can take on the load added by the additional fetcher threads. If the backend producer cannot handle the existing load, then adding more fetcher threads or cluster members will negatively impact performance. In such cases, consider adding more resources for the producers.

22.8.8 HTTP200-HTTP299 (%)

This metric provides the percentage rate of HTTP-2xx responses generated by the Portal Parallel Page Engine (PPE).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

If this number is low, use the diagnostic logs to investigate.

22.8.9 HTTP300-HTTP399 (%)

This metric provides the percentage rate of HTTP-3xx responses generated by the Portal Parallel Page Engine (PPE).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

If the number of redirect responses in the system (HTTP 302) is high, review the cause for these responses and see if something can be optimized.

22.8.10 HTTP400-HTTP499 (%)

This metric provides the percentage rate of HTTP-4xx responses generated by the Portal Parallel Page Engine (PPE).

HTTP-499 is a special code which means that the requested resource is protected and a "Login" is needed to access it. Similarly, "HTTP-470" means that a "Logout" operation was performed.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

If the number of HTTP-4xx responses that are generated by the PPE is high, use the Portal diagnostic logs to investigate.

22.8.11 HTTP500-HTTP599 (%)

This metric provides the percentage rate of HTTP-5xx responses generated by the Portal Parallel Page Engine (PPE).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

If the number of HTTP-5xx responses that are generated by the PPE is high, use the Portal diagnostic logs to investigate.

22.8.12 Timeout (%)

This metric provides the percentage rate of timeout responses generated by the Portal Parallel Page Engine (PPE).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

If the number of timeout responses is high, use the Portal diagnostic logs to find out the cause of any failures. Timeouts may occur because of any of the following reasons:

- Poorly performing portlet

- Sudden increase in the load

- Database performance issues

- Network or database connectivity issues

- Timeout value set to an improper value

22.8.13 WebCache Page Metadata Hits (%)

This metric specifies the percentage of requests that are able to retrieve the cached page metadata content from WebCache.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this value to understand how effectively WebCache is being used for caching the page metadata. If this value is low, review the caching options for the pages.

22.8.14 WebCache Page Metadata Misses (%)

This metric specifies the percentage of requests that are not able to retrieve hit the cached page metadata content from WebCache.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to understand how effectively WebCache is being used for caching the page metadata for your pages.

22.8.15 WebCache Page Metadata Non-Cacheables (%)

This metric specifies the percentage of requests that cannot use WebCache to cache content.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

If this value is high, use this value to analyze how much of the pages are defined to not use WebCache for page metadata caching. This is not a common option for most pages and has performance implications. Unless there are specific reasons, review the caching options for such pages. See "Improving Page Performance" chapter in "User's Guide for Oracle Portal" document in OTN for performance tuning information.

22.9 Response

This category provides information about response metrics.

22.9.1 UpDown Status

This metric indicates the status of Portal. A green up arrow indicates that Portal is up and running. A red down arrow indicates that Portal is down. A "timer-clock" state icon indicates that Enterprise Manager is unable to query and retrieve the Portal status information.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every Minute

After Every 60 Samples

=

Not Defined

0

The Portal Application is down

User Action

If the status of Portal is down, check if the:

- Portal WebLogic container (WLS_PORTAL) is running. If required, start it.

- Portal application within the Portal WebLogic container has been started. If required, start the application.

If the container and the application are running and the status is still down, use the Portal diagnostic logs to find out why.

23 Reports Bridge

This chapter describes Oracle Reports Bridge metrics.

23.1 Log Message Alerts

This category provides information about log message alerts.

23.1.1 Log Monitoring Rules

The log monitoring rules

Target Version

Key

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

odl_message_alert_rule_name: "MSG-110"

Not Defined

After Every Sample

MATCH

YES

Not Defined

[%odl_message_alert_rule_name%] matched %odl_message_alert_occurence_count% log message(s) since last scan. Message Text for the last matching message is as follows - [ %odl_message_alert_matching_text% ].

All Versions

null

Not Defined

After Every Sample

MATCH

Not Defined

Not Defined

[%odl_message_alert_rule_name%] matched %odl_message_alert_occurence_count% log message(s) since last scan. Message Text for the last matching message is as follows - [ %odl_message_alert_matching_text% ].

* Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Alert Rule Name" and "Occurrence Time" objects.

If warning or critical threshold values are currently set for any unique combination of "Alert Rule Name" and "Occurrence Time" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Alert Rule Name" and "Occurrence Time" objects, use the Edit Thresholds page. See "Editing Metrics" for information on accessing the Edit Thresholds page.

23.2 Diagnostic Log Summary

This category provides information about diagnostic log summary metrics.

23.2.1 Log Error Messages (over 15 minutes)

The log error messages over 15 minutes.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Sample

>

Not Defined

Not Defined

Error message rate is %value%, crossed warning (%warning_threshold%) or critical(%critical_threshold%) threshold.

23.2.2 Log Incident Error Messages (over 15 minutes)

Log incident error messages over 15 minutes

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Sample

>

Not Defined

Not Defined

Incident Error message rate is %value%, crossed warning (%warning_threshold%) or critical(%critical_threshold%) threshold.

23.2.3 Log Notification Messages (over 15 minutes)

Log notification messages over 15 minutes

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Sample

>

Not Defined

Not Defined

Notification message rate is %value%, crossed warning (%warning_threshold%) or critical(%critical_threshold%) threshold.

23.2.4 Log Trace Messages (over 15 minutes)

Log trace messages over 15 minutes

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Sample

>

Not Defined

Not Defined

Trace message rate is %value%, crossed warning (%warning_threshold%) or critical(%critical_threshold%) threshold.

23.2.5 Log Unknown Messages (over 15 minutes)

The log of unknown messages over 15 minutes

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Sample

>

Not Defined

Not Defined

Unknown message rate is %value%, crossed warning (%warning_threshold%) or critical(%critical_threshold%) threshold.

23.2.6 Log Warning Messages (over 15 minutes)

Log warning messages over 15 minutes

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 15 Minutes

After Every Sample

>

Not Defined

Not Defined

Warning message rate is %value%, crossed warning (%warning_threshold%) or critical(%critical_threshold%) threshold.

23.3 Remote Elements Discovered

Provides information on Bridges and Servers discovered.

23.3.1 Host.value

This metric specifies the host name of the machine in which the remote element is located.

23.3.2 Name

This metric specifies the name of the remote element.

23.3.3 Discovery Time (ms)

This metric specifies the time taken to discover the remote element.

User Action

If the time taken to complete this action is high, check for any network issues. Also, tune the timeout parameter in the bridge configuration file to allow for high discovery time.

23.3.4 Type of Element

This metric specifies the type of the remote element. Type can be "Server" or "Bridge".

23.4 Resource Usage

This category provides information about resource usage metrics.

23.4.1 CPU Usage (%)

This metric specifies the percentage of CPU usage.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

23.4.2 Memory Usage (MB)

This metric specifies the memory used (in megabytes).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

23.4.3 Memory Usage (%)

This metric specifies the percentage of total memory used.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

23.5 Response

Provides information about the status of Reports Bridge, Up or Down.

23.5.1 Up or Down Status

This metric specifies the status of Reports Bridge. Status can be Up or Down.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every Minute

After Every 60 Samples

=

Not Defined

0

%target% is down

User Action

If status is down, see the Report log files or use EM log viewer to find out why the Reports Bridge is down.

24 Virtual Directory

This chapter describes Oracle Virtual Directory metrics.

24.1 Adapter Metrics

The category specifies the metrics about the currently configured Adapters.

24.1.1 Open Connections

This metric specifies the total number connections opened by a particular Adapter since last collection.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.1.2 Total No of Connections Processed

This metric specifies the total number of connections processed by the Adapter.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.1.3 Total No of Connections Reused

This metric specifies the total number of connections reused by the Adapter.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.1.4 Enabled

This metric specifies if the Adapter is enabled or disabled.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Enable or disable an adapter using Oracle Directory Services Manager by logging in to Oracle Directory Services Manager, selecting Adapter from the task selection bar, clicking the adapter you want to enable or disable, setting the Active option, and then clicking Apply.

24.1.5 Add Operations

This metric specifies the total number of Add operations performed by a particular Adapter since last collection.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.1.6 Total No of Operation Binds

This metric specifies the total number of bind operations by a particular Adapter.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.1.7 Operations Count

Specifies the total number of all operations performed by this particular Adapter.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.1.8 Delete Operations

This metric specifies the total number of delete operations performed by a particular Adapter since last collection.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.1.9 Operational Version

This metric specifies the operational version of Adapters.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.1.10 Modify Operations

This metric specifies the total number of Modify operations performed by a particular Adapter since last collection.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.1.11 Total No of Operations Renamed

This metric specifies the total number of operations renamed by a particular Adapter.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.1.12 Search Operations

This metric specifies the total number of Search operations performed by a particular Adapter since last collection.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.1.13 Provisioned version

This metric specifies the Processed version of Adapters.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.1.14 Type

This metric specifies the type of the Adapter.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.1.15 Average Time to complete a search request

This metric specifies Average Time a particular adapter took to complete a search request since the last Oracle Virtual Directory start.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.1.16 Maximum Time taken to complete a search request

This metric specifies the maximum time since the last Oracle Virtual Directory start that a particular Adapter took to complete an LDAP search request.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.1.17 Minimum Time taken to complete a search request

This metric specifies the minimum time since the last Oracle Virtual Directory start that a particular Adapter took to complete an LDAP search request.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.2 Connected IPs

This category provides information about distinct IP Address that are connected to Oracle Virtual Directory

24.2.1 Current Connections

This metric specifies the Current Open connections from a particular IP Address.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Error message rate is Current Connections %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

Set connection Activity Limits by selecting Administration from the Oracle Virtual Directory menu and then Server Properties. Select the Enable Quota Enforcement option on the Server Properties page, edit the Maximum Connections per IP Address setting, and then click Apply.

24.2.2 Total Connections

This metric specifies the Total number of connections from a particular IP Address.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Error message rate is Total Connections %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

Set connection Activity Limits by selecting Administration from the Oracle Virtual Directory menu and then Server Properties. Select the Enable Quota Enforcement option on the Server Properties page, edit the Maximum Connections per IP Address setting, and then click Apply.

24.3 getUsers

The category provides information about currently connected users

24.3.1 Current Connections

This metric specifies the number of connections that are currently open for a particular user.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Error message rate is Total Connections %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

Set connection Activity Limits by selecting Administration from the Oracle Virtual Directory menu and then Server Properties. Select the Enable Quota Enforcement option on the Server Properties page, edit the Maximum Client Connections, Maximum Connections per Authenticated Subject, and Maximum Connections per IP Address settings, and then click Apply.

24.3.2 Total Connections

This metric specifies the total number of connections opened by a particular user.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Error message rate is Total Connections %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

Set connection Activity Limits by selecting Administration from the Oracle Virtual Directory menu and then Server Properties. Select the Enable Quota Enforcement option on the Server Properties page, edit the Maximum Client Connections, Maximum Connections per Authenticated Subject, and Maximum Connections per IP Address settings, and then click Apply.

24.4 Resource Usage

This category provides information about CPU and memory usage.

24.4.1 CPU Usage (%)

This metric specifies the percentage of the CPU that Oracle Virtual Directory is using.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Error message rate is Total Connections %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

24.4.2 CPU Idle Time (%)

This metric specifies the percentage of the CPU Idle Time on the Oracle Virtual Directory Host.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.4.3 Other CPU Usage (%)

This metric specifies the percentage of the CPU that components other than Oracle Virtual Directory are using.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.4.4 Heap Usage (MB)

This metric specifies the JVM Heap Usage of the Oracle Virtual Directory Server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.4.5 Memory Usage (MB)

This metric specifies the Memory Consumed (in MB) by Oracle Virtual Directory.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.4.6 Free Memory (MB)

This metric specifies the amount of Free Memory on the Oracle Virtual Directory Server Host.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.4.7 Other Memory Usage (MB)

This metric specifies the Memory Consumed (in MB) by components other than Oracle Virtual Directory.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.4.8 Total Memory (MB)

This metric specifies the Total Available Memory on the Oracle Virtual Directory Server Host.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.4.9 Memory Usage (%)

This metric specifies the percentage of Memory Consumed by the Oracle Virtual Directory Server.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Error message rate is The Memory utilization is greater than %value%

24.4.10 Free Memory (%)

This metric specifies the percentage of Free Memory on the Oracle Virtual Directory Server Host.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.4.11 Other Memory Usage (%)

This metric specifies the percentage of Memory Consumed by components other than the Oracle Virtual Directory Server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.4.12 Start Time (ms since Epoch)

This metric specifies the start time (milliseconds since Epoch) of the Oracle Virtual Directory Server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.4.13 Up Time (ms since Epoch)

This metric specifies the amount of time (in milliseconds) that the Oracle Virtual Directory Server has been up and running.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

24.5 Response

This category shows whether the Oracle Virtual Directory instance is up and running or down and unavailable.

24.5.1 UpDown Status

This metric specifies whether the Oracle Virtual Directory instance is up and running or down and unavailable.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every Minute

After Every 60 Samples

=

Not Defined

0

The Oracle Virtual Directory instance is down

User Action

Change the status of the Oracle Virtual Directory instance by selecting Control from the Oracle Virtual Directory menu and then selecting either Start Up or Shut Down.

24.6 Server Latency Metrics

This category defines the Oracle Virtual Directory Server Latency Metrics

24.6.1 Total Operations

This metric specifies the total number of all LDAP operations since the last collection.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.6.2 Average time to complete an LDAP search request

This metric specifies the Average Time to complete an LDAP search request since the last Oracle Virtual Directory start.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every Minute

After Every 60 Samples

=

Not Defined

0

The Oracle Virtual Directory instance is down

24.6.3 Maximum Time to complete a search request

This metric specifies the Maximum Time for Oracle Virtual Directory to complete a search request since its last start.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.6.4 Minimum Time to complete a search request

This metric specifies the Minimum Time for Oracle Virtual Directory to complete a search request since its last start.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24.6.5 Number of LDAP Add Requests

This metric specifies the Number of LDAP Add Requests since the last collection.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

LDAP Add Requests %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

24.6.6 Number of LDAP Binds Requests

This metric specifies the Number of LDAP Bind Requests since the last collection.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

LDAP Binds Requests %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

24.6.7 Number of LDAP Delete Requests

This metric specifies the Number of LDAP Delete Requests since the last collection.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

LDAP Delete Requests %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

24.6.8 Number of LDAP Modify Requests

This metric specifies the Number of LDAP Modify Requests since the last collection.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

LDAP Modify Requests %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

24.6.9 Number of LDAP Rename Requests

This metric specifies the Number of LDAP Rename Requests since the last collection.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

LDAP Rename Requests %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

24.6.10 Number of LDAP Search Requests

This metric specifies the Number of LDAP Search Requests since the last collection.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

LDAP Search Requests %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

24.7 Server wide Connection Metrics

This category shows the Oracle Virtual Directory operational Metrics.

24.7.1 Total No of IPs Currently Connected

This metric specifies the Total number of distinct IP Addresses that are currently connected to Oracle Virtual Directory.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

Total IPs currently connected %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

Set connection Activity Limits by selecting Administration from the Oracle Virtual Directory menu and then Server Properties. Select the Enable Quota Enforcement option on the Server Properties page, edit the Maximum Connections per IP Address setting, and then click Apply.

24.7.2 Total No of Users Currently Connected

This metric specifies the Total number of users that are currently connected to Oracle Virtual Directory.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

Total Users currently connected %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

Set connection Activity Limits by selecting Administration from the Oracle Virtual Directory menu and then Server Properties. Select the Enable Quota Enforcement option on the Server Properties page, edit the Maximum Client Connections, Maximum Connections per Authenticated Subject, and Maximum Connections per IP Address settings, and then click Apply.

24.7.3 Total No of Operations

This metric specifies the Total number of all LDAP operations that have been completed from the last collection.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

Total number of Operations %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

Set the maximum number of operations to allow for each connection by selecting Administration from the Oracle Virtual Directory menu and then Server Properties. Select the Enable Quota Enforcement option on the Server Properties page, enter the maximum number of operations to allow for each connection in the Maximum Operations per Connection field, and click Apply.

24.7.4 Total No of Open Connections

This metric specifies the Total number of open connections to Oracle Virtual Directory.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

Total Open Connections %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25 Internet Directory

This chapter describes Oracle Internet Directory metrics.

25.1 Oracle Internet Directory

Oracle Enterprise Manager can be used to manage Oracle Internet Directory server. You can also use Enterprise Manager to view the metrics collected by Oracle Internet Directory LDAP server, replication server and directory integration server.

25.2 (Resource Statistics) LDAP Server's Active Database Connections

Shows the number of active database connections for the Oracle Internet Directory server.

25.3 Active Database Sessions

The number of active database connections for the Oracle Internet Directory server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

LDAP Active DB Connections %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.4 Closed LDAP Logon Session Statistics

This category provides information about closed LDAP Logon Session statistics.

25.4.1 Total Closed Logon Sessions

Provides information about total closed logon sessions to Oracle Internet Directory servers.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

OID Server Closed TCP conn %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.5 (Historical Resource Statistics)LDAP Server's Database Usage

This metric provides information about database usage by Oracle Internet Directory servers.

25.5.1 Active Database Sessions

Shows the number of active database sessions of the Oracle Internet Directory server instance at the end of the metric collection period.

25.5.2 Date and Time Stamp

Shows the date and time stamp (in UTC) of the metric collection.

25.5.3 Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

25.5.4 Open Database Sessions

Shows the number of open database sessions of the Oracle Internet Directory server instance at the end of the metric collection period.

25.6 Failed Bind Operations

The metric value specifies the number of unsuccessful LDAP bind operations performed by a user

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

Failed Bind Operation %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.7 (Critical Events)General System Resource Events

This category provides information about general system resource events.

25.7.1 Critical General Sys Resource Event Occurrences

Number of occurrences of general system resource events.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

0

LDAP Server crashed %value% times, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.8 LDAP Load

This metric provides information about the total number of LDAP operations in progress.

25.8.1 Server Load

The total number of LDAP operations in progress.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

LDAP Server Load %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.9 Historical LDAP Load and Response

This metric provides information about the total number of LDAP operations in progress and the average LDAP operation response time in Oracle Internet Directory servers.

25.9.1 Date and Time Stamp

Shows the date and time stamp (in UTC) of the metric collection.

25.9.2 Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

25.9.3 Server Load

Shows the number of LDAP operations in progress in the Oracle Internet Directory server at the end of the metric collection period.

25.9.4 Server Average Response Time (in Milliseconds)

Shows the average response time in (milliseconds) for the Oracle Internet Directory server to perform an LDAP operation during the metric collection period.

User Action

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.10 (Resource Statistics)LDAP Server Memory Growth

Provides information about Oracle Internet Directory server memory growth.

25.10.1 Average memory growth (%)

Average Oracle Internet Directory server memory growth.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

OID Average Memory Growth %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.11 New LDAP Logon Session Statistics

This category provides information about new LDAP logon session statistics.

25.11.1 Total New Logon Sessions

Provides information about total new logon sessions to Oracle Internet Directory servers.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

OID Server New TCP conn %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.12 (Resource Statistics) LDAP Server's Open Database Connections

Shows the number of open database connections for the Oracle Internet Directory server.

25.12.1 Open Database Sessions

The number of open database connections for the Oracle Internet Directory server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

LDAP Open DB Connections %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.13 Open LDAP Logon Session Statistics

This category provides information about open LDAP logon session statistics.

25.13.1 Total Open Logon Sessions

Provides information about total logon sessions to Oracle Internet Directory servers.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

Total Logon Sessions %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.14 Historical LDAP Operation Response Time

This category provides information about historical LDAP operation response time metrics.

25.14.1 Bind Operation Response Time

The average server response time for bind operations

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

Bind Operation Response Time %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.14.2 Compare Operation Response Time

The average server response time for compare operations

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

Compare Operation Response Time %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.14.3 Date and Time Stamp

The date and time stamp of this server instance.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.14.4 Instance Number

The instance number of this Oracle Internet Directory server instance.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.14.5 Messaging Search Operation Response Time

The metric value shows the average messaging search response time

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

Mesg Search Operation Response Time %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.15 LDAP Operation Response Time

This category provides information about LDAP operation response time metrics.

25.15.1 Bind Operation Response Time

The metric value shows the response time of LDAP Bind operations

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

Bind Operation Response Time %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.15.2 Compare Operation Response Time

The metric value shows the response time of LDAP compare operations

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

Compare Operation Response Time %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.15.3 Messaging Search Operation Response Time

The metric value shows the average messaging search response time

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

Mesg Search Operation Response Time %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.16 LDAP Server Resource Usage

Provides information about system resources used by Oracle Internet Directory servers.

25.16.1 Total CPU Usage (%)

Provides information about the percentage of CPU used by Oracle Internet Directory servers.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

9.0.4.x

Every 5 Minutes

Not Defined

Not Defined

Total CPU Usage %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.16.2 Total Memory Usage (KB)

Provides information about total virtual memory used by Oracle Internet Directory servers.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

9.0.4.x

Every 5 Minutes

Not Defined

Not Defined

Total Memory Usage %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.16.3 Total Memory Usage (%)

Provides information about percent total virtual memory used by Oracle Internet Directory servers.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

9.0.4.x

Every 5 Minutes

Not Defined

Not Defined

Total Memory Usage %value% (%%) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.17 LDAP Response

This metric provides information about the average LDAP operation response time in Oracle Internet Directory servers.

25.17.1 Server Response

The average LDAP operation response time in Oracle Internet Directory servers.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

LDAP Server Response %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.18 Running instances of LDAP Server

Provides information about running instances of Oracle Internet Directory servers.

25.18.1 Downtime Count

Shows the number of times the instance has gone down and has been restarted by the Oracle Internet Directory monitor daemon.

25.18.2 Host Name

Shows the host name of a running Oracle Internet Directory instance.

25.18.3 Instance Number

The instance number of this Oracle Internet Directory server instance.

25.18.4 Up Since

Shows the time when the Oracle Internet Directory instance was first started.

25.18.5 Non SSL Port Number

The metric value specifies the non-SSL port that an instance of Oracle Internet Directory server is listening on.

25.18.6 SSL Port Number

The metric value specifies the SSL port that an instance of Oracle Internet Directory server is listening on.

25.19 (Historical Resource Statistics)LDAP Server and System Memory

Provides information about system memory and Oracle Internet Directory server memory.

25.19.1 Date and Time Stamp

Shows the date and time stamp (in UTC) of the metric collection.

25.19.2 Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

25.19.3 LDAP Server's average memory growth (%)

Shows the percent of memory growth of the Oracle Internet Directory server instance at the end of the metric collection period.

25.19.4 System's Total Free Physical Memory (KB)

Shows, in kilobytes, the free physical system memory at the end of metric collection period.

25.20 (Critical Events)System Resource Events(3113 Errors)

Provides information about ORA-3113 errors that occurred in Oracle Internet Directory servers.

25.20.1 Number of 3113 Error Occurrences

Provides information about ORA-3113 errors that occurred in Oracle Internet Directory servers. This error indicates a loss of connection to database.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

User Action

Check for network problems. Check whether database has crashed.

25.21 (Critical Events)System Resource Events(3114 Errors)

Provides information about ORA-3114 errors that occurred in Oracle Internet Directory servers.

25.21.1 Number of 3114 Error Occurrences

Provides information about ORA-3114 errors that occurred in Oracle Internet Directory servers. This error indicates a loss of connection to database.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

User Action

Check for network problems. Check whether database has crashed.

25.22 (Historical Critical Events)System Resource Events

Provides information about critical system resource events that occurred in Oracle Internet Directory servers.

25.22.1 Last Event Time

Shows the date and time stamp (in UTC) of the event occurrence.

25.22.2 Number of Event Occurrence

The number of occurrences of this event

25.22.3 Event Name

Shows the name of the event that occurred.

25.22.4 Instance Number

Shows the instance number of the Oracle Internet Directory server for which this metric is collected.

25.22.5 Process ID

Shows the process identifier of the Oracle Internet Directory server instance for which this metric is collected.

25.23 (Critical Events)System Resource Events(Ora Errors)

This category provides information about System Resource Events(Ora Errors) metrics.

25.23.1 Critical Ora Error Occurrences

Number of occurrences of critical ORA Error Code Number.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

ORA-

Ora Error!

25.24 Historical LDAP Logon Session Statistics

This metric provides information about login sessions established with Oracle Internet Directory servers.

25.24.1 Date and Time Stamp

Shows the date and time stamp (in UTC) of the metric collection.

25.24.2 Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

25.24.3 Total LDAP Logon Sessions

Shows the number of LDAP sessions established with the Oracle Internet Directory server at the end of the metric collection period.

25.25 Total Memory Usage

Provides information about total virtual memory use by Oracle Internet Directory servers.

25.25.1 Total Mem. Size(in KB)

Shows total virtual memory use by Oracle Internet Directory servers.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

9.0.2.x and 9.0.3.x

Every 10 Minutes

Not Defined

Not Defined

Memory Usage over %value% KB crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

Specific to your deployment.

25.26 Historical LDAP Operations Profile

This metric provides information about LDAP operations completed by Oracle Internet Directory servers.

25.26.1 Date and Time Stamp

Shows the date and time stamp (in UTC) of the metric collection.

25.26.2 Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

25.26.3 Completed Abandon Operations

The metric value specifies the number of LDAP abandon operations performed by a user

25.26.4 Completed Add Operations

Shows the total number of LDAP add operations completed by the Oracle Internet Directory server instance during the metrics collection period.

25.26.5 Completed Bind Operations

Shows the total number of LDAP bind operations completed by the Oracle Internet Directory server instance during metric collection.

25.26.6 Completed Compare Operations

Shows the total number of LDAP compare operations completed by the Oracle Internet Directory server instance during metric collection.

25.26.7 Completed Delete Operations

Shows the total number of LDAP delete operations completed by the Oracle Internet Directory server instance during metric collection.

25.26.8 Completed Modify Operations

Shows the total number of LDAP modify operations completed by the Oracle Internet Directory server instance during metric collection.

25.26.9 Completed Modrdn Operations

The metric value specifies the number of unsuccessful LDAP modifydn operations performed by a user

25.26.10 Completed Search Operations

Shows the total number of LDAP search operations completed by the Oracle Internet Directory server instance during metric collection.

25.26.11 Completed Unbind Operations

The metric value specifies the number of LDAP unbind operations performed by a user

25.26.12 Failed Bind Operations

The metric value specifies the number of unsuccessful LDAP bind operations performed by a user

25.27 LDAP Operations Profile

This metric provides information about LDAP operations completed by Oracle Internet Directory servers.

25.27.1 Completed Abandon Operations

The metric value specifies the number of LDAP abandon operations performed by a user

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.27.2 Completed Add Operations

Shows the total number of LDAP add operations completed by the Oracle Internet Directory server instance during the metric collection period.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

LDAP Add %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.27.3 Completed Bind Operations

This metric provides information about Oracle Internet Directory server login sessions.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

LDAP Bind %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.27.4 Completed Compare Operations

Shows the total number of LDAP compare operations completed by the Oracle Internet Directory server instance during the metric collection period.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

LDAP Compare %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.27.5 Completed Delete Operations

Shows the total number of LDAP delete operations completed by the Oracle Internet Directory server instance during the metric collection period.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

LDAP Delete %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.27.6 Completed Modify Operations

Shows the total number of LDAP modify operations completed by the Oracle Internet Directory server instance during the metric collection period.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

LDAP Modify %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.27.7 Completed Modrdn Operations

The metric value specifies the number of LDAP Modrdn operations performed by a user

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.27.8 Total Operations

The metric value specifies the total number of LDAP operations performed by a user

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.27.9 Completed Search Operations

Shows the total number of LDAP search operations completed by the Oracle Internet Directory server instance during the metric collection period.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

LDAP Search %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.27.10 Completed Unbind Operations

The metric value specifies the number of LDAP unbind operations performed by a user

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.28 LDAP Server Total User Sessions

Provides information about total LDAP user sessions currently established with Oracle Internet Directory servers.

25.28.1 Total Users Sessions

Shows the total number of user sessions currently established with an Oracle Internet Directory server.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

After Every Sample

>

Not Defined

Not Defined

LDAP User Sessions %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

For information about tuning Oracle Internet Directory, see the Tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.29 Directory Integration Profiles

Provides basic status information about various Directory Integration Platform profiles configured in the system.

25.29.1 Last Execution Time

Shows the time when the profile was last executed by the Directory Integration Platform server.

25.29.2 Last Applied Change Number

Shows the last changenumber in Oracle Internet Directory that was successfully synchronized and propagated to the other end.

25.29.3 Execution Errors

Shows the last error that was encountered (if any) during the execution of the integration profile.

25.29.4 State

Shows the state of the integration profile (ENABLED / DISABLED).

25.29.5 Execution Status

Shows the current execution status of the integration profile.

25.29.6 Schedule (secs)

Shows the scheduling interval of the integration profiles. The Directory Integration Platform server executes the profiles using this scheduling interval.

25.29.7 Type

Shows the type of the integration profile (synchronization or provisioning).

25.30 Directory Integration Server

Provides information about various Directory Integration Platform instances running against this Oracle Internet Directory instance.

25.30.1 Downtime Count

Shows the number of times the Directory Integration Platform server went down unexpectedly.

25.30.2 Directory Integration Server Host

Shows the machine on which this Directory Integration Platform server is running.

25.30.3 Start Time

Shows the time when this Directory Integration Platform server started.

25.30.4 LDAP Server

Shows the Oracle Internet Directory server against which this Directory Integration Platform server is running.

25.31 Size of Audit Log Purge Queue

Provides information about the size of the Audit Log purge queue

25.31.1 Total Number of Audit Log Objects in Purge Queue

The metric value specifies the number of objects in the audit log purge queue

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

10000

100000

Audit Log Purge Queue size %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

For information about tuning Oracle Internet Directory, see the Tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.32 Size of General Statistics Purge Queue

Provides information about the size of the general statistics purge queue.

25.32.1 Total Number of General Statistics Objects in Purge Queue

The metric value specifies the number of objects in the Oracle Internet Directory system statistics purge queue

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

10000

100000

General Stats Purge Queue size %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

For information about tuning Oracle Internet Directory, see the Tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.33 Size of Health Statistics Purge Queue

Provides information about the size of the health statistics purge queue

25.33.1 Total Number of Health Statistics Objects in Purge Queue

The metric value specifies the number of objects in the Oracle Internet Directory health statistics purge queue

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

10000

100000

Health Stats Purge Queue size %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

For information about tuning Oracle Internet Directory, see the Tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.34 Total Number ChangeLogs in Purge Queue

Provides information about the number of objects in local change log purge queue.

25.34.1 Total Number of Local Changelogs in Purge Queue

The metric value specifies the number of objects in local change log purge queue

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

10000

100000

Local Change Log count %value% in Purge Queue crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

If this metric is very high, it might indicate improper purge scheduling. Remove all the change logs that need not be retained. Consider modifying orclpurgetargetage and orclpurgeinterval.

For more information see the Tuning chapter and the Replication Attributes chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.35 Total Number Remote ChangeLogs in Purge Queue

Provides information about the number of objects in remote change log purge queue

25.35.1 Total Number of Remote Changelogs in Purge Queue

The metric value specifies the number of objects in remote change log purge queue

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

10000

100000

Remote Change Log count %value% in Purge Queue crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

For information about tuning Oracle Internet Directory, see the Tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.36 Total Number of HIQ ChangeLogs

Provides information about the total number of change logs in the Human Intervention Queue.

25.36.1 HIQ Changelog Count

The Metric value specifies the total number of change logs in the Human Intervention Queue.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

Total Change Logs in HIQ %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Multiple Thresholds

If warning or critical threshold values are currently set for any "Supplier of changelog " object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Supplier of changelog " object, use the Edit Thresholds page. .

User Action

For information about tuning Oracle Internet Directory, see the Tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.37 Replication Server Configuration Set Information

Provides information about the Replication Server configuration set information metrics.

25.37.1 Number of Threads per Supplier for Change Processing

The number of threads per supplier for change processing.

User Action

If this metric increases suddenly, it might be due to an increased load on the replication server due to new change logs to transport or apply. Consider limiting the number of threads per supplier, using one of these methods:

1. If you want to use autotuning, set replautotune to 1. If orclreplicamaxthreads is set to more than 20, reduce it to 10/20. This will limit the total number of threads used for change processing and transporting changes.

2. If you do not want to use autotuning, set replautotune to 0. Set Orclthreadspersupplier;apply and Orclthreadspersupplier;Trasport to desired number and restart replication server. This will keep the number of threads used for transport and the number used for change processing constant.

For more information see the Tuning chapter and the Replication Attributes chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.37.2 Number of Threads per Supplier for Transporting Changes

The number of threads per supplier for transporting changes.

User Action

If this metric increases suddenly, it might be due to an increased load on the replication server due to new change logs to transport or apply. Consider limiting the number of threads per supplier, using one of these methods:

1. If you want to use autotuning, set replautotune to 1. If orclreplicamaxthreads is set to more than 20, reduce it to 10/20. This will limit the total number of threads used for change processing and transporting changes.

2. If you do not want to use autotuning, set replautotune to 0. Set Orclthreadspersupplier;apply and Orclthreadspersupplier;Trasport to desired number and restart replication server. This will keep the number of threads used for transport and the number used for change processing constant.

For more information see the Tuning chapter and the Replication Attributes chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.38 Running instances of LDAP Replication Server

Provides information about running instances of the directory replication server.

25.38.1 Downtime Count

Shows the number of times the instance went down and was restarted by the Oracle Internet Directory monitor daemon.

25.38.2 Oracle Directory Server

Shows the number of times the Oracle Internet Directory instance went down and was restarted by the Oracle Internet Directory monitor daemon.

25.38.3 Start Time

Shows the time when the instance of the directory replication server was first started.

25.39 Total Number of Local ChangeLogs

Provides information about the total number of local change logs generated.

25.39.1 Total Number of Local Changelogs

This metric value specifies the total number of local change logs generated.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

Total Local Change Logs %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.40 Total Number of New ChangeLogs

Provides information about the total number of change logs entries created.

25.40.1 New Changelog Count

This count of this metric gives the total number of change logs entries created.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

Total New Change Logs %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Supplier of changelog " object.

If warning or critical threshold values are currently set for any "Supplier of changelog " object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Supplier of changelog " object, use the Edit Thresholds page.

User Action

If this metric is increasing at a high rate, it might indicate:

- The number of transport threads per Supplier is set very high and the replication server is not running, so change logs are not being processed. Consider setting orclreplicmaxthreads lower (if using autotuning) or setting both Orclthreadspersupplier;apply and Orclthreadspersupplier;Transport lower (if not using autotuning). Ensure that the replication server is running.

- Orclsizelimit, which determines the number of changes transported from supplier to consumer, is set too high, allowing faster new change log growth. Consider setting orclsizelimit lower. Ensure that the number of replication apply threads is adequate to handle a large volume of changes. Consider setting orclchangeretrycount to a lower value to provide more resource to change log processing. Keep in mind that reducing the value of orclchangeretrycount might increase HIQ.

For more information see the Tuning chapter and the Replication Attributes chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.41 Total number ChangeLogs to be processed

Provides information about the number of change logs that pending.

25.41.1 Total Changelogs to be processed

This metric value specifies the number of change logs that pending.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

5000

20000

Replication backlog. %value% changelog not yet processed, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

For information about tuning Oracle Internet Directory, see the Tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.42 Total Number of Retry ChangeLogs

Provides information about the number of change logs in the retry queue.

25.42.1 Retry Changelog Count

This metric value specifies the number of change logs in the retry queue.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

Total Change Logs in Retry Queue %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Supplier of changelog " object.

If warning or critical threshold values are currently set for any "Supplier of changelog " object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Supplier of changelog " object, use the Edit Thresholds page.

User Action

If this metric is very large,analyze the retry logs to see the reason for conflict and try to resolve it. Make sure orclconflresolution is set to 1. If the same change logs have been retried repeatedly, consider whether orclchangeretrycount is set appropriately.

For more information see the Tuning chapter and the Replication Attributes chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.43 OID Replication Server Virtual Memory Size

Provides information about the total memory used by Oracle Internet Directory Replication Server.

25.43.1 Replication Server Memory Size

The metric value specifies the total memory used by Oracle Internet Directory Replication Server

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Oracle Directory Replication Server Memory Usage %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

If this metric is very high during normal replication, it might indicate:

- There are many change logs to apply and updateschedule is set to 0 (immediate processing). Consider increasing updateschedule to 1 or 2

- There are many change logs in HIQ and orclhiqschedule is set to a short time. Consider increasing orclhiqschedule to 10-15 minutes.

If this metric is high during bootstrapping, it might indicate:

- The attributes orclreplmaxworkerthread, orclthreadspersupplier;apply, and orclthreadspersupplier;transport are set inappropriately high. Consider decreasing these values. Also consider setting replautotune to 1.

- The consumer is a bottleneck and you are bootstrapping an entry larger than 50K. Consider using bulkload instead of bootstrapping. Stop replication server on the consumer before the bulkload and restart when finished.

For more information see the tuning chapter and the replication attributes chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.44 OID Replication Server Percentage CPU

Provides information about the percentage of CPU used by Oracle Internet Directory Replication Server.

25.44.1 Replication Server Percentage CPU

Provides information about the percentage of CPU used by Oracle Internet Directory Replication Server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Oracle Directory Replication Server CPU Usage %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

If this metric is very high during normal replication, it might indicate:

- There are many change logs to apply and updateschedule is set to 0 (immediate processing). Consider increasing updateschedule to 1 or 2.

- There are many change logs in HIQ and orclhiqschedule is set to a short time. Consider increasing orclhiqschedule to 10-15 minutes.

If this metric is high during bootstrapping, it might indicate:

- The attributes orclreplmaxworkerthread, orclthreadspersupplier;apply, and orclthreadspersupplier;transport are set inappropriately high. Consider decreasing these values. Also consider setting replautotune to 1.

- The consumer is a bottleneck and you are bootstrapping an entry larger than 50K. Consider using bulkload instead of bootstrapping. Stop replication server on the consumer before the bulkload and restart when finished.

For more information see the tuning chapter and the replication attributes chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.45 Replication Supplier Details

Provides information about the replication supplier detail metrics.

25.45.1 Replication Agreement Type

The replication agreement type: multimaster, one-way, or two-way replication agreement.

25.45.2 HIQ Changelog Count

The Metric value specifies the total number of change logs in the Human Intervention Queue

User Action

If this metric is very large, it might indicate:

- Change logs are not being retried a sufficient number of times. Consider increasing orclchangeretrycount to 4-10.

- HIQ change log processing is too slow because orclhiqschedule is set too high. Consider setting orclhiqschedule lower.

- Many conflicts occurred while applying change logs. Analyze the change logs. If appropriate, use the compare and reconcile tool to check the difference between directories. Move the change logs to the purge queue or retry queue, as appropriate.

For more information see the tuning chapter and the replication attributes chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.45.3 New Changelog Count

This metric gives the total number of change logs entries created.

User Action

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.45.4 Retry Changelog Count

This metric value specifies the number of change logs in the retry queue.

User Action

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.45.5 Name of the Supplier Replica

The replica ID of the supplier

25.46 Size of Security Refresh events Purge Queue

Provides information about the number of objects in the Oracle Internet Directory Security Refresh event purge queue.

25.46.1 Total Number of Security Refresh events Objects in Purge Queue

The metric value specifies the number of objects in the Oracle Internet Directory Security Refresh event purge queue.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

10000

100000

Security Refresh events Purge Queue size %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.47 Historical LDAP Entry Cache Hit Ratio

Provides information about performance of the entry cache in Oracle Internet Directory servers.

25.47.1 User Action

The entry cache is enabled only in single-system environments. When the cache is enabled, this metric should be close to 100% during searches.

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.47.2 Date and Time Stamp

Shows the date and time stamp (in UTC) of the metric collection.

25.47.3 Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

25.47.4 Server Entry Cache Hit Ratio

Shows in percentage the entry cache hit ratio in Oracle Internet Directory server at the end of the metric collection period.

User Action

The entry cache is enabled only in single-system environments. When the cache is enabled, this metric should be close to 100% during searches.

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.47.5 Process ID

Shows the process identifier of the Oracle Internet Directory server instance for which this metric is collected.

User Action

Specific to your site.

25.47.6 LDAP Entry Cache Hit Ratio

Provides information about performance of the entry cache in Oracle Internet Directory servers.

User Action

The entry cache is enabled only in single-system environments. When the cache is enabled, this metric should be close to 100% during searches.

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.47.7 Server Entry Cache Hit Ratio

Shows in percentage the entry cache hit ratio in Oracle Internet Directory server at the end of the metric collection period.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

Not Defined

Not Defined

Server Entry Cache Hit %value% less than warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

The entry cache is enabled only in single-system environments. When the cache is enabled, this metric should be close to 100% during searches.

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.48 OID Server Virtual Memory Size

Provides information about memory used by Oracle Internet Directory Server.

25.48.1 OID Server Memory Size

The metric value specifies the total memory used by Oracle Internet Directory Server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Oracle Directory Server Memory size %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.49 Stopped instances of LDAP Server

Provides information about Oracle Internet Directory instances that were started earlier and are stopped now.

25.49.1 Config Set Number

Shows the configuration set associated with the stopped instance.

25.49.2 Host Name

Shows the host name of the stopped instance.

25.50 OID Server Percentage CPU Utilization

Provides information about the percentage of CPU used by Oracle Internet Directory servers.

25.50.1 OID Server Percentage CPU

Provides information about the percentage of CPU used by Oracle Internet Directory servers.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Oracle Directory Server CPU Usage %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.51 (Historical Critical Events)Security Events

This metric provides information about security events that occurred in Oracle Internet Directory servers.

25.51.1 Event Time

Shows the date and time stamp (in UTC) of the event occurrence.

25.51.2 Event Result

Shows the result (either success or failure) of the event that occurred.

25.51.3 Event Name

Shows the name of the event that occurred.

25.51.4 Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

25.51.5 Process ID

Shows the process identifier for the Oracle Internet Directory server instance for which this metric is collected.

25.51.6 User DN

Shows the identity of the user who logged into Oracle Internet Directory server and performed the operation that triggered the event.

25.52 (Critical Event)Super User Failed Logins

This metric provides information about failed super user logins that occurred in Oracle Internet Directory servers.

25.52.1 Failed LDAP Super User Login

The number of successful super user logins that occurred in Oracle Internet Directory servers.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

15

20

Superuser Login failure count %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

A high number of failed superuser login attempts might indicate a break-in attempt.

25.53 (Critical Event)Super User Successful Logins

This metric provides information about successful super user logins that occurred in Oracle Internet Directory servers.

25.53.1 Successful LDAP Super User Login

The number of successful super user logins that occurred in Oracle Internet Directory servers.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

40

50

Superuser Login Success count %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

25.54 Size of System Resource events Purge Queue

Provides information about the number of objects in the Oracle Internet Directory System resource event purge queue.

25.54.1 Total Number of System Resource events Objects in Purge Queue

The metric value specifies the number of objects in the Oracle Internet Directory System resource event purge queue.

Target Version

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

>

10000

100000

System Resource events Purge Queue size %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.55 Size of Tombstone Purge Queue

The Tombstone purge queue size metrics are described.

25.55.1 Total Number of Tombstone Objects in Purge Queue

The metric value specifies the number of objects in the tombstone purge queue

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 10 Minutes

10000

100000

Tombstone Purge Queue size %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

25.56 TopProcesses

Provides information about the name of the process.

25.56.1 Process Name

The name of this process.

25.57 Resource Usage

Provides information about resource usage metrics.

25.57.1 CPU Usage (%)

Provides information about the percentage of CPU used by Oracle Internet Directory servers.

25.57.2 CPU Idle Time (%)

Percent CPU Idle time on the system where Oracle Internet Directory is running.

25.57.3 Other CPU Usage (%)

Percentage of CPU used by processes other than Oracle Internet Directory.

25.57.4 Memory Usage (MB)

Provides information about total virtual memory used by Oracle Internet Directory servers.

25.57.5 Free Memory (MB)

The metric value shows the system free memory where Oracle Internet Directory server is running.

25.57.6 Other Memory Usage (MB)

Amount of memory used by processes other than Oracle Internet Directory.

25.57.7 Total Memory (MB)

Metric value represents the total memory as used by Oracle Internet Directory Server.

25.57.8 Memory Usage (%)

Provides information about percent total virtual memory used by Oracle Internet Directory servers.

25.57.9 Free Memory (%)

The metric value shows the percentage of system free memory where Oracle Internet Directory server is running.

25.57.10 Other Memory Usage (%)

Percent of memory used by processes other than Oracle Internet Directory.

25.57.11 Start Time (ms since Epoch)

The start time of the Oracle Internet Directory process.

25.58 Response

For Oracle internal use only.

25.58.1 Status

Shows whether any Oracle Internet Directory LDAP server is up or not.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

0

The Internet Directory is down

User Action

Specific to your deployment.

25.58.2 Total Number

Shows the total number of Oracle Internet Directory servers that are up and running.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

9.0.2.x and 9.0.3.x

Every 5 Minutes

User Action

None.

25.59 User LDAP Operations Stats

Provides information about user LDAP operations stats metrics.

25.59.1 Abandon Operations

The metric value specifies the number of LDAP abandon operations performed by a user

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.2 Failed Add Operations

The metric value specifies the number of unsuccessful LDAP add operations performed by a user.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.3 Failed Base Search Operations

The metric value specifies the number of unsuccessful LDAP base search operations performed by a user

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.4 Failed Bind Operations

The metric value specifies the number of unsuccessful LDAP bind operations performed by a user

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.5 Failed Compare Operations

The metric value specifies the number of unsuccessful LDAP compare operations performed by a user

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.6 Failed Delete Operations

The metric value specifies the number of unsuccessful LDAP delete operations performed by a user.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.7 Failed Modify Operations

The metric value specifies the number of unsuccessful LDAP modify operations performed by a user.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.8 Failed ModRdn Operations

The metric value specifies the number of unsuccessful LDAP ModRdn operations performed by a user.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.9 Failed OneLevel Search Operations

The metric value specifies the number of unsuccessful LDAP OneLevel Search operations performed by a user.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.10 Failed Proxy Bind Operations

The metric value specifies the number of unsuccessful LDAP proxy bind operations performed by a user

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.11 Failed Subtree Search Operations

The metric value specifies the number of unsuccessful LDAP Subtree Search operations performed by a user.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.12 Successful Add Operations

The metric value specifies the number of successful LDAP add operations performed by a user.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.13 Successful Base Search Operations

The metric value specifies the number of successful LDAP base search operations performed by a user

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.14 Successful Bind Operations

The metric value specifies the number of successful LDAP bind operations performed by a user

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.15 Successful Compare Operations

The metric value specifies the number of successful LDAP compare operations performed by a user

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.16 Successful Delete Operations

The metric value specifies the number of successful LDAP delete operations performed by a user.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.17 Successful Modify Operations

The metric value specifies the number of successful LDAP modify operations performed by a user.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.18 Successful ModRdn Operations

The metric value specifies the number of successful LDAP ModRdn operations performed by a user.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.19 Successful OneLevel Search Operations

The metric value specifies the number of successful LDAP OneLevel Search operations performed by a user.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.20 Successful Proxy Bind Operations

The metric value specifies the number of successful LDAP proxy bind operations performed by a user

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.21 Successful Subtree Search Operations

The metric value specifies the number of successful LDAP Subtree Search operations performed by a user.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

25.59.22 Unbind Operations

The metric value specifies the number of LDAP unbind operations performed by a user.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

26 Directory Integration Platform

This chapter describes Oracle Directory Integration Platform (DIP) metrics.

26.1 DIP Aggregated Metrics

The aggregation of all the values across profile executions

26.1.1 Total Changes Attempted

This metric specifies the total number of changes attempted across all profiles.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.1.2 Total Successful Changes

This metric specifies the total number of successful changes across all profiles.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.1.3 Average LDAP Search Time

This metric specifies the average LDAP search time across all profiles.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.1.4 Average LDAP Write Time

This metric specifies the average LDAP write time across all profiles.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.1.5 Average Profile Execution Time

This metric specifies the average profile execution time across all profiles.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.2 DIP All Profiles (Consolidated)

This metric provides a consolidated list of profiles that are currently enabled in DIP

26.2.1 Host

This metric specifies the host where the DIP application is running.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.2.2 Last Change Number

This metric specifies the last change number that was processed by the profile during the previous execution.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.2.3 Last Execution Error

This metric specifies the error when the profile was last executed.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.2.4 Last Execution Time

This metric specifies the time when the profile was last executed.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.2.5 Last Successful Execution Time

This metric specifies the time when the profile was last executed successfully.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.2.6 Status of Last Sync Operation

This metric specifies the status of the last operation during profile execution.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.2.7 DIP Profile Name

This metric specifies the name of the profile.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.2.8 DIP Process

This metric specifies the DIP process name and ID.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.2.9 Average Processing Time

This metric specifies the average processing time (in milliseconds) of the profile.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.2.10 Maximum Processing Time

This metric specifies the largest amount of time (in milliseconds) taken to process the profile.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.2.11 Minimum Processing Time

This metric specifies the least amount of time (in milliseconds) taken to process the profile.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.2.12 Profile Job Status

This metric specifies the status of the quartz job related to this profile.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

Check if the profile is scheduled, then check if the profile is enabled.

26.3 DIP Prov profile runtime operational metrics

This metric provides detailed execution statistics for all the currently enabled provisioning profiles configured in DIP

26.3.1 Failed Add Group operations

This metric specifies the number of failed add group operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.2 Failed Add Identity operations

This metric specifies the number of failed add identity operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.3 Failed Add Subscription operations

This metric specifies the number of failed add subscription operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.4 Failed Add User operations

This metric specifies the number of failed add user operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.5 Failed Delete Group operations

This metric specifies the number of failed delete group operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.6 Failed Delete Identity operations

This metric specifies the number of failed delete identity operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.7 Failed Delete Subscription operations

This metric specifies the number of failed delete subscription operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.8 Failed Delete User operations

This metric specifies the number of failed delete user operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.9 Failed Modify Group operations

This metric specifies the number of failed modify group operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.10 Failed Modify Identity operations

This metric specifies the number of failed modify identity operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.11 Failed Modify User operations

This metric specifies the number of failed modify user operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.12 Profile Name

This metric specifies the provisioning profile name.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.13 Successful Add Group operations

This metric specifies the number of successful add group operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.14 Successful Add Identity operations

This metric specifies the number of successful add identity operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.15 Successful Add Subscription operations

This metric specifies the number of successful add subscription operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.16 Successful Add User operations

This metric specifies the number of successful add user operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.17 Successful Delete Group operations

This metric specifies the number of successful delete group operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.18 Successful Delete Identity operations

This metric specifies the number of successful delete identity operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.19 Successful Delete Subscription operations

This metric specifies the number of successful delete subscription operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.20 Successful Delete User operations

This metric specifies the number of successful delete user operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.21 Successful Modify Group operations

This metric specifies the number of successful modify group operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.22 Successful Modify Identity operations

This metric specifies the number of successful modify identity operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.3.23 Successful Modify User operations

This metric specifies the number of successful modify user operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.4 DIP Sync profile runtime operational metrics

This metric provides detailed execution statistics for all the currently enabled synchronization profiles configured in DIP

26.4.1 Skipped Operations

This metric specifies the number of skipped operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.4.2 Failed Add Operations

This metric specifies the number of failed add operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.4.3 Failed Delete Operations

This metric specifies the number of failed delete operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.4.4 Failed Modify Operations

This metric specifies the number of failed modify operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.4.5 Profile Name

This metric specifies the synchronization profile name.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.4.6 Successful Add Operations

This metric specifies the number of successful add operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.4.7 Successful Delete Operations

This metric specifies the number of successful delete operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.4.8 Successful Modify Operations

This metric specifies the number of successful modify operations.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.5 DIP Health

This metric provides information on the functional health of the DIP server

26.5.1 Host

This metric specifies the host where the WebLogic server is running.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.5.2 MBean Status

This metric specifies the status of the DIP JMX mbeans.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.5.3 Name

This metric specifies the internal name of the DIP application.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.5.4 Quartz Scheduler Status

This metric specifies the status of the internal qurtz scheduler.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.5.5 WLS Server Name

This metric specifies the WebLogic server name.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.6 DIP Provisioning Profiles

This metric provides the list of currently enabled Provisioning profiles

26.6.1 DIP Provisioning Profile Name

This metric specifies the name of the provisioning profile.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.6.2 Host

This metric specifies the host where the DIP application is running.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.6.3 Name

This metric specifies the name of the profile.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.7 DIP Synchronization Profiles

This metric provides the list of currently enabled synchronization profiles

26.7.1 DIP Synchronization Profile Name

This metric specifies the name of the synchronization profile.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.7.2 Host

This metric specifies the host where the DIP application is running.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.7.3 Name

This metric specifies the name of the profile.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

26.8 Resource Usage

Provides information about resource usage metrics.

26.8.1 CPU Usage (%)

The percentage CPU utilization.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

11Plus

Every 15 Minutes

After Every Sample

>

75

90

The CPU utilization is greater than %value%

User Action

No action required.

26.8.2 Memory Usage (%)

The percentage memory utilization.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

11Plus

Every 15 Minutes

After Every Sample

>

75

90

The Memory utilization is greater than %value%

User Action

No action required.

26.9 DIP server status

Provides information about the DIP server status.

26.9.1 Status

The status of the DIP server.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every Minute

After Every Sample

=

Not Defined

0

The DIP Server Instance is down

User Action

Change the status of the Directory Integration Platform instance by selecting Control from the DIP Server menu, and then selecting either Start Up or Shut Down.

27 WebCenter

This chapter describes Oracle WebCenter metrics.

27.1 Response

This metric indicates the current status of the WebCenter application:

Up (Green Up Arrow) - The WebCenter application is up and running and the last operation was successful.

Down (Red Down Arrow) - The WebCenter application is not currently available. The last operation was unsuccessful due to an unexpected error or exception. User errors, such as an authentication failure, do not change the status to ‘Down’.

Unknown (Clock) - Unable to query the status of the WebCenter application for some reason.

27.1.1 UpDown Status

This metric indicates the current status of the WebCenter application:

Up (Green Up Arrow) - The WebCenter application is up and running and the last operation was successful.

Down (Red Down Arrow) - The WebCenter application is not currently available. The last operation was unsuccessful due to an unexpected error or exception. User errors, such as an authentication failure, do not change the status to 'Down'.

Unknown (Clock) - Unable to query the status of the WebCenter application for some reason.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every Minute

After Every 60 Samples

=

Not Defined

0

1

The WebCenter Application is down

User Action

If you are having problems with the WebCenter application and the status is 'Down' or 'Unavailable', check the diagnostic logs to establish why the application is not up and running. The WebCenter application, and maybe the WebLogic server, must be restarted.

27.2 WebCenter Spaces (Aggregated)

Provides information about the WebCenter Spaces (Aggregated) metrics

27.2.1 Application Name

This metric identifies the WebCenter application to which these Space metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.2.2 Status

This metric indicates whether WebCenter Spaces is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.2.3 Successful Invocations (%)

This metric indicates the percentage of Space invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric further. Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Space Metrics.

You can also check the diagnostic logs to establish why Space invocations are failing.

27.2.4 Failed Invocations (%)

This metric indicates the percentage of Space invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Space Metrics.

You can also check the diagnostic logs to establish why Space invocations are failing.

27.2.5 Invocations (per minute)

This metric indicates the number of Space invocations per minute.

All Spaces in the WebCenter application are included in this count. The number of invocations per Space is available on application's Space metric page. See, Monitoring WebCenter Spaces Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for Spaces is high (compared with other WebCenter services), consider prioritizing troubleshooting efforts in this area.

See also, Analyzing Space Metrics.

27.2.6 Page Throughput (per minute)

This metric shows the average number of pages accessed per minute.

All Spaces in the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of Spaces. You can evaluate when pages are accessed the most, as well as the maximum and minimum usage.

See also, Analyzing Space Metrics.

27.2.7 Average Page Processing Time (ms)

This metric indicates the average time (in ms) spent processing Space operations.

All Spaces in the WebCenter application are included in the count. Processing times for individual Spaces are available on application's main metric page. See, Monitoring WebCenter Spaces Information.

The last 10-15 minutes of data is used to calculate the average page processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of Space operations.

If this metric is out-of-bounds (the average time for Space operations is increasing or higher than expected), navigate to the application's metric pages where more detailed metric data for individual Spaces is available.

See also, Analyzing Space Metrics.

27.2.8 Service Name

These metrics apply to the WebCenter Space.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.3 WebCenter Content Repositories (Aggregated)

Provides information about the WebCenter Content Repositories (Aggregated) metrics.

27.3.1 Application Name

This metric identifies the WebCenter application to which these content repository metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.3.2 Average Delete Time (ms)

This metric indicates the average time the Documents service spends deleting documents stored in all content repositories in this WebCenter application.

The last 10-15 minutes of data is used to calculate the average time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Delete operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.3 Average Download Time (ms)

This metric indicates the average time the Documents service spends downloading documents from all content repositories in this WebCenter application.

The last 10-15 minutes of data is used to calculate the average time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Download operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also Analyzing Content Repository Metrics.

27.3.4 Average GetItem Time (ms)

This metric indicates the average time the Documents service spends selecting and displaying items, such as a document or image, in all content repositories in this WebCenter application.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Get Item operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.5 Average ListFolder Time (ms)

This metric indicates the average time Content Presenter task flows spend listing folders stored in all content repositories in this WebCenter application.

The last 10-15 minutes of data is used to calculate the average time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the List Folder operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.6 Average Login Time (ms)

This metric indicates the average time spent logging in to content repositories (in ms).

All the content repositories used by the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate the average login time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of the Login operation. If this metric is out-of-bounds (the average time to login is increasing or higher than expected), navigate to the application’s main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.7 Average Processing Time (ms)

This metric indicates the average time the Documents service spends processing content repository operations (in ms).

Content repository operations include: Download, Upload, Search, Login, Delete. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

All the content repositories used by the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for content repository operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.8 Average Search Time (ms)

This indicates the average time the Documents service spends searching for documents stored in all content repositories in this WebCenter application.

The last 10-15 minutes of data is used to calculate the average time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Search operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.9 Average Upload Time (ms)

This indicates the average time the Documents service spends uploading documents to all content repositories in this WebCenter application.

The last 10-15 minutes of data is used to calculate the average time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Upload operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.10 Deletes (per minute)

This indicates total number of Delete operations the Documents service performs in a minute on all content repositories in this WebCenter application.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues, and the number of the Delete operation is high (compared with other services) consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.11 Download (per minute)

This metric indicates total number of Download operations the Documents service performs in a minute on all content repositories in this WebCenter application.

The last 10-15 minutes of data is used to calculate the average time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues, and the number of the Download operation is high (compared with other services) consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.12 GetItems (per minute)

This metric indicates the number of times, in a minute, an item such as a document or image, is selected or displayed in all content repositories in this WebCenter application.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the number of the Get Item operation is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.13 Invocations (per minute)

This metric indicates the total number of Documents service invocations per minute. All the content repositories used by this WebCenter application are included in this count.

Invocation rates and invocation counts for individual content repositories are available on application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for the Documents service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.14 ListFolder (per minute)

This metric indicates the number of times folder content is displayed through Content Presenter task flows per minute, in all content repositories in this WebCenter application.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the number of the List Folder operation is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.15 Logins (per minute)

This metric counts the number of times a WebCenter user logs in to a content repository per minute.

All the content repositories used by the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of content repositories. You can evaluate when most logins occur, as well as the maximum and minimum usage--which can be useful for tuning content repository performance.

If you are experiencing performance issues outside normal peak login times, navigate to the application's main metric page where detailed metric data for all operations is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.16 Searches (per minute)

This metric indicates the number of times content is searched per minute in all content repositories in this WebCenter application.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the number of the Search operation is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.17 Status

This metric indicates whether the Documents service is up or down. If the value is 1, the service is up. If the value is 0, it is down

27.3.18 Successful Invocations (%)

This metric indicates the percentage of Documents service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count. All the content repositories used by the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data for individual content repositories is also available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.3.19 Failed Invocations (%)

This metric indicates the percentage of the Documents service invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Content Repository Metrics.

27.3.20 Uploads (per minute)

This metric indicates the number of times the Documents service uploads documents in all content repositories in this WebCenter application per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the number of the Upload operation is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.21 Service Name

These metrics apply to content repositories used by the Documents service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.4 WebCenter Events (Aggregated)

Provides information about WebCenter Events (Aggregated).

27.4.1 Application Name

This metric identifies the WebCenter application to which the Events service metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.4.2 Average Create Time (ms)

This metric indicates the average time the Events service spends creating events in the WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Create operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.3 Average Delete Time (ms)

This metric indicates the average time the Events service spends deleting events in a WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Delete operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.4 Average List Time (ms)

This metric indicates the average time the Events service spends retrieving a list of events from the WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the List operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.5 Average Processing Time (ms)

This metric indicates the average time the Events service spends processing events operations in a WebCenter repository (in ms).

Events service operations include: Create Event, Update Event, List Event, Delete Event, Search Event. Processing times for individual operations are available on application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of Events service operations. If this metric is out-of-bounds (the average time for Events operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.6 Average Search Time (ms)

This metric indicates the average time the Events service spends searching for terms within event text in a WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Search operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.7 Average Update Time (ms)

This metric indicates the average time the Events service spends updating events in the WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Update operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.8 Creates (per minute)

This metric indicates the total number of Create operations per minute for the Events service for a WebCenter application.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create operations per minute for the Events service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.9 Deletes (per minute)

This metric indicates the total number of Delete operations per minute for the Events service for a WebCenter application.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Delete operations per minute for the Events service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.10 Failed Invocations (%)

This metric indicates the percentage of Events service invocations that failed for a WebCenter application.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Events Metrics.

27.4.11 Invocations (per minute)

This metric indicates the total number of invocations per minute for the Events service.

The number of invocations per operation is available on application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for the Events service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.12 Lists (per minute)

This metric indicates the total number of List operations per minute for the Events service for a WebCenter application.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of List operations per minute for the Events service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.13 Searches (per minute)

This metric indicates the total number of Search operations per minute for the Events service for a WebCenter application.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Search operations per minute for the Events service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.14 Status

This metric indicates whether the Events service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.4.15 Successful Invocations (%)

This metric indicates the percentage of the Events service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric further. Navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.4.16 Updates (per minute)

This metric indicates the total number of Update operations per minute for the Events service for a WebCenter application.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Update operations per minute for the Events service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.17 Service Name

These metrics apply to events used by the WebCenter application.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.5 WebCenter External Applications (Aggregated)

Provides information about the WebCenter External Applications (Aggregated) metrics.

27.5.1 Application Name

This metric identifies the WebCenter application to which these external application metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.5.2 Automated Logins (per minute)

This metric indicates the total number of logins per minute -- when WebCenter users logs in to external applications using the automated login feature.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of automated logins per minute for external applications is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.3 Average Automated Login Time (ms)

This metric indicates the average time spent logging WebCenter users to external applications using the automated login feature (in ms).

The last 10-15 minutes of data is used to calculate the average login time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of the Login operation. If this metric is out-of-bounds (the average time to login is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.4 Average Fetch Credentials Time (ms)

This metric indicates the average time spent retrieving credentials for external applications (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of the Fetch Credential operation. If this metric is out-of-bounds (the average time to fetch credentials is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.5 Average Fetch External Applications Time (ms)

This metric indicates the average time spent retrieving external applications (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of the Fetch External Application operation. If this metric is out-of-bounds (the average time to fetch credentials is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.6 Average Processing Time (ms)

This metric indicates the average time spent processing external application operations (in ms).

External application operations include: Fetch Credentials, Store Credentials, Fetch External Application, and Automated Logins. Processing times for individual operations are available on application's main metric page. See, Viewing Performance Information.

All external applications used by the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the overall external application performance. If this metric is out-of-bounds (the average time for external application operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.7 Average Store Credentials Time (ms)

This metric indicates the average time spent storing user credentials for external applications (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of the Store Credential operation. If this metric is out-of-bounds (the average time to fetch credentials is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.8 Credential Fetches (per minute)

This metric indicates the total number of Fetch Credential operations per minute for external applications.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Fetch Credential operations per minute for external applications is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.9 Credential Stores (per minute)

This metric indicates the total number of Store Credential operations per minute for external applications.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Store Credential operations per minute for external applications is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.10 External Applications Fetches (per minute)

This metric indicates the total number of Fetch External Application operations per minute for external applications.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Fetch External Application operations per minute for external applications is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.11 Failed Invocations (%)

This metric indicates the percentage of External Applications service invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing External Application Metrics.

27.5.12 Invocations (per minute)

This metric indicates the total number of external application invocations per minute.

All external applications used by this WebCenter application are included in this count. Invocation rates and invocation counts for individual external applications are available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate application performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for external applications is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.13 Status

This metric indicates whether the External Applications service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.5.14 Successful Invocations (%)

This metric indicates the percentage of external application invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count. All the external applications accessed by the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, check the diagnostic logs to establish why service operations are failing. Typical examples are, trying to invoke the automated login servlet without being authenticated or specifying an incorrect external application name. Navigate to the application's main metric page where more detailed metric data for individual external applications is also available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.15 Service Name

These metrics apply to the External Applications service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.6 WebCenter Portlets (Aggregated)

Provides information about WebCenter Portlets (Aggregated) metrics.

27.6.1 Application Name

This metric identifies the WebCenter application to which these portlet metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.6.2 Failed Invocations (%)

This metric indicates the percentage of portlet invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Portlet Metrics.

27.6.3 Average HTTP 2xx Time (ms)

This metric indicates the average time portlets take to process requests returning a HTTP2xx response code (in ms).

All portlets used in the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate the average HTTP 2xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to track overall portlet performance.

If this metric is out-of-bounds, consider prioritizing troubleshooting efforts for the portlets. Navigate to the application's main metric page where additional metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.6.4 Average HTTP 3xx Time (ms)

This metric indicates the average time portlets take to process requests returning a HTTP3xx response code (in ms).

All portlets used in the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate the average HTTP 3xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to track overall portlet performance.

If this metric is out-of-bounds, consider prioritizing troubleshooting efforts for the portlets. Navigate to the application's main metric page where additional metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.6.5 Average HTTP 4xx Time (ms)

This metric indicates the average time portlets take to process requests returning a HTTP4xx response code (in ms).

All portlets used in the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate the average HTTP 4xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to track overall portlet performance.

If this metric is out-of-bounds, consider prioritizing troubleshooting efforts for the portlets. Navigate to the application's main metric page where additional metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.6.6 Average HTTP 5xx Time (ms)

This metric indicates the average time portlets take to process requests returning a HTTP 5xx response code (in ms).

All portlets used in the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate the average HTTP 5xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to track overall portlet performance.

If this metric is out-of-bounds, consider prioritizing troubleshooting efforts for the portlets. Navigate to the application's main metric page where additional metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.6.7 Average Processing Time (ms)

This metric indicates the average time spent processing portlet operations (in ms).

All portlets used in the WebCenter application are included in this count. Maximum processing times for individual HTTP request types are also available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the portlet performance. If this metric is out-of-bounds (the average time for portlet operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.6.8 Average HTTP 2xx Requests (per minute)

This metric indicates total time portlets take to process requests returning a HTTP 2xx response code per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of time taken (per minute) by portlets to process requests is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.6.9 Average HTTP 3xx Requests (per minute)

This metric indicates total time portlets take to process requests returning a HTTP 3xx response code per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of time taken (per minute) by portlets to process requests is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.6.10 Average HTTP 4xx Requests (per minute)

This metric indicates total time portlets take to process requests returning a HTTP 4xx response code per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of time taken (per minute) by portlets to process requests is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.6.11 Average HTTP 5xx Requests (per minute)

This metric indicates total time portlets take to process requests returning a HTTP 5xx response code per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of time taken (per minute) by portlets to process requests is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.6.12 Invocations (per minute)

This metric indicates the total number of portlet invocations per minute.

All portlets used in the WebCenter application are included in this count. The number of invocations is available on application's main metric page. See Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate portlet performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the invocation rate for portlets is high (compared with other WebCenter services), consider prioritizing troubleshooting efforts in this area. Navigate to the application's main metric page where additional metric data is available. See Viewing Performance Information.

See also Analyzing Portlet Metrics.

27.6.13 Status

This metric indicates whether portlets are up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.6.14 Successful Invocations (%)

This metric indicates the percentage of portlet invocations that succeeded.

All portlets used in the WebCenter application are included in this count.

Any request that fails will impact this percentage. This includes WebCenter application-related failures such as timeouts and internal errors, as well as remote/server failures such as requests returned with response codes HTTP4xx or HTTP5xx, responses with a bad content type, and SOAP faults, where applicable. Maximum processing times for individual HTTP request types are also available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate the metric in more detail. Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

See also Analyzing Portlet Metrics.

You can also check the diagnostic logs to establish why portlet requests are failing.

27.6.15 Service Name

These metrics apply to WebCenter portlets.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.7 WebCenter Producers (Aggregated)

Provides information about WebCenter Producers (Aggregated) metrics.

27.7.1 Application Name

This metric identifies the WebCenter application to which these portlet producer metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.7.2 Average HTTP 2xx Time (ms)

This metric indicates the average time that all portlets used in the WebCenter application take to process requests returning a HTTP 2xx response code (in ms).

The last 10-15 minutes of data is used to calculate the average HTTP 2xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to track the overall performance of producers in the WebCenter application.

If this metric is out-of-bounds, consider prioritizing troubleshooting efforts for the producers. Navigate to the application's main metric page where additional metric data is available. See, Viewing Performance Information.

See, Analyzing Portlet Producer Metrics.

27.7.3 Average HTTP 3xx Time (ms)

This metric indicates the average time that all portlets used in the WebCenter application take to process requests returning a HTTP 3xx response code (in ms).

The last 10-15 minutes of data is used to calculate the average HTTP 3xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to track the overall performance of producers in the WebCenter application.

If this metric is out-of-bounds, consider prioritizing troubleshooting efforts for the producers. Navigate to the application's main metric page where additional metric data is available. See, Viewing Performance Information.

See, Analyzing Portlet Producer Metrics.

27.7.4 Average HTTP 4xx Time (ms)

This metric indicates the average time that all portlets used in the WebCenter application take to process requests returning a HTTP 4xx response code (in ms).

The last 10-15 minutes of data is used to calculate the average HTTP 4xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to track the overall performance of producers in the WebCenter application.

If this metric is out-of-bounds, consider prioritizing troubleshooting efforts for the producers. Navigate to the application's main metric page where additional metric data is available. See, Viewing Performance Information.

See, Analyzing Portlet Producer Metrics.

27.7.5 Average HTTP 5xx Time (ms)

This metric indicates the average time that all portlets used in the WebCenter application take to process requests returning a HTTP 5xx response code (in ms).

The last 10-15 minutes of data is used to calculate the average HTTP 5xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to track the overall performance of producers in the WebCenter application.

If this metric is out-of-bounds, consider prioritizing troubleshooting efforts for the producers. Navigate to the application's main metric page where additional metric data is available. See, Viewing Performance Information.

See, Analyzing Portlet Producer Metrics.

27.7.6 Average Processing Time (ms)

This metric indicates the average time spent processing portlet producer operations (in ms).

All portlet producers used in the WebCenter application are included in this count. Maximum processing times for individual HTTP request types are also available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the portlet producer performance. If this metric is out-of-bounds (the average time for producer operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also Analyzing Portlet Producer Metrics.

27.7.7 Failed Invocations (%)

This metric indicates the percentage of producers invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also Analyzing Portlet Producer Metrics.

27.7.8 Average HTTP 2xx Requests (per minute)

This metric indicates total time (per minute) that all portlets used in the WebCenter application take to process requests returning a HTTP 2xx response code.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of time taken (per minute) by portlets to process requests is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.7.9 Average HTTP 3xx Requests (per minute)

This metric indicates total time (per minute) that all portlets used in the WebCenter application take to process requests returning a HTTP 3xx response code.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of time taken (per minute) by portlets to process requests is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.7.10 Average HTTP 4xx Requests (per minute)

This metric indicates total time (per minute) that all portlets used in the WebCenter application take to process requests returning a HTTP 4xx response code.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of time taken (per minute) by portlets to process requests is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.7.11 Average HTTP 5xx Requests (per minute)

This metric indicates total time (per minute) that all portlets used in the WebCenter application take to process requests returning a HTTP 5xx response code.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of time taken (per minute) by portlets to process requests is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.7.12 Invocations (per minute)

This metric indicates the total number of producer invocations per minute.

All portlet producers used in the WebCenter application are included in this count. The number of invocations is available on application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate producer performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the invocation rate for producers is high (compared with other WebCenter services), consider prioritizing troubleshooting efforts in this area. Navigate to the application's main metric page where additional metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.7.13 Status

This metric indicates whether producers are up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.7.14 Successful Invocations (%)

This metric indicates the percentage of producer invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count. All portlet producers used in the WebCenter application are included in this count.

Any request that fails will impact this percentage. This includes WebCenter application-related failures such as timeouts and internal errors, as well as remote/server failures such as requests returned with response codes HTTP4xx or HTTP5xx, responses with a bad content type, and SOAP faults, where applicable. Maximum processing times for individual HTTP request types are also available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

You can also check the diagnostic logs to establish why producer requests are failing.

If Successful Invocations (%) is below 100%), investigate the metric in more detail. Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.7.15 Service Name

These metrics apply to the portlet producers used by the WebCenter application.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.8 WebCenter Search (Aggregated)

Provides information about WebCenter Search (Aggregated) metrics.

27.8.1 Application Name

This metric identifies the WebCenter application to which these Search service metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.8.2 Average Processing Time (ms)

This metric indicates the average time (in ms) the Search service spends processing search operations.

All WebCenter search sources are included in the count: Announcements, Documents, Discussion Forums, Spaces, Events, Lists, Notes, Oracle Secure Enterprise Search, Pages, People Connections, Wikis and Blogs, and Tagged Items. Processing times for individual search sources are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of Search service operations.

If this metric is out-of-bounds (the average time for search operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual search sources is available. See, Viewing Performance Information.

See also, Analyzing Search Metrics.

27.8.3 Failed Invocations (%)

This metric indicates the percentage of Search service invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Search Metrics.

27.8.4 Invocations (per minute)

This metric indicates the total number of Search service invocations per minute across all WebCenter search sources: Announcements, Documents, Discussion Forums, Spaces, Events, Links, Lists, Notes, Oracle Secure Enterprise Search, Pages, People Connections, Wikis and Blogs, and Tagged Items.

Invocation rates and invocation counts for individual search sources are available on application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for the Search service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Search Metrics.

27.8.5 Status

This metric indicates whether the Search service is up or down. If the value is 1, the service is up. If the value is 0, it is down

27.8.6 Successful Invocations (%)

This metric indicates the percentage of Search service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count. All WebCenter search sources are included in the count: Announcements, Documents, Discussion Forums, Spaces, Events, Lists, Notes, Oracle Secure Enterprise Search, Pages, People Connections, Wikis and Blogs, and Tagged Items.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate the metric in more detail. Navigate to the application's main metric page where more detailed metric data for individual search sources is available. See, Viewing Performance Information.

See also, Analyzing Search Metrics.

You can also check the diagnostic logs to establish why search requests are failing.

27.8.7 Service Name

These metrics apply to the Search service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.9 WebCenter Services

Provides information about WebCenter Services metrics.

27.9.1 Application Name

This metric identifies the WebCenter application to which these WebCenter service metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.9.2 Average Processing Time (ms)

This metric indicates the average time spent processing operations for this WebCenter service (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

Use this metric to determine the performance of WebCenter services. If this metric is out-of-bounds (the average time for operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Understanding WebCenter Performance Metrics Information.

27.9.3 Failed Invocations (%)

This metric indicates the percentage of services invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See, Understanding WebCenter Performance Metrics Information.

27.9.4 Invocations (per minute)

This metric indicates the total number of invocations per minute for this WebCenter service. The number of invocations is available on application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the invocation rate for this WebCenter service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

See, Understanding WebCenter Performance Metrics Information.

27.9.5 Status

This metric indicates whether a specific service is up or down. If the value is 1, the service is up. If the value is 0, it is down

27.9.6 Successful Invocations (%)

This metric indicates the percentage of invocations that succeeded for this WebCenter service. Any operation or request that fails will impact this percentage.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric. Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Understanding WebCenter Performance Metrics Information.

You can also check the diagnostic logs to establish why service requests are failing.

27.10 WebCenter BPEL Worklists (Aggregated)

Provides information about WebCenter BPEL Worklists (Aggregated) metrics.

27.10.1 Application Name

This metric identifies the WebCenter application to which these Worklists service metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.10.2 Average Processing Time (ms)

This metric indicates the average time the Worklists service spends processing operations (in ms).

All the BPEL worklists used by the WebCenter application are included in this count. Processing times for individual worklists are available on application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of Worklists service operations. If this metric is out-of-bounds (the average time for worklist operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Worklist Metrics.

27.10.3 Failed Invocations (%)

This metric indicates the percentage of Worklists service invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Worklist Metrics.

27.10.4 Invocations (per minute)

This metric indicates the total number of Worklists service invocations per minute.

All the BPEL worklists used by the WebCenter application are included in this count. Invocation rates and invocation counts for individual worklists are available on application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for the Worklists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Worklist Metrics.

27.10.5 Status

This metric indicates whether the Worklists service is up or down. If the value is 1, the service is up. If the value is 0, it is down

27.10.6 Successful Invocations (%)

This metric indicates the percentage of Worklists service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count. All the BPEL worklists used by the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data for individual worklists is also available. See, Viewing Performance Information.

See also, Analyzing Worklist Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.10.7 Service Name

These metrics apply to the Worklists service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.11 WebCenter Portlets

Provides information about WebCenter Portlet metrics.

27.11.1 Application Name

This metric identifies the WebCenter application to which these portlet metrics apply.

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All versions

Every 300 seconds

27.11.2 Average HTTP 2xx Time (ms)

This metric indicates the average time the portlet takes to process requests returning a HTTP 2xx response code (in ms).

The last 10-15 minutes of data is used to calculate the average HTTP 2xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to detect the most performant portlets. If you use this metric in conjunction with the Invocations (per minute) metric, then you can identify the top performing portlet.

See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.3 Average HTTP 3xx Time (ms)

This metric indicates the average time the portlet takes to process requests returning a HTTP 3xx response code (in ms).

The last 10-15 minutes of data is used to calculate the average HTTP 3xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to detect the most performant portlets. If you use this metric in conjunction with the Invocations (per minute) metric, then you can identify the top performing portlet.

See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.4 Average HTTP 4xx Time (ms)

This metric indicates the average time the portlet takes to process requests returning a HTTP 4xx response code (in ms).

The last 10-15 minutes of data is used to calculate the average HTTP 4xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to detect the most performant portlets. If you use this metric in conjunction with the Invocations (per minute) metric, then you can identify the top performing portlet.

See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.5 Average HTTP 5xx Time (ms)

This metric indicates the average time the portlet takes to process requests returning a HTTP 5xx response code (in ms).

The last 10-15 minutes of data is used to calculate the average HTTP 5xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to detect the most performant portlets. If you use this metric in conjunction with the Invocations (per minute) metric, then you can identify the top performing portlet.

See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.6 Average Processing Time (ms)

This metric indicates the average time spent processing portlet requests (in ms). Maximum processing times for individual HTTP request types are also available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine portlet performance. If this metric is out-of-bounds (the average time for portlet operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.7 Failed Invocations (%)

This metric indicates the percentage of portlet invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Portlet Metrics.

27.11.8 Average HTTP 2xx Requests (per minute)

This metric indicates total time the portlet takes to process requests returning a HTTP 2xx response code per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of time taken (per minute) by this portlet to process requests is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.9 Average HTTP 3xx Requests (per minute)

This metric indicates total time the portlet takes to process requests returning a HTTP 3xx response code per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of time taken (per minute) by this portlet to process requests is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.10 Average HTTP 4xx Requests (per minute)

This metric indicates total time the portlet takes to process requests returning a HTTP 4xx response code per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of time taken (per minute) by this portlet to process requests is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.11 Average HTTP 5xx Requests (per minute)

This metric indicates total time the portlet takes to process requests returning a HTTP 5xx response code per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of time taken (per minute) by this portlet to process requests is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.12 Invocations (per minute)

This metric indicates the total number of invocations per minute for a portlet. The number of invocations is available on application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate portlet performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the invocation rate for the portlet is high (compared with other portlets), consider prioritizing troubleshooting efforts in this area. Navigate to the application's main metric page where additional metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.13 Status

This metric indicates whether portlets are up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.11.14 Successful Invocations (%)

This metric indicates the percentage of portlet invocations that succeeded.

Any request that fails will impact this percentage. This includes WebCenter application-related failures such as timeouts and internal errors, as well as remote/server failures such as requests returned with response codes HTTP4xx or HTTP5xx, responses with a bad content type, and SOAP faults, where applicable. Maximum processing times for individual HTTP request types are also available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

You can also check the diagnostic logs to establish why portlet requests are failing.

27.11.15 Producer Type

The portlet producer type: Web or WSRP

Web portlet producer - deployed to a J2EE application server, which is often remote and communicates through Simple Object Access Protocol (SOAP) over HTTP.

WSRP portlet producer - Web Services for Remote Portlets (WSRP) is a Web services standard that allows interoperability between a standards enabled container and a WSRP client application.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.12 WebCenter Producers

Provides information about the WebCenter Producers metrics.

27.12.1 Application Name

This metric identifies the WebCenter application to which these portlet producer metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.12.2 Average HTTP 2xx Time (ms)

This metric indicates the average time that all portlets from this producer take to process requests returning a HTTP 2xx response code (in ms).

The last 10-15 minutes of data is used to calculate the average HTTP 2xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to detect the most performant producers. If you use this metric in conjunction with the Invocations (per minute) metric, then you can identify the top-performing producer.

See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.12.3 Average HTTP 3xx Time (ms)

This metric indicates the average time that all portlets from this producer take to process requests returning a HTTP 3xx response code (in ms).

The last 10-15 minutes of data is used to calculate the average HTTP 3xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to detect the most performant producers. If you use this metric in conjunction with the Invocations (per minute) metric, then you can identify the top-performing producer.

See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.12.4 Average HTTP 4xx Time (ms)

This metric indicates the average time that all portlets from this producer take to process requests returning a HTTP 4xx response code (in ms).

The last 10-15 minutes of data is used to calculate the average HTTP 4xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to detect the most performant producers. If you use this metric in conjunction with the Invocations (per minute) metric, then you can identify the top-performing producer.

See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.12.5 Average HTTP 5xx Time (ms)

This metric indicates the average time that all portlets from this producer take to process requests returning a HTTP 5xx response code (in ms).

The last 10-15 minutes of data is used to calculate the average HTTP 5xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to detect the most performant producers. If you use this metric in conjunction with the Invocations (per minute) metric, then you can identify the top-performing producer.

See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.12.6 Average Processing Time (ms)

This metric indicates the average time spent processing operations for a particular portlet producer (in ms). Maximum processing times for individual HTTP request types are also available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of portlet producers. If this metric is out-of-bounds (the average time for producer operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.12.7 Failed Invocations (%)

This metric indicates the percentage of producer invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Portlet Producer Metrics.

27.12.8 Average HTTP 2xx Requests (per minute)

This metric indicates total time (per minute) that all portlets in this producer take to process requests returning a HTTP 2xx response code.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of time taken (per minute) by portlets to process requests is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.12.9 Average HTTP 3xx Requests (per minute)

This metric indicates total time (per minute) that all portlets in this producer take to process requests returning a HTTP 3xx response code.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of time taken (per minute) by portlets to process requests is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.12.10 Average HTTP 4xx Requests (per minute)

This metric indicates total time (per minute) that all portlets in this producer take to process requests returning a HTTP 4xx response code.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of time taken (per minute) by portlets to process requests is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.12.11 Average HTTP 5xx Requests (per minute)

This metric indicates total time (per minute) that all portlets in this producer take to process requests returning a HTTP 5xx response code.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of time taken (per minute) by portlets to process requests is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.12.12 Invocations (per minute)

This metric indicates the total number of invocations per minute for a producer. The number of invocations is available on application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate producer performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the invocation rate for the producer is high (compared with other producers), consider prioritizing troubleshooting efforts in this area. Navigate to the application's main metric page where additional metric data is available. See, Viewing Performance Information.

See, Analyzing Portlet Producer Metrics.

27.12.13 Status

This metric indicates whether producers are up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.12.14 Successful Invocations (%)

This metric indicates the percentage of portlet invocations that succeeded for this producer.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

Any request that fails will impact this percentage. This includes WebCenter application-related failures such as timeouts and internal errors, as well as remote/server failures such as requests returned with response codes HTTP4xx or HTTP5xx, responses with a bad content type, and SOAP faults, where applicable. Maximum processing times for individual HTTP request types are also available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate the metric in more detail. Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

You can also check the diagnostic logs to establish why producer requests are failing.

27.12.15 Producer Type

The portlet producer type: Web or WSRP

Web portlet producer - deployed to a J2EE application server, which is often remote and communicates through Simple Object Access Protocol (SOAP) over HTTP.

WSRP portlet producer - Web Services for Remote Portlets (WSRP) is a Web services standard that allows interoperability between a standards enabled container and a WSRP client application.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.13 WebCenter Announcements

Provides information about the WebCenter Announcements metrics.

27.13.1 Application Name

This metric identifies the WebCenter application to which these Announcements service metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.13.2 Average Create Time (ms)

This metric indicates the average time the Announcements service spends creating announcements (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Create operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.3 Average List Time (ms)

This metric indicates the average time the Announcements service spends retrieving a list of announcements (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the List operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.4 Average Login Time (ms)

This metric indicates the average time spent logging in to the back-end discussions server hosting announcements (in ms).

The last 10-15 minutes of data is used to calculate the average login time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of the Login operation. If this metric is out-of-bounds (the average time to login is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help to determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.5 Average Logout Time (ms)

This metric indicates the average time spent logging out from the back-end discussions server hosting announcements (in ms).

The last 10-15 minutes of data is used to calculate the average logout time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of the Logout operation. If this metric is out-of-bounds (the average time to logout is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help to determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.6 Average Processing Time (ms)

This metric indicates the average time the Announcements service spends processing announcement operations (in ms).

Announcement operations include: Create, List, Search, Login, Logout. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of Announcements service operations.

If this metric is out-of-bounds (the average time for announcement operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.7 Average Search Time (ms)

This metric indicates the average time the Announcements service spends searching for terms within announcement text (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Search operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.8 Creates (per minute)

This metric indicates the total number of Create operations the Announcements service performs per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create operations per minute for the Announcements service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.9 Failed Invocations (%)

This metric indicates the percentage of Announcements service invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Announcement Metrics.

27.13.10 Invocations (per minute)

This metric indicates the total number of Announcements service invocations per minute.

The number of invocations per operation is available on application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for the Announcements service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.11 Lists (per minute)

This metric indicates the total number of List operations the Announcements service performs per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of the List operation per minute for the Announcements service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.12 Logins (per minute)

This metric counts the number of times per minute a WebCenter user logs in to the back-end discussions server hosting announcements.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the Announcements service. You can evaluate when most logins occur, as well as the maximum and minimum usage-- which can be useful for tuning discussion server performance.

If you are experiencing performance issues outside normal peak login times, navigate to the application's main metric page where detailed metric data for all operations is available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.13 Logouts (per minute)

This metric counts the number of times per minute a WebCenter user logs out from the back-end discussions server hosting announcements.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the Announcements service. You can evaluate when most logouts occur, as well as the maximum and minimum usage-- which can be useful for tuning discussion server performance.

If you are experiencing performance issues outside normal peak login times, navigate to the application's main metric page where detailed metric data for all operations is available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.14 Searches (per minute)

This metric indicates the total number of Search operations the Announcements service performs per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Search operations per minute for the Announcements service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.15 Status

This metric indicates whether the Announcements service are up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.13.16 Successful Invocations (%)

This metric indicates the percentage of Announcements service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.13.17 Service Name

These metrics apply to the Announcements service.

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.14 WebCenter Spaces

Provides information about WebCenter Spaces metrics.

27.14.1 Application Name

The application name

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.14.2 Failed Invocations (%)

This metric indicates the percentage of Space invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Space Metrics.

27.14.3 Successful Invocations (%)

This metric indicates the percentage of Space invocations that succeeded. Processing time is available on application's main metric page.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100% investigate this metric in more detail. Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

27.14.4 Invocations (per minute)

This metric indicates the number of Space invocations per minute.

The number of invocations for this Space is available on application's Space metric page. See, Monitoring WebCenter Spaces Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for this Space is high (compared with other Spaces), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also,Analyzing Space Metrics.

27.14.5 Page Throughput (per minute)

This metric shows the average number of pages accessed per minute for the Space.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the Space. You can evaluate when pages are accessed the most, as well as the maximum and minimum usage.

See also, Analyzing Space Metrics.

27.14.6 Errors (per minute)

This metric shows the average number of errors that occur per minute in the Space.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average number of errors is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Space Metrics.

27.14.7 Average Page Processing Time (ms)

This metric indicates the average time spent processing operations for a particular Space (in ms).

The last 10-15 minutes of data is used to calculate the average page processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of a Space.

If this metric is out-of-bounds (the average time for Space operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Space Metrics.

27.15 WebCenter Content Repositories

Provides information about WebCenter Content Repository metrics.

27.15.1 Application Name

This metric identifies the WebCenter application to which these content repository metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.15.2 Average Delete Time (ms)

This metric indicates the average time the Documents service spends deleting documents stored in a content repository.

The last 10-15 minutes of data is used to calculate the average time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Delete operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.15.3 Average Download Time (ms)

This metric indicates the average time the Documents service spends downloading documents from a content repository.

The last 10-15 minutes of data is used to calculate the average time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Download operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.15.4 Average Get Item Time (ms)

This metric indicates the average time spent selecting and displaying items, such as a document or image, in Content Presenter task flows.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

User Action

If this metric is out-of-bounds (the average time for the Get Item operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.15.5 Average List Folder Time (ms)

This metric indicates the average time Content Presenter task flows spend listing folders stored in a content repository.

The last 10-15 minutes of data is used to calculate the average time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

User Action

If this metric is out-of-bounds (the average time for the List folder operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.15.6 Average Login Time (ms)

This metric indicates the average time spent logging in to the content repository (in ms).

The last 10-15 minutes of data is used to calculate the average login time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of the Login operation. If this metric is out-of-bounds (the average time to login is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.15.7 Average Processing Time (ms)

This metric indicates the average time the Documents service spends processing operations relating to this content repository (in ms).

Content repository operations include: Download, Upload, Login, Delete. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of Document service operations, for this content repository.

If this metric is out-of-bounds (the average time for content repository operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.15.8 Average Search Time (ms)

This indicates the average time the Documents service spends searching for documents stored in a content repository.

The last 10-15 minutes of data is used to calculate the average time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Search operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.15.9 Average Upload Time (ms)

This indicates the average time the Documents service spends uploading documents to a content repository.

The last 10-15 minutes of data is used to calculate the average time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Upload operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics

27.15.10 Deletes (per minute)

This indicates total number of Delete operations the Documents service performs in a minute on a content repository.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues, and the number of Delete operations is high (compared with other services) consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.15.11 Downloads (per minute)

This metric indicates total number of Download operations the Documents service performs in a minute on a content repository.

The last 10-15 minutes of data is used to calculate the average time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues, and the number of Download operations is high (compared with other services) consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.15.12 Download Throughput (bytes per second)

This metric shows the average download speed per second.

All content repositories in the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor typical and peak download time. You can evaluate when information is downloaded the most, as well as the maximum and minimum downloads.

27.15.13 Failed Invocations (%)

This metric indicates the percentage of the Documents service invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Content Repository Metrics.

27.15.14 Get Item

This metric indicates the number of times an item, such as a document or image, is selected or displayed in Content Presenter task flows.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

User Action

If you are experiencing performance issues and the number of Get Item operations is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.15.15 Invocations (per minute)

This metric indicates the total number of Documents service invocations per minute for this content repository.

The number of invocations per operation is available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for this content repository is high (compared with other content repositories), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.15.16 List Folder

This metric indicates the number of times folder content is displayed through Content Presenter task flows.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

User Action

If you are experiencing performance issues and the number of List Folder operations is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.15.17 Logins (per minute)

This metric counts the number of times a WebCenter user logs in to the content repository per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the content repository. You can evaluate when most logins occur, as well as the maximum and minimum usage--which can be useful for tuning content repository performance.

If you are experiencing performance issues outside normal peak login times, navigate to the application's main metric page where detailed metric data for all operations is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.15.18 Searches (per minute)

This metric indicates the number of times content is searched per minute in a content repository.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the number of Search operations is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.15.19 Status

This metric indicates whether the Documents service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.15.20 Successful Invocations (%)

This metric indicates the percentage of Documents service invocations that succeeded for this content repository.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.15.21 Uploads (per minute)

This metric indicates the number of times the Documents service uploads documents in a content repository per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the number of Upload operations is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.15.22 Upload Throughput (bytes per second)

This metric shows the average upload speed per second.

All content repositories in the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor typical and peak upload time. You can evaluate when information is uploaded the most, as well as the maximum and minimum uploads.

27.16 WebCenter Events

Provides information about the WebCenter events metrics.

27.16.1 Application Name

This metric identifies the WebCenter application to which the Events service metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.16.2 Average Create Time (ms)

This metric indicates the average time the Events service spends creating an event in the WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for Create operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.3 Average Delete Time (ms)

This metric indicates the average time the Events service spends deleting events in a WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for Delete operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.4 Average List Time (ms)

This metric indicates the average time the Events service spends retrieving a list of events from the WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for List operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.5 Average Processing Time (ms)

This metric indicates the average time the Events service spends processing operations (in ms) associated with events.

Events operations include: Create Event, Update Event, List Event, Delete Event, Search Event. Processing times for individual operations are available on the application's main metric page for events. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10- 15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of Events service operations. If this metric is out-of-bounds (the average time for Events operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available for events. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.6 Average Search Time (ms)

This metric indicates the average time the Events service spends searching for terms within event text (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for Search operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.7 Average Update Time (ms)

This metric indicates the average time the Events service spends updating events in the WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for Update operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.8 Creates (per minute)

This metric indicates the total number of Create operations per minute for the Events service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create operations per minute for the Events service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.9 Deletes (per minute)

This metric indicates the total number of Delete operations per minute for the Events service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Delete operations per minute for the Events service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.10 Failed Invocations (%)

This metric indicates the percentage of Events service invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Events Metrics.

27.16.11 Invocations (per minute)

This metric indicates the total number of invocations per minute for the Events service.

The number of invocations per operation for events is available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for the Events service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.12 Lists (per minute)

This metric indicates the total number of List operations per minute for the Events service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of List operations per minute for the Events service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.13 Searches (per minute)

This metric indicates the total number of Search operations per minute for the Events service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Search operations per minute for the Events service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.14 Status

This metric indicates whether the Events service up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.16.15 Successful Invocations (%)

This metric indicates the percentage of Events service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric further. Navigate to the application's main metric page where detailed metric data for individual operations is also available for events. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.16 Updates (per minute)

This metric indicates the total number of Update operations per minute for the Events service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Update operations per minute for the Events service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.17 WebCenter External Applications Connections

Provides information about WebCenter External Applications metrics.

27.17.1 Application Name

This metric identifies the WebCenter application to which these External Application metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.17.2 Invocations (per minute)

This metric indicates the total number of times per minute a single external application was accessed.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate application performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for this external application is high (compared with other external applications), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See, Analyzing External Application Metrics.

27.18 WebCenter External Applications

Provides information about the WebCenter external applications metrics.

27.18.1 Application Name

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

27.18.2 Automated Logins (per minute)

This metric indicates the total number of logins per minute -- when WebCenter users logs in to an external application using the automated login feature.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of automated logins per minute for the external application is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.18.3 Average Automated Login Time (ms)

This metric indicates the average time spent logging WebCenter users to an external application using the automated login feature (in ms).

The last 10-15 minutes of data is used to calculate the average login time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of the Login operation. If this metric is out-of-bounds (the average time to login is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.18.4 Average Fetch Credential Time (ms)

This metric indicates the average time spent retrieving credentials for an external application (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of the Fetch Credential operation. If this metric is out-of-bounds (the average time to fetch credentials is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.18.5 Average Fetch External Application Time (ms)

This metric indicates the average time spent retrieving an external application (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of the Fetch External Application operation. If this metric is out-of-bounds (the average time to fetch credentials is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.18.6 Average Processing Time (ms)

This metric indicates the average time spent processing external application operations (in ms).

External application operations include: Fetch Credentials, Store Credentials, Fetch External Application, and Automated Logins. Processing times for individual operations are available on application's main metric page. See, Viewing Performance Information.

All external applications used by the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the overall external application performance. If this metric is out-of-bounds (the average time for external application operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.18.7 Average Store Credentials Time (ms)

This metric indicates the average time spent storing user credentials for an external application (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of the Store Credential operation. If this metric is out-of-bounds (the average time to fetch credentials is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.18.8 Credential Fetches (per minute)

This metric indicates the total number of Fetch Credential operations per minute for an external application.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Fetch Credential operations per minute for an external application is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.18.9 Credential Stores (per minute)

This metric indicates the total number of Store Credential operations per minute for an external application.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Store Credential operations per minute for an external application is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.18.10 External Application Fetches (per minute)

This metric indicates the total number of Fetch External Application operations per minute for an external application.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Fetch External Application operations per minute for an external application is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.18.11 Failed Invocations (%)

This metric indicates the percentage of External Applications service invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing External Application Metrics.

27.18.12 Invocations (per minute)

This metric indicates the total number of times per minute a single external application was accessed.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate application performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for this external application is high (compared with other external applications), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See, Analyzing External Application Metrics.

27.18.13 Status

This metric indicates whether the External Applications service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.18.14 Successful Invocations (%)

This metric indicates the percentage of external application invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count. All the external applications accessed by the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, check the diagnostic logs to establish why service operations are failing. Typical examples are, trying to invoke the automated login servlet without being authenticated or specifying an incorrect external application name. Navigate to the application's main metric page where more detailed metric data for individual external applications is also available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.18.15 Name

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

27.19 WebCenter Discussion Forum

Provides information about the WebCenter Discussion forum metrics.

27.19.1 Application Name

This metric identifies the WebCenter application to which these Discussions service metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.19.2 Average Create Forum Time (ms)

This metric indicates the average time the Discussions service spends creating a discussion forum in the discussions server, under a specific category (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for Create Forum operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.3 Average Create Topic Time (ms)

This metric indicates the average time the Discussions service spends creating a discussion topic in the discussions server, under a specific forum (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for Create Topic operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.4 Average List Forums Time (ms)

This metric indicates the average time the Discussions service spends retrieving a list of forums, under a specific category, from the discussion server (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for List Forums operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.5 Average List Topics Time (ms)

This metric indicates the average time the Discussions service spends retrieving a list of topics, under a specific forum, from the discussion server (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for List Topics operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.6 Average Login Time (ms)

This metric indicates the average time spent logging in to the back-end discussions server hosting discussion forums (in ms).

The last 10-15 minutes of data is used to calculate the average login time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of Login operations. If this metric is out-of-bounds (the average time to login is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help to determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.7 Average Logout Time (ms)

This metric indicates the average time spent logging out from the back-end discussions server hosting discussion forums (in ms).

The last 10-15 minutes of data is used to calculate the average logout time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of the Logout operation. If this metric is out-of-bounds (the average time to logout is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help to determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.8 Average Processing Time (ms)

This metric indicates the average time the Discussions service spends processing operations (in ms).

Discussions service operations include: Login, Create Forum, Create Topic, List Forums, List Topics, Search, Logout. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of Discussions service operations.

If this metric is out-of-bounds (the average time for discussion forum operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.9 Average Reply Time (ms)

This metric indicates the average time the Discussions service spends replying to a topic, under a specific forum, from the discussion server (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Reply operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.10 Average Search Time (ms)

This metric indicates the average time the Discussions service spends searching for terms within discussion forum text, in the discussions server (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Search operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.11 Create Forum (per minute)

This metric indicates the total number of Create Forum operations per minute for the Discussions service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create Forum operations per minute for the Discussions service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.12 Create Topic (per minute)

This metric indicates the total number of Create Topic operations per minute for the Discussions service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create Topic operations per minute for the Discussions service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.13 Failed Invocations (%)

This metric indicates the percentage of Discussions service invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Discussions Metrics.

27.19.14 Invocations (per minute)

This metric indicates the total number of Discussions service invocations per minute. The number of invocations per operation is available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for the Discussions service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.15 List Forums (per minute)

This metric indicates the total number of List Forums operations per minute for the Discussions service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of List Forums operations per minute for the Discussions service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.16 List Topics (per minute)

This metric indicates the total number of List Topics operations per minute for the Discussions service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of List Forums operations per minute for the Discussions service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.17 Logins (per minute)

This metric counts the number of times per minute a WebCenter user logs in to the back-end discussions server hosting discussion forums.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the Discussions service. You can evaluate when most logins occur, as well as the maximum and minimum usage-- which can be useful for tuning discussion server performance.

If you are experiencing performance issues outside normal peak login times, navigate to the application's main metric page where detailed metric data for all operations is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.18 Logouts (per minute)

This metric counts the number of times per minute a WebCenter user logs out from the back-end discussions server hosting discussion forums.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the Discussions service. You can evaluate when most logouts occur, as well as the maximum and minimum usage-- which can be useful for tuning discussion server performance.

If you are experiencing performance issues outside normal peak login times, navigate to the application's main metric page where detailed metric data for all operations is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.19 Replies (per minute)

This metric indicates the total number of replies to discussion topics per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of replies per minute is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.20 Searches (per minute)

This metric indicates the total number of searches in the discussions server per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of searches per minute is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.21 Status

This metric indicates whether the Discussions service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.19.22 Successful Invocations (%)

This metric indicates the percentage of Discussions service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.19.23 Service Name

These metrics apply to the Discussions service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.20 WebCenter Pages

Provides information about WebCenter pages metrics.

27.20.1 Application Name

This metric identifies the WebCenter application to which these page metrics apply.

User Action

No action required.

27.20.2 Average Page Processing Time (ms)

This metric indicates the average time (in ms) to display the page.

The last 10-15 minutes of data is used to calculate the average page processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of a page.

If this metric is out-of-bounds (the average time to display pages is increasing or higher than expected), navigate to the application's page metric page where more detailed metric data is available.

See, Monitoring Page Metrics for Spaces and Monitoring Page Metrics for WebCenter Applications.

27.20.3 Average Partial Page Processing Time (ms)

This metric indicates the average time (in ms) to refresh the partial page.

The last 10-15 minutes of data is used to calculate the average page processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

27.20.4 Errors (per minute)

This metric shows the average number of errors that occur per minute in the page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average number of errors is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See, Monitoring Page Metrics for Spaces and Monitoring Page Metrics for WebCenter Applications.

27.20.5 Failed Invocations (%)

This metric indicates the percentage of page invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See, Monitoring Page Metrics for Spaces and Monitoring Page Metrics for WebCenter Applications.

27.20.6 Invocations (per minute)

This metric indicates the total number of page invocations per minute.

The number of invocations for this page is available on application's main metric page. See Monitoring Page Metrics for Spaces and Monitoring Page Metrics for WebCenter Applications.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate page performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for this page is high (compared with other pages), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's page metric page where more detailed metric data is available. See, Monitoring Page Metrics for Spaces and Monitoring Page Metrics for WebCenter Applications.

27.20.7 Page Throughput (per minute)

This metric shows the average number of pages accessed per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the page. You can evaluate when this page is accessed the most, as well as the maximum and minimum usage.

See, Monitoring Page Metrics for Spaces and Monitoring Page Metrics for WebCenter Applications.

27.20.8 Partial Page Invocations (per minute)

This metric indicates the total time per minute to refresh the partial page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate partial page performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for this partial page is high (compared with other pages), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's page metric page where more detailed metric data is available.

See, Monitoring Page Metrics for Spaces and Monitoring Page Metrics for WebCenter Applications.

27.20.9 Status

This metric indicates whether or not the page is available. If the value is 1, the service is up. If the value is 0, it is down.

27.20.10 Successful Invocations (%)

This metric indicates the percentage of page invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, navigate to the application's page metric page where more detailed metric data is available.

See Monitoring Page Metrics for Spaces and Monitoring Page Metrics for WebCenter Applications.

You can also check the diagnostic logs to establish why page invocations are failing.

27.21 WebCenter Import/Export

Provides information about WebCenter Import/Export metrics.

27.21.1 Application Name

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

27.21.2 Average Processing Time (ms)

This metric indicates the average time in which an entire WebCenter application is imported or exported (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of import/export operations. If this metric is out-of-bounds (the average time for import/export operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

27.21.3 Failed Invocations (%)

This metric indicates the percentage of import/export invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

27.21.4 Invocations (per minute)

This metric indicates the total number of import/export invocations per minute.

The number of invocations for this page is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate import/export performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for import/export is high (compared with other pages), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's import/export metric page where more detailed metric data is available.

27.21.5 Status

This metric indicates whether import/export is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.21.6 Successful Invocations (%)

This metric indicates the percentage of page invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, navigate to the application's import/export metric page where more detailed metric data is available.

You can also check the diagnostic logs to establish why page invocations are failing.

27.21.7 Service Name

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

27.22 WebCenter Lists

Provides information about WebCenter Lists metrics.

27.22.1 Application Name

This metric identifies the WebCenter application to which these Lists service metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.22.2 Average Copy List Time (ms)

This metric indicates the average time the Lists service spends copying a list in the user session (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Copy List operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.3 Average Copy List Type Time (ms)

This metric indicates the average time the Lists service spends copying a list type in the user session (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Copy List Type operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.4 Average Copy Rows Time (ms)

This metric indicates the average time the Lists service spends copying rows of list data in the user session (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Copy Rows operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.5 Average Create List Time (ms)

This metric indicates the average time the Lists service spends creating a list in the user session (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Create List operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.6 Average Create List Type Time (ms)

This metric indicates the average time the Lists service spends creating a list type in the user session (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Create List Type operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.7 Average Create Row Time (ms)

This metric indicates the average time the Lists service spends creating rows of list data in the user session (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Create Row operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.8 Average Delete List Time (ms)

This metric indicates the average time the Lists service spends deleting a list and its data in the user session (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Delete List operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.9 Average Delete List Type Time (ms)

This metric indicates the average time the Lists service spends deleting a list type in the user session (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Delete List Type operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.10 Average Delete Row Time (ms)

This metric indicates the average time the Lists service spends deleting a row of list data in the user session (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Delete Row operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.11 Average Processing Time (ms)

This metric indicates the average time the Lists service spends processing list operations (in ms).

List operations include: Create List, Copy List, Delete List, Create Row, Delete Row, Update Row, Search, and Save Data. Processing times for individual operations are available on application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of Lists service operations. If this metric is out-of-bounds (the average time for list operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.12 Average Query Time (ms)

This metric indicates the average time the Lists service spends querying list data in the user session (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Query operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.13 Average Retrieve Rows Time (ms)

This metric indicates the average time the Lists service spends retrieving rows and their data in the user session (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Retrieve Rows operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.14 Average Save Time (ms)

This metric indicates the average time the Lists service spends saving lists in the WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Save operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.15 Average Update Row Time (ms)

This metric indicates the average time the Lists service spends updating rows of list data in the user session (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Update Row operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.16 Copy List (per minute)

This metric indicates the total number of Copy List operations per minute for the Lists service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Copy List operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.17 Copy List Type (per minute)

This metric indicates the total number of Copy List Type operations per minute for the Lists service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Copy List Type operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.18 Copy Rows (per minute)

This metric indicates the total number of Copy Rows operations per minute for the Lists service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Copy Rows operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.19 Create List (per minute)

This metric indicates the total number of Create List operations per minute for the Lists service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create List operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.20 Create List Type (per minute)

This metric indicates the total number of Create List Type operations per minute for the Lists service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create List Type operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.21 Create Row (per minute)

This metric indicates the total number of Create Row operations per minute for the Lists service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create Row operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.22 Delete List (per minute)

This metric indicates the total number of Delete List operations per minute for the Lists service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Delete List operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.23 Delete List Type (per minute)

This metric indicates the total number of Delete List Type operations per minute for the Lists service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Delete List Type operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.24 Delete Row (per minute)

This metric indicates the total number of Delete Row operations per minute for the Lists service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Delete Row operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.25 Failed Invocations (%)

This metric indicates the percentage of Lists service invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing List Metrics.

27.22.26 Invocations (per minute)

This metric indicates the total number of Lists service invocations per minute. The number of invocations per operation is available on the application's main metric page. See Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.27 Queries (per minute)

This metric indicates the total number of queries per minute for the Lists service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of queries per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.28 Retrieve Rows (per minute)

This metric indicates the total number of Retrieve Rows operations per minute for the Lists service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Retrieve Rows operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.29 Saves (per minute)

This metric indicates the total number of times lists data is saved per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Save operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.30 Status

This metric indicates whether the Lists service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.22.31 Successful Invocations (%)

This metric indicates the percentage of Lists service invocations that succeeded. Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is less than 100%, navigate to the application's main metric page where more detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.22.32 Update Row (per minute)

This metric indicates the total number of Update Row operations per minute for the Lists service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Update Row operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.33 Service Name

These metrics apply to the Lists service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.23 WebCenter Mail

Provides information about the WebCenter Mail metrics.

27.23.1 Application Name

This metric identifies the WebCenter application to which these Mail service metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.23.2 Average Login Time (ms)

This metric indicates the average time spent logging in to the mail server that is hosting mail services (in ms).

The last 10-15 minutes of data is used to calculate the average login time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of the Login operation. If this metric is out-of-bounds (the average time to login is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.3 Average Logout Time (ms)

This metric indicates the average time spent logging out from the mail server that is hosting mail services (in ms).

The last 10-15 minutes of data is used to calculate the average logout time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of the Logout operation. If this metric is out-of-bounds (the average time to logout is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help to determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.4 Average Processing Time (ms)

This metric indicates the average time the Mail service spends processing operations (in ms).

Mail operations include: Login, Logout, Receive, Send, Search. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of Mail service operations.

If this metric is out-of-bounds (the average time for mail operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.5 Average Receive Time (ms)

This metric indicates the average time the Mail service spends receiving a mail (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Receive operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.6 Average Search Time (ms)

This metric indicates the average time the Mail service spends searching for a mail that contains a specific term (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Search operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.7 Average Send Time (ms)

This metric indicates the average time the Mail service spends sending a mail (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Send operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.8 Failed Invocations (%)

This metric indicates the percentage of Mail service invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Mail Metrics.

27.23.9 Invocations (per minute)

This metric indicates the total number of Mail service invocations per minute.

The number of invocations per operation is available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for the Mail service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.10 Logins (per minute)

This metric counts the number of times per minute a WebCenter user logins to the back-end mail server that is hosting mail services.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the Instant Messaging and Presence (IMP) service.

Use this metric to monitor typical and peak usage of the Mail service. You can evaluate when most logins occur, as well as the maximum and minimum usage--which can be useful for tuning mail server performance.

If you are experiencing performance issues outside normal peak login times, navigate to the application's main metric page where detailed metric data for all operations is available. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.11 Logout (per minute)

This metric counts the number of times per minute a WebCenter user logs out from the mail server that is hosting mail services.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the Mail service. You can evaluate when most logouts occur, as well as the maximum and minimum usage-- which can be useful for tuning discussion server performance.

If you are experiencing performance issues outside normal peak login times, navigate to the application's main metric page where detailed metric data for all operations is available. See, Viewing Performance Information.

27.23.12 Receives (per minute)

This metric indicates the total number of Receive operations per minute for the Mail service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Receive operations per minute for the Mail service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.13 Searches (per minute)

This metric indicates the total number of Search operations per minute for the Mail service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Search operations per minute for the Mail service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.14 Sends (per minute)

This metric indicates the total number of Send operations per minute for the Mail service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Send operations per minute for the Mail service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.15 Status

This metric indicates whether the Mail service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.23.16 Successful Invocations (%)

This metric indicates the percentage of Mail service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.23.17 Service Name

These metrics apply to the Mail service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.24 WebCenter Notes

Provides information about the WebCenter Notes metrics.

27.24.1 Application Name

This metric identifies the WebCenter application to which these Notes service metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.24.2 Average Create Time (ms)

This metric indicates the average time the Notes service spends creating a personal note (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Create operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.3 Average Delete Time (ms)

This metric indicates the average time the Notes service spends deleting a personal note (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Delete operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.4 Average Find Time (ms)

This metric indicates the average time the Notes service spends retrieving a note from the MDS repository (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Retrieve operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.5 Average Processing Time (ms)

This metric indicates the average time the Notes service spends processing note operations (in ms).

Notes operations include: Create, Update, Find. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of Notes service operations. If this metric is out-of-bounds (the average time for note operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.6 Average Save Changes Time (ms)

This metric indicates the average time the Notes service spends saving new notes to the MDS repository (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Save Changes operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.7 Average Update Time (ms)

This metric indicates the average time the Notes service spends updating a personal note (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Update operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.8 Creates (per minute)

This metric indicates the total number of Create operations per minute for the Notes service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create operations per minute for the Notes service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.9 Deletes (per minute)

This metric indicates the total number of Delete operations per minute for the Notes service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Delete operations per minute for the Notes service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.10 Failed Invocations (%)

This metric indicates the percentage of Notes service invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Note Metrics.

27.24.11 Finds (per minute)

This metric indicates the total number of Find operations per minute for the Notes service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Find operations per minute for the Notes service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.12 Invocations (per minute)

This metric indicates the total number of Notes service invocations per minute.

The count includes the following Notes operations: Create, Delete, Find, Find All Notes, Save Changes, Update. The number of invocations per operation is available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for the Notes service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

Also see, Analyzing Note Metrics.

27.24.13 Save Changes (per minute)

This metric indicates the total number of Save Changes operations per minute for the Notes service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Save Changes operations per minute for the Notes service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.14 Status

This metric indicates whether the Notes service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.24.15 Successful Invocations (%)

This metric indicates the percentage of Notes service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%), investigate this metric further. Navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.24.16 Updates (per minute)

This metric indicates the total number of Update operations per minute for the Notes service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Update operations per minute for the Notes service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.17 Service Name

These metrics apply to the Notes service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.25 WebCenter Page Service

Provides information about the WebCenter Page Service metrics.

27.25.1 Application Name

This metric identifies the WebCenter application to which these Page service metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.25.2 Average Copy Time (ms)

This metric indicates the average time the Page service spends copying a page in the WebCenter application (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Copy operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

27.25.3 Average Create Time (ms)

This metric indicates the average time the Page service spends creating a page in the WebCenter application (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Create operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

27.25.4 Average Delete Time (ms)

This metric indicates the average time the Page service spends deleting a page in the WebCenter application (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Delete operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

27.25.5 Average Processing Time (ms)

This metric indicates the average time the Page service spends processing operations associated with the Page service (in ms).

Page operations include: Create, Update Properties, Copy, Delete, Search. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric whilst assessing the overall performance of the Page service.

If this metric is out-of-bounds (the average time for page operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

27.25.6 Average Search Time (ms)

This metric indicates the average time the Page service spends searching for pages that contain a specific term (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Search operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

27.25.7 Average Update Time (ms)

This metric indicates the average time the Page service spends updating a page (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Update operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

27.25.8 Copies (per minute)

This metric indicates the total number of Copy operations per minute for the Page service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Copy operations per minute for the Page service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

27.25.9 Creates (per minute)

This metric indicates the total number of Create operations per minute for the Page service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create operations per minute for the Page service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

27.25.10 Deletes (per minute)

This metric indicates the total number of Delete operations per minute for the Page service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Delete operations per minute for the Page service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

27.25.11 Failed Invocations (%)

This metric indicates the percentage of Pages service invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Page Metrics.

27.25.12 Invocations (per minute)

This metric indicates the total number of Page service invocations per minute.

The number of invocations per operation is available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for the Page service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also Analyzing Page Metrics.

27.25.13 Searches (per minute)

This metric indicates the total number of Search operations per minute for the Page service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Search operations per minute for the Page service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

27.25.14 Status

This metric indicates whether the Pages service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.25.15 Updates (per minute)

This metric indicates the total number of Update operations per minute for the Page service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Update operations per minute for the Page service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

27.25.16 Successful Invocations (%)

This metric indicates the percentage of Page service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.25.17 Service Name

These metrics apply to the Page service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.26 WebCenter People Connections

Provides information about the WebCenter People Connections metrics.

27.26.1 Application name

This metric identifies the WebCenter application to which these People Connections service metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.26.2 Average Processing Time (ms)

This metric indicates the average time the People Connections service spends processing user operations (in ms).

People Connection operations include: Get Profiles, Get Activities, Publish Activities, Get Messages, Get Feedback, Get Connections. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of People Connection service operations. If this metric is out-of-bounds (the average time for user operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.3 Failed Invocations (%)

This metric indicates the percentage of people connection invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing People Connection Metrics.

27.26.4 Get Feedback (per minute)

This metric indicates the total number of Get Feedback operations per minute for the People Connections service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Get Feedback operations per minute for the People Connections service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.5 Get Feedback Average Time (ms)

This metric indicates the average time the People Connections service spends getting the feedback of the user (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Get Feedback operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.6 Invocations (per minute)

This metric indicates the total number of People Connection service invocations per minute.

The count includes the following People Connection operations: Get Profiles, Get Activities, Publish Activities, Get Messages, Get Feedback, Get Connections. The number of invocations per operation is available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for the People Connections service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

Also see, Analyzing People Connection Metrics.

27.26.7 Publish Activity (per minute)

This metric indicates the total number of Publish Activity operations per minute for the People Connections service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Publish Activity operations per minute for the People Connections service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.8 Publish Activity Average Time (ms)

This metric indicates the average time the People Connections service spends publishing an activity in the user session and saving it in the WebCenter application (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Publish Activity operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.9 Retrieve Activities (per minute)

This metric indicates the total number of Retrieve Activity operations per minute for the People Connections service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Retrieve Activity operations per minute for the People Connections service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.10 Retrieve Activities Average Time (ms)

This metric indicates the average time the People Connections service spends retrieving activities based on the user filter options (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Retrieve Activity operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.11 Retrieve Connections Average Time (ms)

This metric indicates the average time the People Connections service spends retrieving connections of users (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Retrieve Connections operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.12 Retrieve Messages (per minute)

This metric indicates the total number of Retrieve Message operations per minute for the People Connections service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Retrieve Message operations per minute for the People Connections service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.13 Retrieve Messages Average Time (ms)

This metric indicates the average time the People Connections service spends retrieving messages of users (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Retrieve Messages operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.14 Retrieve Profiles (per minute)

This metric indicates the total number of Retrieve Profile operations per minute for the People Connections service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Retrieve Profile operations per minute for the People Connections service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.15 Retrieve Profiles Average Time (ms)

This metric indicates the average time the People Connections service spends retrieving profiles of users (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Retrieve Profiles operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.16 Status

This metric indicates whether the People Connections service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.26.17 Successful Invocations (%)

This metric indicates the percentage of People Connections service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%), investigate this metric further. Navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.26.18 Service Name

These metrics apply to the People Connections service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.27 WebCenter Polls

Provides information about WebCenter Polls metrics.

27.27.1 Application Name

This metric identifies the WebCenter application to which these Poll service metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.27.2 Analyze Poll (per minute)

This metric indicates the total number of Analyze Poll operations per minute for the Polls service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Analyze Poll operations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.3 Analyze Poll Average Time (ms)

This metric indicates the average time the Polls service spends analyzing poll results (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Analyze Poll operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.4 Average Processing Time (ms)

This metric indicates the average time the Polls service spends processing poll operations (in ms).

Polls operations include: Create Poll, Edit Poll, Delete Poll, Get Poll By ID, Submit Poll, Analyze Results. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of Poll service operations. If this metric is out-of-bounds (the average time for poll operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.5 Create Poll (per minute)

This metric indicates the total number of Create Poll operations per minute for the Polls service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create Poll operations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.6 Create Poll Average Time (ms)

This metric indicates the average time the Polls service spends creating a poll in the WebCenter application (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Create Poll operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.7 Create Response (per minute)

This metric indicates the total number of Create Response operations per minute for the Polls service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create Response operations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.8 Create Response Average Time (ms)

This metric indicates the average time the Polls service spends creating a response to a poll in the WebCenter application (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Create Response operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.9 Delete Poll (per minute)

This metric indicates the total number of Delete Poll operations per minute for the Polls service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Delete Poll operations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.10 Delete Poll Average Time (ms)

This metric indicates the average time the Polls service spends deleting a poll in the WebCenter application (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Delete Poll operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.11 Edit Poll (per minute)

This metric indicates the total number of Edit Poll operations per minute for the Polls service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Edit Poll operations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.12 Edit Poll Average Time (ms)

This metric indicates the average time the Polls service spends editing a poll in the WebCenter application (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Edit Poll operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.13 Failed Invocations (%)

This metric indicates the percentage of Polls service invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Poll Metrics.

27.27.14 Get Poll (per minute)

This metric indicates the total number of Get Poll operations per minute for the Polls service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Get Poll operations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.15 Get Poll By Id (per minute)

This metric indicates the total number of Get Poll By Id operations per minute for the Polls service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Get Poll By Id operations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.16 Get Poll By Id Average Time (ms)

This metric indicates the average time the Polls service spends displaying the ongoing poll (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Get Poll By Id operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.17 Get Poll Response Average Time (per minute)

This metric indicates the total number of Get Poll Response operations per minute for the Polls service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Get Poll Response operations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.18 Status

This metric indicates whether the Polls service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.27.19 Successful Invocations (%)

This metric indicates the percentage of Poll service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%), investigate this metric further. Navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.27.20 Invocations (per minute)

This metric indicates the total number of Poll service invocations per minute.

The count includes the following Polls operations: Create Poll, Edit Poll, Delete Poll, Get Poll By ID, Submit Poll, Analyze Results. The number of invocations per operation is available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

Also see, Analyzing Poll Metrics.

27.27.21 Service Name

These metrics apply to the Polls service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.28 WebCenter Recent Activity

Provides information about the WebCenter Recent Activity metrics.

27.28.1 Application Name

This metric identifies the WebCenter application to which these Recent Activity metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.28.2 Average Processing Time (ms)

This metric indicates the total time the Recent Activities service spends processing Recent Activity operations (in ms).

Processing time is available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of Recent Activities service operations.

If this metric is out-of-bounds (the average time for recent activity operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Recent Activity Metrics.

27.28.3 Failed Invocations (%)

This metric indicates the percentage of Recent Activities invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Recent Activity Metrics.

27.28.4 Invocations (per minute)

This metric indicates the total number of Recent Activities service invocations per minute.

The number of invocations is available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for the Recent Activities service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Recent Activity Metrics.

27.28.5 Status

This metric indicates whether the Recent Activities service is up or down. If the value is 1, the service is up. If the value is 0, it is down

27.28.6 Successful Invocations (%)

This metric indicates the percentage of Recent Activities service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Recent Activity Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.28.7 Service Name

These metrics apply to the Recent Activities service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.29 WebCenter RSS News Feeds

Provides information about the WebCenter RSS News Feeds metrics.

27.29.1 Application Name

This metric identifies the WebCenter application to which these RSS News Feed metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.29.2 Average Processing Time (ms)

This metric indicates the average time the RSS service spends processing operations (in ms).

Processing time is available on application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of RSS service operations.

If this metric is out-of-bounds (the average time for RSS operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing RSS News Feed Metrics.

27.29.3 Failed Invocations (%)

This metric indicates the percentage of RSS service invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing RSS News Feed Metrics.

27.29.4 Invocations (per minute)

This metric indicates the total number of RSS New Feed invocations per minute.

The number of invocations is available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for RSS news feeds is high (compared with other services consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing RSS News Feed Metrics.

27.29.5 Status

This metric indicates whether the RSS service is up or down. If the value is 1, the service is up. If the value is 0, it is down

27.29.6 Successful Invocations (%)

This metric indicates the percentage of RSS service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing RSS News Feed Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.29.7 Service Name

These metrics apply to the RSS service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.30 WebCenter Instant Messaging and Presence

Provides information about the WebCenter Instant Messaging and Presence metrics.

27.30.1 Application Name

This metric identifies the WebCenter application to which these Instant Messaging and Presence service metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.30.2 Average Get Presence Time (ms)

This metric indicates the average time the IMP service spends retrieving user presence information from the IMP server (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Get Presence operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

27.30.3 Average Login Time (ms)

This metric indicates the average time spent logging in to the back-end server hosting instant messaging and presence services (in ms).

The last 10-15 minutes of data is used to calculate the average login time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of the Login operation. If this metric is out-of-bounds (the average time to login is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

27.30.4 Average Logout Time (ms)

This metric indicates the average time spent logging out from the IMP server hosting presence information (in ms).

The last 10-15 minutes of data is used to calculate the average logout time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of the Logout operation. If this metric is out-of-bounds (the average time to logout is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help to determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

27.30.5 Average Processing Time (ms)

This metric indicates the average time the Instant Messaging and Presence (IMP) service spends processing IMP operations (in ms).

IMP operations include: Get Presence, Login, Logout. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of Instant Messaging and Presence (IMP) service operations.

If this metric is out-of-bounds (the average time for IMP operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

27.30.6 Failed Invocations (%)

This metric indicates the percentage of IMP service invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

27.30.7 Get Presence (per minute)

This metric indicates the total number of Get Presence operations per minute for the Polls service.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Get Presence operations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

27.30.8 Invocations (per minute)

This metric indicates the total number of Instant Messaging and Presence (IMP) service invocations per minute.

The number of invocations per operation is available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for the IMP service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

27.30.9 Logins (per minute)

This metric counts the number of times a minute a WebCenter user logins to the server that is hosting instant messaging and presence services.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the Instant Messaging and Presence (IMP) service. You can evaluate when most logins occur, as well as the maximum and minimum usage-- which can be useful for tuning IMP server performance.

If you are experiencing performance issues outside normal peak login times, navigate to the application's main metric page where detailed metric data for all operations is available. See, Viewing Performance Information.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

27.30.10 Logouts (per minute)

This metric counts the number of times per minute a WebCenter user logs out from the IMP server hosting presence information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the IMP service. You can evaluate when most logouts occur, as well as the maximum and minimum usage-- which can be useful for tuning discussion server performance.

If you are experiencing performance issues outside normal peak login times, navigate to the application's main metric page where detailed metric data for all operations is available. See, Viewing Performance Information.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

27.30.11 Status

This metric indicates whether the Instant Messaging and Presence (IMP) service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.30.12 Successful Invocations (%)

This metric indicates the percentage of Instant Messaging and Presence (IMP) service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.30.13 Service Name

These metrics apply to the Instant Messaging and Presence (IMP) service.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.31 WebCenter Search

Provides information about WebCenter Search metrics.

27.31.1 Application Name

This metric identifies the WebCenter application to which these Search service metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.31.2 Failed Invocations (%)

This metric indicates the percentage of Search service invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Search Metrics.

27.31.3 Successful Invocations (%)

This metric indicates the percentage of Search service invocations that succeeded for a particular search source.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data for the search source is available. See, Viewing Performance Information.

See also, Analyzing Search Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.31.4 Invocations (per minute)

This metric indicates the total number of Search service invocations per minute for a single search source.

WebCenter search sources include data associated with: Announcements, Documents, Discussion Forums, Spaces, Events, Lists, Notes, Oracle Secure Enterprise Search, Pages, Wikis and Blogs, People Connections, and Tagged Items.

The number of invocations for this search source is available on application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for this search source is high (compared with other search sources), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Search Metrics.

27.31.5 Query Throughput (queries per minute)

This metric shows the average search rate per minute.

All Spaces in the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor typical and peak search time. You can evaluate when information is searched the most, as well as the maximum and minimum search rate.

27.31.6 Status

This metric indicates whether the Search service is up or down. If the value is 1, the service is up. If the value is 0, it is down

27.31.7 Average Processing Time (ms)

This metric indicates the average time the Search service spends processing search operations (in ms) for a single search source.

WebCenter search sources include data associated with: Announcements, Documents, Discussion Forums, Spaces, Events, Lists, Notes, Oracle Secure Enterprise Search, Pages, Wikis and Blogs, People Connections, and Tagged Items. Processing times for all search sources are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of Search service operations for a single search source.

If this metric is out-of-bounds (the average time for search operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the search source is available. See, Viewing Performance Information.

See also, Analyzing Search Metrics.

27.32 WebCenter BPEL Worklists

Provides information about the WebCenter BPEL worklists metrics.

27.32.1 Application Name

This metric identifies the WebCenter application to which these Worklists service metrics apply.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

27.32.2 Failed Invocations (%)

This metric indicates the percentage of Worklists service invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Worklist Metrics.

27.32.3 Status

This metric indicates whether the Worklists service is up or down. If the value is 1, the service is up. If the value is 0, it is down

27.32.4 Successful Invocations (%)

This metric indicates the percentage of Worklists service invocations, for this BPEL worklist, that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%), investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data is also available. See, Viewing Performance Information.

See also, Analyzing Worklist Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.32.5 Invocations (per minute)

This metric indicates the total number of Worklists service invocations per minute for a single BPEL worklist. The number of invocations is available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for this BPEL worklist is high (compared with other worklists), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Worklist Metrics.

27.32.6 Average Processing Time (ms)

This metric indicates the average time the Worklists service spends processing operations relating to this BPEL worklist (in ms).

Processing time is available on application's main metric page where detailed metric data is available. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

Use this metric to determine the performance of Worklists service operations, for this BPEL worklist. If this metric is out-of-bounds (the average time for worklist operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Worklist Metrics.

28 Web Cache

This chapter describes Oracle Web Cache metrics.

28.1 Performance by Web Cache Instance

Provides information about the performance metrics for the Web Cache instance.

28.1.1 Instance

This category provides performance-request metrics for the cache.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

28.1.2 Request Processing Time (milli seconds)

This metric specifies the average number of seconds used to process a request during the current time period.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

If the number is low, then improve the connection between the cache and origin server, or upgrade the origin server computer.

28.1.3 Request Throughput (per second)

This metric specifies the average number of requests served for each second during the current time period.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

If this number is high, then increase the capacity of this origin server from the Origin Servers page or load balance the requests among cache cluster members.

28.2 Resource Usage

This category of metrics shows the resource usage of the computer with Oracle Web Cache.

28.2.1 CPU Usage (%)

This metric specifies the percentage of the CPU that is being used for Oracle Web Cache. As traffic increases, CPU utilization increases.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3 Samples

>

Not Defined

Not Defined

CPU Utilization is %value%%%

User Action

If the load is high, then consider upgrading the cache computer.

28.2.2 CPU Idle Time (%)

This metric specifies the percentage of system CPU time that is idle.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

If the load is high, then consider upgrading the cache computer.

28.2.3 Other CPU Usage (%)

The percentage of physical memory usage by applications other than Oracle Web Cache.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

If CPU usage is high, then consider upgrading the cache computer.

28.2.4 Memory Usage (MB)

This metric specifies the total memory used by Oracle Web Cache.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

If the load is high, then consider upgrading the cache computer.

28.2.5 Free Memory (MB)

The metric specifies the amount of free physical memory, in megabytes, for the system.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

28.2.6 Other Memory Usage (MB)

Other memory usage in MB

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

28.2.7 Total Memory (MB)

This metric shows the total memory of the host that has Oracle Web Cache.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

28.2.8 Memory Usage (%)

This metric specifies the percentage of total memory that is being utilized for cache memory.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

After Every 3 Samples

>

80

90

Memory Utilization is %value%%%

28.2.9 Free Memory (%)

This metric specifies the percentage of total memory that is being utilized for cache memory.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

28.2.10 Other Memory Usage (%)

Percent of memory used by processes other than Oracle Web Cache.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

28.2.11 Start Time (ms since Epoch)

This metric shows the start time of Oracle Web Cache.

28.2.12 Up Time (ms since Epoch)

This metric shows the total time the Oracle Web Cache has been running.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

28.3 Response

This category shows the availability of the cache server process, which manages the cache.

28.3.1 Response Admin

This category shows the availability of the admin server process, which provides administrative access to the cache.

28.3.2 Admin Process Status

This metric indicates whether the admin server process for the Oracle Web Cache instance is up (1) or down (0). The admin server process provides administrative access to cache.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every Minute

After Every 60 Samples

=

Not Defined

0

The Oracle Web Cache admin server process is down

User Action

If the admin server process is down, the context pane for the configuration pages displays an error, indicating that configuration is unavailable because the admin server process is down. To start the admin server process, from the Web Cache menu, choose Control, then Start Up, Shut Down, or Restart. See Starting and Stopping Oracle Web Cache for more information about starting Oracle Web Cache.

28.3.3 Response - Status

This metric indicates whether the cache server process for the Oracle Web Cache instance is up (1) or down (0).

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every Minute

After Every 60 Samples

=

Not Defined

0

The Oracle Web Cache cache server process is down

User Action

See Starting and Stopping Oracle Web Cache for more information about starting Oracle Web Cache.

28.4 Performance of each Site with Summary

This category provides performance metrics for each site.

28.4.1 Total Number of Bytes Saved by Compression

This metric specifies the accumulated number of bytes that would be sent to clients if in-cache compression is disabled.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

If the number is low, then compression is not providing much benefit to the site. Try enabling compression in all caching rules to allow Oracle Web Cache to determine compressibility automatically based on the content type.

28.4.2 Cache Size

The metric specifies the size, in megabytes, of the objects currently stored in the cache. For a cache cluster member, this number is an aggregate of the owned and on-demand objects.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action user required. As Oracle Web Cache only cleans up invalid or expired objects on demand when memory is needed, this number may remain at a large value.

28.4.3 Total Number Error Pages Served

The metric specifies the accumulated number of error pages that Oracle Web Cache served to Web browsers since the cache was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Oracle Web Cache serves error pages when there are problems fetching content from the origin server or when there ESI processing issues with the content. Even a small number can indicate an issue with site content or with origin server health.

28.4.4 Hit Rate (in %)

This metric specifies the percentage of requests resolved by cache content. This percentage should be high, except when objects are being invalidated.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

If percentage of hits is low, then perform the following:

1. Review the caching rules configuration in the Caching Rules page.

2. In the Popular Requests page, select Non Cache Popular Requests from the Show Popular Requests list to view the most frequent misses.

3. In the results table, view the Caching Reason column for the most frequent URL requests that were not cached.

4. Configure caching rules to cache the popular requests. See Configure Caching Rules.

28.4.5 Number of Cached

This metric specifies the number of objects cached.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

28.4.6 Currently Open connections

This metric specifies the current number of incoming open connections to the Oracle Web Cache server and outgoing open connections to the origin servers.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

If the number is close to the origin server connection limit, then set a larger capacity for the origin server from the Origin Servers page.

28.4.7 Total Number of Requests Denied

This metric specifies the accumulated number of requests denied by request filters.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

Any non-zero number may be an indication of an attack on the site or an issue with the configuration of request filters.

28.4.8 Total Number of Requests Served

This metric specifies the accumulate number of requests that Oracle Web Cache has served.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

28.5 WebCache_nontimedHost

This category provides performance-request metrics for the origin servers. Please also review the metrics in the WebCache_timedHost category for additional metrics for origin servers.

28.5.1 Capacity.value

This informational metric specifies the capacity you specified in the Origin Servers page for this origin server.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

28.5.2 Load.value

This metric specifies the current number of connections from Oracle Web Cache that the origin server has open.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

28.5.3 MaxLoad.value

The metric specifies the maximum number of connections that the origin server has had open at one time.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

28.5.4 Port.value

The information metric specifies the port number from which the origin server is listening for Oracle Web Cache requests.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

28.6 WebCache_timedHost

This category provides performance-request metrics for the origin servers. Please also review the metrics in the WebCache_nontimedHost category for additional metrics for origin servers.

28.6.1 AvgLatency.value

This metric shows the average amount of time for client requests forwarded by Oracle Web Cache to be resolved.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

If the latency appears high, then the administrator for the origin server or content source may need to add more system resources.

28.6.2 Latency.value

This metric shows the total time for client requests forwarded by Oracle Web Cache to be resolved, since the cache was started.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

If the latency appears high, then the administrator for the origin server or content source may need to add more system resources.

28.6.3 Request.value

This metric specifies the accumulated number of client requests forwarded by Oracle Web Cache that the origin server has processed.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

You can increase cache hit rate and lower the number client requests to the origin server by configuring caching rules for popular requests:

If percentage of hits is low, then perform the following:

1. Review the caching rules configuration in the Caching Rules page.

2. In the Popular Requests page, select Non Cache Popular Requests from the Show Popular Requests list to view the most frequent misses.

3. In the results table, view the Caching Reason column for the most frequent URL requests that were not cached.

4. Configure caching rules to cache the popular requests. See Configure Caching Rules.

28.6.4 RequestFailure.value

This metric specifies the accumulated number of client requests forwarded by Oracle Web Cache that resulted in an error.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

29 Oracle Directory Server Enterprise Edition

Oracle Directory Server Enterprise Edition serves directory data to standards compliant LDAP and DSML applications. Directory Server stores the data in customized, binary tree databases, allowing quick searches even for large data sets.

29.1 Cache Memory Thresholds

These thresholds warn you about directory server internal memory dilatation or contraction. The warnings are issued in the form of messages in the error log.

29.1.1 Heap High Hits

This is the number of heap high hits based on sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.1.2 Heap High Hits (per sec)

This is the number of heap high hits per second based on sampling

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-1 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Heap High Hits (per sec) is %value%

Data Source

Not available

29.1.3 Heap High Hits (per sec) (since startup)

This is the number of heap high hits per second since startup based on sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.1.4 Heap High Hits (since startup)

This is the number of heap high hits since startup based on sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.1.5 Heap Low Hits

This is the number of heap low hits based on sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.1.6 Heap Low Hits (per sec)

This is the number of heap low hits per second based on sampling

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-2 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Heap Low Hits (per sec) is %value%

Data Source

Not available

29.1.7 Heap Low Hits (per sec) (since startup)

This is the number of heap low hits per second since startup based on sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.1.8 Heap Low Hits (since startup)

This is the number of heap low hits since startup based on sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.2 Compare Operations Elapsed Time Metrics

The compare operation elapsed time represents the elapsed time taken by the compare operations in the directory server.

29.2.1 Average Elapsed Time per Compare Operation (ms)

This is the average elapsed time per compare operation measured in milliseconds.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-3 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Average Elapsed Time per Compare Operation is %value% ms

Data Source

Not available

29.2.2 Average Elapsed Time per Compare Operation (since startup) (ms)

This is the average elapsed time per compare operation since startup measured in milliseconds

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.2.3 LDAP Compare operations (since startup)

This is the number of LDAP compare operations since startup based on sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.2.4 Total Elapsed Time for all Compare Operations (ms)

This is the total elapsed time for all compare operations measured in milliseconds

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.2.5 Total Elapsed Time for Compare Operations (since startup) (ms)

This is the total elapsed time for compare operations since startup measured in milliseconds

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.2.6 Total Elapsed Time Squared for Search Operations (since startup) (ms)

This is the total elapsed time squared for search operations since startup measured in milliseconds

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.3 Compare Operations Metrics

The compare operations metrics represent the number of compare operations issued by the directory server.

29.3.1 Compare Operations

This is the number of compare operations based on sampling

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-4 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Number of Compare Operations is %value%

Data Source

Not available

29.3.2 Compare Operations (per sec)

This is the number of compare operations per second based on sampling

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-5 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Number of Compare Operations (per sec) is %value%

Data Source

Not available

29.3.3 Compare Operations (per sec) (since startup)

This is the number of compare operations per second based on sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.3.4 Compare Operations (since startup)

This is the number of compare operations since startup

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.4 Connections Metrics

The connection metrics represent the number of connections established with this directory server, as well as the current established connections and the connection peaks.

29.4.1 Connections Peak

Highest number of established connections since the start of the Directory Server instance.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-6 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

The number of Connections Peak is %value%

Data Source

Not available

29.4.2 Connections Per Sec

The ratio per second based on the sampling of the total number of connections.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.4.3 Connections Per Sec (s start)

The ratio per second based on the number of connections since the start of the instance.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.4.4 Current Connections

Current open connections

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-7 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

The Number of Current Connections is %value%

Data Source

Not available

29.5 Database Cache Metrics

The database cache metrics is the set of metrics around the activity of the internal cache of the Oracle berckey database. In this set we can find the hit and tries in the cache, as well as the paging activity.

29.5.1 Cache Clean Pages

The number of clean pages forced from the cache per second based on the sampling.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-8 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Database Cache Clean Pages is %value%

Data Source

Not available

29.5.2 Cache Dirty Pages

The number of dirty pages forced from the cache per second based on the sampling.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-9 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Database Cache Dirty Pages is %value%

Data Source

Not available

29.5.3 Cache Hits

The number of requested pages found in the database per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.5.4 Cache Page Reads

The number of pages read into the database cache per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.5.5 Cache Page Writes

The number of pages written from the database cache to the backing file per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.5.6 Cache Tries

The total number of requested pages found in the database cache per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.6 Errors Metrics

The errors set of metrics includes security errors as well as operational errors.

29.6.1 Bind Security Errors

The number of bind security errors per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.6.2 Bind Security Errors (Since Start)

The number of bind security errors per second calculated since the start of the Directory Server instance.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.6.3 Operational Errors

The number of operational errors per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.6.4 Operational Errors (Since Start)

The number of operational errors per second calculated since the start of the Directory Server instance.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.6.5 Security Errors

The number of all security errors per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.6.6 Security Errors (Since Start)

The number of all security errors per second calculated since the start of the Directory Server instance

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.6.7 Total Errors

The total number of errors per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.6.8 Total Errors (Since Start)

The total number of errors per second calculated since the start of the Directory Server instance.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.7 General Information

The Directory Server General Information provides a brief set of basic data elements like the server version, the startup time of the server, and the number of backends in this server.

29.7.1 Backend

Backend list in the Directory Server instance.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.7.2 Current Time

Current time from the Directory Service instance.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.7.3 Start Time

The start time of the directory server instance.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.7.4 Version

The version of the directory server instance.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.8 Hashtable Metrics

The hash table metrics are related with the activity of the internal hash tables used by Oracle berckley database. Here we can find typical information about number of lookups, number of elements inspected or the length of chains traversed.

29.8.1 Hash Elements Traversed

The number of hash elements traversed during hast table lookups based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.8.2 Hash Elements Traversed (per sec)

The number of hash elements traversed per second during hast table lookups based on sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-10 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Hash Elements Traversed (per sec) is %value%

Data Source

Not available

29.8.3 Hash Elements Traversed (per sec since startup)

The number of hash elements traversed per second during hast table lookups based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.8.4 Hash Elements Traversed (since startup)

The number of hash elements traversed per second during hast table lookups based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.8.5 Hash Table Lookups

The number of hash table lookups based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.8.6 Hash Table Lookups (per sec)

The number of hash table lookups per second based on the sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-11 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Hash Table Lookups (per sec) is %value%

Data Source

Not available

29.8.7 Hash Table Lookups (per sec since start)

The number of hash table lookups per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.8.8 Hash Table Lookups (since startup)

The number of hash table lookups per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.8.9 Longest Chain During Hash Lookups

The longest chain ever encountered in hash table lookups.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-12 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Longest Chain During Hash Lookup is %value%

Data Source

Not available

29.9 In Out Operation

This set of metrics includes the number of LDAP entries, referrals, and bytes returned by the directory server.

29.9.1 Bytes Returned

The number of bytes returned based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.9.2 Bytes Returned (per sec)

The number of bytes returned per second based on sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-13 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Number of Bytes Returned (per sec) is %value%

Data Source

Not available

29.9.3 Bytes Returned (per sec since startup)

The number of bytes returned per second since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.9.4 Bytes Returned (since startup)

The number of bytes returned since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.9.5 LDAP Entries Returned

The number of LDAP entries returned based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.9.6 LDAP Entries Returned (per sec)

The number of LDAP entries returned per second based on sampling

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-14 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Number of LDAP Entries Returned (per sec) is %value%

Data Source

Not available

29.9.7 LDAP Entries Returned (per sec) (since startup)

The number of LDAP entries returned per second since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.9.8 LDAP Entries Returned (since startup)

The number of LDAP entries returned since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.9.9 Referrals Returned

The number of referrals returned based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.9.10 Referrals Returned (per sec)

The number of referrals returned per second based on sampling

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-15 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Number of Referrals Returned (per sec) is %value%

Data Source

Not available

29.9.11 Referrals Returned (per sec) (since startup)

The number of referrals returned per second since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.9.12 Referrals Returned (since startup)

The number of referrals returned since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10 Locks and DeadLocks

The Locks and deadlocks metrics refer to the usage of internal locks of Oracle berckley database. These metrics includes the number of times a lock was take, the number of conflicts, the number of deadlocks, locks and lockers.

29.10.1 Current Database Locks

The number of current database locks.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10.2 Current Lockers

The current number of database lockers.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10.3 Detected Deadlocks

The number of database deadlocks detected based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10.4 DeadLocks Detected (per sec)

The number of database deadlocks per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10.5 DeadLocks Detected (per sec since startup)

The number of database deadlocks detected per second since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10.6 DeadLocks Detected (since startup)

The number of database deadlocks detected since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10.7 Lock Conflicts

The number of database lock conflicts based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10.8 Lock Conflicts (per sec)

The number of database lock conflicts per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10.9 Lock Conflicts (per sec since startup)

The number of database lock conflicts per second since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10.10 Lock Conflicts (since startup)

The number of database lock conflicts since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10.11 Maximum Database Locks

The maximum number of database locks based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10.12 Total locks Requested

The number of total locks requested based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10.13 Total locks Requested (per sec)

The number of total locks requested per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10.14 Total locks Requested (per sec) (since startup)

The number of total locks requested per second since startup based on the sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10.15 Total locks Requested (since startup)

The number of total locks requested since startup based on the sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10.16 Waits before Database Lock

The number of times that a thread had to wait for a database lock based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10.17 Waits before Database Lock (per sec)

The number of times per second that a thread had to wait for a database lock based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10.18 Waits before Database Lock (per sec since startup)

The number of times per second since startup that a thread had to wait for a database lock based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.10.19 Waits before Database Lock (since startup)

The number of times since startup that a thread had to wait for a database lock based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.11 Operations Metrics

This set of metrics includes the total number of operations initiated by the server and the number of operations completed by the server; as well as the elapsed time taken by these operations.

29.11.1 Average Elapsed Time per Operation (ms)

This is the average elapsed time per operation in milliseconds based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.11.2 Average Elapsed Time per Operation (since startup )(ms)

The is the average elapsed time per operation since startup in milliseconds based on the sampling .

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.11.3 Total Elapsed Time for all Operations (ms)

The is the total elapsed time for all operations in milliseconds based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.11.4 Total Elapsed Time for all Operations (since startup) (ms)

The is the total elapsed time for all operations since startup in milliseconds based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.11.5 Total LDAP Operations Completed

The total number of LDAP operations completed based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.11.6 Total LDAP Operations Completed (per sec)

The total number of LDAP operations completed per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.11.7 Total LDAP Operations Completed (per sec) (since startup)

The total number of LDAP operations completed per second since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.11.8 Total LDAP Operations Completed (since startup)

The total number of LDAP operations completed since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.11.9 Total Operations Completed

The total number of operations completed based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.11.10 Total Operations Completed (per sec)

The total number of operations completed per second based on the sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.11.11 Total Operations Completed (per sec) (since startup)

The total number of operations completed per second since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.11.12 Total Operations Completed (since startup)

The total number of operations completed since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.11.13 Total Operations Initiated

The total number of operations initiated based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.11.14 Total Operations Initiated (per sec)

The total number of operations initiated per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.11.15 Total Operations Initiated (per sec) (since startup)

The total number of operations initiated per second since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.11.16 Total Operations Initiated (since startup)

The total number of operations initiated since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.12 Other Operations

This set of metrics includes the number of searches and referrals

29.12.1 LDAP Referral Operations

The number of LDAP referral operations based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.12.2 LDAP Referral Operations (per sec)

The number of LDAP referral operations per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.12.3 LDAP Referral Operations (per sec) (since startup)

The number of LDAP referral operations per second since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.12.4 LDAP Referral Operations (since startup)

The number of LDAP referral operations since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.12.5 Persistent Searches Running

The number of persistent searches running based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.13 Queues Metrics

The queue metrics set includes the metrics related with internal queues of directory server. These are: the queue of pending requests, the queues of waiting requests and the operations being treated.

29.13.1 Operations In Progress

The number of operations being treated by a worker thread.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.13.2 Operations Queue Back Log

The number of requests waiting to be processed by a thread.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.13.3 Read Waiters Queue

The read waiters queue.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.14 Read Operations Elapsed Time Metrics

This set of metrics is related with the elapsed time of the read operations: bind operations and search operations.

29.14.1 Average Elapsed Time per Bind Operation (ms)

The average elapsed time per bind operation in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.14.2 Average Elapsed Time per Bind Operation (since startup) (ms)

The average elapsed time per bind operation since startup in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.14.3 Average Elapsed Time per Search Operation (ms)

The average elapsed time per search operation in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.14.4 Average Elapsed Time per Search Operation (since startup) (ms)

The average elapsed time per search operation since startup in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.14.5 Average Elapsed Time per UnBind Operation (ms)

The average elapsed time per unbind operation in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.14.6 Average Elapsed Time per Unbind Operation (since startup) (ms)

The average elapsed time per unbind operation since startup in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.14.7 LDAP Binds (since startup)

The number of LDAP binds since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.14.8 LDAP Searches (since startup)

The number of LDAP searches since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.14.9 Total Elapsed Time for Bind Operations (ms)

The total elapsed time for bind operations in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.14.10 Total Elapsed Time for Bind Operations (since startup) (ms)

The total elapsed time for bind operations since startup in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.14.11 Total Elapsed Time for Search Operations (ms)

The total elapsed time for search operations in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.14.12 Total Elapsed Time for Search Operations (since startup) (ms)

The total elapsed time for search operations since startup in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.14.13 Total Elapsed Time for UnBind Operations (ms)

The total elapsed time for unbind operations in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.14.14 Total Elapsed Time for UnBind Operations (since startup) (ms)

The total elapsed time for unbind operations since startup in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.14.15 Total Elapsed Time Squared for Bind Operations (since startup) (ms)

The total elapsed time squared for bind operations since startup in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.14.16 Total Elapsed Time Squared for Search Operations (since startup) (ms)

The total elapsed time squared for search operations since startup in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.14.17 Total Elapsed Time Squared for UnBind Operations (since startup) (ms)

The total elapsed time squared for unbind operations since startup in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15 Read Operations Metrics

The read operations metrics includes the number of bind, search, and compare operations.

29.15.1 Anonymous Binds

The number of anonymous binds based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.2 Anonymous binds (per sec)

The number of anonymous binds per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.3 Anonymous Binds (per sec) (since startup)

The number of anonymous binds per second since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.4 Anonymous Binds (since startup)

The number of anonymous binds since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.5 LDAP Binds

The number of LDAP binds based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.6 LDAP Binds (per sec)

The number of LDAP binds per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.7 LDAP Binds (per sec) (since startup)

The number of LDAP binds per second since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.8 LDAP Binds (since startup)

The number of LDAP binds since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.9 Simple Authorized Binds (per sec) (since startup)

The number of simple authorized binds per second since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.10 Simple Authorized Binds (since startup)

The number of simple authorized binds per second since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.11 Simple Binds

The number of simple binds based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.12 Simple Binds (per sec)

The number of simple binds per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.13 Strong Authorized Binds (per sec) (since startup)

The number of strong authorized binds per second since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.14 Strong Authorized Binds (since startup)

The number of strong authorized binds since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.15 Strong Binds

The strong binds based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.16 Strong Binds (per sec)

The number of strong binds per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.17 Unauthorized Binds

The number of unauthorized binds based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.18 Unauthorized Binds (per sec)

The number of unauthorized binds per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.19 Unauthorized Binds (per sec) (since startup)

The number of unauthorized binds per second since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.15.20 Unauthorized Binds (since startup)

The number of unauthorized binds since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.16 Resource Usage

A system is composed of various resources, for example CPU, Disk, and memory. The resource usage expresses the level of usage of a resource. This can be expressed in terms of percentage of some quantity used (for example kilobytes). Some examples of these include CPU usage, available disk free space in percentage, and amount of used memory by a process in kilobytes.

29.16.1 CPU Utilization (%)

The percentage CPU utilization based on the sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-16 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

CPU Utilization (%) is %value%

Data Source

Not available

29.16.2 Memory Utilization (KB)

The memory utilization in KB based on the sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-17 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Memory Utilization (%) is %value%

Data Source

Not available

29.16.3 Memory Utilization (%)

The percentage memory utilization based on the sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-18 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Memory Utilization (KB) is %value%

Data Source

Not available

29.17 Response

This category provides information about Response metrics

29.17.1 Status

This metric shows the status of the Directory Server.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-19 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 60 Seconds

=

Not Defined

0

The Directory Server is down

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

Data Source

Not available

User Action

No user action is required.

29.18 Suffix-Backend Entry

In directory server, each backend has its own entry cache. This set of metrics includes hit and tries in this cache, as well as the size of the cache and the number of entries in it.

29.18.1 Suffix-Backend Entry - Average Cache Size

The average cache size

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-20 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Suffix-Backend %backendname% Average Entry Cache sizeis %value%

Data Source

Not available

29.18.2 Suffix-Backend Entry - Cache Count

The cache count

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-21 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Suffix-Backend %backendname% Entry Cache count is %value%

Data Source

Not available

29.18.3 Suffix-Backend Entry - Cache Hit Ratio

The cache hit ratio.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-22 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Suffix-Backend %backendname% Entry Cache hit ratio is %value%

Data Source

Not available

29.18.4 Suffix-Backend Entry - Cache Hits

The number of cache hits.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.18.5 Suffix-Backend Entry - Cache Hits (per sec)

The number of cache hits per second.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-23 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Suffix-Backend %backendname% Entry Cache Hits (per sec) is %value%

Data Source

Not available

29.18.6 Suffix-Backend Entry - Cache Hits (per sec) (since startup)

The number of cache hits per second since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.18.7 Suffix-Backend Entry - Cache Hits (since startup)

The number of cache hits since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.18.8 Suffix-Backend Entry - Cache Size

The cache size

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-24 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Suffix-Backend %backendname% Entry Cache size is %value%

Data Source

Not available

29.18.9 Suffix-Backend Entry - Cache Tries

The number of cache tries.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.18.10 Suffix-Backend Entry - Cache Tries (per sec)

The number of cache tries per second.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-25 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Suffix-Backend %backendname% Entry Cache Tries (per sec) is %value%

Data Source

Not available

29.18.11 Suffix-Backend Entry - Cache Tries (per sec) (since startup)

The number of cache tries per second since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.18.12 Suffix-Backend Entry - Cache Tries (since startup)

The number of cache tries since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.18.13 Suffix-Backend Name

The suffix backend name.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.19 Suffix-Backend File Metrics

A backend is composed of files. These files are segmented in pages. The file metrics are related with miss and hits and paging activity.

29.19.1 Suffix-Backend File - Cache Hit Ratio

The cache hit ratio.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-26 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Backend File %backendfilename% Cache Hit Ratio is %value%

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.19.2 Suffix-Backend File - Cache Hits

The number of cache hits

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.19.3 Suffix-Backend File - Cache Hits (per sec)

The number of cache hits per second.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-27 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Backend File %backendfilename% Cache Hits (per sec) (since last collection)is %value%

Data Source

Not available

29.19.4 Suffix-Backend File - Cache Hits (per sec) (since startup)

The number of cache hits per second since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.19.5 Suffix-Backend File - Cache Hits (since startup)

The number of cache hits since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.19.6 Suffix-Backend File - Cache Misses

The number of cache misses.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.19.7 Suffix-Backend File - Cache Misses (per sec)

The number of cache misses per second.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-28 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Backend File %backendfilename% Cache Misses (per sec) (since last collection)is %value%

Data Source

Not available

29.19.8 Suffix-Backend File - Cache Misses (per sec) (since startup)

The number of cache misses per second since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.19.9 Suffix-Backend File - Cache Misses (since startup)

The number of cache misses since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.19.10 Suffix-Backend File - Pages in to Cache

The number of pages in the cache.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.19.11 Suffix-Backend File - Pages in to Cache (per sec)

The number of pages stored in the cache per second.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-29 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Backend File %backendfilename% Page in to Cache (per sec) is %value%

Data Source

Not available

29.19.12 Suffix-Backend File - Pages in to Cache (per sec) (since startup)

The number of pages stored in the cache per second since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.19.13 Suffix-Backend File - Pages in to Cache (since startup)

The number of pages stored in the cache since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.19.14 Suffix-Backend File - Pages Out to Disk

The number of pages sent to the disk.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.19.15 Suffix-Backend File - Pages Out to Disk (per sec)

The number of pages sent to the disk per second.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-30 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Backend File %backendfilename% Page Out to Disk (per sec) is %value%

Data Source

Not available

29.19.16 Suffix-Backend File - Pages Out to Disk (per sec) (since startup)

The number of pages sent to the disk per second since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.19.17 Suffix-Backend File - Pages Out to Disk (since startup)

The number of pages sent to the disk since startup.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.20 Suffix-Backends General Information

The general information of a backend includes the number of entries in this backend as well as the state of the backend.

29.20.1 Suffix-Backend Name

The suffix-backend name.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.20.2 Suffix-Backend Next DB entry ID

The next database entry identification number

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.20.3 Suffix-Backend State

The status of the suffix backend.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.20.4 Suffix-Backend Total DB Entry Count

The total database entry count.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.20.5 Suffix-Backend LDAP Entry Count

The LDAP entry count

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.21 Transaction Log Metrics

These metrics are related with the transaction log element of Oracle Berkley database. They mainly describe the write activity of the transaction log.

29.21.1 Bytes wrote to log

The number of bytes written in this transaction log based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.21.2 Bytes wrote to log (per sec)

The number of bytes per second written in this transaction log based on the sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-31 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Bytes wrote to log (per sec) is %value%

Data Source

Not available

29.21.3 Bytes Wrote to Log (per sec) (since last check point)

The number of bytes per second written in this transaction log since the last checkpoint based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.21.4 Bytes Wrote to Log (since last check point)

The number of bytes written in this transaction log since the last checkpoint based on the sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-32 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Bytes Wrote to Log (since last check point) is %value%

Data Source

Not available

29.21.5 Log Flushes

The number of number of times that the transaction log was flushed to disk based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.21.6 Log Flushes (per sec)

The number of times per second that the transaction log was flushed to disk based on the sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-33 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Log Flushes (per sec) is %value%

Data Source

Not available

29.21.7 Log Flushes (per sec) (since startup)

The number of times per second that the transaction log was flushed to disk since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.21.8 Log Flushes (since startup)

The number of times that the transaction log was flushed to disk since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.21.9 Log Flushes by In-Memory Full

The number of times that the transaction log was flushed to disk by in-memory full based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.21.10 Log Flushes by In-Memory Full (per sec)

The number of times per second that the transaction log was flushed to disk by in-memory full based on the sampling

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-34 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Log Flushes by In-Memory Full (per sec) is %value%

Data Source

Not available

29.21.11 Log Flushes by In-Memory Full (per sec) (since startup)

The number of times per second since startup that the transaction log was flushed to disk by in-memory full based on the sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.21.12 Log Flushes by In-Memory Full (since startup)

The number of times since startup that the transaction log was flushed to disk by in-memory full based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.21.13 Log Flushes with Commits

The number of times that the transaction log was flushed to disk with commits based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.21.14 Log Flushes with Commits (per sec)

The number of times per second that the transaction log was flushed to disk with commits based on the sampling

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-35 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Log Flushes with Commits (per sec) is %value%

Data Source

Not available

29.21.15 Log Flushes with Commits (per sec) (since startup)

The number of times per second since startup that the transaction log was flushed to disk with commits based on the sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.21.16 Log Flushes with Commits (since startup)

The number of times since startup that the transaction log was flushed to disk with commits based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.21.17 Log Written to Disk

The number of logs written to disk based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.21.18 Log Written to Disk (per sec)

The number of logs written to disk per second based on sampling.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-36 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Log Written to Disk (per sec) is %value%

Data Source

Not available

29.21.19 Log Written to Disk (per sec) (since startup)

The number of logs written to disk per second since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.21.20 Log Written to Disk (since startup)

The number of logs written to disk since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.21.21 Maximum Commits in Log Flush

The maximum number of commits in a log flush.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-37 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Maximum Number of Commits in Log Flush is %value%

Data Source

Not available

29.21.22 Minimum Commits in Log Flush

The minimum number of commits in a log flush.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-38 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Minimum number of Commits in Log Flush is %value%

Data Source

Not available

29.21.23 Waits before getting the Log Lock

The number of times that a thread had to wait before getting a transaction log lock

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.21.24 Waits before getting the Log Lock (per sec)

The number of times per second that a thread had to wait before getting a transaction log lock.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-39 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Waits before getting the Log Lock (per sec) is %value%

Data Source

Not available

29.21.25 Waits before getting the Log Lock (per sec) (since startup)

The number of times per second since startup that a thread had to wait before getting a transaction log lock.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.21.26 Waits before getting the Log Lock (since startup)

The number of times since startup that a thread had to wait before getting a transaction log lock.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.22 Transactions

This set of metrics are related with the Oracle Berkley database transaction. In this we can find the number of committed and aborted transactions, the maximum number of used transactions, the number of current transactions, and the umber of times the system waits for a transaction lock.

29.22.1 Aborted Transactions

The number of aborted transactions based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.22.2 Aborted Transactions (per sec)

The number of aborted transactions per second based on the sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-40 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Aborted Transactions (per sec) is %value%

Data Source

Not available

29.22.3 Aborted Transactions (per sec) (since startup)

The number of aborted transactions per second since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.22.4 Aborted Transactions (since startup)

The number of aborted transactions since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.22.5 Committed Transactions

The number of committed transactions based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.22.6 Committed Transactions (per sec)

The number of committed transactions per second based on the sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-41 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Committed Transactions (per sec) is %value%

Data Source

Not available

29.22.7 Committed Transactions (per sec) (since startup)

The number of committed transactions per second since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.22.8 Committed Transactions (since startup)

The number of committed transactions since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.22.9 Current Active Transactions

The number of current active transactions based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.22.10 Maximum Transactions Used

The maximum number of transactions used.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-42 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Maximum Number of Transactions Used are %value%

Data Source

Not available

29.22.11 Waits before Transaction Locks

The number of times a transaction had to wait for a transaction lock based on the sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.22.12 Waits before Transaction Locks (per sec)

The number of times per second that a transaction had to wait for a transaction lock based on the sampling

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-43 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Waits before Transaction Locks (per sec) is %value%

Data Source

Not available

29.22.13 Waits before Transaction Locks (per sec) (since startup)

The number of times per second since startup that a transaction had to wait for a transaction lock based on the sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.22.14 Waits before Transaction Locks (since startup)

The number of times since startup that a transaction had to wait for a transaction lock based on the sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23 Write Operations Elapsed Time Metrics

This set of metrics is related with the elapsed time of the write operations such as add, delete, modify, and modify RDN of an entry.

29.23.1 Average Elapsed Time per Add Operation (ms)

The average elapsed time per add operation in milliseconds based on sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-44 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Average Elapsed Time per Add Operation is %value% ms

Data Source

Not available

29.23.2 Average Elapsed Time per Add Operation (since startup) (ms)

The average elapsed time per add operation since startup in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.3 Average Elapsed Time per Delete Operation (ms)

The average elapsed time per delete operation in milliseconds based on sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-45 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Average Elapsed Time per Delete Operation is %value% ms

Data Source

Not available

29.23.4 Average Elapsed Time per Delete Operation (since startup) (ms)

The average elapsed time per delete operation since startup in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.5 Average Elapsed Time per Modify Operation (ms)

The average elapsed time per modify operation in milliseconds based on sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-46 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Average Elapsed Time per Modify Operation is %value% ms

Data Source

Not available

29.23.6 Average Elapsed Time per Modify Operation (since startup) (ms)

The average elapsed time per modify operation since startup in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.7 Average Elapsed Time per Modify RDN Operation (ms)

The average elapsed time per modify RDN operation in milliseconds based on sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-47 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Average Elapsed Time per Modify RDN Operation is %value% ms

Data Source

Not available

29.23.8 Average Elapsed Time per Modify RDN Operation (since startup) (ms)

The average elapsed time per modify RDN operation since startup in milliseconds based on sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.9 LDAP Add operations (since startup)

The number of LDAP add operations since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.10 LDAP Delete operations (since startup)

The number of LDAP delete operations since startup based on sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.11 LDAP Modify operations (since startup)

The number of LDAP modify operations since startup based on sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.12 LDAP Modify RDN operations (since startup)

The number of LDAP modify RDN operations since startup based on sampling

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.13 Total Elapsed Time for Add Operations (since startup) (ms)

The total elapsed time for add operations since startup in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.14 Total Elapsed Time for all Add Operations (ms)

The total elapsed time for all add operations in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.15 Total Elapsed Time for all Delete Operations (ms)

The total elapsed time for all delete operations in milliseconds.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.16 Total Elapsed Time for all Modify Operations (ms)

The total elapsed time for all modify operations in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.17 Total Elapsed Time for all Modify RDN Operations (ms)

The total elapsed time for all modify RDN operations in milliseconds based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.18 Total Elapsed Time for Delete Operations (since startup) (ms)

The total elapsed time for delete operations in milliseconds since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.19 Total Elapsed Time for Modify Operations (since startup) (ms)

The total elapsed time for modify operations in milliseconds since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.20 Total Elapsed Time for Modify RDN Operations (since startup) (ms)

The total elapsed time for modify RDN operations in milliseconds since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.21 Total Elapsed Time Squared for Add Operations (since startup) (ms)

The total elapsed time squared for add operations in milliseconds since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.22 Total Elapsed Time Squared for Delete Operations (since startup) (ms)

The total elapsed time squared for delete operations in milliseconds since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.23 Total Elapsed Time Squared for Modify Operations (since startup) (ms)

The total elapsed time squared for modify operations in milliseconds since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.23.24 Total Elapsed Time Squared for Modify RDN Operations (since startup) (ms)

The total elapsed time squared for modify RDN operations in milliseconds since startup based on sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.24 Write Operations Metrics

The read operations metrics includes the number of add, delete, modify, and modify RDN operations.

29.24.1 Add Operations

The average elapsed time (etime) of the add operation based on the sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-48 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Number of Add Operations is %value%

Data Source

Not available

29.24.2 Add Operations (per sec)

The number of add operations per second based on the sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-49 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Number of Add Operations (per sec) is %value%

Data Source

Not available

29.24.3 Add Operations (per sec) (since startup)

The number of add operations per second since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.24.4 Add Operations (since startup)

The number of add operations since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.24.5 Delete Operations

The average elapsed time (etime) of the delete operation based on the sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-50 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Number of Delete Operations is %value%

Data Source

Not available

29.24.6 Delete Operations (per sec)

The number of delete operations per second based on the sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-51 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Number of Delete Operations (per sec) is %value%

Data Source

Not available

29.24.7 Delete Operations (per sec) (since startup)

The number of delete operations per second since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.24.8 Delete Operations (since startup)

The number of delete operations per second based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.24.9 Modify Operations

The number of modify operations per second based on the sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-52 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Number of Modify Operations is %value%

Data Source

Not available

29.24.10 Modify Operations (per sec)

The number of modify operations per second based on the sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-53 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Number of Modify Operations (per sec) is %value%

Data Source

Not available

29.24.11 Modify Operations (per sec) (since startup)

The number of modify operations per second since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.24.12 Modify Operations (since startup)

The number of modify operations since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.24.13 Modify RDN (since startup)

The number of modify RDN operations since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

29.24.14 Modify RDN Operations

The number of modify RDN operations based on the sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-54 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Number of Modify RDN Operations is %value%

Data Source

Not available

29.24.15 Modify RDN Operations (per sec)

The number of modify RDN operations per second based on the sampling.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 29-55 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

Number of Modify RDN Operations (per sec) is %value%

Data Source

Not available

29.24.16 Modify RDN Operations (per sec) (since startup)

The number of modify RDN operations per second since startup based on the sampling.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

Not available

30 OC4J Metrics

Enterprise Manager can be used to manage Oracle Application Server Containers for J2EE (OC4J). You can use the All Metrics page for an OC4J target to view the metrics that have been collected for that target by Oracle Management Agent.

30.1 OC4J All Instances Metrics

This metric category provides metrics for all the OC4J instances of an application server.

30.1.1 OC4J Instances - Active Sessions

This metric shows the number of HTTP sessions used by all the OC4J instances of this application server.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.1.2 OC4J Instances - Request Processing Time (seconds)

This metric shows the average amount of time it consumed to execute servlets and JSPs for all the OC4J instances of this application server, during a recent interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.1.3 OC4J Instances - Requests Per Second

This metric shows the rate at which servlets and JSPs are being invoked for all the OC4J instances of this application server, during a recent interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.2 OC4J Application Metrics

This metric category provides metrics for the application.

30.2.1 Application - Active Requests

This metric shows the number of servlets and JSPs currently being executed by this application.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of active servlets and JSPs for application %name% is %value%.

30.2.2 Application - Active Sessions

This metric shows the number of active HTTP sessions used by the application.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of active sessions for application %name% is %value%.

30.2.3 Application - EJB Method Execution Rate (per second)

This metric shows the rate at which EJB methods are currently being executed by this application.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.2.4 Application - EJB Method Execution Time (seconds)

This metric shows the time consumed to execute EJB methods for this application during a recent interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The average execution time for an EJB method for application %name% is %value% seconds.

30.2.5 Application - Request Processing Time (seconds)

This metric shows the average time consumed to execute servlets and JSPs from this application during a recent interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The average processing time for a servlet or JSP for application %name% is %value% seconds

30.2.6 Application - Requests Per Second

This metric shows the rate at which servlets and JSPs are being invoked for this application during a recent interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.2.7 Application - Active EJB Methods

This metric shows the number of EJB methods that are currently being executed by this application.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of active EJB methods for application %name% is %value%.

30.3 OC4J EJB Metrics

This metric category provides metrics for EJBs.

30.3.1 EJB - Active Methods

This metric shows the number of EJB methods that are currently being executed for this EJB.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of active EJB methods for EJB %name%, EJB module %oc4j_ejb_module%, application %oc4j_ear% is %value%

30.3.2 EJB - Method Execution Rate (per second)

This metric shows the rate at which the EJB methods are currently being executed for this EJB during a recent interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.3.3 EJB - Method Execution Time (seconds)

This metric shows the time consumed to execute EJB methods for this EJB during a recent interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The average execution time for an EJB method for EJB %name%, EJB module %oc4j_ejb_module%, application %oc4j_ear% is %value% seconds

30.3.4 Type of EJB

This metric shows the type of the EJB (that is. Entity type or Session type).

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.4 OC4J EJB Module Metrics

This metric category provides metrics for EJB modules.

30.4.1 EJB Module - Active Methods

This metric shows the number of EJB methods that are currently being executed by this EJB module.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of active EJB methods for EJB module %name%, application %oc4j_ear% is %value%

30.4.2 EJB Module - Method Execution Rate (per second)

This metric shows the rate at which the EJB methods are currently being executed for this EJB module during a recent interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.4.3 EJB Module - Method Execution Time (seconds)

This metric shows the time consumed to execute EJB methods for this EJB module during a recent interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The average execution time for an EJB method for EJB module %name%, application %oc4j_ear% is %value% seconds.

30.5 OC4J Instance Metrics

This metric category provides metrics for the OC4J instance.

30.5.1 OC4J Instance - Active Transactions

This metric shows the number of transactions that are currently open for this OC4J instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of active transactions is %value%

30.5.2 OC4J Instance - Active EJB Methods

This metric shows the number of EJB methods that are currently being executed by this OC4J instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of active EJB methods is %value%

30.5.3 OC4J Instance - Active Requests

This metric shows the number of servlets and JSPs currently being executed by this OC4J instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of active servlets and JSPs is %value%

30.5.4 OC4J Instance - Active Sessions

This metric shows the number of active HTTP sessions used by the OC4J instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of active sessions is %value%

30.5.5 OC4J Instance - EJB Method Execution Rate (per second)

This metric shows the rate at which the EJB methods are currently being executed by this OC4J instance during a recent interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.5.6 OC4J Instance - EJB Method Execution Time (seconds)

This metric shows the time consumed to execute EJB methods for this OC4J instance during a recent interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The average execution time for an EJB method is %value% seconds

30.5.7 OC4J Instance - Heap Usage (MB)

This metric shows the amount of heap space used by the OC4J instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

Heap Usage is %value%MB

30.5.8 OC4J Instance - Open JDBC Connections

This metric shows the number of JDBC connections open by applications that are part of the OC4J instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of active JDBC connections is %value%

30.5.9 OC4J Instance - Request Processing Time (seconds)

This metric shows the average time consumed to execute servlets and JSPs for this OC4J instance during a recent interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The average processing time for a servlet or JSP is %value% seconds

30.5.10 OC4J Instance - Requests Per Second

This metric shows the rate at which servlets and JSPs are being invoked for this OC4J instance during a recent interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.5.11 OC4J Instance - Start Time (ms since Epoch)

This metric shows the time when the OC4J instance was started. It is represented in milliseconds since the UNIX epoch (that is, January 1, 1970).

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.6 OC4J JSP Metrics

This metric category provides metrics for JSPs.

30.6.1 Is multi-threaded?

This metric shows whether this JSP is multi-threaded. The value of this metric is either TRUE or FALSE.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.6.2 JSP - Active Instances (STM only)

This metric shows the shows the number of active instances of this JSP.

STM means Single Threaded Model. This metric is only for single threaded JSPs, and not for multi-threaded JSPs.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.6.3 JSP - Active Requests

This metric shows the number of clients that are currently executing this JSP.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.6.4 JSP - Available Instances

This metric shows the number of available instances to execute this JSP.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of active %name% JSPs for web module %oc4j_web_module%, application %oc4j_ear% is %value%

30.6.5 JSP - Available Instances (STM only)

This metric shows the number of available instances to execute this JSP.

STM means Single Threaded Model. This metric is only for single threaded JSPs, and not for multi-threaded JSPs.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.6.6 JSP - Client Processing Time (seconds)

This metric shows the total time spent executing the client code for this JSP since this OC4J instance was started.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The average processing time for JSP %name%, web module %oc4j_web_module%, application %oc4j_ear% is %value% seconds

30.6.7 JSP - Requests Per Second

This metric shows the rate at which this JSP has been invoked by clients during a recent interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.7 OC4J JVM Metrics

This metrics category provides metrics for OC4J JVMs.

30.7.1 JVM - CPU Usage (%)

This metric shows the percentage of CPU time used by the JVM.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 9.0.2, 9.0.4

Every 5 Minutes

Not Defined

Not Defined

CPU Utilization is %value%%% for process %pid.value%

30.7.2 JVM - Active EJB Methods

This metric shows the number of EJB methods currently being executed in the JVM.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 9.0.2, 9.0.4

Every 5 Minutes

Not Defined

Not Defined

The number of active EJB methods is %value% for process %pid.value%

30.7.3 JVM - Heap Usage (MB)

This metric shows the amount of heap space used by the JVM.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 9.0.2, 9.0.4

Every 5 Minutes

Not Defined

Not Defined

Heap Usage is %value% MB for process %pid.value%

30.7.4 JVM - Memory Usage (MB)

This metric shows the amount of physical memory used by the JVM.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 9.0.2, 9.0.4

Every 5 Minutes

Not Defined

Not Defined

Memory Utilization is %value% MB for process %pid.value%

30.7.5 JVM - Active Requests

This metric shows the number of servlet/JSP requests currently being processed in the JVM.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 9.0.2, 9.0.4

Every 5 Minutes

Not Defined

Not Defined

The number of active servlets and JSPs is %value% for process %pid.value%

30.7.6 JVM - Start Time (ms since Epoch)

This metric shows the time when the JVM was started.

Target Version

Collection Frequency

Release 9.0.2, 9.0.4

Every 5 Minutes

30.7.7 JVM - Active Threads

This metric shows the number of threads currently executing in the JVM.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 9.0.2, 9.0.4

Every 5 Minutes

Not Defined

Not Defined

There are %value% active threads for process %pid.value%

30.7.8 PID

This metric shows the process ID of the JVM.

Target Version

Collection Frequency

Release 9.0.2, 9.0.4

Every 5 Minutes

30.8 OC4J Servlet Metrics

This metric category provide metrics for servlets.

30.8.1 Servlet - Active Requests

This metric shows the number of clients that are currently executing this servlet.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of active %name% servlets for web module %oc4j_web_module%, application %oc4j_ear% is %value%

30.8.2 Servlet - Client Processing Time (seconds)

This metric shows the average time consumed to execute the client code for this servlet during a recent interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The average processing time for servlet %name%, web module %oc4j_web_module%, application %oc4j_ear% is %value% seconds

30.8.3 Servlet - Requests Per Second

This metric shows the rate at which the servlet has been invoked by clients during a recent interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.9 OC4J Web Module Metrics

This metric category provides metrics for the OC4J web modules.

30.9.1 Web Module - Active Requests

This metric shows the number of servlets and JSPs currently being executed by this web module.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of active servlets and JSPs for web module %name%, application %oc4j_ear% is %value%

30.9.2 Web Module - Active Sessions

This metric shows the number of active HTTP sessions used by this web module.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The number of active sessions for web module %name%, application %oc4j_ear% is %value%

30.9.3 Web Module - Class Load Time (seconds)

This metric shows the average time consumed to load the classes for this web module during the last interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.9.4 Web Module - Client Time (seconds)

This metric shows the average time spent executing client code for this web module during the last interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.9.5 Web Module - Request Processing Time (seconds)

This metric shows the average time consumed to execute servlets and JSPs for this web module during a recent interval. The interval is the period of time specified as the collection frequency for this metric.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

All Versions

Every 5 Minutes

Not Defined

Not Defined

The average processing time for a servlet or JSP for web module %name%, application %oc4j_ear% is %value% seconds

30.9.6 Web Module - Requests Per Second

This metric shows the number of servlets and JSPs processed by this web module since this OC4J instance was started.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

30.10 Resource Usage Metrics

This metric category provides metrics for the OC4J instance resource usage.

30.10.1 CPU Usage (%)

This metric shows the percentage of CPU time used by the OC4J instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 9.0.2

Every 5 Minutes

Not Defined

Not Defined

CPU Utilization is %value%%%

30.10.2 CPU Idle Time (%)

This metric shows the percentage of CPU idle time.

Target Version

Collection Frequency

Release 9.0.2

Every 5 Minutes

30.10.3 Other CPU Usage (%)

This metric shows the percentage of CPU owned and used by the host processes other than the OC4J instance. If you are having problems with CPU usage on the OC4J host computer, this metric can help you determine whether or not the OC4J instance is causing the problem.

Target Version

Collection Frequency

Release 9.0.2

Every 5 Minutes

30.10.4 Memory Usage (MB)

This metric shows the amount of physical memory used by the OC4J instance.

Target Version

Collection Frequency

Release 9.0.2

Every 5 Minutes

30.10.5 Free Memory (MB)

This metric shows the amount of free physical memory on the system.

Target Version

Collection Frequency

Release 9.0.2

Every 5 Minutes

30.10.6 Other Memory Usage (MB)

This metric shows the physical memory used (in MB) by processes and applications other than the OC4J instance. If you are having problems with physical memory usage on the OC4J host computer, this metric can help you determine whether or not the OC4J instance is causing the problem.

Target Version

Collection Frequency

Release 9.0.2

Every 5 Minutes

30.10.7 Memory Usage (%)

This metric shows the percentage of physical memory used by the OC4J instance.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 9.0.2

Every 5 Minutes

Not Defined

Not Defined

Memory Utilization is %value%%%

30.11 Response Metrics

This metric category provides response metrics for OC4J.

30.11.1 UpDown Status

This metric shows whether the OC4J server is up or down. If the value is 1, OC4J is up. If the value is 0, it is down.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 9.0.2

Every 1 Minute

Not Defined

Not Defined

The OC4J instance is down.

30.12 OC4J JMS Metrics

This metric category provides information about the OC4J JMS.

30.12.1 JMS - Active Connections

This metric shows the total number of active OracleAS JMS connections.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 10.1.3

Every 5 Minutes

Not Defined

Not Defined

JMS active connections are %value%.

30.12.2 JMS - Messages Waiting for Read

This metric shows the total number of messages waiting to be read.

Target Version

Collection Frequency

Release 10.1.3

Every 5 Minutes

30.12.3 JMS - Messages Dequeued Rate

This metric shows the rate at which JMS messages are being dequeued. This includes all the messages received, regardless of whether the receipt has been acknowledged or committed, rolled back, or is still pending.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 10.1.3

Every 5 Minutes

Not Defined

Not Defined

JMS Messages dequeued rate is %value%%%

30.12.4 JMS - Messages Enqueued Rate

This metric shows the rate at which JMS messages are being enqueued. This includes all the messages sent, regardless of whether the delivery has been committed, rolled back, or is still pending.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 10.1.3

Every 5 Minutes

Not Defined

Not Defined

JMS Messages enqueued rate is %value%%%.

30.12.5 JMS - Messages Paged In Rate

This metric shows the rate at which the messages are paged in. If a JMS persistent message's body has been "paged out," then in order for the message to be consumed it must be read from the disk (i.e. "paged in").

Target Version

Collection Frequency

Release 10.1.3

Every 5 Minutes

30.12.6 JMS - Messages Paged Out Rate

This metric shows the rate at which message bodies are being paged out.

Target Version

Collection Frequency

Release 10.1.3

Every 5 Minutes

30.12.7 JMS - Messages Committed Since Startup

This metric shows the total number of JMS message enqueues and dequeues that have been committed. This does not include the non-transactional sends or receives. Note that if a message was sent and committed, and later received and committed, that adds a total of 2 to this count.

Target Version

Collection Frequency

Release 10.1.3

Every 5 Minutes

30.12.8 JMS - Messages Discarded Since Startup

This metric shows the total number of messages discarded since startup.

Target Version

Collection Frequency

Release 10.1.3

Every 5 Minutes

30.12.9 JMS - Messages Expired Since Startup

This metric shows the number of messages that expired since startup.

Target Version

Collection Frequency

Release 10.1.3

Every 5 Minutes

30.12.10 JMS - Messages Recovered Since Startup

This metric shows the total number of messages recovered since startup.

Target Version

Collection Frequency

Release 10.1.3

Every 5 Minutes

30.12.11 JMS - Messages Rolledback Since Startup

This metric shows the number of JMS message enqueues and dequeues that have been rolled back since startup. This does not include the non-transactional sends or receives. Note that if a message is repeatedly received and rolled back, this count is incremented once for each time it was rolled back.

Target Version

Collection Frequency

Release 10.1.3

Every 5 Minutes

30.12.12 JMS - Messages Waiting For Commit

This metric shows the total number of messages waiting to be committed.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 10.1.3

Every 5 Minutes

Not Defined

Not Defined

Pending JMS Messages are %value%

30.12.13 JMS - Start Time

This metric shows the time since epoch when the JMS subsytem was started.

Target Version

Collection Frequency

Release 10.1.3

Every 5 Minutes

30.13 OC4J Web Services Metrics

This metric category provides information about the OC4J WebServices.

30.13.1 WebService - Faults Since Startup

This metric shows the total number of faults encountered since the WebService was last started.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 10.1.3

Every 5 Minutes

Not Defined

Not Defined

Number of WebService Faults are %value%.

30.13.2 WebService - Active Requests

This metric shows the number of active WebService requests.

Target Version

Collection Frequency

Release 10.1.3

Every 5 Minutes

30.13.3 WebService - Requests Since Startup

This metric shows the total number of requests processed since the WebService was last started.

Target Version

Collection Frequency

Release 10.1.3

Every 5 Minutes

30.13.4 WebService - Requests Per Second

This metric shows the number of requests per second in the last interval.

Target Version

Collection Frequency

Release 10.1.3

Every 5 Minutes

30.13.5 WebService - Request Processing Time

This metric shows the time (in milliseconds) taken to process a request in the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 10.1.3

Every 5 Minutes

Not Defined

Not Defined

Service time per WebService request is %value% ms.

30.13.6 WebService - Start Time

This metric shows the time when the WebService was last started.

Target Version

Collection Frequency

Release 10.1.3

Every 5 Minutes

30.13.7 WebService - Error Rate

This metric shows the number of errors per number of completed requests.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

Release 10.1.3

Every 5 Minutes

Not Defined

Not Defined

Percentage value of WebServices error is %value%

31 Oracle Application Server Metrics

Oracle Enterprise Manager gathers performance metrics that provide high-level information about the status, performance, and availability of your Oracle Application Server.

31.1 Application Response Metrics

This category of metrics uses the Application URL to measure the responsiveness and availability of the application server instance

31.1.1 Application URL Response Time (seconds)

The Application URL Response Time is measured by automatically and continuously attempting to access the Application URL. The response time includes the time it takes to access the URL and for the application server to render and display the Application URL content.

This metric is used primarily by Cloud Control to measure the responsiveness of the application server instance. The Application URL is shown in the General section of the Application Server Home page in the Cloud Control Console, and it is used to generate the Application URL Response chart on that page.

By the default, the Application URL consists of the application server host name and default listener port for Oracle HTTP Server component. For example:

http://hostname.domain:7778

If you are using the Cloud Control Console, you can modify the Application URL by modifying the properties of the Application Server target. For more information, see Modifying Target Properties in the Cloud Control online help. Alternatively, you can change the Application URL by clicking Change Application URL on the Application Server Home page in the Cloud Control Console.

31.1.2 Application URL Status

This metric indicates whether or not the Application URL, which is used to define the responsiveness of the Application Server, can be accessed successfully. For example, if the Application URL returns an error, the Application URL Status metric will be down.

This metric is used primarily by Cloud Control to measure the responsiveness of the application server instance. The Application URL is shown in the General section of the Application Server Home page in the Cloud Control Console, and it is used to generate the Application URL Response chart on that page.

A value of one (1) indicates that Oracle Management Agent can access the Application URL; a value of zero (0) indicates that the Application URL cannot be accessed successfully.

For more information, see Section 31.1.1, "Application URL Response Time (seconds)".

31.2 OPMN Process Information Metrics

The OPMN Process Information Metrics provide you with a snapshot of how the primary components of your application server--as well as specific components of Oracle Enterprise Manager--are performing. The list provided here will vary, depending upon the application server components you have installed and configured for this instance of Oracle Application Server.

Enterprise Manager components that you can monitor by reviewing the OPMN Process Information Metrics include Oracle Management Agent (agent), Oracle Application Server Control process (console), and Oracle Management Agent watchdog process (watchdog).

For more information about the Management Agent watchdog process, see Oracle Enterprise Manager Advanced Configuration.

31.2.1 Component CPU Usage (%)

This metric shows the percentage of host CPU used by the selected application server component.

31.2.2 Component Memory Usage (%)

This metric shows the percentage of host memory used by the selected application server component.

31.2.3 Component Memory Usage (MB)

This metric shows the memory usage in megabytes for the selected component.

31.2.4 Component Start Time (ms since epoch)

This metric is for internal use only.

31.2.5 Component Up Time (ms)

This metric is for internal use only.

31.2.6 Component Up/down Status

This metric shows whether the component is up or down. A value of one (1) indicates that the component is up and running; a value of zero (0) indicates that the component is down.

If you are using Cloud Control, see About Availability in the online help for more information about how Enterprise Manager determines the availability of Oracle Application Server or Enterprise Manager component.

31.2.7 Free Memory (%)

This metric shows you the percentage of memory that is free on the application server host. The amount of free memory available can help you determine whether or not the system is ready to handle a heavier load.

31.2.8 Free Memory (MB)

This metric shows you the amount of memory (in megabytes) that are free on the application server host. The amount of free memory available can help you determine whether or not the system is ready to handle a heavier load.

31.2.9 Idle CPU Time (%)

This metric shows the percentage of time that the CPU was idle and the system did not have an outstanding disk I/O request.

31.2.10 Total Memory (MB)

This metric shows you the total physical memory available on the application server host computer.

31.3 Resource Usage Metrics

This category of metrics provides you with information about the CPU and Memory being used by the application server.

31.3.1 CPU Idle Time (%)

This metric shows the percentage of system CPU time that is idle. The amount of idle CPU time can help you determine whether or not the system is ready to handle a heavier load.

31.3.2 CPU Usage (%)

This metric shows the percentage of the host CPU being used by the application server and all its configured and enabled components.

31.3.3 Free Memory (%)

This metric shows you the percentage of memory that is free on the application server host. The amount of free memory available can help you determine whether or not the system is ready to handle a heavier load.

31.3.4 Free Memory (MB)

This metric shows you the amount of memory (in megabytes) that are free on the application server host. The amount of free memory available can help you determine whether or not the system is ready to handle a heavier load.

31.3.5 Memory Usage (%)

This metric shows you the percentage of host memory being used by the application server and its configured and enabled components.

31.3.6 Memory Usage (MB)

This metric shows you the amount of memory (in megabytes) being used by the application server and its configured and enabled components.

31.3.7 Other CPU Usage (%)

This metric shows the amount of CPU owned and used by host processes, other than the application server and its configured and enabled components. If you are having problems with CPU usage on the application server host computer, this metric can help you determine whether or not the application server is causing the problem.

31.3.8 Other Memory Usage (%

This metric shows the percentage of host memory in use by other processes or applications, other than the application server and its configured and enabled components. If you are having problems with memory usage on the application server host computer, this metric can help you determine whether or not the application server is causing the problem.

31.3.9 Other Memory Usage (MB)

This metric shows the amount of memory (in megabytes) currently in use by other processes or applications, other than the application server and its configured and enabled components. If you are having problems with memory usage on the application server host computer, this metric can help you determine whether or not the application server is causing the problem.

31.3.10 Total Memory (MB)

This metric shows you the total physical memory available on the application server host computer.

31.4 Response Metrics

This category contains the UpDown Status metric, which indicates whether the Application Server is up or down.

31.4.1 UpDown Status

This metric shows whether or not all the enabled Application Server components are up and running. For example, if one OC4J instance is down, the UpDown Status will be down even if the other application server components are up and running. The status of the Application Server appears in the General section of the Application Server home page in the Cloud Control Console.

32 IBM WebSphere Application Server Metrics

IBM WebSphere Application Server is one of the non Oracle application servers that is monitored using Oracle Enterprise Manager Cloud Control.

The IBM WebSphere Application Server metrics provide for each metric the following information:

- Description

- Metric summary. The metric summary can include some or all of the following: target version, evaluation frequency, collection frequency, upload frequency, operator, default warning threshold, default critical threshold, consecutive number of occurrences preceding notification, and alert text.

- Multiple Thresholds (where applicable)

32.1 Applications Metrics

This metric category describes the applications running on the server.

32.1.1 Applications - Active Requests

This metric shows the current active requests of the application.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

NotDefined

Not Defined

The No of Active Requests for J2EE Application %Application% is %value%.

32.1.2 Applications - Average EJB Method Execution Time

This metric shows the average EJB method execution time.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

NotDefined

NotDefined

The Average EJB Method Execution Time for J2EE Application %Application% is %value%

32.1.3 No. of Active EJB Methods

This metric shows the number of active EJB methods.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

NotDefined

NotDefined

The No of Active EJB methods for J2EE Application %Application% is %value%.

32.1.4 Request Processing Time

When a request comes to an application server, it passes through a servlet and is then processed. This metric depicts the time taken by the server to fulfill this request. Since the servlet is the entry or exit point of the request, this also describes the time taken by the servlet to fulfill a request

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

NotDefined

NotDefined

The Response Time for J2EE Application %Application% is %value%.

32.1.5 Applications - Status

This metric shows the status of the application.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

NotDefined

3

The application %Application% is down

32.2 Dynamic Cache Metrics

This metric category provides information about the dynamic cache.

32.2.1 DynaCache - InMemory Cache Size

This metric shows the size of the InMemory cache.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.2.2 DynaCache - Max InMemory Cache Size

This metric shows the maximum memory that can be used by the cache.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.2.3 DynaCache - Total Timeout Invalidations

This metric shows the total number of timeout invalidations that have occurred at the server.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.3 EJB Metrics

This category of metrics provides information about the EJBs that were received and responded to maximum requests.

32.3.1 EJB - Active Methods

This metric shows the number of methods of the EJBs that are currently active.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.3.2 Current Average Execution Time

This metric shows the average method execution time for the current period.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.3.3 Method Execution Rate per second

This metric indicates the EJB method execution rate per second.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.3.4 Total Method Calls

This metric shows the total method calls on the EJBs.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.4 EJBModule Metrics

This metric category describes the EJB module deployed on the server.

32.4.1 Active Methods

This metric shows the number of methods of the EJBs that are currently active.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.4.2 Average Method Execution Time During Last Interval

This metric shows the average execution time of the method during the last interval.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.4.3 Avg Method Response Time

This metric shows the average response time of the method.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.4.4 Concurrent Lives

This metric shows the concurrent lives.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.4.5 Current Average Method Execution Time

This metric shows the current average method execution time.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.4.6 Destroys

This metric shows the number of EJBs that were destroyed by the container.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.4.7 Instantiates

This metric shows the number of new instances made.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.4.8 Number of EJB Methods Executed During Last Interval

This metric shows the number of EJB methods executed during the last interval.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.4.9 Ready Count

This metric shows the number of EJBs in the ready state.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.4.10 Total Method Calls

This metric shows the total method calls on the EJBs.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5 EntityBean Metrics

This metric category describes the EJB module deployed on the server.

32.5.1 Activates

This metric shows the number of times an instanced was activated.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.2 Activation Time

This metric shows the time taken by the EJB container to activate the EJB instance.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.3 Active Methods

This metric shows the number of methods which can be invoked for action simultaneously.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.4 Average Method Execution Time During Last Interval

This metric shows the average method execution time during the last interval.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.5 Avg Drain Size

This metric shows the average size of the drain.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.6 Concurrent Lives

This metric shows the number of EJB beans in the live state in the container at the same time. In the live state, the client can invoke a method on these beans for business processes.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.7 Creates

This metric shows the number of new instances that were created for the EJB.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.8 Current average execution time

This metric shows the number of EJB methods that were executed during the last interval.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.9 Destroys

This metric shows the number of instances that were destroyed.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.10 Drains From Pool

This metric shows the number of instance drains from the pool.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.11 EJB Method Execution Rate per second

This metric shows the EJB method execution rate per second.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.12 Gets Found

This metric shows the number of Gets found.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.13 Gets From Pool

This metric shows the number of times the instance was taken from the pool.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.14 Instantiates

This metric shows the number of new instantiates of the EJB object

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.15 Load Time

This metric shows the time taken for loading beans in the server.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.16 Loads

This metric shows the number of times an instance was loaded.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.17 No of EJB Methods Executed during last interval

This metric shows the number of EJB methods that were executed during the last interval.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.18 Passivates

This metric shows the number of times this EJB instance was passivated.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.19 Passivation Time

This metric shows the time taken by the container to passivate the bean.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.20 Pool Size

This metric shows the size of the EJB instances pool.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.21 Ready Count

This metric shows the number of instances that are in the ready state.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.22 Removes

This metric shows the number of instances of this EJB that were removed from the container.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.23 Returns Discarded

This metric shows the number of returns that were discarded.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.24 Returns To Pool

This metric shows the number of instances that were returned to the pool after usage.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.25 Store Time

This metric shows the store time for the EJB instance.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.5.26 Stores

Entity beans are stored in persistent storage devices such as relational databases so that they can be recreated even after the container goes down. This metric depicts the number of times the entity beans instance state is stored in the database or persistent storage, instead of being stored in the container.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.6 J2EE Server Metrics

This metric category describes the current server statistics.

32.6.1 J2EE Server - Active EJB Methods

This metric shows the number of active methods.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.6.2 J2EE Server - Active Requests

This metric shows the number of active requests.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.6.3 J2EE Server - Active Sessions

This metric shows the number of active sessions.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The No of Active Sessions are %value%.

32.6.4 J2EE Server - Active Transactions

This metric shows the number of active transactions.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The No of Global Active Transactions are %value%.

32.6.5 J2EE Server - Delta Method Call

This metric shows the number of EJB methods that were executed during the last interval.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.6.6 J2EE Server - EJB Method Execution Rate per second

This metric shows the EJB method execution rate per second.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.6.7 J2EE Server - EJB Method Execution Time

This metric shows the time taken by EJBs for method execution.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.6.8 J2EE Server - Live Sessions

This metric shows the number of live sessions (including those that are alive but not active.)

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The No of Live Sessions are %value%.

32.6.9 J2EE Server - Open JDBC Connections

This metric shows the number of open JDBC connections.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The No of Open JDBC Connections are %value% .

32.6.10 J2EE Server - Request Processing Time

This metric shows the time taken to process requests.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The Request Processing Time is %value%.

32.6.11 J2EE Server - Requests Processed for second

This metric shows the number of requests processed per second.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.7 JDBCProvider Metrics

This metric category depicts the name of the provider software that is being used to connect to a relational database using Java Database Connectivity (JDBC).

32.7.1 JDBCProvider - Average Wait Time

This metric shows the average waiting time for a new connection. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The Average Connection Wait time for JDBC Provider %Name% is %value%

32.7.2 JDBCProvider - Avg Use Time

This metric shows the average time a provider was used. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

-

The Average Connection use time for JDBC Provider %Name% is %value% .

32.7.3 JDBCProvider - Concurrent Waiters

This metric shows the number of connections that are in the waiting state. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.7.4 JDBCProvider - Faults

This metric shows the number of faults. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The Number of faults for JDBCProvider %Name% is %value%

32.7.5 JDBCProvider - Free Pool Size

This metric shows the size of the free pool. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.7.6 JDBCProvider - Jdbc Operation Timer

This metric shows the JDBC operation timer. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.7.7 JDBCProvider - Number Allocates

This metric shows the number of allocations. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.7.8 JDBCProvider - Number Connection Handles

This metric shows the number of connections that are currently being handled. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.7.9 JDBCProvider - Number Creates

This metric shows the number of times a new instance of the provider was created. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.7.10 JDBCProvider - Number Destroys

This metric shows the number of times the instance of this provider was destroyed. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.7.11 JDBCProvider - Number of Managed Connections

This metric shows the number of managed connections. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.7.12 JDBCProvider - Number Returns

This metric shows the number of returns. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.7.13 JDBCProvider - Percent Maxed

This metric shows the percentage maxed. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.7.14 JDBCProvider - Percent Used

This metric shows the percentage used. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The Percentage Used for JDBCProvider %Name% is %value%.

32.7.15 JDBCProvider - Pool Size

This metric shows the size of the pool. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.7.16 JDBCProvider - Prepared Statement Cache Discards

This metric shows the count of prepared statement cache discard and the statement recompiled.The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.8 JSP Metrics

This metric category provides information about the JSPs running on this server.

32.8.1 JSP - Active Requests

This metric shows the number of requests that are currently being processed by the JSP. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.8.2 JSP - Average Processing Time (seconds)

This metric shows the average JSP processing time. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.8.3 Concurrent Requests

This metric shows the number of concurrent requests. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.8.4 Current Client Processing Time

This metric shows the current client processing time. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The Current Client Processing time for JSP %Name% is %value% .

32.8.5 Number Errors

This metric shows the number of errors that were generated while displaying the JSP. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The Number of Errors for JSP %Name% is %value%.

32.8.6 JSP - Requests Per Second During Last Interval

This metric shows the number of active requests per second during the last interval. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.8.7 JSP - Response Time

This metric shows the JSP response time in seconds. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The Response time for JSP %Name% is %value%.

32.8.8 JSP - Time Taken During Last Interval

This metric shows the time taken during the last interval. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.8.9 JSP - Total Requests

This metric shows the total number of requests received. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.9 JVM Metrics

This category of metrics provides information about the Java Virtual Machines.

32.9.1 JVM - CPU Utilization (%)

This metric shows the percentage of utilized CPU. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The percentage CPU Utilization of JVM is %value%.

32.9.2 JVM - Free Memory

This metric shows the amount of free memory available. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.9.3 JVM - Total Memory

This metric shows the total memory used by the server. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.9.4 JVM - Up Time

This metric shows the time for startup of the server after activation. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.9.5 JVM - Used Memory

This metric shows the memory used by the server. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The Used Memory for JVM is %value%.

32.10 MessageDrivenBean Metrics

This metric category provides information about the message-driven bean.

32.10.1 MessageDrivenBean - Active Methods

This metric shows the number of active methods. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.10.2 MessageDrivenBean - Avg Drain Size

This metric shows the average drain size. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.10.3 MessageDrivenBean - Avg Server Session Wait Time

This metric shows the average server session wait time. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.10.4 MessageDrivenBean - Avg method exec. time during last interval

This metric shows the average method execution time during the last interval. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.10.5 MessageDrivenBean - Concurrent Lives

This metric shows the number of concurrent lives. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.10.6 MessageDrivenBean - Current avg exec. time

This metric shows the current method execution time. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.10.7 MessageDrivenBean - Delta Method Calls

This metric shows the number of EJB methods that were executed during the last interval. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.10.8 MessageDrivenBean - Destroys

This metric shows the number of instances that were destroyed. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.10.9 MessageDrivenBean - Drains From Pool

This metric shows the number of drains from the pool of EJB instances. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.10.10 MessageDrivenBean - EJB Method Execution Rate per second

This metric shows the EJB method execution rate per second. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.10.11 MessageDrivenBean - Gets Found

This metric shows the number of gets that were found. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.10.12 MessageDrivenBean - Gets From Pool

This metric shows the number of gets from the pool of EJB instances.The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.10.13 MessageDrivenBean - Instantiates

This metric shows the number of new instances. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.10.14 MessageDrivenBean - Message Blackout Count

This metric shows the number of messages that were blacked out. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.10.15 MessageDrivenBean - Message Count

This metric shows the number of messages. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.10.16 MessageDrivenBean - Pool Size

This metric shows the size of the pool. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.10.17 MessageDrivenBean - Returns Discarded

This metric shows the number of returns that were discarded by the pool. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.10.18 MessageDrivenBean - Returns To Pool

This metric shows the number of returns to the pool. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.10.19 MessageDrivenBean - Server Session Usage

This metric shows the usage of the server session. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.11 ORB Metrics

This metric category describes the Object Request Broker (ORB).

32.11.1 Concurrent Requests

This metric shows the number of concurrent requests. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.11.2 Reference Lookup Time

This metric shows the time taken to look up a reference of the Object Request Broker. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.11.3 Total Requests

This metric shows the total number of requests to the Object Request Broker. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.12 Response

This metric category provides basic information about the IBM WebSphere Application Server.

32.12.1 Status

This metric indicates whether the IBM WebSphere Application Server is up or down. If the value is 1, the server is up. If the value is 0, it is down. The following table shows how often the metric's value is collected and compared against the default thresholds.

Table 32-1 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every Minute

Not Defined

0

The J2EE Server instance is down

32.13 Servlet Metrics

This metric category provides information about the servlets running on this IBM WebSphere Application Server.

32.13.1 Servlet - Active Requests

This metric shows the number of requests that are currently being processed by the servlet. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.13.2 Servlet - Average Processing Time (seconds)

This metric shows the average processing time for requests. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.13.3 Servlet - Concurrent Requests

This metric shows the number of concurrent requests sent to the servlet. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.13.4 Servlet - Current Client Processing Time

This metric shows the current client processing time in seconds. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The Current Client Processing time for Servlet %Name% is %value%.

32.13.5 Servlet - Number Errors

This metric shows the number of errors that were generated while responding to a request. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The Number of Errors for Servlet %Name% is %value%.

32.13.6 Servlet - Requests Per Second During Last Interval

This metric shows the number of active requests per second during the last interval. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.13.7 Servlet - Response Time

This metric shows the response time in seconds. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The Response time for Servlet %Name% is %value%.

32.13.8 Servlet - Time Taken During Last Interval

This metric shows the time taken during the last interval. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.13.9 Servlet - Total Requests

This metric shows the total number of requests received by the servlet. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.14 SessionManager Metrics

This metric category describes the session managers created for web applications.

32.14.1 Activate NonExist Sessions

This metric shows the number of nonexistent sessions that are activated. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.14.2 Active Sessions

This metric shows the number of active sessions. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.14.3 Affinity Breaks

This metric shows the number of session affinity breaks. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.14.4 Cache Discards

This metric shows the number of times that the cache was discarded. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.14.5 Created Sessions

This metric shows the number of session objects that were created by the server. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.14.6 External ReadSize

This metric shows the external read size. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.14.7 External ReadTime

This metric shows the external read time. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.14.8 External Write Size

This metric shows the external write size for this session. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.14.9 External WriteTime

This metric shows the external write time. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.14.10 Invalidated Sessions

This metric shows the number of sessions that were invalidated. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.14.11 Invalidated Via Timeout

This metric shows the number of sessions that were invalidated by timeouts. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.14.12 Live Sessions

This metric shows the number of live sessions till date. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.14.13 No Room For New Session

This metric shows no room for new sessions.The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.14.14 Session Life Time

This metric shows the session's life time. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.14.15 Time Since Last Activated

This metric shows the time since this session was last activated. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.15 Stateful SessionBean Metrics

This metric category provides information about the stateful session EJB deployed on the IBM WebSphere Application Server. The following table shows how often the metric's value is collected.

32.15.1 Average Method Execution Time

This metric shows the average response time of the methods that were executed during the last interval. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.15.2 Activates

This metric shows the number of times the EJB instance was activated by the container. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.15.3 Activation Time

This metric shows the time taken by the container to put the EJB instance in an active state.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.15.4 Active Methods

This metric shows the number of methods that are currently being invoked by the EJB. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.15.5 Concurrent Lives

This metric shows the number of concurrent lives. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.15.6 Creates

This metric shows the number of times a new instance of this EJB was created by the container. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.15.7 Current Average Execution Time

This metric shows the current average execution time of methods by the EJB. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.15.8 Destroys

This metric shows the number of times the EJB instance was destroyed by the container. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.15.9 EJB Method Execution Rate per second

This metric shows the rate of execution of EJB methods per second. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.15.10 EJB Method Call Count during Last Interval

This metric shows the number of EJB methods that were executed during the last interval. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.15.11 Instantiates

This metric shows the number of times the EJB was instantiated after it was destroyed. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.15.12 Passivates

This metric shows the number of times the EJB was passivated from the EJB container. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.15.13 Passivation Time

This metric shows the time taken by the EJB container to change the state of the EJB from active to passivation. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.15.14 Ready Count

This metric shows the number of EJBs that are in the ready state in the containers. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.15.15 Removes

This metric shows the number of times the EJB was removed from the EJB container. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.16 StatelessSessionBean Metrics

This metric category provides information about the stateless session bean.

32.16.1 Active Methods

This metric shows the number of methods that are currently active. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.16.2 Avg Drain Size

All EJB objects exist in a container. The container can discard them by either destroying or passivating them. This metric indicates the drain size, that is the number of objects removed from a container at a time, or in one drain. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.16.3 Average Method Execution Time

This metric shows the average method execution time during the last interval. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.16.4 Concurrent Lives

This metric shows the number of concurrent lives. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.16.5 Current Average Execution Time

This metric shows the current method execution time. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.16.6 Delta Method Calls

This metric shows the number of EJB methods that were executed during the last interval. The following table shows how often the metric's value is collected

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.16.7 Destroys

This metric shows the number of instances that were destroyed by the container. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.16.8 Drains From Pool

This metric shows the number of drains from the pool. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.16.9 EJB Method Execution Rate per second

This metric shows the EJB method execution rate per second. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.16.10 Gets Found

This metric shows the number of gets that were found. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.16.11 Gets From Pool

This metric shows the number of times instances were fetched from the pool. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.16.12 Instantiates

This metric shows the number of new EJB instances. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.16.13 Pool Size

This metric shows the size of the pool. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.16.14 Ready Count

This metric shows the number of instances that are in the ready state. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.16.15 Returns Discarded

For a stateless or entity bean, after an object is utilized for some action or business process, it is sent back to the container so that it can be reused. However, when the object is in process, the container may recreate more objects in the pool so that when this particular object is returned to the container the container may not be able to accept it because its pool size is full. Hence these objects are discarded. This metrics depicts the number of such objects.

The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.16.16 Returns To Pool

This metric shows the number of returns to the pool. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.17 System Metrics

This metric category provides information about the system that is hosting this IBM WebSphere Application Server.

32.17.1 Avg CPU Utilization

This metric shows the average utilization of the system's CPU. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.17.2 CPU Utilization

This metric shows the current utilization of the system's CPU. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.17.3 Free Memory

This metric shows the amount of free memory currently available in the system. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.18 ThreadPool Metrics

This metric category provides information about the thread pool that contains the current running thread.

32.18.1 Active Threads

This metric shows the number of currently active threads. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.18.2 Percent Maxed

This metric shows the maximum percentage of threads at a time in the pool. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.18.3 Pool Size

This metric shows the maximum number of threads a pool can contain. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.18.4 Thread Creates

This metric shows the number of threads that were created in this pool. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.18.5 Thread Destroys

This metric shows the number of times a thread pool was destroyed. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.19 TransactionService Metrics

This category of metrics describes the transaction service. The following table lists the metrics and their associated descriptions.

32.19.1 Active Global Transactions

This metric shows the number of global transactions that are active. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.19.2 Global Before Completion Duration

This metric shows the global before completion duration. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.19.3 Global Commit Duration

This metric shows the time taken for committing global transaction. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.19.4 Global Prepare Duration

This metric shows the global prepare duration. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.19.5 Global Transaction Duration

This metric shows the time taken by global transactions. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.19.6 Global Transaction Timeout

This metric shows the number of transactions that were timed out. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.19.7 Global Transactions Begun

This metric shows the number of global transactions that were initiated. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.19.8 Global Transactions Committed

This metric shows the number of global transactions that were committed. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.19.9 Global Transactions Involved

This metric shows the global transactions involved. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.19.10 Global Transactions RolledBack

This metric shows the number of transactions that were rolled back. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.19.11 Local Before Completion Duration

This metric shows the local before completion duration. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.19.12 Local Commit Duration

This metric shows the time taken for committing a local transaction. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.19.13 Local Transaction Duration

This metric shows the local transaction duration. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.19.14 Local Transaction Timeout

This metric shows the number of local transactions that were stuck and timed out. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.19.15 Local Transactions Begun

This metric shows the number of local transactions that have begun. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.19.16 Local Transactions Committed

This metric shows the number of local transactions that were committed. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.19.17 Local Transactions RolledBack

This metric shows the time taken for rolling back local transactions. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.19.18 Number Optimizations

This metric shows the number of optimizations. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.20 WebModule Metrics

This metric category provides information about the web module or war file deployed on this server.

32.20.1 Number Loaded Servlets

This metric shows the number of servlets that were reloaded into the server. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.20.2 Number Reloads

This metric shows the number of reloads of the web application inside the server memory. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.21 WebServices Service Metrics

This metric category provides information about the web services running on this IBM WebSphere Application Server.

32.21.1 Dispatch Response Time

This metric shows the dispatch response time. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.21.2 Number Dispatched

This metric shows the number of replies dispatched. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.21.3 Number Loaded Services

This metric shows the number of loaded services. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.21.4 Number Received

This metric shows the number of requests received by this web service. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.21.5 Number Successful

This metric shows the number successful. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.21.6 Reply Response Time

This metric shows the time taken by the web service to respond to a request. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The Reply Response time for WebService %Name% is %value% .

32.21.7 Reply Size

This metric shows the size of the reply sent by this web service. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.21.8 Request Response time

This metric shows the request response time. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The Request Response time for WebService %Name% is %value%

32.21.9 Request Size

This metric shows the size of the request. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

32.21.10 Response Time

This metric shows the time taken to respond to a request. The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 Minutes

Not Defined

Not Defined

The Response time for WebService %Name% is %value%.

32.21.11 Size

This metric shows the size. The following table shows how often the metric's value is collected.

Target Version

Collection Frequency

WebSphere Application Server 5.0, 5.1, 6.0, 6.1, 7.0

Every 15 minutes

33 IBM WebSphere MQ Queue Manager Metrics

WebSphere MQ (formerly MQSeries) is IBM's Message Oriented Middleware offering that allows independent and potentially non-concurrent applications on a distributed system to communicate with each other.

The IBM WebSphere MQ metrics provide for each metric the following information:

- Description

- Metric summary. The metric summary can include some or all of the following: target version, evaluation frequency, collection frequency, upload frequency, operator, default warning threshold, default critical threshold, consecutive number of occurrences preceding notification, and alert text.

- Multiple Thresholds (where applicable)

33.1 Channel Current Status

This metric category provides information about the current status of the channel.

33.1.1 Channel Current Status - Bytes Received

This metric shows the number of bytes received.

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 3 Minutes

33.1.2 Channel Current Status - Bytes Sent

This metric shows the number of bytes sent

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 3 Minutes

33.1.3 Channel Current Status - Delta Bytes Received

This metric shows the number of bytes received since the last collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

IBM Websphere MQ V6, V7

Every 3 Minutes

Not Defined

Not Defined

Bytes received during last collection interval for channel %Name% is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

33.1.4 Channel Current Status - Delta Bytes Sent

This metric shows the number of bytes sent since the last collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

IBM Websphere MQ V6, V7

Every 3 Minutes

Not Defined

Not Defined

Bytes sent during last collection interval for channel %Name% is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

33.1.5 Channel Current Status - Delta Messages Sent/Received

This metric shows the number of messages processed since last collection.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

IBM Websphere MQ V6, V7

Every 3 Minutes

Not Defined

Not Defined

Messages sent or received during last collection interval for channel %Name% is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

33.1.6 Channel Current Status - Messages Sent/Received

This metric shows the number of messages processed.

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 3 Minutes

33.1.7 Channel Current Status - Status

This metric shows the current status.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

IBM Websphere MQ V6, V7

Every 3 Minutes

INACTIVE

STOPPED

The channel is not running.

33.2 Channel Saved Status Metrics

This metric category provides information about the Channel Saved Status.

33.2.1 Last Seq Number

This metric shows the sequence number of the last message sent.

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 2 Minutes

33.2.2 Status

This metric shows the status of the channel

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 2 Minutes

33.2.3 Type

This metric shows the type of the channel

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 2 Minutes

33.2.4 Transmission Queue

This metric shows the transmission queue used by sender channels

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 2 Minutes

33.3 Channels Metrics

This category provides metrics related to the channels.

33.3.1 Alteration Date

This metric shows the date on which the definition was last altered.

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.3.2 Cluster Name

This metric shows the name of the IBM WebSphere MQ Cluster to which this channel belongs

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.3.3 Cluster Name list

Shows the cluster name list

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.3.4 Connection Name

This metric shows the name of the channel connection

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.3.5 Max Message Length

This metric shows the maximum length of the message that can be processed by the channel

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.3.6 Type

This metric shows the type of the channel

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.3.7 Transmission Queue Name

This metric shows the name of the transmission queue used by the sender channels.

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.4 Dynamic Queues

This metric category provides information about Dynamic Queues.

33.4.1 Definition Type

This metric shows the type of queue definition.

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 2 Minutes

33.4.2 Type

This metric shows the type of the queue

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 2 Minutes

33.4.3 Usage

This metric shows information about the usage (normal/transmission)

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 2 Minutes

33.5 Local Queues

This metric category shows metrics related to local queues.

33.5.1 Cluster Name List

This metric shows the cluster Name List

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.5.2 Definition Type

This metric shows the type of the queue definition

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.5.3 Depth

This metric shows the number of messages on the queue

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.5.4 Max Depth

This metric shows the maximum number of messages on the queue

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.5.5 Max Message Length

This metric shows the maximum length of the message can be processed

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.5.6 Open Input Count

This metric shows the number of open input handles, that is the total handles open for input on this queue. This gives you an idean on the number of applications that are currently connected to the queue to put messages on the queue

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.5.7 Open Output Count

This metric shows the number of open output handles, that is the total handles open for output on this Queue. This gives you an idea on the number of applications that are currently connected to the queue to get messages from the queue

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.5.8 Percent Usage

This metric shows the space used (in percentage)

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.5.9 Type

This metric shows the type of the queue

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.5.10 Usage

This metric shows details about the usage, which can be "Normal" or "Trasmission")

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.5.11 Transmission Queue Name

This metric shows the name of the transmission queue

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.6 Queue Manager Cluster

This category provides metrics related to IBM Websphere MQ Queue Manager Cluster, mainly the details about the channel used, the queue manager within this cluster, and the type of queue manager that is within this cluster.

33.6.1 Queue Manager Name

This metric shows the name of the IBM Websphere MQ Queue Manager that is within this IBM Websphere MQ Queue Manager Cluster.

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.6.2 Queue Manager Type

This metric shows the type of the IBM Websphere MQ Queue Manager (full/partial repository)

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.7 Queue Manager General

This caterogy provides metrics related to Queue Manager General.

33.7.1 Command Queue

This metric shows the name of the local queue that is used for accepting commands

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 2 Minutes

33.7.2 Dead Letter Queue

This metric shows the name of the local queue that is to be used for undelivered messages

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 2 Minutes

33.7.3 Default Transmission Queue

This metric shows the name of the default transmission queue that is used for the transmitting messages to remote queue managers, if there is no other indication of which transmission queue to use

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 2 Minutes

33.7.4 Max Handles

This metric shows the maximum number of handles that any one job can have open at a time

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 2 Minutes

33.7.5 Max Message Length

This metric shows the maximum length of message that can be processed

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 2 Minutes

33.7.6 Platform

This metric shows the platform on which the queue manager is running

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 2 Minutes

33.7.7 Repository Name List

This metric shows a list of clusters for which this queue manager provides a repository service

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 2 Minutes

33.8 Queue Manager Load

This metric category provides metrics about the load on the IBM Websphere MQ Queue Manager.

33.8.1 Queue Manager Load - Bytes Received

This metric shows the bytes received since last collection

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

IBM Websphere MQ V6, V7

Every 5 Minutes

Not Defined

Not Defined

Bytes received during last collection interval is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

33.8.2 Queue Manager Load - Bytes Sent

This metric shows the bytes sent since last collection

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

IBM Websphere MQ V6, V7

Every 5 Minutes

Not Defined

Not Defined

Bytes sent during last collection interval is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

33.8.3 Queue Manager Load - Messages Sent/Received

This metric shows the messages sent or received since last collection

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

IBM Websphere MQ V6, V7

Every 5 Minutes

Not Defined

Not Defined

Messages sent or received during last collection interval is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

33.9 Queues

This metric category provides metrics related to Message Queues.

33.9.1 Cluster Name List

This metric shows the list of clusters with which the queue is shared

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.9.2 Depth

This metric shows the current depth (number of messages) of the queue. For this metric you can set different warning and critical threshold values for each "QName" object. If warning or critical threshold values are currently set for any "QName" object, those thresholds can be viewed on the Metric Detail page for this metric.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

IBM Websphere MQ V6, V7

Every 10 Minutes

300

500

The Queue is overflowing.

33.9.3 Max Depth

This metric shows the maximum depth (number of messages) of the queue

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.9.4 Max Message Length

This metric shows the maximum message length allowed on a queue

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.9.5 Open Input Count

This metric shows the number of open input handles, that is the total handles open for input on this Queue. This gives you an idea on the number of applications that are currently connected to the queue to put messages on the queue

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.9.6 Open Output Count

This metric shows the number of open output handles, that is the total handles open for output on this Queue. This gives you an idea on the number of applications that are currently connected to the queue to get messages from the queue.

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.9.7 Remote Queue Manager

This metric shows the name of the remote queue manager (only for remote queues)

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.9.8 Remote Queue Name

This metric shows the remote queues with which this queue interacts

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.9.9 Type

This metric shows the queue type. It can be one of the following: Local, Remote, Model, Alias Queue, or Read-only

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.9.10 Use

This metric shows how the queue is being used. The usage types can be "Normal" or "Tramission".

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.9.11 Transmission Queue Name

This metric shows the transmission queue associated with this queue (only for remote queues)

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

33.10 Response Metrics

This category provides status metrics.

33.10.1 Response

This metric shows the current status of the Queue Manager.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

IBM Websphere MQ V6, V7

Every 1 Minute

Not Defined

0

The Queue Manager instance is down

33.11 Sender Channel Queues

This category provides metrics related to the Sender Channel Queues.

33.11.1 Transmission Queue Name

This metric shows the name of the transmission queue.

Target Version

Collection Frequency

IBM Websphere MQ V6, V7

Every 10 Minutes

34 JBoss Application Server Metrics

JBoss Application Server is the market-leading, open source Java 2 Enterprise Edition (J2EE) application server, delivering a high-performance and enterprise-class platform for e-business applications. JBoss provides enterprise-class security, transaction support, resource management, load balancing, and clustering.

The JBoss Application Server metrics provide for each metric the following information:

- Description

- Metric summary. The metric summary can include some or all of the following: target version, evaluation frequency, collection frequency, upload frequency, operator, default warning threshold, default critical threshold, consecutive number of occurrences preceding notification, and alert text.

- Multiple Thresholds (where applicable)

34.1 BoundedQueue ThreadPools

This metric category provides information about the bounded queue thread pools.

34.1.1 Active Threads

This metric shows the active thread count for the bounded queue thread pool.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

The active thread count for the threadpool %name% is %value%.

34.1.2 Maximum Threads at any time

This metric shows the maximum number of threads for the bounded queue thread pool.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

The maximum thread count for the threadpool %name% is %value%.

34.1.3 Rejected threads - last interval

This metric shows the number of rejected threads for the bounded queue threadpool during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

The rejected thread count for the threadpool %name% during last collection interval is %value%.

34.2 Clustering Service Metrics

This metric category provides metrics about High Availability JNDI (HAJNDI) service of JBoss.

34.2.1 Partition Name

This metric shows the name of the partition under which JBoss Application Server is running.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.2.2 Clustering Service - Bind Address

This metric shows the IP address to which the HAJNDI service is bound.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.2.3 Clustering Service - Port

This metric shows the port used by the HAJNDI service.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.2.4 Clustering Service - Rmi Port

This metric shows the RMI port of the HAJNDI service.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.2.5 Clustering Service - State

This metric shows the state of the HAJNDI service. Number "3" is for "OK" state.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.2.6 Clustering Service - State (Text)

This metric shows the state of the HAJNDI service.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.3 CPU Usage

This metric category provides information about server COU usage.

34.3.1 Server CPU Usage (%)

This metric shows the JBoss Application Server CPU usage during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

The JBoss Server CPU Usage in percentage during last collection interval is %value%. (%)

34.4 Datasource Metrics

This metric category provides information about the Datasource metrics.

34.4.1 Datasource - Available Connections

This metric shows the available connections to the connection pool.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x

Every 15 Minutes

Not Defined

Not Defined

Current free pool size of module %Name% is %value%.

JBoss Application Server 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

Current free pool size of DataSource %Name% is %value%.

34.4.2 Datasource - Connection Pool Size

This metric shows the current connection pool size.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x

Every 15 Minutes

Not Defined

Not Defined

Current pool size of module %Name% is %value%.

JBoss Application Server 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

Current pool size of DataSource %Name% is %value%.

34.4.3 Datasource - Current Waiting Thread Count

This metric shows the number of current waiting threads.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x

Every 15 Minutes

Not Defined

Not Defined

Current waiting thread count of module %Name% is %value%.

34.4.4 Datasource - Connections Created (per min)

This metric shows the rate of connections created per minute during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

The rate of Connections created during last metric collection for DataSource %Name% is %value% (per min).

34.4.5 Datasource - Connections Closed (per min)

This metric shows the rate of connections closed per minute during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

The rate of Connections destroyed during last metric collection for DataSource %Name% is %value% (per min).

34.4.6 Datasource - Connections in Use

This metric shows the number of connections currently in use.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

Count of connections in use for DataSource %Name% is %value%.

34.5 DataSource Bind Metrics

This metric category provides DataSourceBinding service details for JBoss Application Server.

34.5.1 JNDI Name

This metric shows the JNDI Name for DataSourceBinding service for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.6 Entity Ejb Metrics

This metric category shows information for all the entity EJBs loaded inside the JBoss Application Server.

34.6.1 Entity EJB - Cache Size

This metric shows the size of the entity EJB cache size.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

Cache size of entity EJB %Name% is %value%.

34.6.2 Entity EJB - Current Instances Pooled Count

This metric shows the number of instance kept in the pool currently.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x

Every 15 Minutes

Not Defined

Not Defined

Count of current instances pooled for entity EJB %Name% is %value%.

34.6.3 Entity EJB - Current Ready Instances Count

This metric shows the number of instances of this EJB that are in the ready state.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x

Every 15 Minutes

Not Defined

Not Defined

Count of current ready instances for entity EJB %Name% is %value%.

34.6.4 Entity EJB - Current Size

This metric shows the current size of this EJB.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

Current size of entity EJB %Name% is %value%.

34.6.5 Entity EJB - Instances Created Count

This metric shows the count of the instances created for this EJB by the EJB container

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.6.6 Entity EJB - Instances Removed Count

This metric shows the number of instance of this EJB that are removed from the EJB container.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.6.7 Entity EJB - Maximum Instances in the Pool

This metric shows the maximum number of instance of this EJB that can be put in the pool.

Target Version

Collection Frequency

JBoss Application Server 4.x

Every 15 Minutes

34.6.8 Entity EJB - Minimum Instances in the Pool

This metric shows the minimum number of instance of this EJB that should be there in the pool.

Target Version

Collection Frequency

JBoss Application Server 4.x

Every 15 Minutes

34.6.9 Entity EJB - Minimum Ready Instances Count

This metric shows the minimum number of instance of this EJB that should be in the ready state.

Target Version

Collection Frequency

JBoss Application Server 4.x

Every 15 Minutes

34.6.10 Entity EJB - Name

This metric shows the name of the EJB

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.6.11 Entity EJB - Parent

This metric shows the parent or the JAR file to which this EJB belongs.

Target Version

Collection Frequency

JBoss Application Server 4.x

Every 15 Minutes

34.6.12 Entity EJB - State String

This metric shows the state of the EJB.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

State of entity EJB %Name% has changed to %value%.

34.6.13 Statistic Provider

This metric shows performance statistics support for this managed object (whether true or false).

Target Version

Collection Frequency

JBoss Application Server 4.x

Every 15 Minutes

34.7 Ejb Modules Metrics

This category shows the information for the EJB modules that are loaded inside the JBoss Application Server.

34.7.1 Name

This metric shows the name of the EJB module.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.7.2 Statistic Provider

This metric shows that the "Statistic Provider" and "State Manageable" attributes are provided to inform a client that the EJB module that is being looked at does or does not support state management, or does or does not provide statistics as defined by the JSR-77 specification.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.8 Global Request Processor

This metric category provides information about the Global Request Processor metrics.

34.8.1 Data Received (KB per min)

This metric shows the amount of data received per minute by the Global Request Processor during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

The data received during last collection interval by the Global Request Processor %name% is %value% (KB per min).

34.8.2 Data Sent (KB per min)

This metric shows the amount of data sent per minute by the Global Request Processor during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

The data sent during last collection interval by the Global Request Processor %name% is %value% (KB per min).

34.8.3 Errors (per min)

This metric shows the number of errors generated per minute by the Global Request Processor during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

The number of errors during last collection interval for the Global Request Processor %name% is %value% (per min).

34.8.4 Requests (per min)

This metric shows the total number of requests per minute for the Global Request Processor during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

The total request rate during last collection interval for the GlobalRequestProcessor %name% is %value% (per min).

34.8.5 Processing time (ms) - last interval

This metric shows the amount of time taken to process all the requests during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

Time taken to process all the requests during last collection interval by the Global Request Processor %name% is %value% (ms).

34.9 Connection Pools Metrics

This metric category provides Managed Connection Pool details for JBoss Application Server.

34.9.1 Criteria

This metric shows the criteria for managed connection pool for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.9.2 Maximum Size

This metric shows the maximum size for managed connection pool for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.9.3 Minimum Size

This metric shows the maximum size for managed connection pool for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10 JBoss JCA Metrics

This metric category gives information for the Java Connector (JCA) resources of the JBoss Application Server.

34.10.1 JCA - Count Use Time

This metric shows the current use time (in ms) for JCA Resource.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.2 JCA - Count Use Time (Sec)

This metric shows the current use time for JCA Resource (in seconds).

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.3 JCA - Count Wait Time

This metric shows the current wait time (in ms) for JCA Resource.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.4 JCA - Current Free Pool Size

This metric shows the number of instances of this resource in the pool that are not being used currently.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.5 JCA - Current Pool Size

This metric shows number of instances in the pool currently.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.6 JCA - Current Waiting Thread Count

This metric shows the number of threads waiting to acquire JCA connections.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.7 JCA - High Pool Size

This metric shows the High Water mark for JCA Connection pool.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.8 JCA - Instances Close Count

This metric shows the number of instances closed.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.9 JCA - Instances Created Count

This metric shows the number of instances created.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.10 JCA - Low Pool Size

This metric shows the Low Water mark for JCA Connection pool.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.11 JCA - Lower Bound Free Pool Size

This metric shows the minimum number of instances that can be free inside the pool.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.12 JCA - Lower Bound Pool Size

This metric shows the lower bound for lower connection pool.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.13 JCA - Max Wait Time

This metric shows the minimum wait time (in ms) for JCA Resource.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.14 JCA - Maximum Pool Size

This metric shows the maximum number of instances of this resource that can be there in the pool.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.15 JCA - Maximum Use Time

This metric shows the maximum usage time for JCA Resource.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.16 JCA - Maximum Waiting Thread Count

This metric shows the high water mark for waiting thread count for JCA connections.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.17 JCA - Min Wait Time

This metric shows the minimum wait time (in ms) for JCA Resource.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.18 JCA - Minimum Pool Size

This metric shows the minimum free pool size.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.19 JCA - Minimum Used Time

This metric shows the minimum usage time for JCA Resource.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.20 JCA - Minimum Waiting Thread Count

This metric shows the low water mark for waiting thread count for JCA connections.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.21 JCA - Total Used Time

This metric shows the total usage time for JCA Resource.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.22 JCA - Total Wait Time

This metric shows the total wait time for JCA Resource (in ms).

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.23 JCA - Upper Bound Free Pool Size

This metric shows the maximum number of instances that can be free inside the pool.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.24 JCA - Upper Bound Pool Size

This metric shows the upper bound for JCA Connection Pool.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.25 Name

This metric shows the name of the JCA resource.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.26 Parent

This metric shows the name of the resource adaptor to which the JCA resource belongs.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.10.27 Statistics Provider

This metric shows performance statistics support for this managed object (whether true or false).

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.11 JMS Queue Metrics

This metric category provides information about the JMS Queue metrics.

34.11.1 Consumers

This metric shows the number of consumers for the JMS queue.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 6.x

Every 10 Minutes

Not Defined

Not Defined

The number of Consumers for the JMS Queue %name% is %value%.

34.11.2 Messages being delivered

This metric shows the number of messages currently being delivered in the JMS queue.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 6.x

Every 10 Minutes

Not Defined

Not Defined

The number of messages currently being delivered in the JMS Queue %name% is %value%.

34.11.3 Messages in Queue

This metric shows the number of messages in the JMS queue currently.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 6.x

Every 10 Minutes

Not Defined

Not Defined

The number of messages currently present in the JMS Queue %name% is %value%.

34.11.4 Messages currently scheduled

This metric shows the number of the messages scheduled in the JMS queue currently.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 6.x

Every 10 Minutes

Not Defined

Not Defined

The number of messages currently scheduled in the JMS Queue %name% is %value%.

34.11.5 Messages added (per min)

This metric shows the rate of messages (per minute) added to the JMS queue during the last collection interval.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 6.x

Every 10 Minutes

Not Defined

Not Defined

The rate of messages added in the JMS Queue %name% during last collection interval is %value% (per min).

34.12 JVM Metrics

This metric category provides information about the Java Virtual Machine (JVM) on which the JBoss Application Server is running.

34.12.1 JVM - Free Heap (%)

This metric shows the percentage of heap memory that is free and is not used by the JVM.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

25

10

JVM free heap size is %value% %.

34.12.2 JVM - Heap Size (MB)

This metric shows the heap memory (in MB) used by the JVM that is used by JBoss Application Server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

Not Defined

Not Defined

JVM Heap size is %value% MB.

34.12.3 JVM Name

This metric shows the name of the JVM on which JBoss Application Server is running.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

34.12.4 JVM Version

This metric shows the version of the JVM that is used by the JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

34.12.5 Vendor

This metric shows the name of the vendor or provider of the JVM.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

34.13 Mail Service Metrics

This metric category provides information about the JBoss Mail Service.

34.13.1 Service - Default Sender

This metric shows the default sender of the any message that goes via JBoss mail service.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.13.2 Service - JNDI Name

This metric shows the name by which the JBoss mail service is registered with the JNDI server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.13.3 Service - POP3 Server Host

This metric shows the host of the POP3 server for the JBoss mail service.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.13.4 Service - SMTP Server Host

This metric shows the host of the SMTP server for the JBoss mail service.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.13.5 Service - State

This metric shows the current state of the JBoss mail service. If the number is 3, then it is up.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.13.6 Service - State (text)

This metric shows the state of the JBoss mail service.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.13.7 Service - Store Protocol

This metric shows the protocol used by the JBoss mail service for receiving the messages.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.13.8 Service - Transport Protocol

This metric shows the transport protocol used by the JBoss mail service for sending messages.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.14 Message Driven Ejb Metrics

This metric category shows information for all the message driven EJBs loaded inside the JBoss Application Server.

34.14.1 MDB - Current Size

This metric shows the current size of the message driven EJB.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 5.x, 6.x

Every 30 Minutes

Not Defined

Not Defined

Current size of message driven bean %Name% is %value%.

34.14.2 MDB - Instances Created Count

This metric shows the count of the instances created for this EJB by the EJB container.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.14.3 MDB - Instances Removed Count

This metric shows the number of instance of this EJB that are removed from the EJB container.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.14.4 MDB - Messages Count

This metric shows the number of messages received by this EJB.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.14.5 MDB - Name

This metric shows name of the EJB.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.14.6 MDB - Parent

This metric shows the parent or the jar file to which this EJB belongs.

Target Version

Collection Frequency

JBoss Application Server 4.x

Every 15 Minutes

34.14.7 MDB - State String

This metric shows the state of the message driven EJB.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 5.x, 6.x

Every 30 Minutes

Not Defined

Not Defined

State of message driven bean %Name% has changed to %value%.

34.14.8 Statistic Provider

This metric shows performance statistics support for this managed object (whether true or false).

Target Version

Collection Frequency

JBoss Application Server 4.x

Every 15 Minutes

34.15 Naming Service Metrics

This metric category provides information about the naming service of JBoss Application Server.

34.15.1 Listen Port

This metric shows the port on which the naming service of JBoss Application Server is running.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.15.2 RMI Port

This metric shows the RMI port of the naming service of JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.15.3 Service Name

This metric shows the name of the service monitored, that is, in this case it is NamingService only.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.15.4 Service State

This metric shows the current state of the naming service of JBoss Application Server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

Not Defined

Not Defined

State of Naming service has changed to %value%.

34.16 Protocols Ports Metrics

This category provides connection details for JBoss Application Server.

34.16.1 JBoss - Connection Linger Value

This metric represents linger value on the incoming connection for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.16.2 JBoss - Connection Timeout

This metric shows the timeout value on the incoming connection for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.16.3 JBoss - KeyStore File

This metric shows the KeyStore file for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.16.4 KeyStore Type

This metric shows the configured keystore type for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.16.5 JBoss - Protocol

This metric shows the coyote protocol handler in use for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.16.6 JBoss - Redirect Port

This metric shows the redirect port for non-SSL to SSL redirects for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.16.7 JBoss - Redirect Port Protocol

This metric shows the protocol name for this Connector (http, https) for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.17 Server Configuration Metrics

This category provides information about the configuration of JBoss Application Server.

34.17.1 JBoss - Base Directory

This metric shows the base directory (directory 'server') for the JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

34.17.2 JBoss - Configuration Name

This metric shows the name of the configuration that is used by JBoss Application Server. By default, JBoss Application Server comes with some configuration, for example, 'all', 'minimal', and so on.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

34.17.3 JBoss - Deployment Filename

This metric shows the name of the main deployment file of JBoss Application Server. By default, it is jboss-service.xml. The configuration directory contains the "jboss-service.xml" bootstrap descriptor file for a given server configuration. This defines the core service-configurations that are fixed for the lifetime of the server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

34.17.4 JBoss - Home Directory

This metric shows the installation directory of the JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

34.17.5 JBoss - Server Home Directory

This metric shows the configuration directory of JBoss Application Server that is running. If JBoss Application Server is running under 'minimal' configuration, then this metric shows the path to that configuration.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

34.18 Server Details Metrics

This category provides server details for JBoss Application Server.

34.18.1 JBoss - Active Thread Count

This metric shows the active thread count for JBoss Application Server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

The number of active threads is %value%.

34.18.2 JBoss - Active Thread Group Count

This metric shows the active thread group count for JBoss Application Server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

The number of active thread groups is %value%.

34.18.3 JBoss - Available No. of Processors

This metric shows the available number of processors for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.18.4 JBoss - Free Heap Size

This metric shows the free heap memory for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.18.5 JBoss - Free Heap Size %

This metric shows the percentage of available heap memory out of total configured heap memory for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.18.6 JBoss - Heap Size

This metric shows the available heap memory (in MB) for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.18.7 JBoss - Heap Size (MB)

This metric shows the available heap memory (in MB) for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.18.8 JBoss - Host Name

This metric provides the host name on which JBoss Application Server is installed.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.18.9 JBoss - Java Vendor Name

This metric provides Java Vendor Name for JBoss Application Server

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.18.10 JBoss - Java Version

This metric shows the version of JDK/JRE for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.18.11 JBoss - Java VM Name

This metric shows the name of the Java Virtual Machine (JVM) used for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.18.12 JBoss - Java VM Vendor Name

This metric shows the Java VM vendor name with which this JBoss Application Server is running.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.18.13 JBoss - Java VM Version

This metric shows the Java VM version with which JBoss Application Server is running.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.18.14 JBoss - Maximum Memory

This metric shows the maximum available memory on which JBoss Application Server is running.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.18.15 JBoss - OS Architecture

This metric provides operating system architecture details on which JBoss Application Server is running.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.18.16 JBoss - OS Name

This metric provides operating system name on which JBoss Application Server is running.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.18.17 JBoss - OS Version

This metric shows the operating system version on which JBoss Application Server is running.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.18.18 JBoss - Total Heap Size

This metric shows the total heap memory for JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.18.19 JBoss - Total Heap Size(MB)

This metric shows the total heap memory (in MB) for JBoss Application Server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

Total Heap size is %value% MB.

34.19 JBoss Server Metrics

This category provides information about JBoss Application Server.

34.19.1 Host Address

This metric shows the IP address of the host on which the JBoss Application Server is running.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

34.19.2 Host Name

This metric shows the host name on which the JBoss Application Server is running.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

34.19.3 Host Operating System

This metric shows the operating system of the host on which the JBoss Application Server is running.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

34.19.4 JBoss - Build Date

This metric shows the build date for the JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

34.19.5 JBoss - Build ID

This metric shows the build ID of the JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

34.19.6 JBoss - Listen Port

This metric shows the naming service port or Java Naming Provider (JNP) port for the JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

34.19.7 JBoss - Start Time

This metric shows date on which the JBoss Application Server was started.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

34.19.8 JBoss - Version

This metric shows the version (build version) of the JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

34.19.9 JBoss - Version Name

This metric shows the version name of the JBoss Application Server.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 30 Minutes

34.20 JBoss Servlets Raw Metrics

This metric category provides information for the servlets loaded inside the JBoss Application Server.

34.20.1 Parent

This metric shows the parent or the application to which this servlet belongs.

34.20.2 Servlet - Active Requests / Sec

This metric shows rate of requests (per sec) on the servlet.

34.20.3 Servlet - Active Requests since last Upload

This metric shows the current active requests for the servlet.

34.20.4 Servlet - Active Requests, Response Time (Sec)

This metric shows the response time (per sec) for the servlet for handling those requests.

34.20.5 Servlet - Maximum Response Time

This metric shows the maximum processing time of a request (depicted by a long value)

34.20.6 Servlet - Minimum Response Time

This metric shows the minimum processing time of a request (depicted by a long value).

34.20.7 Servlet - Response Time Unit

This metric shows the unit of time for the requests.

34.20.8 Servlet - Total Requests

This metric shows the number of requests processed by this servlet.

34.20.9 Servlet - Total Response Time

This metric shows the average response time for the request.

34.20.10 Servlet Name

This metric shows the name of the JBoss servlet.

34.20.11 Statistic Description

This metric shows the description of the statistic instance.

34.20.12 Statistic Name

This metric shows the name of the statistic instance.

34.20.13 Statistic Provider

This metric shows the performance statistics support for this managed object (whether true or false).

34.21 Server Servlet/JSP Metrics

This metric category provides information about the Server Servlet/JSP metrics.

34.21.1 Active Sessions

This metric shows the number of current active sessions for the server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 10 Minutes

Not Defined

Not Defined

The number of current active sessions for the server is %value%.

34.21.2 Servlet and JSP - Requests (per min)

This metric shows the request rate (per minute) for the server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 10 Minutes

Not Defined

Not Defined

The request rate for the server is %value% per second.

34.21.3 Servlet and JSP - Request Processing Time (ms)

This metric shows the average response time for processing requests for the server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 10 Minutes

Not Defined

Not Defined

The average response time (since last upload) for the server is %value% (ms).

34.22 Stateful Session EJB Metrics

This category shows information about the stateful EJBs loaded inside the JBoss Application Server.

34.22.1 Stateful Ejb - Current Method Ready Count

This metric shows the count of the instances that are in the ready state in the EJB container.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x

Every 15 Minutes

Not Defined

Not Defined

Current method ready count of stateful EJB %Name% is %value%.

34.22.2 Stateful Ejb - Current Passive Instances Count

This metric shows the number of instances (of this EJB) that are in the passive state.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x

Every 15 Minutes

Not Defined

Not Defined

Current passive instances count of stateful EJB %Name% is %value%.

34.22.3 Stateful Ejb - Current Size

This metric shows the current size of this EJB.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

Current size of stateful EJB %Name% is %value%.

34.22.4 Stateful Ejb - Instances Created Count

This metric shows the count of the instances created for this EJB by the EJB container.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.22.5 Stateful Ejb - Instances Removed Count

This metric shows the number of instance of this EJB that are removed from the EJB container.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.22.6 Stateful Ejb - Maximum Method Ready Count

This metric shows the maximum number of instances that can be in the ready state in the EJB container.

Target Version

Collection Frequency

JBoss Application Server 4.x

Every 15 Minutes

34.22.7 Stateful Ejb - Maximum Passive Instances Count

This metric shows the maximum number of instances that can be in the passive state.

Target Version

Collection Frequency

JBoss Application Server 4.x

Every 15 Minutes

34.22.8 Stateful Ejb - Minimum Method Ready Count

This metric shows the minimum number of instances that can be in the ready state in the EJB container.

Target Version

Collection Frequency

JBoss Application Server 4.x

Every 15 Minutes

34.22.9 Stateful Ejb - Minimum Passive Instances Count

This metric shows the minimum number of instances that can be in the ready state in the EJB container.

Target Version

Collection Frequency

JBoss Application Server 4.x

Every 15 Minutes

34.22.10 Stateful Ejb - Name

This metric shows the name of the EJB.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.22.11 Stateful Ejb - Parent

This metric shows the parent or the JAR file to which this EJB belongs.

Target Version

Collection Frequency

JBoss Application Server 4.x

Every 15 Minutes

34.22.12 Stateful Ejb - State String

This metric shows the state of this EJB.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

State of stateful EJB %Name% has changed to %value%.

34.22.13 Statistic Provider

This metric shows performance statistics support for this managed object (whether true or false).

Target Version

Collection Frequency

JBoss Application Server 4.x

Every 15 Minutes

34.23 Stateless Session EJB Metrics

This category shows information about the stateless EJBs loaded inside the jboss server.

34.23.1 Stateless Ejb - Current Method Ready Count

This metric shows the count of the instances which are in the ready state in the EJB container.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x

Every 15 Minutes

Not Defined

Not Defined

Current method ready count of stateless EJB %Name% is %value%.

34.23.2 Stateless Ejb - Instances Created Count

This metric shows the count of the instances created for this EJB by the EJB container.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.23.3 Stateless Ejb - Instances Removed Count

This metric shows the count of the instances removed for this EJB by the EJB container.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.23.4 Stateless Ejb - Maximum Method Ready Count

This metric shows the maximum number of instances that can be in the ready state in the EJB container.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.23.5 Stateless Ejb - Minimum Method Ready Count

This metric shows the minimum number of instances that can be in the ready state in the EJB container.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.23.6 Stateless Ejb - Name

This metric shows the name of the EJB.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.23.7 Stateless Ejb - Parent

This metric shows the parent or the JAR file to which this EJB belongs.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.23.8 Statistic Provider

This metric shows performance statistics support for this managed object (whether true or false).

Target Version

Collection Frequency

JBoss Application Server 4.x

Every 15 Minutes

34.23.9 Stateless Ejb - Current Size

This metric shows the current size of the stateless EJB.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

Current size of stateless EJB %Name% is %value%.

34.23.10 Stateless Ejb - State String

This metric shows the state of the stateless EJB.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

State of stateless EJB %Name% has changed to %value%.

34.24 Top EJBs Metrics

This category shows information for the top performing EJBs of JBoss

34.24.1 JBoss - Ejb Create Count

This metric shows the number of instances created for this EJB by the container.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.24.2 JBoss - Ejb Remove Count

This metric shows the number of instances removed for this EJB by the container.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.24.3 JBoss - Ejb Type

This metric shows the name of the EJB.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.25 Top Servlets Metrics

This category gives information for the top performing servlets of the JBoss Application Server.

34.25.1 Servlet WAR Name

This metric shows the parent or application to which the servlet belongs.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.25.2 Web Component Type

This metric shows the name of the servlet.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.25.3 Servlet - Requests Processed Per Sec

This metric shows rate of request per second to this servlet.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

The rate of requests for servlet %Name% of web-module %parent% is %value% per second.

34.25.4 Servlet - Requests Processing Time (ms)

This metric shows the response time for processing requests for this servlet.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

The response time for servlet %Name% of web-module %parent% is %value% ms.

34.26 Transactions Metrics

This category shows the information for the transaction manager service of the JBoss Application Server.

34.26.1 Committed last interval

This metric shows the number of transaction committed since last interval.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.26.2 JBoss - Active Transactions Count

This metric shows the number of current active transactions.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

The count of active %Name% transactions is %value%.

34.26.3 JBoss - Transactions / Sec

This metric shows the rate of active transactions per second.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

The rate of change in the number of active %Name% transactions is %value% per second.

34.26.4 JBoss - Transactions Committed / Sec

This metric shows the rate of transactions committed per second.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

The rate at which %Name% transactions are committed is %value% per second.

34.26.5 JBoss - Transactions Committed Count

This metric shows the number of transaction that have been committed.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.26.6 JBoss - Transactions Rolled Back / Sec

This metric shows the rate of transactions rolled back per second.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

The rate at which %Name% transactions are rolled-back is %value% per second.

34.26.7 JBoss - Transactions RolledBack Count

This metric shows the number of transaction that have been rolled back.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.26.8 JBoss - Transactions Timeout (Secs)

This metric shows the time interval in seconds after which the transactions will time out.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

Not Defined

Not Defined

%Name% - Transaction timeout is %value% seconds.

34.26.9 Rolledback last interval

This metric shows the number of transactions rolled back since last interval.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.26.10 Transaction last interval

This metric shows the transaction that was made since last interval.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.27 JBoss Web Applications Metrics

This category shows performance information about the Web application loaded inside the JBoss Application Server.

34.27.1 Web Apps - Active requests since last agent upload

This metric shows the current active requests for the application.

34.27.2 Web Apps - Average maximum response time

This metric shows the average maximum response time for the active requests.

34.27.3 Web Apps - Average minimum response time

This metric shows the average minimum response time for the active requests.

34.27.4 Web Apps - Average Response Time

This metric shows the average response given by these applications for the request.

34.27.5 Web Apps - Requests rate per second

This metric shows the current rate of requests (per sec) to this application.

34.27.6 Web Apps - Total Requests

This metric shows the total requests for the application.

34.27.7 Web Apps - Total Response Time

This metric shows the total time take for servicing those requests.

34.27.8 Web Apps - Total Response time for Active Requests

This metric shows the total response time for all the active requests.

34.28 Web Service Metrics

This category provides information for the Web services running on the JBoss Application Server.

34.28.1 Service - Bind Address

This metric shows the IP address to which the Web service is bound.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.28.2 Service - Host

This metric shows host name on which the Web service is running.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.28.3 Service - Port

This metric shows the port on which the Web service is listening.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.28.4 Service - State

This metric shows the state of the Web service as a number. Number "3" depicts that the service is up.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.28.5 Service - State (text)

This metric shows the state of the Web service.

Target Version

Collection Frequency

JBoss Application Server 4.x, 5.x, 6.x

Every 15 Minutes

34.29 Resource Usage Metrics

This category provides metrics related to JBoss Application Server resource usage.

34.29.1 Free Memory (%)

This metric shows the percentage of heap memory that is free and is not used by the Java Virtual Machine (JVM).

34.29.2 Maximum Memory Size (MB)

This metric provides total heap memory configured for JBoss Application Server.

34.29.3 Memory Usage (MB)

This metric shows the memory used by JBoss Application Server in MBs.

34.30 Response Metrics

This category provides response metrics for JBoss Application Server.

34.30.1 UpDown Status

This metric shows whether the JBoss Application Server is up or down. If the value is 1, then the JBoss Application Server is up. If the value is 0, then it is down.

If the JBoss Application Server instance is down, then restart it from the scripts that come with JBoss Application Server.

Target Version

Evaluation and Collection Frequency

Default Warning Threshold

Default Critical Threshold

Alert Text

JBoss Application Server 4.x, 5.x, 6.x

Every Minute

Not Defined

0

The JBoss instance is down.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2016, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Alpha and Beta Draft Documentation Notice

If this document is in private preproduction status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your beta trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.