Oracle Enterprise Manager Oracle Fusion Middleware Metric Reference Manual, 12c Release 1 (12.1.0.2.0)

12c Release 1 (12.1.0.2.0)

E25158-04

Contents

Title and Copyright Information

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

How to Use This Manual

- Structure of the Oracle Enterprise Manager Oracle Fusion Middleware Metric Reference Manual

- Background Information on Metrics, Thresholds, and Alerts

1 WebLogic Server

- Application Overview Metrics

- Application - Cached Beans

- Application - Cache Accesses (per minute)

- Application - Bean Activations (per minute)

- Application - Cache Hits (%)

- Application - Cache Misses (per minute)

- Application - Bean Accesses (per minute)

- Application - Bean Access Successes (%)

- Application - Free Bean Instances

- Application - Bean Destroys (per minute)

- Application - Bean Access Failures (per minute)

- Application - Beans in Use

- Application - Bean Transaction Commits (%)

- Application - Bean Transaction Commits (per minute)

- Application - Bean Transaction Rollbacks (per minute)

- Application - Bean Transaction Timeouts (per minute)

- Application - MDB Messages (per minute)

- Application - Requests (per minute)

- Application - Request Processing Time (ms)

- Application - Active Sessions

- Application - Work Manager Pending Requests

- Application - Work Manager Requests (per minute)

- Application Work Manager - Work Manager Pending Requests

- Application Work Manager - Work Manager Requests (per minute)

- Application Work Manager - Work Manager Stuck Threads

- Application Metrics

- Application - Status

- Datasource Metrics

- Datasource - Available Connections

- Datasource - Connections Created (per minute)

- Datasource - Connections in Use

- Datasource - Connection Leaks (per minute)

- Datasource - Connection Pool Size

- Datasource - Connection Refresh Failures (per minute)

- Datasource - Connection Request Failures (per minute)

- Datasource - Connection Requests (per minute)

- Datasource - Successful Connections (%)

- Datasource - Unavailable Connections

- Datasource - Connection Requests Waiting

- Datasource - Failed Waiting Connection Requests (per minute)

- Datasource - Connection Requests that Waited (per minute)

- Datasource - Connection Wait Successes (%)

- Datasource - Connection Wait Successes (per minute)

- Datasource - State

- Datasource - Statements Added to Cache (per minute)

- Datasource - Statements Discarded from Cache (per minute)

- Datasource - Cached Statements not Used (per minute)

- Datasource - Cached Statements Used (%)

- Datasource - Cached Statements Used (per minute)

- Datasource - Statement Cache Size

- EJB Module Metrics

- EJB Module - Cached Beans

- EJB Module - Cache Accesses (per minute)

- EJB Module - EJB Activations (per minute)

- EJB Module - EJB Cache Hits (%)

- EJB Module - EJB Cache Misses (per minute)

- EJB Module - EJB Passivations (per minute)

- EJB Module - Bean Accesses (per minute)

- EJB Module - Bean Successes (%)

- EJB Module - Free Bean Instances

- EJB Module - Bean Destroys (per minute)

- EJB Module - Failed Bean Accesses (per minute)

- EJB Module - Beans in Use

- EJB Module - Bean Transaction Commits (per minute)

- EJB Module - Bean Transaction Rollbacks (per minute)

- EJB Module - Bean Transaction Timeouts (per minute)

- EJB Module - MDB Messages (per minute)

- EJB Pool Metrics

- EJB Pool - Bean Accesses (per minute)

- EJB Pool - Successful Bean Accesses (%)

- EJB Pool - Available Beans

- EJB Pool - Bean Destroys (per minute)

- EJB Pool - Bean Access Failures (per minute)

- EJB Pool - Beans in Use

- EJB Transaction Metrics

- EJB Transaction - Bean Transaction Commits (%)

- EJB Transaction - Bean Transaction Commits (per minute)

- EJB Transaction - Bean Transaction Rollbacks (per minute)

- EJB Transaction - Bean Transaction Timeouts (per minute)

- JMS Destination Metrics

- JMS Destination - Bytes Current Count

- JMS Destination - Bytes Pending Count

- JMS Destination - Bytes Received Count

- JMS Destination - Bytes Received Current Count

- JMS Destination - Bytes Received Current Count Per Second

- JMS Destination - Consumers Current Count

- JMS Destination - Consumers Total Count

- JMS Destination Type

- JMS Destination - Messages Current Count

- JMS Destination - Messages Pending Count

- JMS Destination - Messages Received Count

- JMS Destination - Messages Received Current Count

- JMS Destination - Messages Received Current Count Per Second

- JMS Server Metrics

- Bytes Pageable

- Bytes Paged In (per minute)

- Bytes Paged Out (per minute)

- Bytes Pending

- Bytes Received (per minute)

- Bytes Stored

- Destinations

- Messages Paged In (per minute)

- Messages Paged Out (per minute)

- Messages Pending

- Messages Received (per minute)

- Messages Stored

- Session Pools

- JTA Metrics

- Abandoned Transactions (per minute)

- Committed Transactions (%)

- Committed Transactions (per minute)

- Committed Transaction Time (seconds)

- Heuristic Transactions (per minute)

- Transactions Processed (per minute)

- Transaction Rollbacks (per minute)

- Transaction Rollbacks due to Application Error (per minute)

- Transaction Rollbacks due to Resource Error (per minute)

- Transaction Rollbacks due to System Error (per minute)

- Transaction Rollbacks due to Timeout (per minute)

- Active Transactions

- JVM Metrics

- JVM Class Loading

- Classes Currently Loaded

- Classes Loaded (since startup)

- Classes Unloaded (since startup)

- JVM Compilation Metrics

- Compilation Time (since startup) (ms)

- CPU Usage (%)

- Active Daemon Threads

- Heap Usage (MB)

- Heap Usage (%)

- JDK Vendor

- JDK Version

- JVM Garbage Collectors

- Name

- Garbage Collector - Garbage Collection Invocations (since startup)

- Garbage Collector - Garbage Collection Invocations (per min)

- Garbage Collector - Garbage Collection Invocation Time (ms)

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

- JVM Memory Pools

- Memory Pool - Current Usage (KB)

- Memory Pool - Current Usage (MB)

- Memory Pool - Peak Usage (KB)

- JVM Memory Usage

- Heap Memory Usage (KB)

- Non-Heap Memory Usage (KB)

- Objects Pending Finalization

- Nursery Size (MB)

- JVM Runtime Metrics

- VM Name

- VM Version

- JVM ThreadContention

- Blocked Count

- Blocked Time (since startup) (seconds)

- CPU Usage (since startup) (seconds)

- Lock Name

- Thread State

- Wait Count

- Wait Time (since startup) (seconds)

- JVM Threads

- Active Daemon Threads

- Deadlocked Threads

- Peak Threads

- Active Threads

- Threads Started (since startup)

- Response

- Status

- Server Metrics

- Listen Port

- Active Sockets

- Start Time

- State

- Server Datasource Metrics

- Server Datasource - Available Connections

- Server Datasource - Connections Created (per minute)

- Server Datasource - Connections in Use

- Server Datasource - Connection Pool Size

- Server Datasource - Connection Requests (per minute)

- Server Datasource - Successful Connections (%)

- Server Datasource - Connection Requests Waiting

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

- Server Datasource - Connection Wait Successes (%)

- Server Datasource - Connection Wait Successes (per minute)

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

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

- Server Datasource - Cached Statements Used (%)

- Server Datasource - Cached Statements Used (per minute)

- Server Datasource - Statement Cache Size

- Server Work Manager Metrics

- Server Work Manager - Work Manager Pending Requests

- Server Work Manager - Work Manager Requests (per minute)

- Server Work Manager - Work Manager Stuck Threads

- Servlet/JSP Metrics

- Servlet/JSP - Reloads (per minute)

- Servlet/JSP - Requests (per minute)

- Servlet/JSP - Request Processing Time (ms)

- Servlet Rollup

- Servlet - Active Invocations

- Servlet - Current Client Processing Time

- Servlet - Average Execution Time

- Servlet - Total Execution Time

- Servlet - Invocations Per Second

- Servlet - Invocation Total Count

- Web Module Metrics

- Web Module - Requests (per minute)

- Web Module - Request Processing Time (ms)

- Web Module - Active Sessions

- Java JEE Web Service Endpoints

- Dispatch Time Total

- Execution Time Total

- Invocation Count

- Response Count

- Response Error Count

- Response Time Total

- Work Manager Metrics

- Work Manager Pending Requests

- Work Manager Requests (per minute)

- Work Manager Stuck Threads

2 Oracle Access Manager

- OAM Application Clients

- Average Application Authentication Latency (ms)

- Application Authentication Requests per second

- Application Authentication Success Rate (%)

- Average Application Authorization Latency (ms)

- Application Authorization Requests per second

- Application Authorization Success Rate (%)

- OAM 10g Client

- OAM Client Average Authentication Latency (ms)

- OAM Client Authentication Requests per second

- OAM Client Authentication Success Rate (%)

- OAM Client Average Authorization Latency (ms)

- OAM Client Authorization Requests per second

- OAM Client Authorization Success Rate (%)

- Oracle SSO 10g Client

- OSSO Client Average Authentication Latency (ms)

- OSSO Client Authentication Requests per second

- OSSO Client Authentication Success Rate (%)

- Audit Operations

- Average Audit Latency (ms)

- Audit Operations per second

- Server Name

- Authentication

- Average Authentication Latency (ms)

- Authentication Requests per second

- Authentication Success Rate (%)

- Server Name

- Authorization

- Average Authorization Latency (ms)

- Authorization Requests per second

- Authorization Success Rate (%)

- Server Name

- Token Generation Operations

- Tokens Issued

- Token Issuances per second

- Issuance Latency (ms)

- Token Validation Operations

- Number of Tokens Validated

- Token Validations per second

- Token Validation Latency (ms)

- Log Operations

- Average Log Latency (ms)

- Log Operations per second

- Server Name

- Token Service Clients

- Issuance Latency (ms)

- Tokens Issued

- Token Issuances per second

- Issuance Success Rate (%)

- Validation Success Rate (%)

- Token Validation Latency (ms)

- Number of Tokens Validated

- Token Validations per second

- Response

- UpDown Status

- Token Requests

- Issuance Latency (ms)

- Tokens Issued

- Token Issuances per second

- Issuance Success Rate (%)

- Token Validation Latency (ms)

- Number of Tokens Validated

- Token Validations per second

- Validation Success Rate (%)

- LDAP Operations

- LDAP Operations per second

- Average LDAP Operation Latency (ms)

- LDAP Success Rate (%)

- Server Name

3 Oracle Access Manager Cluster

- OAM Applications Domains (Aggregated)

- Application Authentication Latency (ms)

- Application Authentication Requests per second

- Application Authentication Success Rate (%)

- Application Authorization Latency (ms)

- Application Authorization Requests per second

- Application Authorization Success Rate (%)

- OAM 10g Aggregates

- OAM Client Average Authentication Latency (ms)

- OAM Client Authentication Requests per second

- OAM Client Authentication Success Rate (%)

- OAM Client Average Authorization Latency (ms)

- OAM Client Authorization Requests per second

- OAM Client Authorization Success Rate (%)

- OAM 10g Throughput (Aggregated)

- OAM Client Authentications per second

- OAM Client Authorizations per second

- OSSO 10g (Aggregated)

- OSSO Client Average Authentication Latency (ms)

- OSSO Client Authentication Requests per second

- Authentication Success Rate (%)

- OSSO 10g Throughput (Aggregated)

- OSSO Client Operations per second

- Audit Operations (Aggregated)

- Average Audit Latency (ms)

- Audit Operations per second

- Audit Operations Throughput (Aggregated)

- Operations per second

- Authentication Aggregates

- Average Authentication Latency (ms)

- Authentication Requests per second

- Authentication Success Rate (%)

- Authentications Throughput (Aggregated)

- Authentication Requests per second

- Authorizations (Aggregated)

- Average Authorization Latency (ms)

- Authorization Requests per second

- Authorization Success Rate (%)

- Authorizations Throughput (Aggregated)

- Authorization Requests per second

- Core Token Generation Operations

- Number of Tokens Issued

- Tokens Issued per second

- Token Issuance Latency (ms)

- Core Token Validation Operations

- Custom Tokens Validated

- Tokens Validated per second

- Token Validation Latency (ms)

- Log Operations (Aggregated)

- Average Latency (ms)

- Log Operations per second

- Log Operations Throughput (Aggregated)

- Log Operations per second

- Token Service Clients

- Token Issuance Latency (ms)

- Tokens Issued

- Tokens Issued per second

- Token Issuance Success Rate (%)

- Requester

- Token Validation Success Rate (%)

- Token Validation Latency (ms)

- Tokens Validated

- Token Validations per second

- Response

- Status

- Token Issuances

- Token Issuance Latency (ms)

- Tokens Issued

- Tokens Issued per second

- Issuance Success Rate (%)

- Validation Latency (ms)

- Tokens Validated

- Validations per second

- Validation Success Rate (%)

- LDAP Operations (Aggregated)

- LDAP_Operations per second

- Operation Name

- Average Latency (ms)

- LDAP Operations Success Rate (%)

- LDAP Operations Throughput (Aggregated)

- LDAP Operations per second

4 Oracle Adaptive Access Manager

- Datasource Metrics

- Available Connections

- Connections Created (per minute)

- Connections in Use

- Connection Leaks (per minute)

- Connection Pool Size

- Connection Refresh Failures (per minute)

- Connection Request Failures (per minute)

- Connection Requests (per minute)

- Successful Connections (%)

- Unavailable Connections

- Connection Requests Waiting

- Failed Waiting Connection Requests (per minute)

- Connection Requests that Waited (per minute)

- Connection Wait Successes (%)

- Connection Wait Successes (per minute)

- Datasource - State

- Statements Added to Cache (per minute)

- Statements Discarded from Cache (per minute)

- Cached Statements not Used (per minute)

- Cached Statements Used (%)

- Cached Statements Used (per minute)

- Statement Cache Size

- EJB Module Metrics

- Cached Beans

- Bean Activations (per minute)

- Cache Hits (%)

- Cache Misses (per minute)

- Bean Accesses (per minute)

- Bean Access Successes (%)

- Free Bean Instances

- Bean Destroys (per minute)

- Bean Access Failures (per minute)

- Beans in Use

- Bean Transaction Commits (per minute)

- Bean Transaction Rollbacks (per minute)

- Bean Transaction Timeouts (per minute)

- EJB Transaction Metrics

- Bean Transaction Commits (%)

- Bean Transaction Commits (per minute)

- Bean Transaction Rollbacks (per minute)

- Bean Transaction Timeouts (per minute)

- Overview Metrics

- Cached Beans

- Cache Accesses (per minute)

- Bean Activations (per minute)

- Cache Hits (%)

- Cache Misses (per minute)

- Bean Accesses (per minute)

- Bean Successes (%)

- Free Bean Instances

- Bean Destroys (per minute)

- Bean Access Failures (per minute)

- Beans in Use

- Bean Transaction Commits (%)

- Bean Transaction Commits (per minute)

- Bean Transaction Rollbacks (per minute)

- Bean Transaction Timeouts (per minute)

- MDB Messages (per minute)

- Requests (per minute)

- Request Processing Time (ms)

- Active Sessions

- Work Manager Pending Requests

- Work Manager Requests (per minute)

- Servlet/JSP Metrics

- Reloads (per minute)

- Requests (per minute)

- Request Processing Time (ms)

- Web Module Metrics

- Requests (per minute)

- Request Processing Time (ms)

- Active Sessions

- Login Metrics Summary

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

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

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

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

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

- Number of Failed Logins per Sec since the Server Startup

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

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

- Number of Successful Logins per Sec Since the Server Startup

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

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

- Policy Execution Summary

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

- Total Number of Policies Processed

- Total Number of Policies Processed since Last Sample

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

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

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

- Response

- UpDown Status

- Rule Execution Summary

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

- Total Number of Requests Completed

- Total Number of Requests Completed Since Last Sample

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

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

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

- Checkpoint Execution Summary

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

- Total Number of Checkpoints Completed

- Total Number of Checkpoints Completed Since Last Sample

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

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

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

- Update Authorization Status Summary

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

- Total Number of Requests Completed

- Total Number of Requests Completed Since Last Sample

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

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

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

- Update Log Summary

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

- Total Number of Requests Completed

- Total Number of Requests Completed Since Last Sample

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

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

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

5 Oracle Adaptive Access Manager Cluster

- Oracle Adaptive Access Manager Datastore Information

- JDBC URL

- Login Metrics Summary

- Blocked Logins Rate (%)

- Blocked Logins

- Challenged Logins Rate (%)

- Challenged Logins

- Failed Logins Rate (%)

- Failed Logins

- Successful Logins Rate (%)

- Successful Logins

- Total Logins Attempted

- Login Metrics Rate Summary

- Failed Logins per second

- Successful Logins per second

- Response

- Status

6 Oracle Identity Manager

- Oracle Adaptive Metrics

- Adapter Name

- Average Adapter Execution Time (ms)

- Completed Adapter Executions

- Maximum Adapter Execution Time (ms)

- Minimum Adapter Execution Time (ms)

- Datasource Metrics

- Datasource - Available Connections

- Datasource - Connections Created (per minute)

- Datasource - Connections in Use

- Datasource - Connection Leaks (per minute)

- Datasource - Connection Pool Size

- Datasource - Connection Refresh Failures (per minute)

- Datasource - Connection Request Failures (per minute)

- Datasource - Connection Requests (per minute)

- Datasource - Successful Connections (%)

- Datasource - Unavailable Connections

- Datasource - Connection Requests Waiting

- Datasource - Failed Waiting Connection Requests (per minute)

- Datasource - Connection Requests that Waited (per minute)

- Datasource - Connection Wait Successes (%)

- Datasource - Connection Wait Successes (per minute)

- Datasource - State

- Datasource - Statements Added to Cache (per minute)

- Datasource - Statements Discarded from Cache (per minute)

- Datasource - Cached Statements not Used (per minute)

- Datasource - Cached Statements Used (%)

- Datasource - Cached Statements Used (per minute)

- Datasource - Statement Cache Size

- EJB Module Metrics

- Cached Beans

- Bean Activations (per minute)

- Cache Hits (%)

- Cache Misses (per minute)

- Bean Accesses (per minute)

- Bean Access Successes (%)

- Free Bean Instances

- Bean Destroys (per minute)

- Bean Access Failures (per minute)

- Beans in Use

- Bean Transaction Commits (per minute)

- Bean Transaction Rollbacks (per minute)

- Bean Destroys (per minute)

- EJB Transaction Metrics

- Bean Transaction Commits (%)

- Bean Transaction Commits (per minute)

- Bean Transaction Rollbacks (per minute)

- Bean Transaction Timeouts (per minute)

- Overview Metrics

- Cached Beans

- Cache Accesses (per minute)

- Bean Activations (per minute)

- Cache Hits (%)

- Cache Misses (per minute)

- Bean Accesses (per minute)

- Bean Successes (%)

- Free Bean Instances

- Bean Destroys (per minute)

- Bean Access Failures (per minute)

- Beans in Use

- Bean Transaction Commits (%)

- Bean Transaction Commits (per minute)

- Bean Transaction Rollbacks (per minute)

- Bean Transaction Timeouts (per minute)

- MDB Messages (per minute)

- Requests (per minute)

- Request Processing Time (ms)

- Active Sessions

- Work Manager Pending Requests

- Work Manager Requests (per minute)

- Servlet/JSP Metrics

- Reloads (per minute)

- Requests (per minute)

- Request Processing Time (ms)

- Web Module Metrics

- Requests (per minute)

- Request Processing Time (ms)

- Active Sessions

- Events Handler

- Average Events Execution Time (ms)

- Completed Events Executions

- Maximum Events Execution Time (ms)

- Minimum Events Execution Time (ms)

- Java JEE Web Service Endpoints

- Dispatch Time Total

- Execution Time Total

- Invocation Count

- Response Count

- Response Error Count

- Response Time Total

- JMS Queue

- Average Processing Time (ms)

- Number of Processed Messages

- Maximum Processing Time (ms)

- Minimum processing Time (ms)

- MDS Metrics

- Metadata Object Gets Per Second

- Metadata Object Get Processing Time (seconds)

- IOs Per Document Get

- IOs Per MO Content Get

- IOs Per Metadata Object Get

- Metadata Updates Per Second

- Metadata Update Processing Time (seconds)

- Executions and Messages

- Total Adapter Executions

- Total Events Handler Executions

- Total JMS Messages

- SPML Web Services

- Average Response Time (ms)

- Incoming Calls

- Response

- Status

7 Oracle BI Instance

- Oracle BI PS Requests Rate

- Active Sessions

- Bad Requests

- Completed Requests

- Completed Requests/sec

- Current Requests

- Failed Requests

- GET Requests Throughput

- GET Requests

- GET/POST Requests Throughput

- GET/POST Requests

- Long Requests

- Peak Requests

- POST Requests Throughput

- POST Requests

- SOAP Requests Throughput

- SOAP Requests

- Oracle BI PS Aggregation

- Active sessions

- Completed Requests/sec

- Current Requests

- Failed Requests

- GET/POST Throughput

- SOAP Throughput

- Oracle BI Aggregation

- Avg Query Elapsed Time

- Queries/sec

- Total sessions

- Oracle BI Data Cache

- Hit Ratio as %

- Hits/sec

- Qualified queries misses / second

- Unqualified queries misses / second

- Oracle BI DB Connection Pool

- Accumulated Opened Connections

- Accumulated Requests

- Accumulated Stolen Connections

- Average Queued Requests

- Average Queued Time (ms)

- Avg. Opened Connections/sec

- Avg. Request/sec

- Avg. Stolen Connections/sec

- Capacity

- Current Busy Connection Count

- Current Connection Count

- Current Queued Requests

- Current Queued Time (ms)

- Lowest Queued Requests

- Lowest Queued Time (ms)

- Peak Busy Connection Count

- Peak Connection Count

- Peak Queued Requests

- Peak Queued Time (ms)

- Producer ID of the Oldest Queued Request

- Request ID of the Oldest Queued Request

- Oracle BI General

- Active Execute Requests

- Active Fetch Requests

- Active File Handles

- Active Initblock Executions

- Active Logins

- Active Prepare Requests

- Avg. Failed Logins Elapsed Time

- Avg. Initblock Executions Elapsed Time

- Avg. query elapsed time

- Avg. Succeeded Logins Elapsed Time

- Busy File Handles

- File Handle Waiters

- Free File Handles

- Max. Initblock Execution Elapsed Time

- Max File Handles

- New Execute Requests

- New Fetch Requests

- New Initblock Executions

- New Logins

- New Prepare Requests

- New Requests

- Queries/sec

- Succeeded Initblock Execution Ratio as %

- Succeeded Logins Ratio as %

- Total sessions

- Oracle BI Generic Cache

- Average hits / second

- Average misses / second

- Average new entries / second

- Average replacements / second

- Average requests / second

- Capacity

- Total requests

- Utilization ratio as %

- Oracle BI LDAP Authentication

- Active LDAP Requests

- Avg. Failed LDAP Requests Elapsed Time

- Avg. Succeeded LDAP Requests Elapsed Time

- LDAP Requests Cache Hit Ratio as %

- New Impersonated LDAP Requests

- New LDAP Requests

- Succeeded LDAP Requests Ratio as %

- Oracle BI Physical DB

- Active Executes

- Active Fetches

- Active Prepares

- Avg. query request response time

- Failed Queries/sec

- KiloBytes/sec

- New Executes

- New Fetches

- New Prepares

- Queries/sec

- Rows/sec

- Oracle BI PS Caches

- Cache Hits

- Cache Misses

- Cache Stale

- Cleanups

- Current Entries

- Peak Entries

- Oracle BI PS Catalog Access

- Attribute Retrievals

- Create Folders

- Create Links

- Delete Items

- Read Objects

- Searches

- Write Objects

- Write Objects Successfully

- Oracle BI PS Catalog Attribute Cache

- Cache Hits

- Cache Misses

- Cache Stale Misses

- Current Cache Entries

- Peak Cache Entries

- Oracle BI PS Chart Engine

- Cache Hits

- Charts Submitted/sec

- Current Cached Charts

- Current Charts Queued

- Current Running Charts

- Peak Cached Charts

- Peak Charts Queued

- Peak Running Charts

- Total Charts Rejected

- Total Charts Submitted

- Oracle BI PS Connection Pool

- Current Authentications

- Current Open Connections

- New Connections/sec

- Peak Authentications

- Peak Open Connections

- Total Connections

- Total Failed

- Total Rejected

- Oracle BI PS DirectorySearches

- Total Search Start Requests

- Total Search Stop Requests

- Total Searches Started

- Total Searches Stopped

- Oracle BI PS DXE

- Total Actual Aggregate Queries Compiled

- Total Actual Cube Queries Compiled

- Total Actual Expression Queries Compiled

- Total Actual Presort Cube Queries Compiled

- Total Actual Presort Table Queries Compiled

- Total Actual Regular Queries Compiled

- Total Actual Union Queries Compiled

- Total Input Aggregate Query Requests

- Total Input Cube Query Requests

- Total Input Regular Query Requests

- Total Input Union Query Requests

- Total Order By Requests

- Total Order By Requests Optimized Away

- Total Query Requests

- Oracle BI PS File Accesses

- Current Open Files

- Peak Open File

- Total Files

- Total Files/sec

- Oracle BI PS HTTP Socket Pool

- Total Closed At Reuse

- Total Closed Exception

- Total Closed First Read

- Total Closed HTTP

- Total Closed Outstanding

- Total Closed Timedout

- Total Closed Unknown

- Total Endpoints

- Total New sockets

- Total Reused

- Oracle BI PS JavaHost Proxy Requests

- Requests to Generate Briefing Books

- Requests to Generate PDFs

- Requests to Generate Powerpoints

- Oracle BI PS Metadata

- Current Subject Areas

- Peak Subject Areas

- Subject Area Loads/sec

- Total Subject Area Loads

- Oracle BI PS Query Cache

- Cache Clean Ups/sec

- Cache Hits/sec

- Canceled Queries/sec

- Current Cache Entries

- Current Query Preps

- Current Query Preps Cache Size

- Current Queued Immediate Queries

- Current Queued Queries

- Current Running Immediate Queries

- Current Running Queries

- Errored Queries/sec

- New Queries/sec

- Peak Cache Entries

- Peak Query Preps

- Peak Query Preps Cache Size

- Peak Queued Immediate Queries

- Peak Queued Queries

- Peak Running Immediate Queries

- Peak Running Queries

- Proactive Cache Clean Ups/sec

- Query Piggybacks/sec

- Query Preps Errors/sec

- Query Preps/sec

- Successful Queries/sec

- Total Cache Clean Ups

- Total Cache Hits

- Total Canceled Queries

- Total Errored Queries

- Total Proactive Cache Clean Ups

- Total Query Attempts

- Total Query Piggybacks

- Total Query Prep Cache Hits

- Total Query Prep Cache Misses

- Total Query Preps

- Total Query Preps Errors

- Total Successful Queries

- Oracle BI PS Request Processor

- Bad Requests

- Completed Requests

- Completed Requests/sec

- Current Requests

- Failed Requests

- GET Requests

- Long Requests

- Peak Requests

- POST Requests

- SOAP Requests

- Oracle BI PS Sessions

- Active Sessions

- Current Embryonic Sessions

- Current Sessions

- Failed Logins/sec

- New Logins/sec

- New Sessions/sec

- Peak Active Sessions

- Peak Embryonic Sessions

- Peak Logged In

- Peak Sessions

- Sessions Logged In

- Total Failed Logins

- Total Lifetime Sessions

- Total Logins

- Oracle BI PS Sockets

- Total Close Requests

- Total Closed

- Total Open Requests

- Total Opened

- Oracle BI PS Thread Pools

- Current Jobs Queued

- Current Jobs Running

- Current Threads

- Peak Jobs Queued

- Peak Jobs Running

- Peak Threads

- Total Jobs Completed

- Total Jobs Submitted

- Total Jobs Unfinished

- Oracle BI PS Threads

- Total Close Requests

- Total Closed

- Total Created

- Total Open Requests

- Oracle BI PS User Population Searches

- UserPopulationAPI.SearchByGUID

- UserPopulationAPI.SearchByName

- UserPopulationAPI.SearchByPattern

- Oracle BI PS XML Document Caches

- Current Disk Entries

- Current Disk Usage (KB)

- Current Memory Entries

- Disk Added (KB)

- Disk Cache Hits

- Disk Cache Misses

- Disk Deleted (KB)

- Invalid Requests

- Memory Cache Hits

- Peak Memory Entries

- Total Memory Entries

- Oracle BI PS XML Validator

- Current Validations

- Current Validators in Pool

- Peak Validations

- Peak Validators in Pool

- Total Validations

- Validations/sec

- Oracle BI Thread Pool

- Accumulated Requests

- Average Execution Time (ms)

- Average Queued Requests

- Average Queued Time (ms)

- Avg. Request/sec

- Capacity

- Current Busy Thread Count

- Current Execution Time (ms)

- Current Queued Requests

- Current Queued Time (ms)

- Current Thread Count

- Lowest Execution Time (ms)

- Lowest Queued Requests

- Lowest Queued Time (ms)

- Maximum Stack Size (bytes)

- Peak Busy Thread Count

- Peak Execution Time (ms)

- Peak Queued Requests

- Peak Queued Time (ms)

- Peak Thread Count

- Weblogic BI Metrics By Server

- Weblogic BI Action Framework Metrics

- Requests (per minute)

- Request Processing Time (ms)

- Weblogic BI Analytics Metrics

- Requests (per minute)

- Request Processing Time (ms)

- Active Sessions

- Weblogic BI SOA Metrics

- Requests (per minute)

- Request Processing Time (ms)

- Weblogic Server Metrics

- CPU Usage Percentage

- Heap Used (MB)

- Requests (per minute)

- Request Processing Time (ms)

- Active Sessions

8 Oracle Essbase Server Metrics

- Server Information

- Connected Users

- Running Apps

- Unaccessed Apps

- Response (ms)

- Resource Usage

- CPU Usage (%)

- Memory Usage (MB)

- Memory Usage (%)

- Response

- Response - Status

9 Oracle Essbase Applications

- Application Information

- Response (ms)

- Memory Usage (MB)

- Threads

- Response

- Response - Status

10 Oracle Coherence Metrics

- Cache Performance - Aggregated Over Nodes

- Service

- Cache Hits Rate

- Cache Misses Rate

- Number of Loads Rate

- Number of Stores-Erases Rate

- Number of Gets Rate

- Number of Puts Rate

- Total Time for Gets-Hit (ms) Rate

- Total Time for Gets-Miss (ms) Rate

- Time For Loads Rate (ms)

- Time For Stores-Erases Rate (ms)

- Time For Puts Rate (ms)

- Time For Gets Rate (ms)

- Number Of Objects In Cache(underutilized threshold)

- Number Of Objects In Cache(overutilized threshold)

- Case Size Measured In Units

- Cache Hits

- Cache Misses

- Total Number Of Puts

- Total Number Of Gets

- Total Number Of Loads

- Total Number Of Stores-Erases

- Cache Hits to Gets Ratio

- Average Time For Gets (ms)

- Average Time For Gets-Hit(ms)

- Average Time For Gets-Miss(ms)

- Average Time For Put Invokation(ms)

- Average Time Spent For Write Operation (ms)

- Average Time Spent For Read Operation (ms)

- Cache Configuration

- Name

- Node ID

- Service

- Tier

- Loader

- Batch Factor

- Description

- The Time-To-live For Cache Entries

- Time Between Cache Flushes (ms)

- Cache Size High Limit (in Units)

- Cache Size Low Limit (in Units)

- Persistence Type

- Queue Delay (secs)

- Refresh Factor

- Refresh Time

- Requeue Threshold

- Cache Performance

- Average Time For Gets (ms) -Per Node

- Average Time For Gets-Hit(ms) -Per Node

- Average Time For Gets-Miss(ms) -Per Node

- Average Time For Put Invokation(ms) -Per Node

- Cache Hits -Per Node

- Cache Hits Rate -Per Node

- Total Time for Gets-Hit (ms) -Per Node

- Total Time for Gets-Hit (ms) Rate -Per Node

- Cache Misses -Per Node

- Cache Misses Rate -Per Node

- Total Time for Gets-Miss (ms) -Per Node

- Total Time for Gets-Miss (ms) Rate -Per Node

- Hit Probability -Per Node

- The No. Of Entries In The Cache -Per Node

- The size of the write-behind queue -Per Node

- Average No. Of Entries Per CacheStore Write Operation -Per Node

- Average Time Spent For Read Operation (ms) -Per Node

- Average Time Spent For Write Operation (ms) -Per Node

- Total No. Of Cache Store Failures -Per Node

- CacheStore Failures Rate -Per Node

- Total Time For Loads (ms) -Per Node

- Time For Loads Rate (ms) -Per Node

- Total No. Of Loads -Per Node

- No. Of Loads Rate -Per Node

- Total Time For Store and Erase Operation (ms) -Per Node

- Time For Stores-Erases Rate (ms) -Per Node

- Total No. Of Stores-Erases -Per Node

- Stores-Erases Rate -Per Node

- Total No. Of Gets -Per Node

- Gets Rate -Per Node

- Total Time For Gets (ms) -Per Node

- Time For Gets Rate (ms) -Per Node

- Total No. Of Puts -Per Node

- Puts Rate -Per Node

- Total Time For Puts (ms) -Per Node

- Time For Puts Rate (ms) -Per Node

- Case Size Measured In Units -Per Node

- Cluster

- Cluster Name

- Cluster Nodes

- License Mode

- Local Member Id

- Member IDs

- Members

- Oldest Member ID

- Running

- Cluster Aggregated

- Cluster Name

- Cluster Nodes

- Publisher Success Rate - Cluster

- Receiver Success Rate - Cluster

- Memory Usage (MB)

- No. of Caches

- Change in No. of Caches Since Last Collection

- Change in No. of Nodes Since Last Collection

- Cluster Alerts

- Cluster Name

- Cluster Nodes

- Change in No. of Nodes Since Last Collection

- Change in Number of Nodes

- Connection

- Name

- Node ID

- UUID

- Connection Time (ms)

- Outgoing Queue Backlog (bytes)

- Outgoing Message Queue Backlog

- Refresh Time

- Remote Address

- Remote Port

- Timestamp

- Total Bytes Received - Connection

- Bytes Received Since Last Collection- Connection

- Total Bytes Sent - Connection

- Bytes Sent Since Last Collection - Connection

- Total Messages Received - Connection

- Message Received Since Last Collection - Connection

- Total Messages Sent - Connection

- Message Sent Since Last Collection - Connection

- Connection Manager

- Name

- Node ID

- Connection Count

- Host IP

- Incoming Buffer Pool Capacity

- Incoming Buffer Pool Size

- Outgoing Buffer Pool Capacity

- Outgoing Buffer Pool Size

- Outgoing Queue Backlog (bytes)

- Outgoing Message Queue Backlog

- RefreshTime

- Total Bytes Received - Connection Manager

- Bytes Received Since Last Collection - Connection Manager

- Total Bytes Sent - Connection Manager

- Bytes Sent Since Last Collection - Connection Manager

- Total Messages Received - Connection Manager

- Message Received Since Last Collection - Connection Manager

- Total Messages Sent - Connection Manager

- Message Sent Since Last Collection - Connection Manager

- Garbage Collector after GC

- Name

- Node ID

- GC Thread Count

- Start Time (ms)

- End Time (ms)

- Key of Memory Usage after GC

- Committed of Memory Usage after GC

- Init of Memory Usage after GC

- Max of Memory Usage after GC

- Used of Memory Usage after GC

- Garbage Collector Before GC

- Name

- Node ID

- GC Thread Count

- Start Time (ms)

- End Time (ms)

- Key of Memory Usage Before GC

- Committed of Memory Usage Before GC

- Init of Memory Usage Before GC

- Max of Memory Usage Before GC

- Used of Memory Usage Before GC

- Garbage Collector Collection

- Name

- Node ID

- Collection Count

- Garbage Collection Rate

- Collection Time

- HTTP Session

- Application ID

- Node ID

- Collection Class Name

- Factory Class Name

- Local Attribute Cache Name

- Number of Local Attributes in Local Attribute Cache

- Local Session Cache Name

- Number of Local Sessions in Local Session Cache

- Overflow Average Size

- Overflow Cache Name

- Overflow Max Size

- Overflow Threshold

- Updates to Attributes Stored in Overflow Cache

- Updates to Attributes Stored in Overflow Cache Per Min -Per Min

- Servlet Context Cache Name

- Servlet Context Name

- Session Average Lifetime

- Session Cache Name

- Session ID Length

- Session Object Maximum Size (bytes)

- Number of Http Session Objects

- Session Timeout

- Updates to Object Store in Session Cache -Per Node

- Updates to Object Store in Session Cache Per Min -Per Node

- HTTP Session - Aggregated Over Nodes

- Application ID

- No. of Attributes in Local Attribute Cache

- No. of Sessions in Local Session Cache

- Updates to Attributes Stored in Overflow Cache

- Updates to Attributes Stored in Overflow Cache Per Min

- Updates to Object Store in Session Cache

- Updates to Object Store in Session Cache Per Min

- Memory Performance

- Node ID

- Heap Memory Committed for JVM to use (bytes)

- Heap Memory that JVM initially Requests from OS (bytes)

- Maximum Heap Memory That Can Be Used (bytes)

- Heap Memory Used (bytes)

- Non Heap Memory Committed for JVM to use (bytes)

- Non Heap Memory that JVM initially Requests from OS (bytes)

- Non Heap Memory Used (bytes)

- Object Pending Finalization Count

- Verbose

- Node Performance - Aggregate Over Caches

- Node ID

- Total Number Of Gets

- Number of Gets Rate

- Total Number of Puts

- Number of Puts Rate

- Node Configuration

- Buffer Publish Size

- Buffer Receive Size

- Burst Count

- Burst Delay

- Flow Control Enabled

- ID

- Logging Format

- Logging Level

- Logging Limit

- Machine Id

- Machine Name

- Member Name

- Memory Max (MB)

- Multicast Address

- Multicast Enabled

- Multicast Port

- Multicast Threshold

- Multicast TTL

- Nack Enabled

- Process Name

- Product Edition

- Rack Name

- RefreshTime

- Resend Delay

- Role Name

- Site Name

- Timestamp

- Traffic Jam Count

- Traffic Jam Delay

- Unicast Address

- Unicast Port

- Node Performance

- Cpu Count

- Machine Id

- Machine Name

- Member Name

- Memory Available (MB)

- Packet Delivery Efficiency

- Packets Bundled

- Packets Bundled Rate

- Packets Received

- Packets Received Rate

- Packets Repeated

- Packets Repeated Rate

- Packets Resent

- Packets Resent Rate

- Packets Resent Early

- Packets Resent Early Rate

- Packets Resent Excess

- Packets Resent Excess Rate

- Packets Sent

- Packets Sent Rate

- Process Name

- Publisher Success Rate

- Publisher Success Rate - Per Node

- Rack Name

- Receiver Success Rate

- Receiver Success Rate Delta

- Refresh Time

- Role Name

- Send Queue Size

- Site Name

- Tcp Ring Failures

- Tcp Ring Failures Rate

- Tcp Ring Timeouts

- Tcp Ring TimeOuts Rate

- Timestamp

- Weakest Channel

- Operating System

- Node ID

- Architecture

- Available Processors

- Committed Virtual Memory Size (bytes)

- Free Physical Memory Size (bytes)

- Free Swap Space Size (bytes)

- Max File Descriptor Count

- Name

- Open File Descriptor Count

- Process Cpu Time

- Total Physical Memory Size (bytes)

- Total Swap Space Size (bytes)

- Version

- Resource Usage

- Memory Usage (MB)

- Response

- Status

- Runtime

- Row ID

- Node ID

- Input Arguments

- VM Name

- VM Vendor

- VM Version

- Service Configuration

- Total No. Of Partitions For Cache

- Default Timeout Value For Requests (ms)

- Running

- Statistics

- High Availability Status

- Is Storage Enabled

- Execution Time Before Task is Considered Hung (ms)

- Default Timeout Value For Tasks (ms)

- No. Of Threads

- Service Type

- Service Performance

- No. Of Backups For Cache Storage - Per Node

- Owned Partitions Backup - Per Node

- Owned Partitions Primary - Per Node

- Partitions Endangered - Per Node

- Partitions Unbalanced - Per Node

- Partitions Vulnerable - Per Node

- Refresh Time

- Synchronous Request Average Duration (ms) - Per Node

- Synchronous Request Max Duration (ms) - Per Node

- The No. Of Pending Synchronous Request - Per Node

- Duration of Oldest Pending Synchronous Request (ms) - Per Node

- Total No. Of Timed-Out Requests - Per Node

- No. Of Timed-Out Requests Since Last Collection - Per Node

- Total No. Of Requests - Per Node

- No. Of Requests Since Last Collection - Per Node

- High Availability Status

- No. Of Storage Nodes Running The Service - Per Node

- Average Duration Of Individual Task Execution(ms) - Per Node

- No. Of Task Waiting For Execution - Per Node

- Total No. Of Executed Tasks - Per Node

- No. Of Executed Tasks Since Last Collection - Per Node

- No. Of Executing Hung Tasks - Per Node

- Duration of Longest Running Hung Task (ms) - Per Node

- Longest Currently Hung Task ID - Per Node

- Maximum Size Of Backlog Queue Since statistics Reset -Per Node

- Total No. Of Timed-Out Tasks - Per Node

- No. Of Timed Out Tasks Since Last Collection - Per Node

- Total No. Of Abandoned Threads - Per Node

- No. Of Abandoned Threads Since Last Collection - Per Node

- Average No. Of Active Threads - Per Node

- No. Of Threads

- No. Of Idle Threads

- Service Performance - Aggregated Over Nodes

- No. Of Backups For Cache Storage

- Owned Partitions Backup

- Owned Partitions Primary

- Partitions Endangered

- Partitions Unbalanced

- Partitions Vulnerable

- Synchronous Request Average Duration (ms)

- Synchronous Request Max Duration (ms)

- The No. Of Pending Synchronous Request

- Duration of Oldest Pending Synchronous Request (ms)

- Total No. Of Timed-Out Requests

- Request Timeout Count Rate

- Request Total Count

- Request Total Count Rate

- Storage Enabled Count

- Task Average Duration

- Task Backlog

- Task Count

- Task Count Rate

- Task Hung Count

- Task Hung Duration

- Task Max Backlog

- Task Timeout Count

- Task Timeout Count Rate

- Thread Abandoned Count

- Thread Abandoned Count Rate

- Thread Average Active Count

- Thread Count

- Thread Idle Count

- Storage Manager

- Events Dispatched - Per Node

- Eviction Count - Per Node

- Insert Count - Per Node

- Listener Filter Count - Per Node

- Listener Key Count - Per Node

- Listener Registrations - Per Node

- Locks Granted - Per Node

- Locks Pending - Per Node

- Remove Count - Per Node

- Store Manager - Aggregated Over Nodes

- Events Dispatched

- Eviction Count

- Insert Count

- Listener Filter Counts

- Listener Key Count

- Listener Registrations

- Locks Granted

- Locks Pending

- Remove Counts

- Threading

- Node ID

- Thread Count

- Peak Thread Count

11 HTTP Server

- OHS Process Metrics

- Heap Usage (MB)

- Oracle HTTP Server General Metrics

- Start Time (ms since Epoch)

- OHS Module Metrics

- Active Requests for a Module

- Request Handling Time, for a Module (seconds)

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

- OHS Response Code Metrics

- HTTP 4xx errors

- HTTP 5xx errors

- OHS Server Metrics

- Busy Processes

- Percentage of Busy Processes

- Active HTTP Connections

- Connection Duration (seconds)

- Error Rate (%)

- Idle Processes

- Active HTTP Requests

- Request Processing Time (seconds)

- Request Processing Time (milliseconds)

- Request Throughput (requests per second)

- Response Data Processed (KB per response)

- Response Data Throughput (KB per second)

- OHS Virtual Host Metrics

- Active Requests for a Virtual Host

- Request Processing Time for a Virtual Host (seconds)

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

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

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

- Virtual Host Type

- Resource Usage

- CPU Usage (%)

- CPU Idle Time (%)

- Other CPU Usage (%)

- Memory Usage (MB)

- Free Memory (MB)

- Other Memory Usage (MB)

- Total Memory (MB)

- Memory Usage (%)

- Free Memory (%)

- Other Memory Usage (%)

- Start Time (ms since Epoch)

- Up Time (ms since Epoch)

- Response

- Response - Status

12 Java EE Application

- ADFC Taskflow Metrics

- Total Active Taskflows

- Active Taskflows

- Active throughput

- Active Taskflows

- Total Entered Taskflows

- Entered Taskflows

- Invoke Taskflows

- Invoked Taskflows completed

- Taskflow Invoke time

- Average Time

- Maximum Time

- Minimum Time

- Module Removals

- Pool Checkouts

- Average Creation time(ms)

- Free Instances

- Maximum Creation Time (ms)

- Request Count

- Available Instances in last 5 Minutes

- Available Instances in last 1 min

- Unavailable Instances in last 5 Minutes

- Unavailable Instances in last 1 Minute

- Activations

- Pool check Ins

- Pool Check Outs

- Pool Check Out Failures

- Referenced Modules Reused

- Unreferenced Modules Recycled

- Datasource Metrics

- Datasource - Available Connections

- Datasource - Connections Created (per minute)

- Datasource - Connections in Use

- Datasource - Connection Leaks (per minute)

- Datasource - Connection Pool Size

- Datasource - Connection Refresh Failures (per minute)

- Datasource - Connection Request Failures (per minute)

- Datasource - Connection Requests (per minute)

- Datasource - Successful Connections (%)

- Datasource - Unavailable Connections

- Datasource - Connection Requests Waiting

- Datasource - Failed Waiting Connection Requests (per minute)

- Datasource - Connection Requests that Waited (per minute)

- Datasource - Connection Wait Successes (%)

- Datasource - Connection Wait Successes (per minute)

- Datasource - State

- Datasource - Statements Added to Cache (per minute)

- Datasource - Statements Discarded from Cache (per minute)

- Datasource - Cached Statements not Used (per minute)

- Datasource - Cached Statements Used (%)

- Datasource - Cached Statements Used (per minute)

- Datasource - Statement Cache Size

- EJB Module Metrics

- EJB Module - Cached Beans

- EJB Module - Bean Activations (per minute)

- EJB Module - Cache Hits (%)

- EJB Module - Cache Misses (per minute)

- EJB Module - Bean Accesses (per minute)

- EJB Module - Bean Access Successes (%)

- EJB Module - Free Bean Instances

- EJB Module - Bean Destroys (per minute)

- EJB Module - Bean Access Failures (per minute)

- EJB Module - Beans In Use

- EJB Module - Bean Transaction Commits (per minute)

- EJB Module - Bean Transaction Rollbacks (per minute)

- EJB Module - Bean Transaction Timeouts (per minute)

- EJB Transaction Metrics

- EJB Transaction - Bean Transaction Commits (%)

- EJB Transaction - Bean Transaction Commits (per minute)

- EJB Transaction - Bean Transaction Rollbacks (per minute)

- EJB Transaction - Bean Transaction Timeouts (per minute)

- Overview Metrics

- Cached Beans

- Cache Accesses (per minute)

- Bean Activations (per minute)

- Cache Hits (%)

- Cache Misses (per minute)

- Bean Accesses (per minute)

- Bean Successes (%)

- Free Bean Instances

- Bean Destroys (per minute)

- Bean Access Failures (per minute)

- Beans In Use

- Bean Transaction Commits (%)

- Bean Transaction Commits (per minute)

- Bean Transaction Rollbacks (per minute)

- Bean Transaction Timeouts (per minute)

- MDB Messages (per minute)

- Requests (per minute)

- Request Processing Time (ms)

- Active Sessions

- Work Manager Pending Requests

- Work Manager Requests (per minute)

- Servlet/JSP Metrics

- Servlet/JSP - Reloads (per minute)

- Servlet/JSP - Requests (per minute)

- Servlet/JSP - Request Processing Time (ms)

- Status Metrics

- Server Name

- State

- Web Module Metrics

- Web Module - Requests (per minute)

- Web Module - Request Processing Time (ms)

- Web Module - Active Sessions

- MDS Metrics

- Metadata Object Gets Per Second

- Metadata Object Get Processing Time (seconds)

- IOs Per Document Get

- IOs Per MO Content Get

- IOs Per Metadata Object Get

- Metadata Updates Per Second

- Metadata Update Processing Time (seconds)

- Response

- UpDown Status

13 Oracle Service Bus

- Oracle Service Bus

- Flow Component Resource Details Metrics

- Average Response Time (Flow Component)

- Open Instance Count (FLOW_COMPONENT)

- Error Instance Count (Flow Component)

- End Point URI Resource Details Metrics

- Average Response Time (End Point URI)

- Open Instance Count (End Point URI)

- Error Instance Count (End Point URI)

- End Point Operation Resource Details Metrics

- Average Response Time (End Point Operation)

- Open Instance Count (End Point Operation)

- Error Instance Count (End Point Operation)

- OSB Service Details Metrics

- Contains Sensitive Details

- Created User

- Created Time

- End Point URI

- Last Modified User

- Last Modified Time

- Protocol

- Status

- Version

- OSB Service Metrics

- Average Response Time

- Total Average Response Time

- Open Instance Count

- Total Open Instance Count

- Error Instance Count

- Total Error Instance Count

- Failure Rate

- Maximum Response Time

- Minimum Response Time

- Service Name

- Path

- Project Name

- Service Type

- WebService Security Violation Instance Count

- Total WebService Security Violation Instance Count

- OSB Proxy Service Metrics

- Average Response Time

- Total Average Response Time

- Open Instance Count

- Total Open Instance Count

- Error Instance Count

- Total Error Instance Count

- Failure Rate

- Maximum Response Time

- Minimum Response Time

- Service Name

- Path

- Project Name

- Service Type

- WebService Security Violation Instance Count

- Total WebService Security Violation Instance Count

- OSB Service Dependency Metrics

- Dependent Service ID

- Response

- Status

- SLA Alert Metrics

- Service Name

- Project Name

- SLA Severity Critical Alerts

- Total SLA Severity Critical Alerts

- SLA Severity Fatal Alerts

- Total SLA Severity Fatal Alerts

- SLA Severity Major Alerts

- Total SLA Severity Major Alerts

- SLA Severity Minor Alerts

- Total SLA Severity Minor Alerts

- SLA Severity Warning Alerts

- Total SLA Severity Warning Alerts

- Service Type

14 Oracle SOA Infra

- B2B Active Entities Metrics

- Number of Active Agreements

- Number of Active Documents

- Number of Active Trading Partners

- B2B Document Metrics Table

- Number of Inbound Messages

- Number of inbound message faults

- Inbound Message Size (KB)

- Inbound Messages processing time

- B2B Document Name

- Number of Outbound Messages

- Number of outbound message faults

- Outbound Message Size (KB)

- Outbound Messages processing time

- B2B Inbound Endpoint Metrics

- B2B Inbound Endpoint Status

- B2B Outbound Endpoint Metrics

- B2B Outbound Endpoint Status

- B2B Trading Partner Metrics

- Number of inbound messages

- Number of inbound message faults

- Inbound Message Size (KB)

- Processing time of Inbound Messages

- Trading partner name

- Number of outbound messages

- Number of outbound message faults

- Outbound Message Size (KB)

- Processing time of outbound messages

- BPEL Engine Requests Rate Metric Table

- Active request throughput in the last 5 minutes

- Last active request value

- Scheduled request throughput in the last 5 minutes

- Last scheduled request value

- Business Rules Engine Cache Metrics Table

- Total Access Count since server startup

- Last value of access count

- Total Count since server startup

- Last value of total count

- Business Rule Engine Request Breakdown Rate Metric Table

- Request count since server startup

- Throughput of requests in the last 5 minutes

- Last value of request

- Average request processing time

- Number of completed requests

- Response

- UpDown Status

- SOA Infrastructure Bindings Rate Metric Table

- Active request throughput in the last 5 minutes

- Number of faults since server startup

- Average request processing time

- Total number of processed requests since server startup

- SOA Composite Bindings/References Rate Metric

- Total number of faults since server start

- Throughput of faults in the last 5 minutes

- Average Incoming Messages Processing Time

- Total completed incoming messages since server start

- Incoming messages throughput in the last 5 minutes

- Total Incoming Messages Processing Time

- Total Incoming Message processing time

- Total number of incoming messages since server start

- Incoming message throughput in the last 5 minutes

- Average Outbound Messages Processing Time

- Total completed outgoing messages since server start

- Outbound messages throughput in the last 5 minutes

- Total Outbound Messages Processing Time since server start

- Total Outbound Message processing time

- Total number of outgoing messages since server start

- Outbound message events throughput in the last 5 minutes

- BPEL Dispatcher Rate Metric Table

- Total number of messages processed per thread since server startup

- Throughput of total messages in the last 5 minutes

- Last value of total message

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

- Last value of average thread allocation time

- Throughput of average thread lifetime in the last 5 minutes

- Last value of average thread lifetime

- Throughput of maximum threads in the last 5 minutes

- Last value of maximum thread

- Throughput of minimum threads in the last 5 minutes

- Last value of minimum thread

- Number of active threads since server startup

- Throughput of thread count in the last 5 minutes

- Last value of thread count

- Number of thread highs since server startup

- Throughput of thread high in the last 5 minutes

- Last value of thread high

- Number of pending threads since server startup

- Throughput of pending threads in the last 5 minutes

- Last value of pending thread

- Total number of threads since server startup

- Throughput of total threads in the last 5 minutes

- Last value of total thread metric

- BPMN Dispatcher Rate Metric Table

- Last value of maximum thread

- Number of active threads since server startup

- Throughput of thread count in the last 5 minutes

- SOA Mediator Engine Cache

- Last value of metadata cache

- Last value of transformation cache

- SOA Mediator Engine Requests

- Callback Requests

- Delay Requests

- Dequeue Requests

- Timeout Requests

- SOA Mediator Engine Request Breakdown Rate Metric Table

- enqueue-phase.active

- Avg Enqueue Time (ms)

- Enqueued

- Throughput of Enqueue phase

- Total Enqueue Time (ms)

- invoke-phase.active

- Avg Invoke Time (ms)

- Invoked

- Throughput of Invoke phase

- Total Invoke Time (ms)

- invokeOneway-phase.active

- Avg Oneway Invoke Processing Time (ms)

- Oneway Invocations

- Throughput of Oneway Invocations

- Total Oneway Invocation Time (ms)

- publish-phase.active

- Avg Publication Time (ms)

- Publications

- Throughput of Publication phase

- Total Publication Time (ms)

- transformation-phase.active

- Avg Transformation Time (ms)

- Transformations

- Throughput of Transformations

- Total Transformation Time (ms)

- SOA Infra Mesh

- Number of active messages in the mesh

- Total number of messages in the mesh since server startup

- Number of faulted messages in the mesh

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

- SOA Infra Mesh Message Count Table

- Total number of messages in the mesh since server startup

- Mesh Name

- Throughput of faulted asynchronous messages in the last 5 minutes

- Number of active asynchronous messages

- Average processing time of asynchronous messages

- Number of completed asynchronous messages

- Throughput of asynchronous messages in the last 5 minutes

- Total processing time of asynchronous messages

- Throughput of faulted synchronous messages in the last 5 minutes

- Number of active synchronous messages

- Average processing time of synchronous messages

- Number of completed synchronous messages

- Throughput of synchronous messages in the last 5 minutes

- Total processing time of synchronous messages

- SOA Message Processing Rate Metric Table

- Total number of active requests since server startup

- Throughput of the active requests in the last 5 minutes

- Last value of active request

- BPEL Service Engine

- Total number of BPEL messages since startup

- Engine Name

- Decision Service Engine

- Total number of decision service messages since startup

- Engine Name

- Number of faults since server startup

- Throughput of faulted requests in the last 5 minutes

- Rate of processing faulted requests

- Mediator Service Engine

- Total number of mediator messages since startup

- Engine Name

- Total number of messages since server startup

- Total number of asynchronous requests since server startup

- Throughput of asynchronous invocations in the last 5 minutes

- Rate of processing asynchronous invocations

- Average asynchronous message processing time since server startup

- Total number of synchronous requests since server startup

- Synchronous invocations throughput in the last 5 minutes

- Rate of processing synchronous invocations

- Average synchronous message processing time since server startup

- Workflow Service Engine

- Total number of workflow messages since startup

- Engine Name

- Total Composite Instances

- Total number of instances since server startup

- Domain Name

- Total Composite Faults

- Total number of faults since server startup

- Workflow Request Breakdown Rate Metrics

- Number of invocations since server startup

- Service Name

- Number of active requests

- Average request processing time

- Number of completed requests

15 SOA Composite

- SOA Composite B2B Inbound Metrics

- InBound Message Count

- Inbound Messages Faults

- Inbound Messages Size

- Inbound Message Processing Time

- ServerName

- Total Outbound Messages Count

- SOA Composite B2B Outbound Metrics

- Name

- OutBound Message Count

- Outbound Messages Faults

- Outbound Messages Size

- Outbound Message Processing Time

- ServerName

- Total Outbound Messages Count

- BPEL Activity Time Distribution

- Average Execution Time (ms)

- Activity Count

- Activity Name

- Server Name

- SOA Composite - Response Metrics

- Status

- SOA Composite Bindings/References Rate Metric

- Total number of faults since server start

- Average Incoming Messages Processing Time

- Total number of incoming messages since server start

- Incoming message throughput in last 5 minutes

- Average Outbound Messages Processing Time

- Total number of outgoing messages since server start

- Outbound message throughput in last 5 minutes

- SOA Component References

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

- Number of Faults

- Number of Messages

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

- Reference Name

- Component References

- Component Type

- SOA Component Rollup Metric

- Business faults throughput in the last 5 minutes

- Number of active faulted instances

- Average processing time for faulted instances

- Number of faulted instances

- Throughput of faulted instances in the last 5 minutes

- Total time spent on processing faulted instances

- Total average faulted processing time

- Instance throughput in the last 5 minutes

- Server Name

- Number of active successful instances

- Average processing time for successful instances

- Number of successful instances

- Throughput of successful instances in the last 5 minutes

- Total time spent on processing successful instances

- Total average successful processing time

- System faults throughput in the last 5 minutes

- Total faults throughput in the last 5 minutes

- SOA Composite - Rate Metrics

- Instance throughput in the last 5 minutes

- Asynchronous message event throughput in the last 5 minutes

- Average asynchronous message Processing time

- Asynchronous messages throughput in the last 5 minutes

- Total asynchronous message processing time

- Synchronous message event throughput in the last 5 minutes

- Average synchronous message processing time

- Synchronous messages throughput in the last 5 minutes

- Total synchronous message processing time

- Server Name

- Mediator Case

- Average processing time of invocations

- Invocation throughput in the last 5 minutes

- Total processing time for invocations

- Failed filtered messages throughput in the last 5 minutes

- Average processing time of faulted cases

- Number of faulted cases

- Faulted case throughput in the last 5 minutes

- Total processing time for faulted cases

- Filtered messages throughput in the last 5 minutes

- Invocation Count throughput in the last 5 minutes

- Component Type

- Composite Label

- Case Target

- Mediator Flow

- Flow Type

- Average processing time of successful cases

- Number of successful cases

- Successful case throughput in the last 5 minutes

- Total processing time for successful cases

- Mediator Flow Metric

- Deferred message count throughput in last 5 minutes

- Failed filter case throughput in last 5 minutes

- Average faulted instance processing time

- Faulted instances throughput in last 5 minutes

- Total faulted instance processing time

- Instance throughput in last 5 minutes

- Component Type

- Composite Label

- Flow Type

- Average successful instance processing time

- Successful instances throughput in last 5 minutes

- Total successful instance processing time

- Total Composite Instances

- Total number of composite instances since server startup

- Domain Name

- Total Composite Faults

- Total number of faults since server startup

- Reference Binding Rollup

- Average Incoming Messages Processing Time

- Average Incoming Messages Processing Time (ms)

- Average Outbound Messages Processing Time

- Average Outbound Messages Processing Time (ms)

- Binding - Error rate

- Composite Revision

- Composite Name

- Domain Name

- End Point URL

- Incoming message throughput in last 5 minutes

- Incoming message throughput in last 5 minutes (sec)

- Outbound message throughput in last 5 minutes

- Outbound message throughput in last 5 minutes (sec)

- Reference Name

- Reference Type

- Total number of faults since last collection

- Total number of faults since startup

- Total number of incoming messages Since Last Collection

- Total number of incoming messages since startup

- Total number of outgoing messages since last collection

- Total number of outgoing messages since startup

- WSDL Port

- WSDL URL of the service

- Service Binding Rollup

- Average Incoming Messages Processing Time

- Average Incoming Messages Processing Time (ms)

- Average Outbound Messages Processing Time

- Average Outbound Messages Processing Time (ms)

- Binding - Error rate

- Composite Revision

- Composite Name

- Domain Name

- End Point URL

- Incoming message throughput in last 5 minutes

- Incoming message throughput in last 5 minutes (sec)

- Outbound message throughput in last 5 minutes

- Outbound message throughput in last 5 minutes (sec)

- Reference Name

- Reference Type

- Total number of faults since last collection

- Total number of faults since startup

- Total number of incoming messages Since Last Collection

- Total number of incoming messages since startup

- Total number of outgoing messages since last collection

- Total number of outgoing messages since startup

- WSDL Port

- WSDL URL of the service

16 Forms

- Forms Resource Usage

- CPU Usage (%)

- Total CPU Time (millisec)

- instname.value

- Total Private Memory (KB)

- JVM Controllers

- CPU Usage (%)

- CPU Time (millisec)

- Number of JVMs running for this JVM Controller

- Private Memory (KB)

- UP Time (millisec)

- Number Of Sessions

- Number Of Sessions

- Response

- instname.value

- Status

- Servlet ResponseTime

- Average Response Time (millisec)

- instname.value

- Servlet Name

- Response Time (millisec)

- Number Of Tasks

- Total Time

- Web Module Name

17 Portal

- Portlets (All)

- Cache Hit (%)

- Average Time (ms)

- Requests (per minute)

- Availability (%)

- Producer Type

- Portlets (Top 5)

- Cache Hit (%)

- Average Time (ms)

- Requests (per minute)

- Availability (%)

- Producer Type

- Producers (All)

- Cache Hit (%)

- Average Time (ms)

- Requests (per minute)

- Availability (%)

- Producer Type

- Producers (Top 5)

- Cache Hit (%)

- Average Time (ms)

- Requests (per minute)

- Availability (%)

- Producer Type

- Portal Cache

- Average Expire Hit Time (ms)

- Expire Hit (%)

- Average New Time (ms)

- New (%)

- Average Ping Hit Time (ms)

- Ping Hit (%)

- Requests (per minute)

- Average Stale Time (ms)

- Stale (%)

- Database Connection Pool Statistics

- Average Fetch Time (ms)

- Requests (per minute)

- Hit (%)

- New (%)

- Stale (%)

- Database Repository Response Code Statistics

- Responses (per minute)

- Average Processing Time (ms)

- Page Engine Statistics

- Average Queue Wait Time (ms)

- Average Page Processing Time (ms)

- Pages (per minute)

- Average Page Metadata Fetch Time (ms)

- Page Metadata Fetches (per minute)

- Average Page Metadata Wait Time (ms)

- Queue Timeouts (per minute)

- HTTP200-HTTP299 (%)

- HTTP300-HTTP399 (%)

- HTTP400-HTTP499 (%)

- HTTP500-HTTP599 (%)

- Timeout (%)

- WebCache Page Metadata Hits (%)

- WebCache Page Metadata Misses (%)

- WebCache Page Metadata Non-Cacheables (%)

- Response

- UpDown Status

18 Reports Bridge

- Log Message Alerts

- Log Monitoring Rules

- Diagnostic Log Summary

- Log Error Messages (over 15 minutes)

- Log Incident Error Messages (over 15 minutes)

- Log Notification Messages (over 15 minutes)

- Log Trace Messages (over 15 minutes)

- Log Unknown Messages (over 15 minutes)

- Log Warning Messages (over 15 minutes)

- Remote Elements Discovered

- Host.value

- Name

- Discovery Time (ms)

- Type of Element

- Resource Usage

- CPU Usage (%)

- Memory Usage (MB)

- Memory Usage (%)

- Response

- Up or Down Status

19 Virtual Directory

- Adapter Metrics

- Open Connections

- Total No of Connections Processed

- Total No of Connections Reused

- Enabled

- Add Operations

- Total No of Operation Binds

- Operations Count

- Delete Operations

- Operational Version

- Modify Operations

- Total No of Operations Renamed

- Search Operations

- Provisioned version

- Type

- Average Time to complete a search request

- Maximum Time taken to complete a search request

- Minimum Time taken to complete a search request

- Connected IPs

- Current Connections

- Total Connections

- getUsers

- Current Connections

- Total Connections

- Resource Usage

- CPU Usage (%)

- CPU Idle Time (%)

- Other CPU Usage (%)

- Heap Usage (MB)

- Memory Usage (MB)

- Free Memory (MB)

- Other Memory Usage (MB)

- Total Memory (MB)

- Memory Usage (%)

- Free Memory (%)

- Other Memory Usage (%)

- Start Time (ms since Epoch)

- Up Time (ms since Epoch)

- Response

- UpDown Status

- Server Latency Metrics

- Total Operations

- Average time to complete an LDAP search request

- Maximum Time to complete a search request

- Minimum Time to complete a search request

- Number of LDAP Add Requests

- Number of LDAP Binds Requests

- Number of LDAP Delete Requests

- Number of LDAP Modify Requests

- Number of LDAP Rename Requests

- Number of LDAP Search Requests

- Server wide Connection Metrics

- Total No of IPs Currently Connected

- Total No of Users Currently Connected

- Total No of Operations

- Total No of Open Connections

20 Internet Directory

- Oracle Internet Directory

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

- Active Database Sessions

- Closed LDAP Logon Session Statistics

- Total Closed Logon Sessions

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

- Active Database Sessions

- Date and Time Stamp

- Instance Number

- Open Database Sessions

- Failed Bind Operations

- (Critical Events)General System Resource Events

- Critical General Sys Resource Event Occurrences

- LDAP Load

- Server Load

- Historical LDAP Load and Response

- Date and Time Stamp

- Instance Number

- Server Load

- Server Average Response Time (in Milliseconds)

- (Resource Statistics)LDAP Server Memory Growth

- Average memory growth (%)

- New LDAP Logon Session Statistics

- Total New Logon Sessions

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

- Open Database Sessions

- Open LDAP Logon Session Statistics

- Total Open Logon Sessions

- Historical LDAP Operation Response Time

- Bind Operation Response Time

- Compare Operation Response Time

- Date and Time Stamp

- Instance Number

- Messaging Search Operation Response Time

- LDAP Operation Response Time

- Bind Operation Response Time

- Compare Operation Response Time

- Messaging Search Operation Response Time

- LDAP Server Resource Usage

- Total CPU Usage (%)

- Total Memory Usage (KB)

- Total Memory Usage (%)

- LDAP Response

- Server Response

- Running instances of LDAP Server

- Downtime Count

- Host Name

- Instance Number

- Up Since

- Non SSL Port Number

- SSL Port Number

- (Historical Resource Statistics)LDAP Server and System Memory

- Date and Time Stamp

- Instance Number

- LDAP Server's average memory growth (%)

- System's Total Free Physical Memory (KB)

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

- Number of 3113 Error Occurrences

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

- Number of 3114 Error Occurrences

- (Historical Critical Events)System Resource Events

- Last Event Time

- Number of Event Occurrence

- Event Name

- Instance Number

- Process ID

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

- Critical Ora Error Occurrences

- Historical LDAP Logon Session Statistics

- Date and Time Stamp

- Instance Number

- Total LDAP Logon Sessions

- Total Memory Usage

- Total Mem. Size(in KB)

- Historical LDAP Operations Profile

- Date and Time Stamp

- Instance Number

- Completed Abandon Operations

- Completed Add Operations

- Completed Bind Operations

- Completed Compare Operations

- Completed Delete Operations

- Completed Modify Operations

- Completed Modrdn Operations

- Completed Search Operations

- Completed Unbind Operations

- Failed Bind Operations

- LDAP Operations Profile

- Completed Abandon Operations

- Completed Add Operations

- Completed Bind Operations

- Completed Compare Operations

- Completed Delete Operations

- Completed Modify Operations

- Completed Modrdn Operations

- Total Operations

- Completed Search Operations

- Completed Unbind Operations

- LDAP Server Total User Sessions

- Total Users Sessions

- Directory Integration Profiles

- Last Execution Time

- Last Applied Change Number

- Execution Errors

- State

- Execution Status

- Schedule (secs)

- Type

- Directory Integration Server

- Downtime Count

- Directory Integration Server Host

- Start Time

- LDAP Server

- Size of Audit Log Purge Queue

- Total Number of Audit Log Objects in Purge Queue

- Size of General Statistics Purge Queue

- Total Number of General Statistics Objects in Purge Queue

- Size of Health Statistics Purge Queue

- Total Number of Health Statistics Objects in Purge Queue

- Total Number ChangeLogs in Purge Queue

- Total Number of Local Changelogs in Purge Queue

- Total Number Remote ChangeLogs in Purge Queue

- Total Number of Remote Changelogs in Purge Queue

- Total Number of HIQ ChangeLogs

- HIQ Changelog Count

- Replication Server Configuration Set Information

- Number of Threads per Supplier for Change Processing

- Number of Threads per Supplier for Transporting Changes

- Running instances of LDAP Replication Server

- Downtime Count

- Oracle Directory Server

- Start Time

- Total Number of Local ChangeLogs

- Total Number of Local Changelogs

- Total Number of New ChangeLogs

- New Changelog Count

- Total number ChangeLogs to be processed

- Total Changelogs to be processed

- Total Number of Retry ChangeLogs

- Retry Changelog Count

- OID Replication Server Virtual Memory Size

- Replication Server Memory Size

- OID Replication Server Percentage CPU

- Replication Server Percentage CPU

- Replication Supplier Details

- Replication Agreement Type

- HIQ Changelog Count

- New Changelog Count

- Retry Changelog Count

- Name of the Supplier Replica

- Size of Security Refresh events Purge Queue

- Total Number of Security Refresh events Objects in Purge Queue

- Historical LDAP Entry Cache Hit Ratio

- User Action

- Date and Time Stamp

- Instance Number

- Server Entry Cache Hit Ratio

- Process ID

- LDAP Entry Cache Hit Ratio

- Server Entry Cache Hit Ratio

- OID Server Virtual Memory Size

- OID Server Memory Size

- Stopped instances of LDAP Server

- Config Set Number

- Host Name

- OID Server Percentage CPU Utilization

- OID Server Percentage CPU

- (Historical Critical Events)Security Events

- Event Time

- Event Result

- Event Name

- Instance Number

- Process ID

- User DN

- (Critical Event)Super User Failed Logins

- Failed LDAP Super User Login

- (Critical Event)Super User Successful Logins

- Successful LDAP Super User Login

- Size of System Resource events Purge Queue

- Total Number of System Resource events Objects in Purge Queue

- Size of Tombstone Purge Queue

- Total Number of Tombstone Objects in Purge Queue

- TopProcesses

- Process Name

- Resource Usage

- CPU Usage (%)

- CPU Idle Time (%)

- Other CPU Usage (%)

- Memory Usage (MB)

- Free Memory (MB)

- Other Memory Usage (MB)

- Total Memory (MB)

- Memory Usage (%)

- Free Memory (%)

- Other Memory Usage (%)

- Start Time (ms since Epoch)

- Response

- Status

- Total Number

- User LDAP Operations Stats

- Abandon Operations

- Failed Add Operations

- Failed Base Search Operations

- Failed Bind Operations

- Failed Compare Operations

- Failed Delete Operations

- Failed Modify Operations

- Failed ModRdn Operations

- Failed OneLevel Search Operations

- Failed Proxy Bind Operations

- Failed Subtree Search Operations

- Successful Add Operations

- Successful Base Search Operations

- Successful Bind Operations

- Successful Compare Operations

- Successful Delete Operations

- Successful Modify Operations

- Successful ModRdn Operations

- Successful OneLevel Search Operations

- Successful Proxy Bind Operations

- Successful Subtree Search Operations

- Unbind Operations

21 Directory Integration Platform

- DIP Aggregated Metrics

- Total Changes Attempted

- Total Successful Changes

- Average LDAP Search Time

- Average LDAP Write Time

- Average Profile Execution Time

- DIP All Profiles (Consolidated)

- Host

- Last Change Number

- Last Execution Error

- Last Execution Time

- Last Successful Execution Time

- Status of Last Sync Operation

- DIP Profile Name

- DIP Process

- Average Processing Time

- Maximum Processing Time

- Minimum Processing Time

- Profile Job Status

- DIP Prov profile runtime operational metrics

- Failed Add Group operations

- Failed Add Identity operations

- Failed Add Subscription operations

- Failed Add User operations

- Failed Delete Group operations

- Failed Delete Identity operations

- Failed Delete Subscription operations

- Failed Delete User operations

- Failed Modify Group operations

- Failed Modify Identity operations

- Failed Modify User operations

- Profile Name

- Successful Add Group operations

- Successful Add Identity operations

- Successful Add Subscription operations

- Successful Add User operations

- Successful Delete Group operations

- Successful Delete Identity operations

- Successful Delete Subscription operations

- Successful Delete User operations

- Successful Modify Group operations

- Successful Modify Identity operations

- Successful Modify User operations

- DIP Sync profile runtime operational metrics

- Skipped Operations

- Failed Add Operations

- Failed Delete Operations

- Failed Modify Operations

- Profile Name

- Successful Add Operations

- Successful Delete Operations

- Successful Modify Operations

- DIP Health

- Host

- MBean Status

- Name

- Quartz Scheduler Status

- WLS Server Name

- DIP Provisioning Profiles

- DIP Provisioning Profile Name

- Host

- Name

- DIP Synchronization Profiles

- DIP Synchronization Profile Name

- Host

- Name

- Resource Usage

- CPU Usage (%)

- Memory Usage (%)

- DIP server status

- Status

22 WebCenter

- Response

- UpDown Status

- WebCenter Spaces (Aggregated)

- Application Name

- Status

- Successful Invocations (%)

- Failed Invocations (%)

- Invocations (per minute)

- Page Throughput (per minute)

- Average Page Processing Time (ms)

- Service Name

- WebCenter Content Repositories (Aggregated)

- Application Name

- Average Delete Time (ms)

- Average Download Time (ms)

- Average GetItem Time (ms)

- Average ListFolder Time (ms)

- Average Login Time (ms)

- Average Processing Time (ms)

- Average Search Time (ms)

- Average Upload Time (ms)

- Deletes (per minute)

- Download (per minute)

- GetItems (per minute)

- Invocations (per minute)

- ListFolder (per minute)

- Logins (per minute)

- Searches (per minute)

- Status

- Successful Invocations (%)

- Failed Invocations (%)

- Uploads (per minute)

- Service Name

- WebCenter Events (Aggregated)

- Application Name

- Average Create Time (ms)

- Average Delete Time (ms)

- Average List Time (ms)

- Average Processing Time (ms)

- Average Search Time (ms)

- Average Update Time (ms)

- Creates (per minute)

- Deletes (per minute)

- Failed Invocations (%)

- Invocations (per minute)

- Lists (per minute)

- Searches (per minute)

- Status

- Successful Invocations (%)

- Updates (per minute)

- Service Name

- WebCenter External Applications (Aggregated)

- Application Name

- Automated Logins (per minute)

- Average Automated Login Time (ms)

- Average Fetch Credentials Time (ms)

- Average Fetch External Applications Time (ms)

- Average Processing Time (ms)

- Average Store Credentials Time (ms)

- Credential Fetches (per minute)

- Credential Stores (per minute)

- External Applications Fetches (per minute)

- Failed Invocations (%)

- Invocations (per minute)

- Status

- Successful Invocations (%)

- Service Name

- WebCenter Portlets (Aggregated)

- Application Name

- Failed Invocations (%)

- Average HTTP 2xx Time (ms)

- Average HTTP 3xx Time (ms)

- Average HTTP 4xx Time (ms)

- Average HTTP 5xx Time (ms)

- Average Processing Time (ms)

- Average HTTP 2xx Requests (per minute)

- Average HTTP 3xx Requests (per minute)

- Average HTTP 4xx Requests (per minute)

- Average HTTP 5xx Requests (per minute)

- Invocations (per minute)

- Status

- Successful Invocations (%)

- Service Name

- WebCenter Producers (Aggregated)

- Application Name

- Average HTTP 2xx Time (ms)

- Average HTTP 3xx Time (ms)

- Average HTTP 4xx Time (ms)

- Average HTTP 5xx Time (ms)

- Average Processing Time (ms)

- Failed Invocations (%)

- Average HTTP 2xx Requests (per minute)

- Average HTTP 3xx Requests (per minute)

- Average HTTP 4xx Requests (per minute)

- Average HTTP 5xx Requests (per minute)

- Invocations (per minute)

- Status

- Successful Invocations (%)

- Service Name

- WebCenter Search (Aggregated)

- Application Name

- Average Processing Time (ms)

- Failed Invocations (%)

- Invocations (per minute)

- Status

- Successful Invocations (%)

- Service Name

- WebCenter Services

- Application Name

- Average Processing Time (ms)

- Failed Invocations (%)

- Invocations (per minute)

- Status

- Successful Invocations (%)

- WebCenter BPEL Worklists (Aggregated)

- Application Name

- Average Processing Time (ms)

- Failed Invocations (%)

- Invocations (per minute)

- Status

- Successful Invocations (%)

- Service Name

- WebCenter Portlets

- Application Name

- Average HTTP 2xx Time (ms)

- Average HTTP 3xx Time (ms)

- Average HTTP 4xx Time (ms)

- Average HTTP 5xx Time (ms)

- Average Processing Time (ms)

- Failed Invocations (%)

- Average HTTP 2xx Requests (per minute)

- Average HTTP 3xx Requests (per minute)

- Average HTTP 4xx Requests (per minute)

- Average HTTP 5xx Requests (per minute)

- Invocations (per minute)

- Status

- Successful Invocations (%)

- Producer Type

- WebCenter Producers

- Application Name

- Average HTTP 2xx Time (ms)

- Average HTTP 3xx Time (ms)

- Average HTTP 4xx Time (ms)

- Average HTTP 5xx Time (ms)

- Average Processing Time (ms)

- Failed Invocations (%)

- Average HTTP 2xx Requests (per minute)

- Average HTTP 3xx Requests (per minute)

- Average HTTP 4xx Requests (per minute)

- Average HTTP 5xx Requests (per minute)

- Invocations (per minute)

- Status

- Successful Invocations (%)

- Producer Type

- WebCenter Announcements

- Application Name

- Average Create Time (ms)

- Average List Time (ms)

- Average Login Time (ms)

- Average Logout Time (ms)

- Average Processing Time (ms)

- Average Search Time (ms)

- Creates (per minute)

- Failed Invocations (%)

- Invocations (per minute)

- Lists (per minute)

- Logins (per minute)

- Logouts (per minute)

- Searches (per minute)

- Status

- Successful Invocations (%)

- Service Name

- WebCenter Spaces

- Application Name

- Failed Invocations (%)

- Successful Invocations (%)

- Invocations (per minute)

- Page Throughput (per minute)

- Errors (per minute)

- Average Page Processing Time (ms)

- WebCenter Content Repositories

- Application Name

- Average Delete Time (ms)

- Average Download Time (ms)

- Average Get Item Time (ms)

- Average List Folder Time (ms)

- Average Login Time (ms)

- Average Processing Time (ms)

- Average Search Time (ms)

- Average Upload Time (ms)

- Deletes (per minute)

- Downloads (per minute)

- Download Throughput (bytes per second)

- Failed Invocations (%)

- Get Item

- Invocations (per minute)

- List Folder

- Logins (per minute)

- Searches (per minute)

- Status

- Successful Invocations (%)

- Uploads (per minute)

- Upload Throughput (bytes per second)

- WebCenter Events

- Application Name

- Average Create Time (ms)

- Average Delete Time (ms)

- Average List Time (ms)

- Average Processing Time (ms)

- Average Search Time (ms)

- Average Update Time (ms)

- Creates (per minute)

- Deletes (per minute)

- Failed Invocations (%)

- Invocations (per minute)

- Lists (per minute)

- Searches (per minute)

- Status

- Successful Invocations (%)

- Updates (per minute)

- WebCenter External Applications Connections

- Application Name

- Invocations (per minute)

- WebCenter External Applications

- Application Name

- Automated Logins (per minute)

- Average Automated Login Time (ms)

- Average Fetch Credential Time (ms)

- Average Fetch External Application Time (ms)

- Average Processing Time (ms)

- Average Store Credentials Time (ms)

- Credential Fetches (per minute)

- Credential Stores (per minute)

- External Application Fetches (per minute)

- Failed Invocations (%)

- Invocations (per minute)

- Status

- Successful Invocations (%)

- Name

- WebCenter Discussion Forum

- Application Name

- Average Create Forum Time (ms)

- Average Create Topic Time (ms)

- Average List Forums Time (ms)

- Average List Topics Time (ms)

- Average Login Time (ms)

- Average Logout Time (ms)

- Average Processing Time (ms)

- Average Reply Time (ms)

- Average Search Time (ms)

- Create Forum (per minute)

- Create Topic (per minute)

- Failed Invocations (%)

- Invocations (per minute)

- List Forums (per minute)

- List Topics (per minute)

- Logins (per minute)

- Logouts (per minute)

- Replies (per minute)

- Searches (per minute)

- Status

- Successful Invocations (%)

- Service Name

- WebCenter Pages

- Application Name

- Average Page Processing Time (ms)

- Average Partial Page Processing Time (ms)

- Errors (per minute)

- Failed Invocations (%)

- Invocations (per minute)

- Page Throughput (per minute)

- Partial Page Invocations (per minute)

- Status

- Successful Invocations (%)

- WebCenter Import/Export

- Application Name

- Average Processing Time (ms)

- Failed Invocations (%)

- Invocations (per minute)

- Status

- Successful Invocations (%)

- Service Name

- WebCenter Lists

- Application Name

- Average Copy List Time (ms)

- Average Copy List Type Time (ms)

- Average Copy Rows Time (ms)

- Average Create List Time (ms)

- Average Create List Type Time (ms)

- Average Create Row Time (ms)

- Average Delete List Time (ms)

- Average Delete List Type Time (ms)

- Average Delete Row Time (ms)

- Average Processing Time (ms)

- Average Query Time (ms)

- Average Retrieve Rows Time (ms)

- Average Save Time (ms)

- Average Update Row Time (ms)

- Copy List (per minute)

- Copy List Type (per minute)

- Copy Rows (per minute)

- Create List (per minute)

- Create List Type (per minute)

- Create Row (per minute)

- Delete List (per minute)

- Delete List Type (per minute)

- Delete Row (per minute)

- Failed Invocations (%)

- Invocations (per minute)

- Queries (per minute)

- Retrieve Rows (per minute)

- Saves (per minute)

- Status

- Successful Invocations (%)

- Update Row (per minute)

- Service Name

- WebCenter Mail

- Application Name

- Average Login Time (ms)

- Average Logout Time (ms)

- Average Processing Time (ms)

- Average Receive Time (ms)

- Average Search Time (ms)

- Average Send Time (ms)

- Failed Invocations (%)

- Invocations (per minute)

- Logins (per minute)

- Logout (per minute)

- Receives (per minute)

- Searches (per minute)

- Sends (per minute)

- Status

- Successful Invocations (%)

- Service Name

- WebCenter Notes

- Application Name

- Average Create Time (ms)

- Average Delete Time (ms)

- Average Find Time (ms)

- Average Processing Time (ms)

- Average Save Changes Time (ms)

- Average Update Time (ms)

- Creates (per minute)

- Deletes (per minute)

- Failed Invocations (%)

- Finds (per minute)

- Invocations (per minute)

- Save Changes (per minute)

- Status

- Successful Invocations (%)

- Updates (per minute)

- Service Name

- WebCenter Page Service

- Application Name

- Average Copy Time (ms)

- Average Create Time (ms)

- Average Delete Time (ms)

- Average Processing Time (ms)

- Average Search Time (ms)

- Average Update Time (ms)

- Copies (per minute)

- Creates (per minute)

- Deletes (per minute)

- Failed Invocations (%)

- Invocations (per minute)

- Searches (per minute)

- Status

- Updates (per minute)

- Successful Invocations (%)

- Service Name

- WebCenter People Connections

- Application name

- Average Processing Time (ms)

- Failed Invocations (%)

- Get Feedback (per minute)

- Get Feedback Average Time (ms)

- Invocations (per minute)

- Publish Activity (per minute)

- Publish Activity Average Time (ms)

- Retrieve Activities (per minute)

- Retrieve Activities Average Time (ms)

- Retrieve Connections Average Time (ms)

- Retrieve Messages (per minute)

- Retrieve Messages Average Time (ms)

- Retrieve Profiles (per minute)

- Retrieve Profiles Average Time (ms)

- Status

- Successful Invocations (%)

- Service Name

- WebCenter Polls

- Application Name

- Analyze Poll (per minute)

- Analyze Poll Average Time (ms)

- Average Processing Time (ms)

- Create Poll (per minute)

- Create Poll Average Time (ms)

- Create Response (per minute)

- Create Response Average Time (ms)

- Delete Poll (per minute)

- Delete Poll Average Time (ms)

- Edit Poll (per minute)

- Edit Poll Average Time (ms)

- Failed Invocations (%)

- Get Poll (per minute)

- Get Poll By Id (per minute)

- Get Poll By Id Average Time (ms)

- Get Poll Response Average Time (per minute)

- Status

- Successful Invocations (%)

- Invocations (per minute)

- Service Name

- WebCenter Recent Activity

- Application Name

- Average Processing Time (ms)

- Failed Invocations (%)

- Invocations (per minute)

- Status

- Successful Invocations (%)

- Service Name

- WebCenter RSS News Feeds

- Application Name

- Average Processing Time (ms)

- Failed Invocations (%)

- Invocations (per minute)

- Status

- Successful Invocations (%)

- Service Name

- WebCenter Instant Messaging and Presence

- Application Name

- Average Get Presence Time (ms)

- Average Login Time (ms)

- Average Logout Time (ms)

- Average Processing Time (ms)

- Failed Invocations (%)

- Get Presence (per minute)

- Invocations (per minute)

- Logins (per minute)

- Logouts (per minute)

- Status

- Successful Invocations (%)

- Service Name

- WebCenter Search

- Application Name

- Failed Invocations (%)

- Successful Invocations (%)

- Invocations (per minute)

- Query Throughput (queries per minute)

- Status

- Average Processing Time (ms)

- WebCenter BPEL Worklists

- Application Name

- Failed Invocations (%)

- Status

- Successful Invocations (%)

- Invocations (per minute)

- Average Processing Time (ms)

23 Web Cache

- Performance by Web Cache Instance

- Instance

- Request Processing Time (milli seconds)

- Request Throughput (per second)

- Resource Usage

- CPU Usage (%)

- CPU Idle Time (%)

- Other CPU Usage (%)

- Memory Usage (MB)

- Free Memory (MB)

- Other Memory Usage (MB)

- Total Memory (MB)

- Memory Usage (%)

- Free Memory (%)

- Other Memory Usage (%)

- Start Time (ms since Epoch)

- Up Time (ms since Epoch)

- Response

- Response Admin

- Admin Process Status

- Response - Status

- Performance of each Site with Summary

- Total Number of Bytes Saved by Compression

- Cache Size

- Total Number Error Pages Served

- Hit Rate (in %)

- Number of Cached

- Currently Open connections

- Total Number of Requests Denied

- Total Number of Requests Served

- WebCache_nontimedHost

- Capacity.value

- Load.value

- MaxLoad.value

- Port.value

- WebCache_timedHost

- AvgLatency.value

- Latency.value

- Request.value

- RequestFailure.value

24 Business Activity Monitoring

- Report Server Active Data Page

- Open Connections

- Open Reports

- Open Viewsets

- Activity Message Rate (per sec)

- Average Time To Open Viewsets (in sec)

- Response

- UpDown Status

25 Business Activity Monitoring Server

- ADC Client Requests For All DataObjects

- Client Requests In Progress

- Client Requests Total

- ADC Waiting Threads For All DataObjects

- Deletes Per Second

- Inserts Per Second

- Updates Per Second

- Upserts Per Second

- Deletes Per Second

- Inserts Per Second

- Updates Per Second

- Upserts Per Second

- ADC Waiting Threads For All DataObjects

- Waiting Threads For All DataObjects

- ADC Waiting Threads For All DataObjects

- Waiting Threads For All DataObjects

- ADC Batch Size For All DataObjects

- Current Delete Batch Size

- Current Insert Batch Size

- Current Update Batch Size

- Current Upsert Batch Size

- Current Update Batch Size

- Current Insert Batch Size

- Current Delete Batch Size

- Current Upsert Batch Size

- Current Delete Batch Size

- Current Delete Batch Size

- Current Insert Batch Size

- Current Insert Batch Size

- Waiting Threads For All DataObjects

- Active Data Cache Transaction Information

- Committed Transactions

- Completed Transactions

- Open Transaction

- Rolledback Transactions

- EMS Metrics

- Total number of received messages

- Total number of rejected messages

- Total delete operations

- Total insert operations

- Total update operations

- Total upsert operations

- Total number of received messages

- Total number of rejected messages

- Delete operations rate

- Insert operations rate

- Update operations rate

- Upsert operations rate

- Total received messages

- Total rejected messages

- Delete operations rate

- Insert operations rate

- Update operations rate

- Upsert operations rate

- Total received messages

- Total rejected messages

- Total delete operations

- Total insert operations

- Total update operations

- Total upsert operations

- Event Engine General Information

- Active Rules

- Action Queue Size

- Alert History Queue Size

- Rule Fire Queue Size

- Event Engine Activity Rule Fire Rate

- Events Accepted Rate (per sec)

- Events Fire Rate (per sec)

- Events Rejected Rate (per sec)

- Active Data Reports Information

- Active Data Reports

- Active Data Sessions

- Outgoing Message Rate (per sec)

- File Count

- Element Count

- Viewset Average Open Time (in sec)

- Independent Viewsets

- Open Viewsets

- Shared Viewsets

- Sharing Viewsets

- Response

- UpDown Status

26 Oracle Directory Server Enterprise Edition

- Cache Memory Thresholds

- Heap High Hits

- Heap High Hits (per sec)

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

- Heap High Hits (since startup)

- Heap Low Hits

- Heap Low Hits (per sec)

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

- Heap Low Hits (since startup)

- Compare Operations Elapsed Time Metrics

- Average Elapsed Time per Compare Operation (ms)

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

- LDAP Compare operations (since startup)

- Total Elapsed Time for all Compare Operations (ms)

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

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

- Compare Operations Metrics

- Compare Operations

- Compare Operations (per sec)

- Compare Operations (per sec) (since startup)

- Compare Operations (since startup)

- Connections Metrics

- Connections Peak

- Connections Per Sec

- Connections Per Sec (s start)

- Current Connections

- Database Cache Metrics

- Cache Clean Pages

- Cache Dirty Pages

- Cache Hits

- Cache Page Reads

- Cache Page Writes

- Cache Tries

- Errors Metrics

- Bind Security Errors

- Bind Security Errors (Since Start)

- Operational Errors

- Operational Errors (Since Start)

- Security Errors

- Security Errors (Since Start)

- Total Errors

- Total Errors (Since Start)

- General Information

- Backend

- Current Time

- Start Time

- Version

- Hashtable Metrics

- Hash Elements Traversed

- Hash Elements Traversed (per sec)

- Hash Elements Traversed (per sec since startup)

- Hash Elements Traversed (since startup)

- Hash Table Lookups

- Hash Table Lookups (per sec)

- Hash Table Lookups (per sec since start)

- Hash Table Lookups (since startup)

- Longest Chain During Hash Lookups

- In Out Operation

- Bytes Returned

- Bytes Returned (per sec)

- Bytes Returned (per sec since startup)

- Bytes Returned (since startup)

- LDAP Entries Returned

- LDAP Entries Returned (per sec)

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

- LDAP Entries Returned (since startup)

- Referrals Returned

- Referrals Returned (per sec)

- Referrals Returned (per sec) (since startup)

- Referrals Returned (since startup)

- Locks and DeadLocks

- Current Database Locks

- Current Lockers

- Detected Deadlocks

- DeadLocks Detected (per sec)

- DeadLocks Detected (per sec since startup)

- DeadLocks Detected (since startup)

- Lock Conflicts

- Lock Conflicts (per sec)

- Lock Conflicts (per sec since startup)

- Lock Conflicts (since startup)

- Maximum Database Locks

- Total locks Requested

- Total locks Requested (per sec)

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

- Total locks Requested (since startup)

- Waits before Database Lock

- Waits before Database Lock (per sec)

- Waits before Database Lock (per sec since startup)

- Waits before Database Lock (since startup)

- Operations Metrics

- Average Elapsed Time per Operation (ms)

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

- Total Elapsed Time for all Operations (ms)

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

- Total LDAP Operations Completed

- Total LDAP Operations Completed (per sec)

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

- Total LDAP Operations Completed (since startup)

- Total Operations Completed

- Total Operations Completed (per sec)

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

- Total Operations Completed (since startup)

- Total Operations Initiated

- Total Operations Initiated (per sec)

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

- Total Operations Initiated (since startup)

- Other Operations

- LDAP Referral Operations

- LDAP Referral Operations (per sec)

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

- LDAP Referral Operations (since startup)

- Persistent Searches Running

- Queues Metrics

- Operations In Progress

- Operations Queue Back Log

- Read Waiters Queue

- Read Operations Elapsed Time Metrics

- Average Elapsed Time per Bind Operation (ms)

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

- Average Elapsed Time per Search Operation (ms)

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

- Average Elapsed Time per UnBind Operation (ms)

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

- LDAP Binds (since startup)

- LDAP Searches (since startup)

- Total Elapsed Time for Bind Operations (ms)

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

- Total Elapsed Time for Search Operations (ms)

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

- Total Elapsed Time for UnBind Operations (ms)

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

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

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

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

- Read Operations Metrics

- Anonymous Binds

- Anonymous binds (per sec)

- Anonymous Binds (per sec) (since startup)

- Anonymous Binds (since startup)

- LDAP Binds

- LDAP Binds (per sec)

- LDAP Binds (per sec) (since startup)

- LDAP Binds (since startup)

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

- Simple Authorized Binds (since startup)

- Simple Binds

- Simple Binds (per sec)

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

- Strong Authorized Binds (since startup)

- Strong Binds

- Strong Binds (per sec)

- Unauthorized Binds

- Unauthorized Binds (per sec)

- Unauthorized Binds (per sec) (since startup)

- Unauthorized Binds (since startup)

- Resource Usage

- CPU Utilization (%)

- Memory Utilization (KB)

- Memory Utilization (%)

- Response

- Status

- Suffix-Backend Entry

- Suffix-Backend Entry - Average Cache Size

- Suffix-Backend Entry - Cache Count

- Suffix-Backend Entry - Cache Hit Ratio

- Suffix-Backend Entry - Cache Hits

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

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

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

- Suffix-Backend Entry - Cache Size

- Suffix-Backend Entry - Cache Tries

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

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

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

- Suffix-Backend Name

- Suffix-Backend File Metrics

- Suffix-Backend File - Cache Hit Ratio

- Suffix-Backend File - Cache Hits

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

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

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

- Suffix-Backend File - Cache Misses

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

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

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

- Suffix-Backend File - Pages in to Cache

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

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

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

- Suffix-Backend File - Pages Out to Disk

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

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

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

- Suffix-Backends General Information

- Suffix-Backend Name

- Suffix-Backend Next DB entry ID

- Suffix-Backend State

- Suffix-Backend Total DB Entry Count

- Suffix-Backend LDAP Entry Count

- Transaction Log Metrics

- Bytes wrote to log

- Bytes wrote to log (per sec)

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

- Bytes Wrote to Log (since last check point)

- Log Flushes

- Log Flushes (per sec)

- Log Flushes (per sec) (since startup)

- Log Flushes (since startup)

- Log Flushes by In-Memory Full

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

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

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

- Log Flushes with Commits

- Log Flushes with Commits (per sec)

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

- Log Flushes with Commits (since startup)

- Log Written to Disk

- Log Written to Disk (per sec)

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

- Log Written to Disk (since startup)

- Maximum Commits in Log Flush

- Minimum Commits in Log Flush

- Waits before getting the Log Lock

- Waits before getting the Log Lock (per sec)

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

- Waits before getting the Log Lock (since startup)

- Transactions

- Aborted Transactions

- Aborted Transactions (per sec)

- Aborted Transactions (per sec) (since startup)

- Aborted Transactions (since startup)

- Committed Transactions

- Committed Transactions (per sec)

- Committed Transactions (per sec) (since startup)

- Committed Transactions (since startup)

- Current Active Transactions

- Maximum Transactions Used

- Waits before Transaction Locks

- Waits before Transaction Locks (per sec)

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

- Waits before Transaction Locks (since startup)

- Write Operations Elapsed Time Metrics

- Average Elapsed Time per Add Operation (ms)

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

- Average Elapsed Time per Delete Operation (ms)

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

- Average Elapsed Time per Modify Operation (ms)

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

- Average Elapsed Time per Modify RDN Operation (ms)

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

- LDAP Add operations (since startup)

- LDAP Delete operations (since startup)

- LDAP Modify operations (since startup)

- LDAP Modify RDN operations (since startup)

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

- Total Elapsed Time for all Add Operations (ms)

- Total Elapsed Time for all Delete Operations (ms)

- Total Elapsed Time for all Modify Operations (ms)

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

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

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

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

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

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

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

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

- Write Operations Metrics

- Add Operations

- Add Operations (per sec)

- Add Operations (per sec) (since startup)

- Add Operations (since startup)

- Delete Operations

- Delete Operations (per sec)

- Delete Operations (per sec) (since startup)

- Delete Operations (since startup)

- Modify Operations

- Modify Operations (per sec)

- Modify Operations (per sec) (since startup)

- Modify Operations (since startup)

- Modify RDN (since startup)

- Modify RDN Operations

- Modify RDN Operations (per sec)

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

Oracle® Enterprise Manager

Oracle Fusion Middleware Metric Reference Manual

12c Release 1 (12.1.0.2.0)

E25158-04

August 2012

Oracle Enterprise Manager Oracle Fusion Middleware Metric Reference Manual, 12c Release 1 (12.1.0.2.0)

E25158-04

Copyright © 2006, 2012, 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, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

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 and documentation may provide access to or information on 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. 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.

Preface

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

Audience

This document is intended for Oracle Enterprise Manager users interested in Oracle Database and database-related 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 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, see the following manuals in the Oracle Enterprise Manager 12c Release 1 documentation set:

- Oracle Enterprise Manager Cloud Control Basic Installation Guide

- Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide

- Oracle Enterprise Manager Concepts

- Oracle Enterprise Manager Cloud Control Quick Start Guide

- Oracle Enterprise Manager Administration

- Oracle Enterprise Manager Framework, Host, and Services Metric Reference Manual

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.

How to Use This Manual

The Oracle Enterprise Manager Oracle Fusion Middleware Metric Reference Manual lists all the Oracle Fusion Middleware target metrics that Enterprise Manager monitors. This manual compiles in one place all the Oracle Fusion Middleware target metric help available online, eliminating the need to have the Cloud Control Console up and running.

This preface describes:

- Structure of the Oracle Enterprise Manager Oracle Fusion Middleware Metric Reference Manual

- Background Information on Metrics, Thresholds, and Alerts

Structure of the Oracle Enterprise Manager Oracle Fusion Middleware Metric Reference Manual

This manual contains a chapter for each Oracle Fusion 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, collection frequency, upload frequency, operator, default warning threshold, default critical threshold, consecutive number of occurrences preceding notification, and alert text for the metric. Examples follow.

- 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 you will see in the Oracle Enterprise Manager Oracle Fusion Middleware Metric Reference Manual.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

The following table shows a metric where the server evaluation frequency is the same as the collection frequency.

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 10 Minutes

After Every Sample

>

10000000

12500000

1

Bytes sent by the server are %value%

The following table shows a metric where the server evaluation frequency is different from the collection frequency.

Target Version

Server Evaluation Frequency

Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

10.1.0.x

Every Minute

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

2

Generated By Database Server

Definitions of Columns in Metric Summary Tables

As previously mentioned, the Metric Summary table is part of the overall metric information. The following table provides descriptions of columns in the Metric Summary table.

Column Header

Column Definition

Target Version

Version of the target, for example, 9.0.2.x and 10.1.0.x. The x at the end of a version (for example, 9.0.2.x) represents the subsequent patchsets associated with that release.

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.

Comparison Operator

The comparison method Enterprise Manager uses to evaluate the metric value against the threshold values.

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.

Consecutive Number of Occurrences Preceding Notification

Consecutive number of times a metric's value reaches either the warning threshold or critical threshold before a notification is sent.

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%.

Abbreviations and Acronyms

To reduce the page count in this document, the following abbreviations and acronyms are used:

Abbreviation/Acronym

Name

Agent

Oracle Management Agent

Database

Oracle Database

Listener

Oracle Listener

Background Information on 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, others are not.

Once a threshold is reached, an alert is generated. 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

Editing

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, the key is to choose acceptable values to avoid unnecessary alerts, while still being notified of issues in a timely manner.

You can establish thresholds that will provide pertinent information in a timely manner by defining metric baselines that reflect how your system runs for a normal period of time.

The metrics listed on the Edit Thresholds page are either default metrics provided by Oracle or metrics whose thresholds you can change.

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.

Accessing Metrics Using the Cloud Control Console

To access metrics in the Cloud Control Console, use the All Metrics page associated with a particular target by doing the following:

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

2. On the target's home page, click All Metrics in the Related Links section.

3. On the All Metrics page, choose the metric of interest and click Help. The help for that metric displays.

1 WebLogic Server

This chapter describes Oracle WebLogic Server metrics.

Application Overview Metrics

This category provides information about application metrics.

Application - Cached Beans

For the selected application, the total number of Enterprise JavaBeans (EJB) currently in the EJB cache.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of cached beans is %value%.

Application - Cache Accesses (per minute)

For the selected application, the number of cache access attempts per minute in the last five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

Application - Bean Activations (per minute)

For the selected application, this metric shows the total number of EJB that have been activated since the server started.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

Application - 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.

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.

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 60 Samples

<

Not Defined

Not Defined

-

The EJB cache hit rate is %value%%%

Application - Cache Misses (per minute)

For the selected application, the number of cache misses per minute in the last five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

Application - Bean Accesses (per minute)

For the selected application, the EJB pool accesses per minute in the last five minutes.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application - Bean Access Successes (%)

For the selected application, the percentage of pool accesses that were successful in the last five minutes.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application - Free Bean Instances

For the selected application, the current number of available bean instances in the free pool.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application - Bean Destroys (per minute)

For the selected application, the bean destroys performed per minute in the last five minutes.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application - Bean Access Failures (per minute)

For the selected application, failed EJB pool accesses per minute in the last five minutes.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application - Beans in Use

For the selected application, the number of bean instances currently being used from the free pool.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application - Bean Transaction Commits (%)

For the selected application, the percentage of transactions that were committed during the last five minutes.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application - Bean Transaction Commits (per minute)

For the selected application, the transaction commits per minute for the last five minutes.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application - 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.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application - Bean Transaction Timeouts (per minute)

For the selected application, the transaction timeouts per minute for the last five minutes.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application - 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.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application - 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.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application - 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.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application - Active Sessions

This metric shows the number of active sessions for the selected application.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application - Work Manager Pending Requests

For the selected application, the number of waiting requests in the work manager queue.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application - Work Manager Requests (per minute)

For the selected application, the number of requests processed per minute in the last five minutes.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application Work Manager - Work Manager Pending Requests

For the selected application, this metric shows the number of work manager requests waiting in the queue.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application Work Manager - 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.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application Work Manager - 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.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Application Metrics

This category provides information about application metrics.

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.

Datasource Metrics

This category provides information about datasource metrics.

Datasource - Available Connections

For the selected data source, this metric shows the number of database connections currently available (not in use).

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.

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 60 Samples

<

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

Datasource - Connections in Use

For the selected data source, this metric shows the number of JDBC connections currently in use by applications.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

Datasource - Connection Pool Size

For the current data source, this metric shows the current count of JDBC connections in the JDBC connection pool.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

<

Not Defined

Not Defined

-

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

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).

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

Datasource - Connection Requests Waiting

For the selected data source, this metric shows the current number of JDBC connection requests waiting for a database connection.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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

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.

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 60 Samples

<

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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

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.

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 60 Samples

!=

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

<

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

<

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

<

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

<

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

EJB Module Metrics

This category provides information about EJB module metrics.

EJB Module - Cached Beans

This metric shows the total number of beans currently in the EJB cache.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of cached beans is %value%.

EJB Module - 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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

EJB Module - 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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

EJB Module - EJB Cache Hits (%)

For the current EJB module, this metric shows the percentage of cache accesses that completed successfully in the last five minutes.

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.

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 60 Samples

<

Not Defined

Not Defined

-

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

EJB Module - 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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

EJB Module - 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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

EJB Module - 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.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

EJB Module - Bean Successes (%)

For the current EJB module, this metric shows the percentage of pool accesses that were successful in the last five minutes.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

EJB Module - Free Bean Instances

For the selected EJB, this metric shows the current number of available bean instances in the free pool.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

EJB Module - Bean Destroys (per minute)

For the selected EJB Module, this metric shows the bean destroys per minute in the last five minutes.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

EJB Module - Failed Bean Accesses (per minute)

For the selected EJB module, this metric shows the failed pool accesses per minute over the past five minutes.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

EJB Module - Beans in Use

For the current EJB module, this metric shows the number of bean instances currently being used from the free pool.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

EJB Module - Bean Transaction Commits (per minute)

For the selected EJB module, this metric shows the transaction commits per minute, averaged over the past five minutes.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

EJB Module - 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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

EJB Module - 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.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

EJB Module - 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.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

EJB Pool Metrics

This category provides information about EJB pool metrics.

EJB Pool - 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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

EJB Pool - Successful Bean Accesses (%)

This metric shows the percentage of attempts to access the pool that were successful in the last five minutes.

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.

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 60 Samples

<

Not Defined

Not Defined

-

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

EJB Pool - Available Beans

This metric shows the current number of available bean instances in the selected EJB pool.

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.

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 60 Samples

<

Not Defined

Not Defined

-

The number of available beans is %value%.

EJB Pool - Bean Destroys (per minute)

For the selected EJB pool, this metric shows the bean destroys per minute over the last five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

EJB Pool - 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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

EJB Pool - Beans in Use

This metric shows the number of bean instances currently being used from the free pool.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of beans in use is %value%.

EJB Transaction Metrics

This category provides information about EJB transaction metrics.

EJB Transaction - Bean Transaction Commits (%)

This metric shows the percentage of EJB transactions that were committed during the last five minutes.

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.

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 60 Samples

<

Not Defined

Not Defined

-

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

EJB Transaction - Bean Transaction Commits (per minute)

This metric shows the EJB transaction commits per minute, averaged over the past five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

EJB Transaction - Bean Transaction Rollbacks (per minute)

This metric shows the EJB transaction rollbacks per minute, averaged over the past five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

EJB Transaction - Bean Transaction Timeouts (per minute)

This metric shows the EJB transaction timeouts per minute, averaged over the past five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

JMS Destination Metrics

This category provides information about JMS Destination metrics.

JMS Destination - Bytes Current Count

This metric shows the current bytes count.

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

JMS Destination - Bytes Pending Count

This metric shows the pending bytes count

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

JMS Destination - Bytes Received Count

This metric shows the bytes received count

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

JMS Destination - Bytes Received Current Count

This metric shows the current bytes received count

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

JMS Destination - Bytes Received Current Count Per Second

This metric shows the current bytes received per second count

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

JMS Destination - Consumers Current Count

This metric shows the count of the current number of consumers

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

JMS Destination - Consumers Total Count

This metric shows the total number of consumers

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

JMS Destination Type

This metric shows the JMS destination type

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

JMS Destination - Messages Current Count

This metric shows the current message count

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.

Target Version

Collection Frequency

Versions 7, 8, and 9.

Every 15 Minutes

JMS Destination - Messages Pending Count

This metric shows the pending message count

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

JMS Destination - Messages Received Count

This metric shows the messages received count

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

JMS Destination - Messages Received Current Count

This metric shows the current number of messages received

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

JMS Destination - Messages Received Current Count Per Second

This metric shows the current number of messages received per second

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

JMS Server Metrics

This category provides information about JMS server metrics.

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

Bytes Received (per minute)

This metric shows the number of bytes received by the selected JMS server in the past five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

Bytes Stored

This metric shows the current number of bytes stored on this JMS server.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

Destinations

This metric shows the current number of destinations defined for the selected JMS server.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

Messages Received (per minute)

This metric shows the number of messages received by this JMS server in the past five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

Messages Stored

This metric shows the current number of messages stored on the selected JMS server. This number does not include the pending messages.

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.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x, 12.1.0.x

Every 15 Minutes

After Every 60 Samples

>

Not Defined

Not Defined

-

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

Session Pools

This metric shows the current number of session pools instantiated on the selected JMS server.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

JTA Metrics

This category provides information about JTA metrics.

Abandoned Transactions (per minute)

For the selected server, this metric shows the number of transactions abandoned per minute, averaged over the past five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

Committed Transactions (%)

For the selected server, this metric shows the percentage of transactions committed over the last five minutes.

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.

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 60 Samples

<

Not Defined

Not Defined

-

The committed transaction rate is %value%%%..

Committed Transactions (per minute)

For the selected server, this metric shows the total number of transactions committed per minute, averaged over the past five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The committed transaction time is %value% seconds..

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

Transactions Processed (per minute)

For the selected server, this metric shows the number of transactions processed per minute, averaged over the past five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

Active Transactions

This metric shows the number of currently active JTA transactions on the selected server.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active JTA transactions is %value%.

JVM Metrics

This category provides information about JVM metrics.

JVM Class Loading

This metric provides information about JVM class loading metrics.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active JTA transactions is %value%.

Classes Currently Loaded

This metric shows the number of Java classes currently loaded into the selected Java Virtual Machine (JVM).

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Classes Loaded (since startup)

This metric shows the total number of Java classes that have been loaded into the Java Virtual Machine (JVM) since the JVM was started.

Compare this metric with the number of classes that have been unloaded from the JVM since it was started.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Classes Unloaded (since startup)

This metric shows the total number of Java classes that have been unloaded from the Java Virtual Machine (JVM) since the JVM was started.

Compare this metric with the number of classes that have been loaded into the JVM since it was started.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

JVM Compilation Metrics

his category provides information about JVM compilation metrics.

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The CPU usage is %value%%%.

Active Daemon Threads

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

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active daemon threads is %value%.

Heap Usage (MB)

This metric shows the current size of the Java Virtual Machine (JVM) memory heap, in megabytes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The heap usage is %value% MB.

Heap Usage (%)

This metric shows the current size of the Java Virtual Machine (JVM) memory heap, in percent.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The heap usage is %value%%%.

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

JDK Version

This metric shows the version of the Java Development Kit (JDK) that is currently in use by the selected server.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

JVM Garbage Collectors

This category provides information about JVM garbage collectors metrics.

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Garbage Collector - Garbage Collection Invocations (per min)

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

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Garbage Collector - Garbage Collection Invocation Time (ms)

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

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

JVM Memory Pools

This category provides information about JVM memory pools metrics.

Memory Pool - Current Usage (KB)

This metric shows the current memory usage (in kilobytes) of the selected Java Virtual Machine (JVM).

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Memory Pool - Current Usage (MB)

This metric shows the current memory usage (in megabytes) of the selected Java Virtual Machine (JVM).

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

JVM Memory Usage

This category provides information about JVM memory usage metrics.

Heap Memory Usage (KB)

This metric shows the total heap memory (in kilobytes) currently in use by the selected Java Virtual Machine (JVM).

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.

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 60 Samples

>

Not Defined

Not Defined

-

The heap memory usage is %value% KB

Non-Heap Memory Usage (KB)

This metric shows the total non-heap memory (in kilobytes) currently in use by the selected Java Virtual Machine (JVM).

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.

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 60 Samples

>

Not Defined

Not Defined

-

The non-heap memory usage is %value% KB

Objects Pending Finalization

This metric shows the number of objects pending finalization in the selected Java Virtual Machine (JVM).

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of objects pending finalization is %value%

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The nursery size is %value% MB.

JVM Runtime Metrics

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

VM Name

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

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

VM Version

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

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

JVM ThreadContention

This category provides information about JVM thread contention metrics.

Blocked Count

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

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.

Target Version

Collection Frequency

All Versions

Every 30 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 30 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 30 Minutes

Lock Name

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

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.

Target Version

Collection Frequency

All Versions

Every 30 Minutes

Thread State

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

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.

Target Version

Collection Frequency

All Versions

Every 30 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 30 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 30 Minutes

JVM Threads

This category provides information about JVM threads metrics.

Active Daemon Threads

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

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active daemon threads is %value%

Deadlocked Threads

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

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Peak Threads

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

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Active Threads

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

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Threads Started (since startup)

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

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Response

This category provides information about response metrics.

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 down and unavailable.

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.

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 J2EE Server instance is down

Server Metrics

This category provides information about server metrics.

Listen Port

This metric returns the port number on which the WebLogic server is listening for requests.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Active Sockets

This metric shows the current number of sockets listening on this server.

This value is equal to the number of sockets registered with the tuning muxer. For more information, see "Tuning Muxers" in Oracle Fusion Middleware Performance and Tuning for Oracle WebLogic Server.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active sockets is %value%

Start Time

This metric shows the time when the server was started.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

State

This metric shows the current state of the server as an integer. A value of "1" indicates that the server is up; a value of "2" indicates that the server is down.

This metric is used to determine the value of the Server Status metric, which is shown on the Server home page.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Server Datasource Metrics

This category provides information about server datasource metrics.

Server Datasource - Available Connections

The number of database connections currently available (not in use) in this data source.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active sockets is %value%

Server Datasource - Connections Created (per minute)

For the selected server, the number of database connections created per minute in the last five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active sockets is %value%

Server Datasource - Connections in Use

For the selected server, the number of JDBC connections currently in use by applications on the server.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active sockets is %value%

Server Datasource - Connection Pool Size

For the current server, the current count of JDBC connections in the connection pool in the data source.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active sockets is %value%

Server Datasource - Connection Requests (per minute)

The number of connection requests per minute for a connection from this data source in the last five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active sockets is %value%

Server Datasource - Successful Connections (%)

The percentage of connection requests that successfully returned connections during the last five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active sockets is %value%

Server Datasource - Connection Requests Waiting

The current number of connection requests waiting for a database connection.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active sockets is %value%

Server Datasource - Connection Requests that Waited (per minute)

The number of connection waits per minute in the last five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active sockets is %value%

Server Datasource - Connection Wait Successes (%)

The percentage of requests waiting for a connection that successfully got a connection during the last five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active sockets is %value%

Server Datasource - Connection Wait Successes (per minute)

The number of connection wait successes per minute in the last five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active sockets is %value%

Server Datasource - Statements Added to Cache (per minute)

The number of statements per minute added to the statement cache in the last five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active sockets is %value%

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active sockets is %value%

Server Datasource - Cached Statements Used (%)

The percentage of statements satisfied by the statement cache during the last five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active sockets is %value%

Server Datasource - Cached Statements Used (per minute)

The number of statements per minute satisfied by the statement cache in the last five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active sockets is %value%

Server Datasource - 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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of active sockets is %value%

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.

Server Work Manager - Work Manager Pending Requests

For the selected server, this metric shows the number of work manager requests pending in the queue.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of pending requests for work manager %name% is %value%.

Server Work Manager - 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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The work manager requests for work manager %name% are %value% (per minute).

Server Work Manager - 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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The number of work manager stuck threads is %value%.

Servlet/JSP Metrics

This category provides information about server/JSP metrics.

Servlet/JSP - Reloads (per minute)

This metric shows the average number of reloads per minute of the selected servlet or JSP in the last five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The reloads is %value% (per minute)..

Servlet/JSP - Requests (per minute)

This metric shows the average number of invocations per minute of the selected servlet or JSP in the last five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The requests processed is %value% (per minute).

Servlet/JSP - 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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

The request processing time is %value% ms.

Servlet Rollup

This category provides information about servlet rollup metrics.

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Servlet - Current Client Processing Time

This metric indicates the time taken to execute the servlet during the last interval.

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.

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

1

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 Thresholds for information on accessing the Edit Thresholds page.

Servlet - Average Execution Time

This metric indicates the average time taken by a servlet to respond.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Servlet - Total Execution Time

This metric indicates the total execution time for a request.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Servlet - Invocations Per Second

This metric indicates the number of number of requests to the server per second.

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.

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

1

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 Thresholds for information on accessing the Edit Thresholds page.

Servlet - Invocation Total Count

This metric indicates the total number of invocations for this servlet.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Web Module Metrics

This category provides information about Web module metrics.

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Web Module - Active Sessions

This metric shows the number of active sessions for the selected web module.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Java JEE Web Service Endpoints

This category provides information about Java JEE service endpoints metrics.

Dispatch Time Total

This metric shows the total amount of dispatch time since the Web service was started.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Execution Time Total

This metrics represents the total time that the Web service port has spent executing since the Web service was started.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Invocation Count

This metric represents the total number of invocations for the selected Web services port since the Web service was started.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Response Count

This metric shows the total number of responses since the Web service was started.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Response Error Count

This number provides the total number of response errors since the Web service was started.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Response Time Total

This metric represents the total response time of this Web services port since the Web service was started.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Work Manager Metrics

This category provides information about work manager metrics.

Work Manager Pending Requests

This metric shows the number of work manager requests processed per minute, averaged over the past five minutes.

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.

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 number of work manager pending requests is %value%.

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.

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.

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 work manager requests are %value% (per minute).

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.

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.

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 number of work manager stuck threads is %value%.

2 Oracle Access Manager

Oracle Enterprise Manager can be used to manage Oracle Access Manager metrics that show the performance for Oracle Access Manager 11g servers and OAM server clusters.

OAM Application Clients

Metrics related to Oracle Access Manager application domains.

Average Application Authentication Latency (ms)

This metric specifies the average latency, in milliseconds, for authorization operations in an application domain.

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.

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

>

Not Defined

Not Defined

-

Authentication Latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Application Authentication Requests per second

This metric specifies the rate of authentication requests processed, per second, in an application domain.

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.

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

>

Not Defined

Not Defined

-

Authentication Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Application Authentication Success Rate (%)

This metric specifies the success to failure ratio for authorization operations in an application domain.

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.

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

>

Not Defined

Not Defined

-

Authentication Success Rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Average Application Authorization Latency (ms)

This metric specifies the average latency, in milliseconds, for authorization requests in an application domain.

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.

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

>

Not Defined

Not Defined

-

Authorization Latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Application Authorization Requests per second

This metric specifies the rate of authorization requests, per second, for an application domain.

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.

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

>

Not Defined

Not Defined

-

Authorization Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Application Authorization Success Rate (%)

This metric specifies the success to failure ratio, as a percentage, for authorization operations in an application domain.

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.

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

>

Not Defined

Not Defined

-

Authorization Success Rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

OAM 10g Client

Metrics related to Oracle Access Manager operations in support of an OAM 10g Agent.

OAM Client Average Authentication Latency (ms)

This metric specifies the average latency, in milliseconds, of the authentication requests coming from an OAM 10g Agent.

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

OAM Client Authentication Requests per second

This metric specifies the authentication throughput (requests per second) coming from a OAM 10g Agent.

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

OAM Client Average Authorization Latency (ms)

This metric specifies the average latency, in milliseconds, for authorization requests coming from an OAM 10g Agent.

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.

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

>

Not Defined

Not Defined

-

Authorization Latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

OAM Client Authorization Requests per second

This metric specifies the authorization throughput (requests per second) coming from an OAM 10g Agent.

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.

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

>

Not Defined

Not Defined

-

Authorization Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Authorization Success Rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Oracle SSO 10g Client

Metrics related to Oracle Access Manager operations in support of an OSSO 10g Agent.

OSSO Client Average Authentication Latency (ms)

This metric specifies the average latency, in milliseconds, of authentication requests coming from an OSSO 10g agent.

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.

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

>

Not Defined

Not Defined

-

Authentication Latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

OSSO Client Authentication Requests per second

This metric specifies the authentication throughput (requests per second) coming from an OSSO 10g Agent.

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.

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

>

Not Defined

Not Defined

-

Authentication Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

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.

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.

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

>

Not Defined

Not Defined

-

Authentication Success Rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Audit Operations

Metrics related to auditing operations for Oracle Access Manager.

Average Audit Latency (ms)

This metric specifies the average latency, in milliseconds, of the audit operations for this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Audit Operations Latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Audit Operations per second

This metric specifies the audit throughput (audit operations per second) for this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Audit Operations Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Server Name

This metric specifies the name of the server performing audit operations.

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Authentication

Metrics related to Oracle Access Manager authentication operations.

Average Authentication Latency (ms)

This metric specifies the average latency, in milliseconds, of the authentication requests handled by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Authentication Latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Authentication Requests per second

This metric specifies the rate of authentication request throughput (requests per second) for this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Authentication Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Authentication Success Rate (%)

This metric specifies the success to failure rate, as a percentage, for authorization requests handled by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Authentication Success Rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Server Name

This metric specifies the name of the OAM server handling the authentication request.

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Authorization

Metrics related to Oracle Access Manager authorization operations. .

Average Authorization Latency (ms)

This metric specifies the average latency, in milliseconds, for authorization requests for this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Authorization Latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Authorization Requests per second

This metric specifies the authorization request throughput (requests per second) for this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Authorization Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Authorization Success Rate (%)

This metric specifies the authorization request throughput (requests per second) for this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Authorization Success Rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Server Name

This metric specifies the name of the server handling the authorization request.

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Token Generation Operations

Metrics pertaining to core (primitive) security token creation/generation operations for this OAM instance.

Tokens Issued

This metric specifies the total number of security tokens that were created/generated by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Token creations during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Token Issuances per second

This metric specifies the throughput of the security token creation/generation (tokens per second) by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Token creation throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Issuance Latency (ms)

This metric specifies the average latency of security token creation/generation for this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Token issue creation latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Token Validation Operations

Metrics pertaining to core (primitive) security token validation operations for this OAM instance.

Number of Tokens Validated

This metric specifies the total number of security tokens that were validated by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Token validations during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Token Validations per second

This metric specifies the throughput of security token validation (tokens per second) by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Token validation throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Token Validation Latency (ms)

This metric specifies the average latency of security token validation (in milliseconds) by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Token issue validation latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Log Operations

Metrics related to logging operations for Oracle Access Manager.

Average Log Latency (ms)

This metric specifies the average latency, in milliseconds, of the logging operations for this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Log Operations Latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Log Operations per second

This metric specifies the logging throughput (log operations per second) for this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Log Operations Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Server Name

This metric specifies the name of the server performing the logging operations for this OAM instance.

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Token Service Clients

Metrics pertaining to Security Token Service Partners for this OAM instance.

Issuance Latency (ms)

This metric specifies the average latency of processing security token issuance requests received from a partner by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Partner token issue latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Tokens Issued

This metric specifies the total count of security token issuance requests received from a partner by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Partner token requests during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

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.

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.

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

>

Not Defined

Not Defined

-

Partner token issue request throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

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.

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.

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

>

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.

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.

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.

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

>

Not Defined

Not Defined

-

Partner token validation success rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Token Validation Latency (ms)

This metric specifies the average latency of processing security token validation requests from a partner by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Partner token validation latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold .

Number of Tokens Validated

This metric specifies the total number of security token validation requests received from a partner by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Partner token validation requests during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Token Validations per second

This metric specifies the throughput of the processing security token validation requests from a partner by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Partner token validation request throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Response

Response metrics represent the availability of the selected OAM instance.

UpDown Status

This metric shows the availability of this OAM instance.

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.

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 Oracle Access Manager is down.  .

Token Requests

Metrics related to Oracle Access Manager security tokens for this OAM instance.

Issuance Latency (ms)

This metric specifies the latency of the security token issuance request processing (in milliseconds) for this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Token issue request latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Tokens Issued

This metric specifies the total number of security token issuance requests processed by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Token issue requests during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Token Issuances per second

This metric specifies the throughput of the security token issuance (requests per second) by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Token issue request throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Issuance Success Rate (%)

This metric specifies the success to failure ratio, as a percentage, for security token issuance requests by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Token issue request success rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Token Validation Latency (ms)

This metric specifies the average latency of the security token validation request processing (in milliseconds) by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Token validation request latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Number of Tokens Validated

This metric specifies the total number of security token validation requests processed by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Token validation requests during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Token Validations per second

This metric specifics the throughput of the security token validation request processing (in milliseconds) by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Token validation request throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Validation Success Rate (%)

This metric specifies the success to failure ratio, as a percentage, for security token validation request processing by this OAM instance.

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.

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

>

Not Defined

Not Defined

-

Token validation request success rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

LDAP Operations

Metrics related to Oracle Access Manager user identity operations.

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.

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.

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

>

Not Defined

Not Defined

-

LDAP Operations Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

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.

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.

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

>

Not Defined

Not Defined

-

LDAP Operation Latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold .

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.

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.

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

>

Not Defined

Not Defined

-

LDAP Operations Success Rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Server Name

This metric identifies the name of the server performing user identity operations.

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

3 Oracle Access Manager Cluster

Oracle Enterprise Manager can be used to manage Oracle Access Manager metrics that show the performance for Oracle Access Manager 11g servers and OAM server clusters.

OAM Applications Domains (Aggregated)

Metrics for OAM application domains in the cluster.

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.

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.

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

>

Not Defined

Not Defined

-

Authentication Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Application Authentication Requests per second

This metric specifies the authentication throughput (requests per second) in this application domain for OAM instances in the cluster.

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.

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

>

Not Defined

Not Defined

-

Authentication Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Authentication Success Failure Ratio during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Authorization Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Authorization Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Authorization Success Failure Ratio during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

OAM 10g Aggregates

Metrics for all OAM 10g agents related to OAM Instances in the cluster.

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.

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.

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

>

Not Defined

Not Defined

-

Authorization Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Authorization Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Authorization Success Failure Ratio during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Authorization Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Authorization Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Authorization Success Failure Ratio during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

OAM 10g Throughput (Aggregated)

Metrics for OAM 10g agents related to OAM Instances in the cluster.

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.

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

OSSO 10g (Aggregated)

Metrics related to OSSO 10g Agents across the OAM cluster.

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.

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.

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

>

Not Defined

Not Defined

-

Authentication Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Authentication Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Authentication Success Failure Ratio during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

OSSO 10g Throughput (Aggregated)

Metrics for OSSO agents communicating with OAM instances in the cluster.

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.

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Audit Operations (Aggregated)

Metrics related to auditing operations for Oracle Access Manager servers in the cluster.

Average Audit Latency (ms)

This metric specifies the average latency, in milliseconds, of the audit operations for all OAM instances in the cluster.

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.

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

>

Not Defined

Not Defined

-

Audit Operations Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Audit Operations per second

This metric specifies the rate of audit operation (per second) for all OAM instances in the cluster.

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.

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

>

Not Defined

Not Defined

-

Audit Operations Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Audit Operations Throughput (Aggregated)

Metrics related to auditing operations for Oracle Access Manager across the cluster.

Operations per second

This metric specifies the audit throughput (audit operations per second) for all OAM instances in the cluster.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Authentication Aggregates

Metrics for aggregated authentication operations with Oracle Access Manager.

Average Authentication Latency (ms)

This metric specifies the average latency, in milliseconds, for authentication requests handled by all OAM instances in the cluster.

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.

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

>

Not Defined

Not Defined

-

Authentication Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Authentication Requests per second

This metric specifies the authentication throughput (requests per second) for all OAM instances in the cluster.

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.

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

>

Not Defined

Not Defined

-

Authentication Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Authentication Success Failure Ratio during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Authentications Throughput (Aggregated)

Metrics representing aggregated authentication throughput for requests handled by all OAM instances in the cluster.

Authentication Requests per second

This metric specifies the rate of authentication request throughput (requests per second) for all OAM instances in the cluster.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Authorizations (Aggregated)

Metrics related to authorization operations performed by Oracle Access Manager instances in the cluster.

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.

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.

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

>

Not Defined

Not Defined

-

Authorization Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Authorization Requests per second

This metric specifies the rate of authorization request throughput (requests per second) for all OAM instances in the cluster.

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.

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

>

Not Defined

Not Defined

-

Authorization Requests Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Authorization Success Failure Ratio during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Authorizations Throughput (Aggregated)

Metrics related to authorization operations aggregated across all OAM instances in the cluster.

Authorization Requests per second

This metric specifies the authorization request throughput (requests per seconds) handled by all OAM instances in the cluster.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Core Token Generation Operations

Metrics pertaining to core token operations in the cluster.

Number of Tokens Issued

This metric specifies the total number of security tokens created/generated. This value has been aggregated across all OAM instances in the cluster.

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.

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

>

Not Defined

Not Defined

-

Token creations during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Tokens Issued per second

This metric specifies the average latency of security token creation/generation. This value has been aggregated across all OAM instances in the cluster.

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.

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

>

Not Defined

Not Defined

-

Token creation throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Token Issuance Latency (ms)

This metric specifies the average latency of security token creation/generation. This value has been aggregated across all OAM instances in the cluster.

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.

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

>

Not Defined

Not Defined

-

Token issue creation latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Core Token Validation Operations

Metrics related to core token validation in the cluster.

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.

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.

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

>

Not Defined

Not Defined

-

Token validations during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Token validation throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Token issue validation latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Log Operations (Aggregated)

Metrics related to logging operations for Oracle Access Manager instances within the cluster.

Average Latency (ms)

This metric specifies the average latency, in milliseconds, of the logging operations for all OAM instances in the cluster.

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.

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

>

Not Defined

Not Defined

-

Log Operations Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Log Operations per second

This metric specifies the logging operations throughput (per second) for all OAM instances in the cluster.

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.

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

>

Not Defined

Not Defined

-

Log Operations Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Log Operations Throughput (Aggregated)

Metrics related to logging operations for Oracle Access Manager.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Token Service Clients

Metrics pertaining to Token Service partners for all OAM Instances in the cluster.

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.

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.

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

>

Not Defined

Not Defined

-

Partner token issue latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Partner token requests during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Partner token issue request throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

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

Requester

This metric specifies the name of a requester partner. This value has been aggregated across all OAM instances in the cluster.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

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

>

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

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.

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.

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

>

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

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.

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.

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

>

Not Defined

Not Defined

-

Partner token validation requests during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Partner token validation request throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Response

Response metrics represent the availability of the selected instance.

Status

This metric specifies the availability of this OAM server cluster.

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.

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 Oracle Access Manager instance is down

Token Issuances

Metrics related to security token issuance requests aggregated across all OAM instances in the cluster.

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.

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.

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

>

Not Defined

Not Defined

-

Token issue request latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Token issue requests during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Token issue request throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Token issue request success rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Token validation request latency (ms) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Token validation requests during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Token validation request throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

Token validation request success rate (%) during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

LDAP Operations (Aggregated)

Metrics for all LDAP operations for all OAM instances in the cluster.

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.

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.

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

>

Not Defined

Not Defined

-

LDAP Operations Throughput during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

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

>

Not Defined

Not Defined

-

LDAP Operation Latency during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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

>

Not Defined

Not Defined

-

LDAP Operations Success Failure Ratio during the last collection Interval %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

4 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.

Datasource Metrics

This category of metrics provides information about the connection metrics.

Available Connections

For the selected datasource, this metric shows the number of database connections currently available (not in use).

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.

Connections in Use

This metric shows the number of data source connections that are currently in use by applications.

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.

Connection Pool Size

This metrics shows the average number of database connections created for this datasource per minute in the last 5 minutes.

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.

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.

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.

Successful Connections (%)

This metric shows the percentage of requests that successfully returned connections for this datasource over the last 5 minutes.

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.

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.

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.

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.

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.

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.

Datasource - State

This metric shows the current state of the 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.

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.

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.

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.

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.

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.

EJB Module Metrics

These metrics provide information about the EJB home over the last 5 minutes.

Cached Beans

This metric shows the total number of beans from this EJB Home that are currently in the EJB cache.

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.

Cache Hits (%)

This metric shows the percentage of cache accesses that completed successfully in the last 5 minutes.

Cache Misses (per minute)

This metric shows the average number of cache misses per minute for this EJB module in the last 5 minutes.

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.

Bean Access Successes (%)

This metric shows the percentage of EJB pool accesses that were successful in the last 5 minutes.

Free Bean Instances

This metric shows the current number of available EJB instances in the free pool.

Bean Destroys (per minute)

This metric shows the average number of EJB destroys per minute for this EJB module over the last 5 minutes.

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.

Beans in Use

This metric shows the number of EJB instances currently being used from the free pool.

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.

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.

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.

EJB Transaction Metrics

These metrics show the transaction information for this EJB over the last 5 minutes.

Bean Transaction Commits (%)

This metric shows the EJB transaction commits per minute, averaged over the past five minutes.

Bean Transaction Commits (per minute)

This metric shows the EJB transaction commits per minute, averaged over the past five minutes.

Bean Transaction Rollbacks (per minute)

This metric shows the EJB transaction rollbacks per minute, averaged over the past five minutes.

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.

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.

Cached Beans

This metric shows the total number of EJBs currently active in the EJB cache.

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.

Bean Activations (per minute)

This metric shows the average number of Enterprise Java Beans activated per minute over the last 5 minutes.

Cache Hits (%)

This metrics indicates the percentage of cache accesses that completed successfully in the last 5 minutes.

Cache Misses (per minute)

This metric shows the number of EJB cache misses per minute in the last 5 minutes.

Bean Accesses (per minute)

This metrics shows the average number of Pool accesses per minute for the selected server in the last 5 minutes.

Bean Successes (%)

For the selected server, this metric displays the percentage of EJB pool accesses that were successful in the last 5 minutes.

Free Bean Instances

For the selected server, this metric indicates the current number of available Java bean instances in the free pool.

Bean Destroys (per minute)

This metric shows the average number of EJB destroys per minute for the selected server in the last 5 minutes.

Bean Access Failures (per minute)

This metric shows the percentage of pool accesses to the server that were successful in the last 5 minutes.

Beans in Use

This metric shows the number of EJB instances currently being used from the free pool.

Bean Transaction Commits (%)

For the selected server, this metric identifies the EJB transaction commits per minute for the last 5 minutes.

Bean Transaction Commits (per minute)

For the selected server, this metric identifies the EJB transaction commits per minute for the last 5 minutes.

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.

Bean Transaction Timeouts (per minute)

This metric shows the EJB transaction timeouts per minute for the last 5 minutes on the selected server.

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.

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.

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.

Active Sessions

The number of active sessions for the selected OAAM server.

Work Manager Pending Requests

For the selected server, this metric shows the number of work manager requests pending in the queue.

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.

Servlet/JSP Metrics

These metrics provide information about the selected servlet or JSP per minute over the last 5 minutes.

Reloads (per minute)

This metric shows the average number of reloads of the selected servlet or JSP per minute over the last 5 minutes.

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.

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).

Web Module Metrics

These metrics provide information for the selected 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.

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.

Active Sessions

This metric shows the number of active sessions for this web module.

Login Metrics Summary

This category of metrics provides status and performance data related to OAAM server login requests.

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.

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

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.

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.

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

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.

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.

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

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.

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.

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

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.

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.

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

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.

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.

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

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.

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.

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

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.

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.

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

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.

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.

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

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.

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.

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

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.

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.

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

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.

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.

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.

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total Number of Policies Processed

This metric captures the total number of policies that completed processing.

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total Number of Policies Processed since Last Sample

This metric captures the total number of policies processed at the end of the sampling interval.

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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).

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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).

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Response

This category of metrics indicates whether the target OAAM Server is available.

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.

Rule Execution Summary

The category of metrics that pertain to rule execution.

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.

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

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.

Total Number of Requests Completed

This metric captures the total number of rules processed.

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

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.

Total Number of Requests Completed Since Last Sample

This metric captures the total number of rules processed since the last sample.

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

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.

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.

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

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.

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.

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

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.

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.

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

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.

Checkpoint Execution Summary

This metric presents a summary of the time spent to execute all the policies in a checkpoint.

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."

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

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.

Total Number of Checkpoints Completed

This metric captures the total number of checkpoints executed.

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

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.

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.

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

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.

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.

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

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.

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.

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

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.

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.

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

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.

Update Authorization Status Summary

This category of metrics provides information related to updates in user authorization status.

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.

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

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.

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.

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

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.

Total Number of Requests Completed Since Last Sample

This metric captures the total number of updateAuthStatus() API calls since the last sample.

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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

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.

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.

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

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.

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.

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

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.

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.

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.

Total Number of Requests Completed

This metric captures the total number of times the "updateLog()" API Call was executed.

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.

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.

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.

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.

5 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.

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.

JDBC URL

This metric provides information about the database connections of the OAAM server instances in the OAAM cluster.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

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.

Blocked Logins Rate (%)

This metric represents the aggregate percentage of login requests to the OAAM servers in the OAAM cluster that were blocked.

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 5-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

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.

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 5-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

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.

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 5-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

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.

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 5-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

Failed Logins Rate (%)

This metric represents the aggregate percentage of login requests to the OAAM servers in the OAAM cluster that have failed.

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 5-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

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.

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 5-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

Successful Logins Rate (%)

This metric specifies the aggregate percentage of login requests to the OAAM servers in the OAAM cluster that were successful.

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 5-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

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.

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 5-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

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.

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 5-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

Login Metrics Rate Summary

This category of metrics represents the status and performance of the logins to the OAAM servers in the OAAM cluster.

Failed Logins per second

This metric represents the aggregate number of failed login requests per second to the OAAM servers in the OAAM cluster.

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 5-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

Successful Logins per second

This metric represents the aggregate number of successful login requests per second for the OAAM servers in the OAAM cluster.

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 5-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

Response

This category of metrics represents the status and performance of the OAAM servers in the OAAM cluster.

Status

This metric represents the current status of the OAAM Servers in the OAAM cluster.

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 5-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

6 Oracle Identity Manager

This chapter describes the Oracle Identity Manager metrics.

Oracle Adaptive Metrics

This category of metrics provides information on Adapter metrics.

Adapter Name

The name of the adapter.

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.

Target Version

Collection Frequency

All Versions

Every 600 Seconds

Average Adapter Execution Time (ms)

The average time in milliseconds to execute an adapter in the last five minutes.

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.

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 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

Average Adapter Execution Time (ms) %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Completed Adapter Executions

The total number of completed adapter executions in the last five minutes.

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.

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 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

Completed Adapter Executions %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold..

Maximum Adapter Execution Time (ms)

The maximum time in milliseconds to execute an adapter in the last five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 600 Seconds

Minimum Adapter Execution Time (ms)

The minimum time in milliseconds to execute an adapter in the last five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 600 Seconds

Datasource Metrics

This section provides details on the datasource metrics.

Datasource - Available Connections

This metric shows the number of database connections currently available (not in use) for this data source.

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 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 600 Seconds

After Every Sample

<

Not Defined

Not Defined

-

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

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.

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 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 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

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

Datasource - Connections in Use

This metric shows the number of data source connections that are currently in use by applications.

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 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 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

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

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.

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 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 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

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

Datasource - Connection Pool Size

This metric shows the current number of JDBC connections in the connection pool in the selected data source.

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 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

-

The connection pool size is %value%.

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.

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 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 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

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

Datasource - Connection Request Failures (per minute)

This metric shows the average number of failed connection requests per minute in the last five minutes.

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 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 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

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

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.

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 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 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

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

Datasource - Successful Connections (%)

This metric shows the percentage of requests that successfully returned connections for this data source over the last five minutes.

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 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 600 Seconds

After Every Sample

<

Not Defined

Not Defined

-

The successful connection rate for datasource %name% is %value%%%.

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.

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 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 600 Seconds

After Every Sample

>

Not Defined

Not Defined

-

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

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.

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 6-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%.

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.

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 6-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).

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.

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 6-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).

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.

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 6-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%%%.

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.

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 6-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).

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

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 6-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%.

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.

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 6-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).

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.

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 6-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).

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.

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 6-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).

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.

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 6-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%%%.

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.

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 6-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).

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.

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 6-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%.

EJB Module Metrics

This section provides details on the EJB module metrics.

Cached Beans

This metric shows the total number of beans from this EJB Home that are currently in the EJB cache.

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 6-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%.

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.

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 6-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).

Cache Hits (%)

This metric shows the percentage of cache accesses that completed successfully in the last 5 minutes.

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 6-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%%%.

Cache Misses (per minute)

This metric shows the average number of cache misses per minute for this EJB module in the last 5 minutes.

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 6-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).

Bean Accesses (per minute)

This metric shows the average EJB pool accesses per minute over the last 5 minutes.

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 6-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).

Bean Access Successes (%)

This metric shows the percentage of EJB pool accesses that were successful in the last 5 minutes.

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 6-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%%%.

Free Bean Instances

This metric shows the current number of available EJB instances in the free pool.

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 6-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%.

Bean Destroys (per minute)

This metric shows the average number of EJB destroys per minute for this EJB module over the last 5 minutes.

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 6-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).

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.

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 6-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).

Beans in Use

This metric shows the number of EJB instances currently being used from the free pool.

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 6-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%.

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.

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 6-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).

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.

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 6-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).

Bean Destroys (per minute)

This metric shows the average number of EJB destroys per minute for this EJB module over the last 5 minutes.

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 6-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).

EJB Transaction Metrics

This section provides details on the EJB transaction metrics.

Bean Transaction Commits (%)

This metric shows the percentage of EJB transactions that were committed for the select EJB over the last 5 minutes.

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 6-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%%%.

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.

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 6-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).

Bean Transaction Rollbacks (per minute)

This metric shows the average number of transaction rollbacks per minute for this EJB over the last 5 minutes.

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 6-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).

Bean Transaction Timeouts (per minute)

This metrics shows the average number of transaction timeouts per minute for this EJB over the last 5 minutes.

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 6-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).

Overview Metrics

This section provides details on the overview metrics.

Cached Beans

This metrics shows the total number of EJBs currently active in the EJB cache.

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 6-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

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.

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 6-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

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.

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 6-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

Cache Hits (%)

This metrics indicates the percentage of cache accesses that completed successfully in the last 5 minutes.

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 6-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

Cache Misses (per minute)

This metric shows the average number of EJB cache misses per minute in this application in the last 5 minutes.

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 6-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

Bean Accesses (per minute)

This metric shows the average EJB pool accesses per minute over the last 5 minutes.

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 6-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

Bean Successes (%)

This metric shows the percentage of EJB pool accesses that were successful for this application in the last 5 minutes.

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 6-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

Free Bean Instances

This metric shows the current number of available EJB instances in the free pool.

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 6-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

Bean Destroys (per minute)

This metric shows the average number of EJB destroys per minute for this application in the last 5 minutes.

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 6-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

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.

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 6-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

Beans in Use

This metric shows the number of EJB instances currently being used from the free pool.

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 6-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

Bean Transaction Commits (%)

This metric shows the percentage of EJB transactions that were committed for this application during the last 5 minutes.

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 6-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

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.

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 6-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

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.

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 6-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

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.

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 6-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

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.

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 6-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

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.

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 6-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

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.

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 6-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

Active Sessions

This metric shows the number of active sessions for this application.

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 6-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

Work Manager Pending Requests

This metric shows the number of Work Manager requests waiting in the queue.

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 6-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

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.

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 6-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

Servlet/JSP Metrics

This category of metrics provides information on Servlet/JSP metrics.

Reloads (per minute)

This metric shows the average number of reloads of the selected servlet or JSP per minute over the last 5 minutes.

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 6-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).

Requests (per minute)

This metrics shows the average number of invocations of the selected servlet or JSP per minute over the last 5 minutes.

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 6-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).

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.

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 6-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.

Web Module Metrics

This category of metrics provides information on web module metrics.

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.

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.

Active Sessions

This metric shows the number of active sessions for this web module.

Events Handler

This category of metrics provides information on events handler metrics.

Average Events Execution Time (ms)

The average time in milliseconds to process an event handler in the last 5 minutes.

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 6-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.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Completed Events Executions

The total number of completed event handler executions in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

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 6-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.

Maximum Events Execution Time (ms)

The maximum time in milliseconds to process an event handler in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Minimum Events Execution Time (ms)

The minimum time in milliseconds to process an event handler in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Java JEE Web Service Endpoints

This category of metrics provides information on Java JEE Web Service Endpoint metrics.

Dispatch Time Total

This metric shows the total amount of dispatch time since the Web service was started.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Execution Time Total

This metrics represents the total time that the Web service port has spent executing since the Web service was started.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Invocation Count

This metric represents the total number of invocations for the selected Web services port since the Web service was started.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Response Count

This metric shows the total number of responses since the Web service was started.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Response Error Count

This number provides the total number of response errors since the Web service was started.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Response Time Total

This metric represents the total response time of this Web services port since the Web service was started.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

JMS Queue

This category of metrics provides information on JMS Queue metrics.

Average Processing Time (ms)

The average time in milliseconds to process a JMS message in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Number of Processed Messages

The total number of processed JMS messages in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Maximum Processing Time (ms)

The maximum time in milliseconds to process a JMS message in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Minimum processing Time (ms)

The minimum time in milliseconds to process a JMS message in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

MDS Metrics

This category of metrics provides information on MDS metrics.

Metadata Object Gets Per Second

The number of metadata object gets per second.

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.

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.

Metadata Object Get Processing Time (seconds)

The average elapsed time in seconds to get a metadata object.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Metadata Updates Per Second

The average number of metadata objects updated per second.

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.

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).

Metadata Update Processing Time (seconds)

The average elapsed time in seconds taken to update a metadata object.

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.

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).

Executions and Messages

This category of metrics provides information on executions and messages metrics.

Total Adapter Executions

The total number of all adapter executions in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Total Events Handler Executions

The total number of all event handler executions in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Total JMS Messages

The total number of all processed JMS messages in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

SPML Web Services

This category of metrics provides information on SPML Web service metrics.

Average Response Time (ms)

The average time in milliseconds taken to respond to SPML requests in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Incoming Calls

The total number of SPML calls made in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Response

This category of metrics represents the status and performance of the OAAM servers in the OAAM cluster.

Status

This metric represents the current status of the OAAM Servers in the OAAM cluster.

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 6-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

7 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.

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.

Active Sessions

The number of active Presentation Services sessions.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Bad Requests

The total number of bad requests.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Completed Requests

The total number of requests completed.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Completed Requests/sec

The number of requests completed each second.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Current Requests

The current number of requests being processed.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Failed Requests

The total number of failed requests.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

GET Requests Throughput

The number of GET requests completed each second.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

GET Requests

The total number of GET requests completed.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

GET/POST Requests Throughput

The number of GET/POST requests completed each second.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

GET/POST Requests

The total number of GET/POST requests completed.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Long Requests

The total number of long running requests.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Peak Requests

The peak number of requests concurrently being processed.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

POST Requests Throughput

The number of POST requests completed each second.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

POST Requests

The total number of POST requests completed.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

SOAP Requests Throughput

The number of SOAP requests completed each second.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

SOAP Requests

The total number of SOAP requests completed.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

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.

Active sessions

The number of active sessions for all Oracle BI Presentation Services components in the BI cluster.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Completed Requests/sec

The number of requests completed each second for all Oracle BI Presentation Services components in the BI cluster.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Current Requests

The current number of requests being processed across all Oracle BI Presentation Services components in the BI cluster.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Failed Requests

The total number of failed requests across all Oracle BI Presentation Services components in the BI cluster.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

GET/POST Throughput

The number of GET/POST requests completed each second for all Oracle BI Presentation Services components in the BI cluster.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

SOAP Throughput

The number of SOAP requests completed each second for all Oracle BI Presentation Services components in the BI cluster.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Oracle BI Aggregation

This category shows performance information and metrics for all Oracle BI Server components in the BI cluster.

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Queries/sec

The number of queries completed each second by all Oracle BI Servers across the BI cluster during the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Total sessions

The total number of sessions that connected clients to all Oracle BI Servers across the BI cluster during the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Oracle BI Data Cache

This category shows performance information about the Oracle BI Server query cache.

Hit Ratio as %

The percentage of hits for the Oracle BI data cache during the sampling period.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Hits/sec

The number of times each second that a query was satisfied from the data cache during the sampling period.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Qualified queries misses / second

The number of times each second a qualified query was not satisfied from the data cache during the sampling period.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Oracle BI DB Connection Pool

This category provides information about the database connection pools used by Oracle Business Intelligence.

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Accumulated Requests

The total number of requests that have been submitted to the given database connection pool.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Capacity

The maximum number of connections that the given database connection pool allows.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Current Busy Connection Count

The current number of connections assigned to process a query in the given database connection pool.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Current Connection Count

The current number of open connections in the thread pool.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Current Queued Requests

The number of requests that are currently queued, waiting for a connection to become available.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Current Queued Time (ms)

The number of milliseconds that the request that is next in line for processing has waited in queue.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Lowest Queued Requests

The smallest number of requests that have been in queue since the server was started.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Lowest Queued Time (ms)

The smallest number of milliseconds that a request has had to wait in queue since the server was started.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Peak Busy Connection Count

The maximum number of connections assigned to process a query during the lifetime of the given database connection pool.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Peak Connection Count

The maximum of number of open connections during the lifetime of the thread pool.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Peak Queued Requests

The peak number of requests that have been in queue since the server was started.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Peak Queued Time (ms)

The peak number of milliseconds that a request has had to wait in queue since the server was started.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Oracle BI General

This category shows performance information and metrics for the given Oracle BI Server.

Active Execute Requests

The number of execute requests active within the Oracle BI Server at the end of the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Active Fetch Requests

The number of fetch requests active within the Oracle BI Server at the end of the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Active Initblock Executions

The number of initialization block requests active within the Oracle BI Server at the end of the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Active Logins

The number of active logins within the Oracle BI Server at the end of the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Active Prepare Requests

The number of query prepare requests active within the Oracle BI Server at the end of the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Avg. Failed Logins Elapsed Time

The average elapsed time, in seconds, for failed logins that completed during the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Avg. Initblock Executions Elapsed Time

The average elapsed time, in seconds, for the execution of initialization blocks that completed during the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Avg. Succeeded Logins Elapsed Time

The average elapsed time, in seconds, for successful logins that completed during the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Busy File Handles

The number of file handles currently being written to or being read from.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

File Handle Waiters

The number of objects waiting for a file handle to become available.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Free File Handles

The number of available file handles in the file handle pool.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Max File Handles

The peak number of concurrently running file handles since the server was started.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

New Execute Requests

The number of new execute requests received by the Oracle BI Server during the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

New Fetch Requests

The number of new fetch requests received by the Oracle BI Server during the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

New Initblock Executions

The total number of new initialization block requests received by the Oracle BI Server during the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

New Logins

The total number of new login requests received by the Oracle BI Server during the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

New Prepare Requests

The number of new query prepare requests received by the Oracle BI Server during the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

New Requests

The total number of new requests received by the Oracle BI Server during the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Queries/sec

The number of queries completed per second by the Oracle BI Server during the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Succeeded Initblock Execution Ratio as %

The percentage of initialization block requests that succeeded during the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Succeeded Logins Ratio as %

The percentage of logins that succeeded during the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Total sessions

The total number of sessions that connected clients to the Oracle BI Server during the sampling interval.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

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

Average hits / second

The average number of hits each second for the specified cache object during the sampling interval.

Average misses / second

The average number of misses each second for the specified cache object during the sampling interval.

Average new entries / second

The average number of entries added each second to the specified cache object during the sampling interval.

Average replacements / second

The average number of entries deleted each second from the specified cache object during the sampling interval.

Average requests / second

The average number of requests each second against the specified cache object during the sampling interval.

Capacity

The total capacity of the specified cache object.

Total requests

The total number of requests during the sampling interval against the specified cache object.

Utilization ratio as %

The percentage of the specified cache object in use.

Oracle BI LDAP Authentication

This category shows performance information and metrics for LDAP requests. Only legacy custom LDAP server requests are included.

Active LDAP Requests

The number of active LDAP authentication requests received by the Oracle BI Server during the sampling interval.

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.

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.

LDAP Requests Cache Hit Ratio as %

The percentage of LDAP authentication requests that successfully hit the LDAP cache during the sampling period.

New Impersonated LDAP Requests

The total number of new impersonated LDAP authentication requests received by the Oracle BI Server during the sampling interval.

New LDAP Requests

The total number of new LDAP authentication requests received by the Oracle BI Server during the sampling interval.

Succeeded LDAP Requests Ratio as %

The percentage of LDAP authentication requests that succeeded during the sampling interval.

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.

Active Executes

The number of outstanding executes that remain at the given physical database at the end of the sampling interval.

Active Fetches

The number of outstanding fetches that remain at the given physical database at the end of the sampling interval.

Active Prepares

The number of outstanding prepares that remain at the given physical database at the end of the sampling interval.

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.

Failed Queries/sec

The number of queries that failed each second in the given physical database during the sampling interval.

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.

New Executes

The number of executes sent to the given physical database during the sampling interval.

New Fetches

The number of fetches sent to the given physical database during the sampling interval.

New Prepares

The number of prepares sent to the given physical database during the sampling interval.

Queries/sec

The number of queries completed each second by the given physical database during the sampling interval.

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.

Oracle BI PS Caches

This category provides information about caches within Oracle BI Presentation Services.

Cache Hits

The number of requests satisfied by the cache.

Cache Misses

The number of requests not satisfied by the cache.

Cache Stale

The number of requests satisfied by the cache, but stale.

Cleanups

The number of cleanup passes that have finished.

Current Entries

The current number of entries in this cache.

Peak Entries

The peak number of entries in this cache.

Oracle BI PS Catalog Access

This category provides information related to Oracle BI Presentation Catalog access.

Attribute Retrievals

The number of item attributes retrieved.

Create Folders

The number of folders created.

Create Links

The number of links created.

Delete Items

The number of items deleted.

Read Objects

The number of objects read.

Searches

The number of searches performed.

Write Objects

The number of objects written.

Write Objects Successfully

The number of successful writes.

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.

Cache Hits

The total number of requests satisfied by the attribute cache.

Cache Misses

The total number of requests not satisfied by the attribute cache.

Cache Stale Misses

The total number of requests that missed cache because the cache entry had expired.

Current Cache Entries

The current number of entries in the attribute cache.

Peak Cache Entries

The peak number of entries in the attribute cache.

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.

Cache Hits

The total number of chart requests retrieved from the chart cache.

Charts Submitted/sec

The number of charts submitted for creation each second. This does not include chart requests satisfied by the chart cache.

Current Cached Charts

The current number of entries in the chart cache. This includes finished, queued, and running charts in the cache.

Current Charts Queued

The current number of charts waiting in queue for processing.

Current Running Charts

The number of charts that are currently being processed. This does not include charts waiting in queue for processing.

Peak Cached Charts

The peak number of entries in the chart cache.

Peak Charts Queued

The peak number of charts concurrently waiting in queue for processing.

Peak Running Charts

The peak number of charts being concurrently processed.

Total Charts Rejected

The total number of chart requests rejected because the maximum allowed queued number of charts was reached.

Total Charts Submitted

The total number of charts submitted for creation. This does not include chart requests satisfied by the chart cache.

Oracle BI PS Connection Pool

This category provides information related to connections established from Oracle BI Presentation Services to the Oracle BI Server.

Current Authentications

The current number of Oracle BI Server connections in the process of being authenticated and established.

Current Open Connections

The current number of open Oracle BI Server connections.

New Connections/sec

The number of Oracle BI Server connections established each second.

Peak Authentications

The peak number of Oracle BI Server connections being concurrently authenticated and established.

Peak Open Connections

The peak number of open Oracle BI Server connections.

Total Connections

The total number of Oracle BI Server connections established.

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.

Total Rejected

The total number of Oracle BI Server connection requests rejected because too many connections were in the process of being established.

Oracle BI PS DirectorySearches

This category provides information related to Oracle BI Presentation Services directory searches.

Total Search Start Requests

The total number of requests to start searching a directory.

Total Search Stop Requests

The total number of requests to stop searching a directory.

Total Searches Started

The total number of directory searches started.

Total Searches Stopped

The total number of directory searches stopped.

Oracle BI PS DXE

This category provides information related to the Oracle BI Presentation Data Exchange Engine (DXE).

Total Actual Aggregate Queries Compiled

The total number of queries compiled as Aggregate type.

Total Actual Cube Queries Compiled

The total number of queries compiled as Cube type.

Total Actual Expression Queries Compiled

The total number of queries compiled as Expression type.

Total Actual Presort Cube Queries Compiled

The total number of queries compiled as Presort Cube type.

Total Actual Presort Table Queries Compiled

The total number of queries compiled as Presort Table type.

Total Actual Regular Queries Compiled

The total number of queries compiled as Regular type.

Total Actual Union Queries Compiled

The total number of queries compiled as Union type.

Total Input Aggregate Query Requests

The total number of requests to process Aggregate type queries.

Total Input Cube Query Requests

The total number of requests to process Cube type queries.

Total Input Regular Query Requests

The total number of requests to process Regular type queries.

Total Input Union Query Requests

The total number of requests to process Union type queries.

Total Order By Requests

The total number of queries that requested Order By.

Total Order By Requests Optimized Away

The total number of queries with Order By requests that were optimized away.

Total Query Requests

The total number of requests to process queries.

Oracle BI PS File Accesses

This category provides information related to file access within Oracle BI Presentation Services.

Current Open Files

The current number of open files.

Peak Open File

The peak number of open files.

Total Files

The total number of files that have been opened.

Total Files/sec

The number of files that have been opened each second.

Oracle BI PS HTTP Socket Pool

This category provides information related to Oracle BI Presentation Services HTTP 1.1 socket usage.

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.

Total Closed Exception

The total number of sockets closed because of an exception.

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.

Total Closed HTTP

The total number of sockets closed because the HTTP protocol requested explicit closure.

Total Closed Outstanding

The total number of sockets that could not be reused because their response was not fully consumed.

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.

Total Closed Unknown

The total number of sockets that were closed for no known reason.

Total Endpoints

The total number of distinct HTTP servers that are, or have been, the target of HTTP requests.

Total New sockets

The total number of sockets created.

Total Reused

The total number of socket requests satisfied by reusing an existing socket.

Oracle BI PS JavaHost Proxy Requests

This category provides information about the JavaHost proxy requests, used for PDF, charts, and so on.

Requests to Generate Briefing Books

The current number of requests to generate Briefing Books.

Requests to Generate PDFs

The current number of requests to generate PDFs.

Requests to Generate Powerpoints

The current number of requests to generate a Powerpoint presentation.

Oracle BI PS Metadata

This category provides information related to metadata retrieved by Oracle BI Presentation Services from the Oracle BI Server.

Current Subject Areas

The current number of subject areas loaded in memory.

Peak Subject Areas

The peak number of subject areas loaded in memory.

Subject Area Loads/sec

The number of subject areas loaded each second.

Total Subject Area Loads

The total number of subject areas loaded.

Oracle BI PS Query Cache

This category provides information about the Oracle BI Presentation Services cache for Oracle BI Server queries.

Cache Clean Ups/sec

The number of query cache cleanup jobs run each second.

Cache Hits/sec

The number of cache hits each second.

Canceled Queries/sec

The number of queries each second that have been returned as canceled by the Oracle BI Server.

Current Cache Entries

The current number of entries in the Presentation Services query cache.

Current Query Preps

The number of query preparations currently being executed against the Oracle BI Server.

Current Query Preps Cache Size

The current number of entries in the query preparation cache.

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.

Current Queued Queries

The number of queries that are currently queued waiting for execution against the Oracle BI Server.

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.

Current Running Queries

The number of queries that are currently being executed against the Oracle BI Server.

Errored Queries/sec

The number of queries each second that have failed to execute against the Oracle BI Server.

New Queries/sec

The number of new queries that have been attempted each second.

Peak Cache Entries

The peak number of entries concurrently in the Presentation Services query cache.

Peak Query Preps

The peak number of concurrent query preparations being executed against the Oracle BI Server.

Peak Query Preps Cache Size

The peak number of entries in the query preparation cache.

Peak Queued Immediate Queries

The peak number of immediate queries concurrently queued waiting for execution. Immediate queries bypass the Presentation Services query cache.

Peak Queued Queries

The peak number of queries concurrently queued waiting for execution.

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.

Peak Running Queries

The peak number of concurrently running queries against the Oracle BI Server.

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.

Query Piggybacks/sec

The number of queries each second that have 'piggybacked' off of an equivalent running query.

Query Preps Errors/sec

The number of query preparations that failed each second.

Query Preps/sec

The number of query preparations each second.

Successful Queries/sec

The number of queries each second that have been returned by the Oracle BI Server without error.

Total Cache Clean Ups

The number of query cache cleanup jobs that have been run.

Total Cache Hits

The total number of cache hits.

Total Canceled Queries

The total number of queries that have been returned as canceled by the Oracle BI Server.

Total Errored Queries

The total number of queries that have failed to execute against the Oracle BI Server.

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.

Total Query Attempts

The total number of queries that have been attempted.

Total Query Piggybacks

The total number of queries that have 'piggybacked' off of an equivalent running query.

Total Query Prep Cache Hits

The total number of query preparations resolved by the cache.

Total Query Prep Cache Misses

The total number of query preparations resolved by the Oracle BI Server.

Total Query Preps

The total number of query preparations.

Total Query Preps Errors

The total number of query preparations that failed.

Total Successful Queries

The total number of queries that have been returned by the Oracle BI Server without error.

Oracle BI PS Request Processor

This category shows performance information related to requests processed by Oracle BI Presentation Services.

Bad Requests

The total number of bad requests.

Completed Requests

The total number of requests completed.

Completed Requests/sec

The number of requests completed each second.

Current Requests

The current number of requests being processed.

Failed Requests

The total number of failed requests.

GET Requests

The total number of GET requests completed.

Long Requests

The total number of long running requests.

Peak Requests

The peak number of requests concurrently being processed.

POST Requests

The total number of POST requests completed.

SOAP Requests

The total number of SOAP requests completed.

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.

Active Sessions

The number of active Presentation Services sessions.

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.

Current Sessions

The number of current Presentation Services sessions.

Failed Logins/sec

The number of failed logins each second.

New Logins/sec

The number of new logins each second.

New Sessions/sec

The number of new sessions each second.

Peak Active Sessions

The peak number of concurrent active sessions.

Peak Embryonic Sessions

The peak number of embryonic sessions.

Peak Logged In

The peak number of concurrent browser sessions logged in.

Peak Sessions

The peak number of concurrent sessions.

Sessions Logged In

The current number of browser sessions that are logged in.

Total Failed Logins

The total number of failed logins.

Total Lifetime Sessions

The total number of sessions created since the Oracle BI Presentation Services server was started.

Total Logins

The total number of successful logins.

Oracle BI PS Sockets

This category provides information related to Oracle BI Presentation Services sockets.

Total Close Requests

The total number of requests to close sockets.

Total Closed

The total number of sockets closed.

Total Open Requests

The total number of requests to open sockets.

Total Opened

The total number of sockets opened.

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.

Current Jobs Queued

The number of jobs currently waiting in queue for processing by this thread pool.

Current Jobs Running

The number of jobs currently being processed by this thread pool.

Current Threads

The number of threads currently in this thread pool.

Peak Jobs Queued

The peak number of concurrent jobs waiting in queue for processing by this thread pool.

Peak Jobs Running

The peak number of concurrent jobs being processed by this thread pool.

Peak Threads

The peak number of concurrent threads in this thread pool.

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.

Total Jobs Submitted

The total number of jobs submitted for processing by this thread pool.

Total Jobs Unfinished

The total number of jobs that ended prematurely or unexpectedly during processing.

Oracle BI PS Threads

This category provides information related to Oracle BI Presentation Services threads.

Total Close Requests

The total number of requests to destroy a thread.

Total Closed

The total number of threads destroyed.

Total Created

The total number of threads created.

Total Open Requests

The total number of requests to create a thread.

Oracle BI PS User Population Searches

This category provides performance information related to all searches made using the User Population Manager.

UserPopulationAPI.SearchByGUID

The number of user population searches by GUID.

UserPopulationAPI.SearchByName

The number of user population searches by user name.

UserPopulationAPI.SearchByPattern

The number of user population searches by pattern.

Oracle BI PS XML Document Caches

This category provides information related to the Oracle BI Presentation Services XML document caches.

Current Disk Entries

The current number of cache entries stored on disk.

Current Disk Usage (KB)

The current disk usage of the cache in kilobytes.

Current Memory Entries

The current number of cache entries in memory.

Disk Added (KB)

The amount of disk space added in kilobytes since the server was started.

Disk Cache Hits

The number of cache requests satisfied from disk.

Disk Cache Misses

The number of cache requests that were not satisfied from disk.

Disk Deleted (KB)

The amount of disk space deleted in kilobytes since the server was started.

Invalid Requests

The total number of cache requests that were invalid. Typically, invalid cache requests contain an invalid cache key.

Memory Cache Hits

The number of cache requests satisfied in memory.

Peak Memory Entries

The peak number of cache entries concurrently in memory.

Total Memory Entries

The total number of cache entries in memory since the server was started.

Oracle BI PS XML Validator

This category provides information related to XML validations within Oracle BI Presentation Services.

Current Validations

The current number of XML validations.

Current Validators in Pool

The current number of XML validators.

Peak Validations

The peak number of concurrent XML validations.

Peak Validators in Pool

The peak number of XML validators.

Total Validations

The total number of XML instances validated.

Validations/sec

The number of XML instances validated each second.

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.

Accumulated Requests

The total number of requests serviced by the Oracle BI Server thread pools since the server was started.

Average Execution Time (ms)

The average number of milliseconds that it took for a request to be processed.

Average Queued Requests

The average number of requests waiting for a thread to become available.

Average Queued Time (ms)

The average number of milliseconds that a request waited for a thread to become available.

Avg. Request/sec

The average number of requests that were processed each second by the Oracle BI Server.

Capacity

The maximum allowed number of threads in the Oracle BI Server thread pools.

Current Busy Thread Count

The number of threads currently in use.

Current Execution Time (ms)

The number of milliseconds that it took for the most recent request to be processed.

Current Queued Requests

The number of requests currently waiting for a thread to become available.

Current Queued Time (ms)

The number of milliseconds that the request that is next in line for processing has waited in queue.

Current Thread Count

The total number of threads currently in the Oracle BI Server thread pools.

Lowest Execution Time (ms)

The smallest number of milliseconds that it has taken to process a request since the server was started.

Lowest Queued Requests

The smallest number of requests that have been in queue since the server was started.

Lowest Queued Time (ms)

The smallest number of milliseconds that a request has had to wait in queue.

Maximum Stack Size (bytes)

The peak stack size used by the set of active threads, in bytes.

Peak Busy Thread Count

The peak number of concurrently active threads.

Peak Execution Time (ms)

The peak number of milliseconds that it took for a request to be processed.

Peak Queued Requests

The peak number of requests that have been in queue since the server was started.

Peak Queued Time (ms)

The peak number of milliseconds that a request has had to wait in queue.

Peak Thread Count

The peak number of threads in the Oracle BI Server thread pools.

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.

Weblogic BI Action Framework Metrics

This category shows average performance information for Action Framework requests across the Oracle WebLogic Server cluster.

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.

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.

Weblogic BI Analytics Metrics

This category shows total/average performance information for all managed servers across the Oracle WebLogic Server cluster.

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.

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.

Active Sessions

The total number of active sessions for the BI Analytics Web application across the Oracle WebLogic Server cluster.

Weblogic BI SOA Metrics

This category shows average performance information for Web services requests across the Oracle WebLogic Server cluster.

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.

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.

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.

CPU Usage Percentage

The percentage of the CPU that is being used by the Oracle WebLogic Server. As traffic increases, CPU utilization increases.

Heap Used (MB)

The amount of heap space (total program memory) used, in megabytes, by the Oracle WebLogic Server.

Requests (per minute)

The average number of servlet and/or JSP invocations per minute for the Oracle WebLogic Server in the last 5 minutes.

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.

Active Sessions

The number of active sessions for the Oracle WebLogic Server.

8 Oracle Essbase Server Metrics

This chapter describes the Oracle Essbase server metrics.

Server Information

This category of metrics shows the number of current users and applications on the Essbase server.

Connected Users

This metric shows the number of users connected to the Essbase server.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Running Apps

This metric shows the number of Essbase applications running on the Essbase server.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Unaccessed Apps

This metric shows the number of available Essbase applications that are not running on the Essbase server.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Response (ms)

This metric shows the time required, in milliseconds, for the Essbase server to respond to requests.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Resource Usage

This category of metrics shows the resource usage of the Essbase server.

CPU Usage (%)

This metric shows the percentage of CPU being used by the Essbase server.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Memory Usage (MB)

This metric shows the amount of physical memory, in megabytes, being used by the Essbase server.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Memory Usage (%)

This metric shows the percentage of physical memory being used by the Essbase server.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Response

This category of metrics shows the status and performance of the Essbase server.

Response - Status

This metric shows whether the Essbase server is responding to requests.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

9 Oracle Essbase Applications

These metrics show the performance of Oracle Essbase applications.

Application Information

This category of metrics shows the resource usage of applications running on the Oracle Essbase server.

Response (ms)

This metric shows the time required, in milliseconds, for the Oracle Essbase application to respond to requests.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Memory Usage (MB)

This metric shows the amount of physical memory, in megabytes, being used by the Oracle Essbase application.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Threads

This metric shows the number of independent processes currently in use within the Oracle Essbase application.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Response

This category of metrics shows the status and performance of Oracle Essbase applications.

Response - Status

This metric shows whether the Oracle Essbase application is responding.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

10 Oracle Coherence Metrics

The oracle_coherence metrics provide description, collection statistics, data source, multiple thresholds (where applicable), and user action information for each metric.

Cache Performance - Aggregated Over Nodes

Aggregated cache performance across all nodes on which a cache is running

Service

Caching Service Name (such as Replicated, Distributed)

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Cache Hits Rate

Cache Hits in a sample interval summed across all nodes

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Cache Misses Rate

Cache Misses in a sample interval summed across all nodes

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Number of Loads Rate

Total number of load operations in a sample interval summed across all nodes.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Number of Stores-Erases Rate

Total number of store and erase operations in a sample interval summed across all nodes.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Number of Gets Rate

Total number of get() operations in a sample interval summed across all nodes.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Number of Puts Rate

Total number of put() operations in a sample interval summed across all nodes.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Total Time for Gets-Hit (ms) Rate

Total number of milliseconds for the get() operations in a sample interval summed across all nodes.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Total Time for Gets-Miss (ms) Rate

Total number of milliseconds for the get() operations for which no entry existed in the map in a sample interval summed across all nodes.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Time For Loads Rate (ms)

Cumulative time spent on load operations in a sample interval summed across all nodes

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Time For Stores-Erases Rate (ms)

Cumulative time spent on store and erase operations in a sample interval summed across all nodes.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Time For Puts Rate (ms)

Total number of milliseconds spent on put() operations in a sample interval summed across all nodes.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Time For Gets Rate (ms)

The total number of milliseconds spent on get() operations in a sample interval summed across all nodes.

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 10-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

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Number Of Objects In Cache(underutilized threshold)

The number of entries in the cache in a sample interval summed across all nodes

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Number Of Objects In Cache(overutilized threshold)

The number of entries in the cache in a sample interval summed across all nodes.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Case Size Measured In Units

The size of the cache measured in units in a sample interval summed across all nodes

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Cache Hits

The rough number of cache hits in a sample interval summed across all nodes.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Cache Misses

The rough number of cache misses in a sample interval summed across all nodes.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Total Number Of Puts

The total number of put() operations in a sample interval summed across all nodes

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Total Number Of Gets

The total number of get() operations in a sample interval summed across all nodes

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Total Number Of Loads

The total number of load operations in a sample interval summed across all nodes.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Total Number Of Stores-Erases

The total number of store and erase operation in a sample interval summed across all nodes.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Cache Hits to Gets Ratio

Cache Hits to Gets Ratio in a sample interval summed across all nodes.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Average Time For Gets (ms)

The average number of milliseconds per get() invocation in a sample interval summed across all nodes.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Average Time For Gets-Hit(ms)

The average number of milliseconds per get() invocation that is a hit in a sample interval summed across all nodes.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Average Time For Gets-Miss(ms)

The average number of milliseconds per get() invocation that is a miss in a sample interval summed across all nodes.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Average Time For Put Invokation(ms)

The average number of milliseconds per put() invocation in a sample interval summed across all nodes.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Average Time Spent For Write Operation (ms)

The average time (in millis) spent per read operation in a sample interval summed across all nodes.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Average Time Spent For Read Operation (ms)

The average time (in millis) spent per write operation in a sample interval summed across all nodes.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" 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" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Cache Configuration

This metric addresses the cache configuration

Name

The name of the cache configuration

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Node ID

The coherence node identification.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Service

The Caching Service Name (such as Replicated, Distributed)

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Tier

The cache tier

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Loader

The cache loader

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Batch Factor

The BatchFactor is used to calculate the `soft-ripe` time for write-behind queue entries. A queue entry is considered to be `ripe` for a write operation if it has been in the write-behind queue for no less than the QueueDelay interval. The `soft-ripe` time is the point in time prior to the actual `ripe` time after which an entry will be included in a batched asynchronous write operation to the CacheStore

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Description

The cache description.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

The Time-To-live For Cache Entries

The time-to-live for cache entries in milliseconds. Value of zero indicates that the automatic expiry is disabled. Change of this attribute will not affect already-scheduled expiry of existing entries.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Time Between Cache Flushes (ms)

The number of milliseconds between cache flushes. Value of zero indicates that the cache will never flush.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Cache Size High Limit (in Units)

The limit of the cache size measured in units. The cache will prune itself automatically once it reaches its maximum unit level. This is often referred to as the `high water mark` of the cache.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Cache Size Low Limit (in Units)

The number of units to which the cache will shrink when it prunes. This is often referred to as a `low water mark` of the cache.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Persistence Type

The persistence type for this cache. Possible values include: NONE, READ-ONLY, WRITE-THROUGH, WRITE-BEHIND.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Queue Delay (secs)

The number of seconds that an entry added to a write-behind queue will sit in the queue before being stored via a CacheStore. Applicable only for WRITE-BEHIND persistence type.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Refresh Factor

The RefreshFactor attribute is used to calculate the `soft-expiration` time for cache entries. Soft-expiration is the point in time prior to the actual expiration after which any access request for an entry will schedule an asynchronous load request for the entry.

This attribute is only applicable for a ReadWriteBackingMap which has an internal LocalCache with scheduled automatic expiration. The value of this element is expressed as a percentage of the internal LocalCache expiration interval. Valid values are doubles in the interval[0.0, 1.0]. If zero, refresh-ahead scheduling will be disabled.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Refresh Time

The timestamp when this model was last retrieved from a corresponding node. For local servers it is the local time.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Requeue Threshold

The maximum size of the write-behind queue for which failed CacheStore write operations are requeued. If zero, the write-behind requeueing will be disabled. Applicable only for WRITE-BEHIND persistence type.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Cache Performance

The cache performance metrics

Average Time For Gets (ms) -Per Node

The average number of milliseconds per get() invocation since the last time statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Average Time For Gets-Hit(ms) -Per Node

The average number of milliseconds per get() invocation that is a hit.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Average Time For Gets-Miss(ms) -Per Node

The average number of milliseconds per get() invocation that is a miss.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Average Time For Put Invokation(ms) -Per Node

The average number of milliseconds per put() invocation since the cache statistics were last reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Cache Hits -Per Node

The rough number of cache hits since the last time statistics were reset. A cache hit is a read operation invocation (i.e. get()) for which an entry exists in this map.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Cache Hits Rate -Per Node

The cache hits rate since the last time statistics were reset. A cache hit is a read operation invocation (i.e. get()) for which an entry exists in this map

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total Time for Gets-Hit (ms) -Per Node

The total number of milliseconds (since the last time statistics were reset) for the get() operations for which an entry existed in this map.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total Time for Gets-Hit (ms) Rate -Per Node

The total number of milliseconds (since the last time statistics were reset) for the get() operations rate for which an entry existed in this map.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Cache Misses -Per Node

The rough number of cache misses since the last time statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Cache Misses Rate -Per Node

The rate of cache misses since the last time statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total Time for Gets-Miss (ms) -Per Node

The total number of milliseconds ( since the last time statistics were reset) for the get() operations for which no entry existed in this map.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total Time for Gets-Miss (ms) Rate -Per Node

The total number of milliseconds ( since the last time statistics were reset) for the get() operations rate for which no entry existed in this map.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Hit Probability -Per Node

The rough probability (0 <= p <= 1) that the next invocation will be a hit, based on the statistics collected since the last time statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

The No. Of Entries In The Cache -Per Node

The number of entries in the cache.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

The size of the write-behind queue -Per Node

The size of the write-behind queue size. Applicable only for WRITE-BEHIND persistence type.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Average No. Of Entries Per CacheStore Write Operation -Per Node

The average number of entries stored per CacheStore write operation. A call to the store() method is counted as a batch of one, whereas a call to the storeAll() method is counted as a batch of the passed Map size. The value of this attribute is -1 if the persistence type is NONE.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Average Time Spent For Read Operation (ms) -Per Node

The average time (in millis) spent per read operation; -1 if persistence type is NONE.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Average Time Spent For Write Operation (ms) -Per Node

The average time (in millis) spent per write operation; -1 if persistence type is NONE.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total No. Of Cache Store Failures -Per Node

The total number of CacheStore failures (load, store and erase operations); -1 if persistence type is NONE.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

CacheStore Failures Rate -Per Node

The rate of CacheStore failures (load, store and erase operations); -1 if persistence type is NONE.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total Time For Loads (ms) -Per Node

The cumulative time (in millis) spent on load operations; -1 if persistence type is NONE.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Time For Loads Rate (ms) -Per Node

The cumulative time (in millis) per node spent on load operations; -1 if persistence type is NONE.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total No. Of Loads -Per Node

The total number of load operations per node; -1 if persistence type is NONE.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

No. Of Loads Rate -Per Node

The cumulative number of load operations per node; -1 if persistence type is NONE

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total Time For Store and Erase Operation (ms) -Per Node

The cumulative time (in milliseconds) spent on store and erase operations; -1 if persistence type is NONE or READ-ONLY.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Time For Stores-Erases Rate (ms) -Per Node

The cumulative time for store erase operations

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total No. Of Stores-Erases -Per Node

The total number of store and erase operations; -1 if persistence type is NONE or READ-ONLY.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Stores-Erases Rate -Per Node

The cumulative store erase operations per node.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total No. Of Gets -Per Node

The total number of get() operations since the last time statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Gets Rate -Per Node

The cumulative number of get() operations since the last time statistics were reset

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total Time For Gets (ms) -Per Node

The total number of milliseconds spent on get() operations since the last time statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Time For Gets Rate (ms) -Per Node

The cumulative time (in millis) per node spent on get operations; -1 if persistence type is NONE

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total No. Of Puts -Per Node

The total number of put() operations since the last time statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Puts Rate -Per Node

The cumulative number of put operations since the last time statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total Time For Puts (ms) -Per Node

The total number of milliseconds spent on put() operations since the last time statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Time For Puts Rate (ms) -Per Node

The cumulative time for put operations since the last time statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Case Size Measured In Units -Per Node

The size of the cache measured in units. This value needs to be adjusted by the UnitFactor.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Cluster

This cluster metrics are described.

Cluster Name

The name of the cluster.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Cluster Nodes

The total number of cluster nodes.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

License Mode

The license mode that this cluster is using. Possible values are Evaluation, Development or Production.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Local Member Id

The member id for the cluster member that is co-located with the reporting MBeanServer; -1 if the cluster service is not running.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Member IDs

An array of all existing cluster member ids.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Members

An array of all existing cluster members.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Oldest Member ID

The senior cluster member id; -1 if the cluster service is not running.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Running

Specifies whether or not the cluster is running.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Cluster Aggregated

The aggregated coherence cluster metrics are described

Cluster Name

The name of the cluster.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Cluster Nodes

The total number of cluster nodes.

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 10-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 300 Seconds

After Every Sample

<

Not Defined

Not Defined

1

Cluster size is below threshold

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Cluster Name" object.

If warning or critical threshold values are currently set for any "Cluster 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 "Cluster Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Publisher Success Rate - Cluster

The publisher success rate for this cluster node since the node statistics were last reset. Publisher success rate is a ratio of the number of packets successfully delivered in a first attempt to the total number of sent packets. A failure count is incremented when there is no ACK received within a timeout period. It could be caused by either very high network latency or a high packet drop rate.

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 10-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 300 Seconds

After Every Sample

<

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Cluster Name" object.

If warning or critical threshold values are currently set for any "Cluster 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 "Cluster Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Receiver Success Rate - Cluster

The receiver success rate for this cluster node since the node statistics were last reset. Receiver success rate is a ratio of the number of packets successfully acknowledged in a first attempt to the total number of received packets. A failure count is incremented when a re-delivery of previously received packet is detected. It could be caused by either very high inbound network latency or lost ACK packets.

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 10-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 300 Seconds

After Every Sample

<

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Cluster Name" object.

If warning or critical threshold values are currently set for any "Cluster 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 "Cluster Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Memory Usage (MB)

The memory usage in MB.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

No. of Caches

The number of entries in the cache.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Change in No. of Caches Since Last Collection

The change in the number of caches since the last collection.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Number of caches exceeded threshold

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Cluster Name" object.

If warning or critical threshold values are currently set for any "Cluster 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 "Cluster Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Change in No. of Nodes Since Last Collection

The change in the number of node since last collection.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Cluster Alerts

The coherence cluster alert metrics are described.

Cluster Name

The name of the cluster.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Cluster Nodes

The total number of cluster nodes.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Change in No. of Nodes Since Last Collection

The change in the number of nodes since the last collection.

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 10-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 60 Seconds

After Every Sample

<

0

-5

1

Nodes departed the Cluster

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Cluster Name" object.

If warning or critical threshold values are currently set for any "Cluster 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 "Cluster Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Change in Number of Nodes

The change in the number of nodes since the last time statistics were collected.

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 10-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 60 Seconds

After Every Sample

>

0

Not Defined

1

Nodes added to Cluster

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Cluster Name" object.

If warning or critical threshold values are currently set for any "Cluster 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 "Cluster Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Connection

The coherence connection metric s are described.

Name

The connection name.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Node ID

The connection node id.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

UUID

The connection node uuid

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Connection Time (ms)

The connection time in milliseconds.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name", "NodeID", and "UUID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name", "NodeID", and "UUID" 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", "NodeID", and "UUID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Outgoing Queue Backlog (bytes)

The backlog (in bytes) of the outgoing queue

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name", "NodeID", and "UUID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name", "NodeID", and "UUID" 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", "NodeID", and "UUID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Outgoing Message Queue Backlog

The backlog of the outgoing message queue.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name", "NodeID", and "UUID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name", "NodeID", and "UUID" 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", "NodeID", and "UUID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Refresh Time

The timestamp when this model was last retrieved from a corresponding node. For local servers it is the local time.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Remote Address

The IP address of the corresponding client.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Remote Port

The port of the corresponding client.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Timestamp

The date/time value (in local time) that the corresponding client connected to the Proxy.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total Bytes Received - Connection

The total number of bytes received since the last time the statistics were reset.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name", "NodeID", and "UUID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name", "NodeID", and "UUID" 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", "NodeID", and "UUID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Bytes Received Since Last Collection- Connection

The number of bytes received since the last collection.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name", "NodeID", and "UUID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name", "NodeID", and "UUID" 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", "NodeID", and "UUID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Total Bytes Sent - Connection

The total number of bytes sent since the last time the statistics were reset.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name", "NodeID", and "UUID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name", "NodeID", and "UUID" 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", "NodeID", and "UUID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Bytes Sent Since Last Collection - Connection

The number of bytes sent since the last collection.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name", "NodeID", and "UUID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name", "NodeID", and "UUID" 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", "NodeID", and "UUID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Total Messages Received - Connection

The total number of messages received since the last time the statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Message Received Since Last Collection - Connection

The number of messages received since the last collection.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total Messages Sent - Connection

The total number of messages sent since the last time the statistics were reset.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name", "NodeID", and "UUID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name", "NodeID", and "UUID" 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", "NodeID", and "UUID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Message Sent Since Last Collection - Connection

The messages sent since the last collection.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name", "NodeID", and "UUID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name", "NodeID", and "UUID" 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", "NodeID", and "UUID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Connection Manager

The connection manager metrics are described.

Name

This is the name of the connection manager

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Node ID

An ID is automatically assigned to any node that is part of the cluster.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Connection Count

The number of client connections.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Host IP

The IP address and port of the Proxy host.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Incoming Buffer Pool Capacity

The pool capacity (in bytes) of the incoming buffer.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Incoming Buffer Pool Size

The number of buffers in the incoming pool.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Outgoing Buffer Pool Capacity

The pool capacity (in bytes) of the outgoing buffer.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Outgoing Buffer Pool Size

The number of buffers in the outgoing pool.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Outgoing Queue Backlog (bytes)

The backlog (in bytes) of the outgoing queue.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Outgoing Message Queue Backlog

The backlog of the outgoing message queue.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

RefreshTime

The timestamp when this model was last retrieved from a corresponding node. For local servers it is the local time.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total Bytes Received - Connection Manager

The total number of bytes received by the Proxy host since the statistics were last reset.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Bytes Received Since Last Collection - Connection Manager

The bytes received since the last collection.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total Bytes Sent - Connection Manager

The total number of bytes sent by the Proxy host since the statistics were last reset.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Bytes Sent Since Last Collection - Connection Manager

The bytes sent since the last collection.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Total Messages Received - Connection Manager

The total number of messages received by the Proxy host since the statistics were last reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Message Received Since Last Collection - Connection Manager

The messages received since the last collection.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total Messages Sent - Connection Manager

The total number of messages sent by the Proxy host since the statistics were last reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Message Sent Since Last Collection - Connection Manager

The messages sent since the last collection.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Garbage Collector after GC

Garbage Collector memory pool metrics after completion of garbage collection per node.

Name

Garbage Collector Name.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Node ID

Coherence Node ID.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

GC Thread Count

GC Thread Count per garbage collector.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Start Time (ms)

GC Start Time for a garbage collector.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

End Time (ms)

GC End Time for a garbage collector.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Key of Memory Usage after GC

Garbage Collector key.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Committed of Memory Usage after GC

The amount of memory that is guaranteed to be available for use by the JVM after GC.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Init of Memory Usage after GC

The initial amount of memory that the JVM requested for a memory pool from the operating system during startup.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Max of Memory Usage after GC

The maximum amount of memory that can be used by the JVM.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Used of Memory Usage after GC

The amount of memory currently in use.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Garbage Collector Before GC

Garbage Collector memory pool metrics before completion of garbage collection per node.

Name

Garbage Collector Name.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Node ID

Coherence Node ID.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

GC Thread Count

GC Thread Count per garbage collector

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Start Time (ms)

GC Start Time for a garbage collector.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

End Time (ms)

GC End Time for a garbage collector.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Key of Memory Usage Before GC

Garbage Collector key.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Committed of Memory Usage Before GC

The amount of memory that is guaranteed to be available for use by the JVM after GC.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Init of Memory Usage Before GC

The initial amount of memory that the JVM requested for a memory pool from the operating system during startup.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Max of Memory Usage Before GC

The maximum amount of memory that can be used by the JVM.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Used of Memory Usage Before GC

The amount of memory currently in use.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Garbage Collector Collection

Metrics from a garbage collection for each garbage collector per node.

Name

Garbage Collector Name.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Node ID

Coherence Node ID

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Collection Count

Number of items garbage collected

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Garbage Collection Rate

Number of items garbage collected in a sample interval

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Collection Time

Time to garbage collect items

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

HTTP Session

Metrics indicating session usage by a web application using Coherence.

Application ID

Coherence Web Application ID.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Node ID

Coherence Node ID.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Collection Class Name

The fully qualified class name of the HttpSessionCollection implementation in use.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Factory Class Name

The fully qualified class name of the Factory implementation in use.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Local Attribute Cache Name

The name of the local cache that stores non-distributed session attributes.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Number of Local Attributes in Local Attribute Cache

The number of non-distributed session attributes stored in the local session attribute cache.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Local Session Cache Name

The name of the local cache that stores non-distributed sessions.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Number of Local Sessions in Local Session Cache

The number of non-distributed sessions stored in the local session cache

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Overflow Average Size

The average size (in bytes) of the session attributes stored in the "overflow" clustered cache.

Overflow Cache Name

The name of the clustered cache that stores the "large attributes" that exceed a certain size.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Overflow Max Size

The maximum size (in bytes) of a session attribute stored in the "overflow" clustered cache.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Overflow Threshold

The minimum length (in bytes) that the serialized form of an attribute value must be for that attribute value to be stored in the separate "overflow" cache.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Updates to Attributes Stored in Overflow Cache

The number of updates to session attributes stored in the "overflow" clustered cache.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Updates to Attributes Stored in Overflow Cache Per Min -Per Min

The number of updates to session attributes stored in the "overflow" clustered cache per minute.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Servlet Context Cache Name

The name of the clustered cache that stores javax.servlet.ServletContext attributes.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Servlet Context Name

The name of the web application Servlet Context.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Session Average Lifetime

The average lifetime (in seconds) of session objects invalidated.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Session Cache Name

The name of the clustered cache that stores serialized session objects.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Session ID Length

The length (in characters) of generated session IDs.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Session Object Maximum Size (bytes)

The maximum size (in bytes) of a session object placed in the session storage clustered cache.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Number of Http Session Objects

The number of session objects that are pinned to this instance of the web application.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Session Timeout

The session expiration time (in seconds).

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Updates to Object Store in Session Cache -Per Node

The number of updates of session object stored in the session storage clustered cache.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Updates to Object Store in Session Cache Per Min -Per Node

The number of updates of session object stored in the session storage clustered cache per minute.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

HTTP Session - Aggregated Over Nodes

Metrics indicating session usage by a web application using Coherence aggregated over all nodes where application session information is stored.

This metric is a subset of Http Session Metrics aggregated over nodes where application session data is stored. Therefore, metric column descriptions are the same as those contained in the Http Session metric, but Application ID is the key and aggregation of metrics happens over all nodes where application id session information is stored.

Application ID

The application id number.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

No. of Attributes in Local Attribute Cache

The number of attributes in the local attribute cache

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

No. of Sessions in Local Session Cache

The number of updates of session object stored in the session storage clustered cache per minute.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Updates to Attributes Stored in Overflow Cache

The updates to attributes stored in the overflow cache.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Updates to Attributes Stored in Overflow Cache Per Min

The number of attributes stored in the overflow cache per minute.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Updates to Object Store in Session Cache

The updates to the object store in the session cache.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Updates to Object Store in Session Cache Per Min

The number of updates to the object store in the session cache per minute.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Memory Performance

Memory usage metrics for heap and non-heap memory for each Coherence node.

Node ID

Coherence Node ID.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Heap Memory Committed for JVM to use (bytes)

The amount of heap memory that is guaranteed to be available for use by the JVM.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Heap Memory that JVM initially Requests from OS (bytes)

The initial amount of heap memory that the JVM requested for a memory pool from the operating system during startup.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Maximum Heap Memory That Can Be Used (bytes)

The maximum amount of heap memory that can be used by the JVM.

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 10-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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Heap Memory Used (bytes)

The amount of heap memory currently in use.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Non Heap Memory Committed for JVM to use (bytes)

The amount of non-heap memory that is guaranteed to be available for use by the JVM.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Non Heap Memory that JVM initially Requests from OS (bytes)

The initial amount of non-heap memory that the JVM requested for a memory pool from the operating system during startup.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Non Heap Memory Used (bytes)

The amount of non-heap memory currently in use.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Object Pending Finalization Count

The approximate number of objects for which finalization is pending.

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 10-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 300 Seconds

After Every Sample

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Verbose

Boolean value indicating whether verbose logging is enabled or not.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Node Performance - Aggregate Over Caches

The node performance metrics aggregated over caches are described.

Node ID

Coherence Node ID

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total Number Of Gets

The total number of get() operations in a sample interval summed across all nodes

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Number of Gets Rate

Total number of get() operations in a sample interval summed across all nodes.

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 10-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

>

Not Defined

Not Defined

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Total Number of Puts

The total number of put() operations in a sample interval summed across all nodes.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Number of Puts Rate

Total number of put() operations in a sample interval summed across all nodes.

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 10-69 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Node Configuration

The node configuration metrics are described.

Buffer Publish Size

The buffer size of the unicast datagram socket used by the Publisher, measured in the number of packets. Changing this value at runtime is an inherently unsafe operation that will pause all network communications and may result in the termination of all cluster services.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Buffer Receive Size

The buffer size of the unicast datagram socket used by the Receiver, measured in the number of packets. Changing this value at runtime is an inherently unsafe operation that will pause all network communications and may result in the termination of all cluster services.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Burst Count

The burst count.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Burst Delay

The burst delay.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Flow Control Enabled

Indicates whether or not FlowControl is enabled.

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.

Target Version

Collection Frequency

All Versions

Every Hour

ID

The short Member id that uniquely identifies the Member at this point in time and does not change for the life of this Member.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Logging Format

Specifies how messages will be formatted before being passed to the log destination

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.

Target Version

Collection Frequency

All Versions

Every Hour

Logging Level

Specifies which logged messages will be output to the log destination. Valid values are non-negative integers or -1 to disable all logger output.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Logging Limit

The maximum number of characters that the logger daemon will process from the message queue before discarding all remaining messages in the queue. Valid values are integers in the range [0...]. Zero implies no limit.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Machine Id

The Member`s machine Id.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Machine Name

A configured name that should be the same for all Members that are on the same physical machine, and different for Members that are on different physical machines.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Member Name

A configured name that must be unique for every Member.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Memory Max (MB)

The maximum amount of memory that the JVM will attempt to use in MB.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Multicast Address

The IP address of the Member`s MulticastSocket for group communication.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Multicast Enabled

Specifies whether or not this Member uses multicast for group communication. If false, this Member will use the WellKnownAddresses to join the cluster and point-to-point unicast to communicate with other Members of the cluster.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Multicast Port

The port of the Member`s MulticastSocket for group communication.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Multicast Threshold

The percentage (0 to 100) of the servers in the cluster that a packet will be sent to, above which the packet will be multicasted and below which it will be unicasted.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Multicast TTL

The time-to-live for multicast packets sent out on this Member`s MulticastSocket.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Nack Enabled

A configured name that must be unique for every Member.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Process Name

A configured name that should be the same for Members that are in the same process (JVM), and different for Members that are in different processes. If not explicitly provided, for processes running with JRE 1.5 or higher the name will be calculated internally as the Name attribute of the system RuntimeMXBean, which normally represents the process identifier (PID).

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.

Target Version

Collection Frequency

All Versions

Every Hour

Product Edition

The product edition this Member is running. Possible values are: Standard Edition (SE), Enterprise Edition (EE).

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.

Target Version

Collection Frequency

All Versions

Every Hour

Rack Name

A configured name that should be the same for Members that are on the same physical "rack" (or frame or cage), and different for Members that are on different physical "racks".

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.

Target Version

Collection Frequency

All Versions

Every Hour

RefreshTime

The timestamp when this model was last retrieved from a corresponding node. For local servers it is the local time.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Resend Delay

The minimum number of milliseconds that a packet will remain queued in the Publisher`s re-send queue before it is resent to the recipient(s) if the packet has not been acknowledged. Setting this value too low can overflow the network with unnecessary repetitions. Setting the value too high can increase the overall latency by delaying the re-sends of dropped packets. Additionally, change of this value may need to be accompanied by a change in SendAckDelay value.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Role Name

A configured name that can be used to indicate the role of a Member to the application. While managed by Coherence, this property is used only by the application

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.

Target Version

Collection Frequency

All Versions

Every Hour

Site Name

A configured name that should be the same for Members that are on the same physical site (e.g. data center), and different for Members that are on different physical sites.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Timestamp

The date/time value (in cluster time) that this Member joined the cluster.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Traffic Jam Count

The maximum total number of packets in the send and resend queues that forces the publisher to pause client threads. Zero means no limit.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Traffic Jam Delay

The number of milliseconds to pause client threads when a traffic jam condition has been reached. Anything less than one (e.g. zero) is treated as one millisecond.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Unicast Address

The IP address of the Member`s DatagramSocket for point-to-point communication.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Unicast Port

The port of the Member`s DatagramSocket for point-to-point communication.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Node Performance

The node performance metrics are described.

Cpu Count

Number of CPU cores for the machine this Member is running on.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Machine Id

The Member`s machine Id.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Machine Name

A configured name that should be the same for all Members that are on the same physical machine, and different for Members that are on different physical machines.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Member Name

A configured name that must be unique for every Member.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Memory Available (MB)

The total amount of memory in the JVM available for new objects in MB.

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 10-70 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Id" object.

If warning or critical threshold values are currently set for any "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 "Id" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Packet Delivery Efficiency

The efficiency of packet loss detection and retransmission. A low efficiency is an indication that there is a high rate of unnecessary packet retransmissions.

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 10-71 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Packets Bundled

The total number of packets which were bundled prior to transmission. The total number of network transmissions is equal to (PacketsSent - PacketsBundled).

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 10-72 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Packets Bundled Rate

The cumulative number of packets bundled.

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 10-73 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Packets Received

The number of packets received since the node statistics were last reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Packets Received Rate

The cumulative number of packets received.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Packets Repeated

The number of packets received since the node statistics were last reset.

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 10-74 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Packets Repeated Rate

The cumulative number of packets repeated.

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 10-75 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Packets Resent

The number of packets resent since the node statistics were last reset. A packet is resent when there is no ACK received within a timeout period.

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 10-76 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Packets Resent Rate

A configured name that must be unique for every Member.

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 10-77 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Packets Resent Early

The total number of packets resent ahead of schedule. A packet is resent ahead of schedule when there is a NACK indicating that the packet has not been received.

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 10-78 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Packets Resent Early Rate

A configured name that must be unique for every Member.

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 10-79 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Packets Resent Excess

The total number of packet retransmissions which were later proven unnecessary.

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 10-80 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Packets Resent Excess Rate

The total number of packet retransmissions which were later proven unnecessary.

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 10-81 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Packets Sent

The number of packets sent since the node statistics were last reset.

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 10-82 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Packets Sent Rate

The total number of packet retransmissions which were later proven unnecessary.

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 10-83 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Process Name

A configured name that should be the same for Members that are in the same process (JVM), and different for Members that are in different processes. If not explicitly provided, for processes running with JRE 1.5 or higher the name will be calculated internally as the Name attribute of the system RuntimeMXBean, which normally represents the process identifier (PID).

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Publisher Success Rate

The publisher success rate for this cluster node since the node statistics were last reset. Publisher success rate is a ratio of the number of packets successfully delivered in a first attempt to the total number of sent packets. A failure count is incremented when there is no ACK received within a timeout period. It could be caused by either very high network latency or a high packet drop rate.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Publisher Success Rate - Per Node

The cumulative publisher success rate since the node statistics were last reset.

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 10-84 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Rack Name

A configured name that should be the same for Members that are on the same physical "rack" (or frame or cage), and different for Members that are on different physical "racks".

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Receiver Success Rate

The receiver success rate for this cluster node since the node statistics were last reset. Receiver success rate is a ratio of the number of packets successfully acknowledged in a first attempt to the total number of received packets. A failure count is incremented when a re-delivery of previously received packet is detected. It could be caused by either very high inbound network latency or lost ACK packets.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Receiver Success Rate Delta

The cumulative receiver success rate for this cluster nodesince the node statistics were last reset

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 10-85 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Id" object.

If warning or critical threshold values are currently set for any "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 "Id" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Refresh Time

The timestamp when this model was last retrieved from a corresponding node. For local servers it is the local time.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Role Name

The timestamp when this model was last retrieved from a corresponding node. For local servers it is the local time.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Send Queue Size

The number of packets currently scheduled for delivery. This number includes both packets that are to be sent immediately and packets that have already been sent and awaiting for acknowledgment. Packets that do not receive an acknowledgment within ResendDelay interval will be automatically resent.

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 10-86 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Id" object.

If warning or critical threshold values are currently set for any "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 "Id" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Site Name

A configured name that should be the same for Members that are on the same physical site (for example, data center), and different for Members that are on different physical sites.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Tcp Ring Failures

The number of recovered TcpRing disconnects since the node statistics were last reset. A recoverable disconnect is an abnormal event that is registered when the TcpRing peer drops the TCP connection, but recovers after no more then maximum configured number of attempts.This value will be -1 if the TcpRing is disabled.

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 10-87 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Tcp Ring Failures Rate

The cumulative number of recovered TcpRing disconnects since the node statistics were last reset

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 10-88 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Tcp Ring Timeouts

The recovered TcpRing time outs since the node statistics were last reset.

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 10-89 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Tcp Ring TimeOuts Rate

The cumulative recovered TcpRing timeouts since the node statistics were last reset.

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 10-90 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Timestamp

The date/time value (in cluster time) that this Member joined the cluster.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Weakest Channel

The id of the cluster node to which this node is having the most difficulty communicating, or -1 if none is found. A channel is considered to be weak if either the point-to-point publisher or receiver success rates are below 1.0.

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 10-91 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Operating System

System properties and resources about the operating system on which the Coherence node JVM is running.

Node ID

Coherence Node ID.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Architecture

Operating system architecture.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Available Processors

Number of processors available to the Coherence node JVM.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Committed Virtual Memory Size (bytes)

Amount of virtual memory that is guaranteed to be available to running Coherence node JVM in bytes.

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 10-92 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Free Physical Memory Size (bytes)

The amount of free physical memory.

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 10-93 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Free Swap Space Size (bytes)

The amount of free swap space.

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 10-94 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Max File Descriptor Count

Maximum permissible open file descriptor.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Name

Operating system name.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Open File Descriptor Count

Current count of open file descriptors.

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 10-95 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Process Cpu Time

The CPU time used by the process on which the Java virtual machine is running.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total Physical Memory Size (bytes)

The amount of total physical memory.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total Swap Space Size (bytes)

The amount of total swap space.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Version

Operating system version.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Resource Usage

Memory resource usage aggregated across all nodes.

Memory Usage (MB)

Memory usage is the difference between Maximum memory and Available memory aggregated across all nodes.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Response

This category provides details on the R esponse metrics.

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 down and unavailable.

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.

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 J2EE Server instance is down

Runtime

Coherence Node Runtime metrics

Row ID

Internal key metric

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Node ID

Coherence Node ID

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Input Arguments

Start or input parameters a Coherence Node JVM process is started with

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

VM Name

Virtual Machine name

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

VM Vendor

Virtual Machine vendor

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

VM Version

Virtual Machine version

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Service Configuration

The service configuration metrics are described.

Total No. Of Partitions For Cache

The total number of partitions that every cache storage will be divided into.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Default Timeout Value For Requests (ms)

The default timeout value in milliseconds for requests that can be timed-out (e.g. implement the com.tangosol.net.PriorityTask interface), but do not explicitly specify the request timeout value.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Running

Specifies whether or not the service is running.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Statistics

Statistics for this service in human readable format.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

High Availability Status

The High Availability status for this service. The value of MACHINE-SAFE means that all the cluster nodes running on any given machine could be stopped at once without data loss. The value of NODE-SAFE means that any cluster node could be stopped without data loss. The value of ENDANGERED indicates that abnormal termination of any cluster node that runs this service may cause data loss.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Is Storage Enabled

Specifies whether or not the local storage is enabled for this cluster Member.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Execution Time Before Task is Considered Hung (ms)

The amount of time in milliseconds that a task can execute before it is considered hung. Note that a posted task that has not yet started is never considered as hung.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Default Timeout Value For Tasks (ms)

The default timeout value in milliseconds for tasks that can be timed-out (e.g. implement the com.tangosol.net.PriorityTask interface), but do not explicitly specify the task execution timeout value.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

No. Of Threads

The number of threads in the service thread pool.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Service Type

The type identifier of the service.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Service Performance

The service performance metrics are described.

No. Of Backups For Cache Storage - Per Node

The number of backups for every cache storage.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Owned Partitions Backup - Per Node

The number of partitions that this Member backs up (responsible for the backup storage).

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Owned Partitions Primary - Per Node

The number of partitions that this Member owns (responsible for the primary storage).

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Partitions Endangered - Per Node

The total number of partitions that are not currently backed up.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Partitions Unbalanced - Per Node

The total number of primary and backup partitions which remain to be transferred until the partition distribution across the storage enabled service members is fully balanced.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Partitions Vulnerable - Per Node

The total number of partitions that are backed up on the same machine where the primary partition owner resides.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Refresh Time

The timestamp when this model was last retrieved from a corresponding node. For local servers it is the local time.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Synchronous Request Average Duration (ms) - Per Node

The average duration (in milliseconds) of an individual synchronous request issued by the service since the last time the statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Synchronous Request Max Duration (ms) - Per Node

The maximum duration (in milliseconds) of a synchronous request issued by the service since the last time the statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

The No. Of Pending Synchronous Request - Per Node

The number of pending synchronous requests issued by the service.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Duration of Oldest Pending Synchronous Request (ms) - Per Node

The duration (in milliseconds) of the oldest pending synchronous request issued by the service.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total No. Of Timed-Out Requests - Per Node

The total number of timed-out requests since the last time the statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

No. Of Timed-Out Requests Since Last Collection - Per Node

The number of timed out requests per node since the last collection.

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 10-96 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Total No. Of Requests - Per Node

The total number of synchronous requests issued by the service since the last time the statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

No. Of Requests Since Last Collection - Per Node

The number of requests per node since the last collection.

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 10-97 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

High Availability Status

The High Availability status for this service. The value of MACHINE-SAFE means that all the cluster nodes running on any given machine could be stopped at once without data loss. The value of NODE-SAFE means that any cluster node could be stopped without data loss. The value of ENDANGERED indicates that abnormal termination of any cluster node that runs this service may cause data loss.

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 10-98 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

MATCH

Not Defined

ENDANGERED

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

No. Of Storage Nodes Running The Service - Per Node

Specifies the total number of cluster nodes running this Service for which local storage is enabled.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Average Duration Of Individual Task Execution(ms) - Per Node

The average duration (in milliseconds) of an individual task execution.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

No. Of Task Waiting For Execution - Per Node

The size of the backlog queue that holds tasks scheduled to be executed by one of the service threads.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total No. Of Executed Tasks - Per Node

The total number of executed tasks since the last time the statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

No. Of Executed Tasks Since Last Collection - Per Node

The number of executed tasks per node since the last collection.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

No. Of Executing Hung Tasks - Per Node

The total number of currently executing hung tasks.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Duration of Longest Running Hung Task (ms) - Per Node

The longest currently executing hung task duration in milliseconds.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Longest Currently Hung Task ID - Per Node

The ID of the of the longest currently executing hung task.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Maximum Size Of Backlog Queue Since statistics Reset -Per Node

The maximum size of the backlog queue since the last time the statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total No. Of Timed-Out Tasks - Per Node

The total number of timed-out tasks since the last time the statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

No. Of Timed Out Tasks Since Last Collection - Per Node

The number of timed out tasks per node since the last collection.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total No. Of Abandoned Threads - Per Node

The number of abandoned threads from the service thread pool. A thread is abandoned and replaced with a new thread if it executes a task for a period of time longer than execution timeout and all attempts to interrupt it fail.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

No. Of Abandoned Threads Since Last Collection - Per Node

The number of abandoned threads per node since the last collection.

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 10-99 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Average No. Of Active Threads - Per Node

The average number of active (not idle) threads in the service thread pool since the last time the statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

No. Of Threads

The number of threads in the service thread pool.

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 10-100 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

No. Of Idle Threads

The number of currently idle threads in the service thread pool.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Service Performance - Aggregated Over Nodes

The service performance metrics aggregated over nodes are described.

No. Of Backups For Cache Storage

The number of backups for every cache storage.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Owned Partitions Backup

The number of partitions that this Member backs up (responsible for the backup storage).

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 10-101 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Owned Partitions Primary

The number of partitions that this Member owns (responsible for the primary storage).

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 10-102 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Partitions Endangered

The total number of partitions that are not currently backed up.

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 10-103 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Partitions Unbalanced

The total number of primary and backup partitions which remain to be transferred until the partition distribution across the storage enabled service members is fully balanced.

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 10-104 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Partitions Vulnerable

The total number of partitions that are backed up on the same machine where the primary partition owner resides.

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 10-105 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Synchronous Request Average Duration (ms)

The average duration (in milliseconds) of an individual synchronous request issued by the service since the last time the statistics were reset.

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 10-106 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Synchronous Request Max Duration (ms)

The maximum duration (in milliseconds) of a synchronous request issued by the service since the last time the statistics were reset.

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 10-107 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

The No. Of Pending Synchronous Request

The number of pending synchronous requests issued by the service.

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 10-108 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Duration of Oldest Pending Synchronous Request (ms)

The duration (in milliseconds) of the oldest pending synchronous request issued by the service.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Total No. Of Timed-Out Requests

The total number of timed-out requests since the last time the statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Request Timeout Count Rate

The cumulative number of synchronous requests issued by the service since the last time the statistics were reset.

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 10-109 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Request Total Count

The total number of synchronous requests issued by the service since the last time the statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Request Total Count Rate

The cumulative total number of synchronous requests issued by the service since the last time the statistics were reset.

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 10-110 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Storage Enabled Count

Specifies the total number of cluster nodes running this Service for which local storage is enabled.

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 10-111 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Task Average Duration

The average duration (in milliseconds) of an individual task execution.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Task Backlog

The size of the backlog queue that holds tasks scheduled to be executed by one of the service threads.

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 10-112 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Task Count

The total number of executed tasks since the last time the statistics were reset.

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 10-113 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Task Count Rate

The cumulative total number of executed tasks since the last time the statistics were reset.

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 10-114 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Task Hung Count

The total number of currently executing hung tasks.

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 10-115 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Task Hung Duration

The longest currently executing hung task duration in milliseconds.

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 10-116 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Task Max Backlog

The maximum size of the backlog queue since the last time the statistics were reset.

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 10-117 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Task Timeout Count

The total number of timed-out tasks since the last time the statistics were reset.

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 10-118 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Task Timeout Count Rate

The cumulative number of timed-out tasks across all nodes since the last time the statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Thread Abandoned Count

The number of abandoned threads from the service thread pool. A thread is abandoned and replaced with a new thread if it executes a task for a period of time longer than execution timeout and all attempts to interrupt it fail.

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 10-119 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Thread Abandoned Count Rate

The cumulative number of abandoned threads from the service thread pool.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Thread Average Active Count

The average number of active (not idle) threads in the service thread pool since the last time the statistics were reset.

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 10-120 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Thread Count

The number of threads in the service thread pool.

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 10-121 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Thread Idle Count

The number of currently idle threads in the service thread pool.

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 10-122 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Storage Manager

The store manager metrics are described.

Events Dispatched - Per Node

The total number of events dispatched by the StorageManager since the last time the statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Eviction Count - Per Node

The number of evictions from the backing map managed by this StorageManager caused by entries expiry or insert operations that would make the underlying backing map to reach its configured size limit. The eviction count is used to audit the cache size in a static system. Cache Size = Insert Count - Remove Count - Eviction count. Therefore the eviction count is not reset by the reset statistics method.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Insert Count - Per Node

The number of inserts into the backing map managed by this StorageManager. In addition to standard inserts caused by put and invoke operations or synthetic inserts caused by get operations with read-through backing map topology, this counter is incremented when distribution transfers move resources `into` the underlying backing map and is decremented when distribution transfers move data `out`. The insert count is used to audit the cache size in a static system. Cache Size = Insert Count - Remove Count - Eviction count. Therefore the insert count is not reset by the reset statistics method.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Listener Filter Count - Per Node

The number of filter-based listeners currently registered with the StorageManager.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Listener Key Count - Per Node

The number of key-based listeners currently registered with the StorageManager.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Listener Registrations - Per Node

The total number of listener registration requests processed by the StorageManager since the last time the statistics were reset.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Locks Granted - Per Node

The number of locks currently granted for the portion of the partitioned cache managed by the StorageManager.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Locks Pending - Per Node

The number of pending lock requests for the portion of the partitioned cache managed by the StorageManager.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Remove Count - Per Node

The number of removes from the backing map managed by this StorageManager caused by operations such as clear, remove or invoke. The remove count is used to audit the cache size in a static system. Cache Size = Insert Count - Remove Count - Eviction count. Therefore the remove count is not reset by the reset statistics method.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Store Manager - Aggregated Over Nodes

Events Dispatched

The sum of events dispatched by the StorageManager since the last time the statistics were reset.

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 10-123 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Eviction Count

The sum of evictions from the backing map managed by this StorageManager caused by entries expiry or insert operations that would make the underlying backing map to reach its configured size limit. The eviction count is used to audit the cache size in a static system. Cache Size = Insert Count - Remove Count - Eviction count. Therefore the eviction count is not reset by the reset statistics method.

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 10-124 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Insert Count

The sum of inserts into the backing map managed by this StorageManager. In addition to standard inserts caused by put and invoke operations or synthetic inserts caused by get operations with read-through backing map topology, this counter is incremented when distribution transfers move resources `into` the underlying backing map and is decremented when distribution transfers move data `out`. The insert count is used to audit the cache size in a static system. Cache Size = Insert Count - Remove Count - Eviction count. Therefore the insert count is not reset by the reset statistics method.

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 10-125 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Listener Filter Counts

The sum of filter-based listeners currently registered with the StorageManager.

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 10-126 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Listener Key Count

The sum of key-based listeners currently registered with the StorageManager.

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 10-127 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Listener Registrations

The sum of listener registration requests processed by the StorageManager since the last time the statistics were reset.

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 10-128 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.

Locks Granted

The sum of locks currently granted for the portion of the partitioned cache managed by the StorageManager.

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 10-129 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Locks Pending

The sum of pending lock requests for the portion of the partitioned cache managed by the StorageManager.

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 10-130 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Remove Counts

The sum of removes from the backing map managed by this StorageManager caused by operations such as clear, remove or invoke. The remove count is used to audit the cache size in a static system. Cache Size = Insert Count - Remove Count - Eviction count. Therefore the remove count is not reset by the reset statistics method.

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 10-131 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Threading

The threading metrics are described.

Node ID

Coherence Node ID.

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.

Target Version

Collection Frequency

All Versions

Every Hour

Thread Count

Current live thread count for a Coherence node JVM.

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 10-132 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Peak Thread Count

Peak thread could for a Coherence node JVM.

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 10-133 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

1

Metric Value is %value%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.

If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" 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" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

11 HTTP Server

This chapter describes Oracle HTTP Server (OHS) metrics.

OHS Process Metrics

Provides metrics about Oracle HTTP Server processes.

Heap Usage (MB)

The amount of heap space (total program memory) used by Apache's parent process.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in Enterprise Manager Cloud 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.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x

Every 5 Minutes

After Every 12 Samples

>

Not Defined

Not Defined

2

Heap Usage is %value%MB

Oracle HTTP Server General Metrics

Provides general Oracle HTTP Server metrics.

Start Time (ms since Epoch)

This metric shows the start time of the Oracle HTTP Server.

Metric Summary

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

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; 9.0.4.x and 10.1.2.x

Every 5 Minutes

OHS Module Metrics

Contains metrics about Oracle HTTP Server modules.

Active Requests for a Module

This metric specifies the number of requests currently being handled by this module.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 rest of the information in this section is only valid for this metric when it appears in Enterprise Manager Cloud Control (if applicable).

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

OHS Response Code Metrics

Includes metrics about the amount of Oracle HTTP Server response codes since the Oracle HTTP Server was last restarted.

HTTP 4xx errors

The number of HTTP 4xx errors generated since the Oracle HTTP Server was last restarted.

Metric Summary

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

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; 9.0.4.x and 10.1.2.x

Every 15 Minutes

HTTP 5xx errors

This metric specifies the number of HTTP 5xx errors generated since the Oracle HTTP Server was last restarted.

Metric Summary

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

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; 9.0.4.x and 10.1.2.x

Every 15 Minutes

OHS Server Metrics

Displays information about the Oracle HTTP Server.

Busy Processes

This metric specifies the number of child servers that are busy.

Metric Summary

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

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; 9.0.4.x and 10.1.2.x

Every 5 Minutes

Percentage of Busy Processes

This metric shows the percentage of Oracle HTTP Server child processes that are currently servicing requests.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in Enterprise Manager Cloud 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.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x

Every 5 Minutes

After Every 12 Samples

>

85

90

2

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 Fusion Middleware Console. For more information about the MaxClients, MinSpareServers, and MaxSpareServers directives, go to the Apache HTTP Server Documentation section of the http://www.apache.org Web site, then navigate to the Directives information.

Active HTTP Connections

This metric shows the number of open HTTP connections.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in Enterprise Manager Cloud 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.

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 12 Samples

>

135

140

2

The number of active connections is %value%

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.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in Enterprise Manager Cloud 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.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x

Every 5 Minutes

After Every 12 Samples

>

1

1.5

2

The percentage of requests that resulted in errors is %value%%%

User Action

Use the Fusion Middleware Control Console to examine the errors in this Oracle HTTP Server's error log file. For information about viewing Oracle HTTP Server error logs in the Fusion Middleware Control, see the "Viewing Oracle HTTP Server Logs" topic in the Fusion Middleware Administrator's Guide.

Idle Processes

This metric specifies the number of child servers that are available.

Metric Summary

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

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; 9.0.4.x and 10.1.2.x

Every 5 Minutes

Active HTTP Requests

This metric specifies the number of requests currently being serviced.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in Enterprise Manager Cloud 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.

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 12 Samples

>

135

140

2

The number of active requests is %value%

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.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in Enterprise Manager Cloud 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.

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 12 Samples

>

Not Defined

Not Defined

2

The average processing time for a request is %value% seconds

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.

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.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in Enterprise Manager Cloud 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.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x

Every 5 Minutes

After Every 12 Samples

>

Not Defined

Not Defined

2

The average size of a request is %value%KB

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.

Metric Summary

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

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; 9.0.4.x and 10.1.2.x

Every 5 Minutes

OHS Virtual Host Metrics

Provides virtual host information.

Active Requests for a Virtual Host

This metric specifies the total number of active requests currently being processed by the virtual host.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in Enterprise Manager Cloud 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.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x

Every 5 Minutes

After Every 12 Samples

>

135

140

2

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 Thresholds for information on accessing the Edit Thresholds page.

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.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in Enterprise Manager Cloud 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.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x

Every 5 Minutes

After Every 12 Samples

>

Not Defined

Not Defined

2

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 Thresholds for information on accessing the Edit Thresholds page.

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.

Metric Summary

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

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; 9.0.4.x and 10.1.2.x

Every 5 Minutes

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.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in Enterprise Manager Cloud 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.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x

Every 5 Minutes

After Every 12 Samples

>

Not Defined

Not Defined

2

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. See Editing Thresholds for information on accessing the Edit Thresholds page.

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.

Metric Summary

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

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; 9.0.4.x and 10.1.2.x

Every 5 Minutes

Virtual Host Type

This metrics provides the type of virtual host, which can be IP_DEFAULT, NAME_DEFAULT, IP_BASED, or NAME_BASED.

Metric Summary

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

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

Target Version

Collection Frequency

9.0.4.x and 10.1.2.x

Every 5 Minutes

Resource Usage

Provides information about CPU and memory usage.

CPU Usage (%)

Shows the percentage of CPU used by the Oracle HTTP server.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in Enterprise Manager Cloud 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.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x

Every 5 Minutes

After Every 12 Samples

>

Not Defined

Not Defined

2

CPU Utilization is %value%%%

CPU Idle Time (%)

Shows the percentage of time the CPU has been idle on the host.

Metric Summary

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

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; 9.0.4.x and 10.1.2.x

Every 5 Minutes

Other CPU Usage (%)

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.

Metric Summary

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

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; 9.0.4.x and 10.1.2.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.

Memory Usage (MB)

This metric shows the current physical memory used by Oracle HTTP Server.

Metric Summary

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

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; 9.0.4.x and 10.1.2.x

Every 5 Minutes

Free Memory (MB)

This metric shows current free memory on the host that has an Oracle HTTP Server.

Metric Summary

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

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; 9.0.4.x and 10.1.2.x

Every 5 Minutes

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.

Metric Summary

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

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; 9.0.4.x and 10.1.2.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.

Total Memory (MB)

Amount of physical memory (in MB) for the host where Oracle HTTP Server is running.

Metric Summary

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

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; 9.0.4.x and 10.1.2.x

Every 5 Minutes

Memory Usage (%)

Shows the current percentage of physical memory used by the component.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in Enterprise Manager Cloud 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.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

9.0.2.x and 9.0.3.x; 9.0.4.x and 10.1.2.x

Every 5 Minutes

After Every 12 Samples

>

80

90

2

Memory Utilization is %value%%%

Free Memory (%)

This metric shows the percentage of current free memory on the host that has Oracle HTTP Server.

Metric Summary

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

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; 9.0.4.x and 10.1.2.x

Every 5 Minutes

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.

Metric Summary

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

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; 9.0.4.x and 10.1.2.x

Every 5 Minutes

Start Time (ms since Epoch)

This metric shows the start time of Oracle HTTP Server.

Metric Summary

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

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

Target Version

Collection Frequency

9.0.4.x and 10.1.2.x

Every 5 Minutes

Up Time (ms since Epoch)

This metric shows the total time the Oracle HTTP Server has been running.

Response

Contains metrics that give availability information about Oracle HTTP Server.

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.

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in Enterprise Manager Cloud 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.

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 Oracle HTTP Server instance is down

User Action

If the Oracle HTTP Server instance is down, start it using the Home page for the Oracle HTTP Server in the Fusion Middleware Control.

12 Java EE Application

This chapter describes metrics for Java EE applications deployed to Oracle WebLogic Server.

ADFC Taskflow Metrics

Metrics concerning ADFc (ADF Controller)

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Active Taskflows

This metric represents the number of currently active ADF task flows.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Active throughput

The rate at which task flows are processed since the data was last collected.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Active Taskflows

The number of active task flows processed since the last time metric data was collected.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Total Entered Taskflows

This metric displays the number of task flows entered at the current time.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Invoked Taskflows completed

The number of invoked task flows that have been completed at the current time.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Taskflow Invoke time

The average time taken over the past five minutes to invoke ADF taskflows.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Average Time

The average time to process task flows since the data was last collected.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Maximum Time

The maximum time taken to process task flows since the data was last collected.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Minimum Time

The minimum time taken to process the task flow since the data was last collected.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Module Removals

The number of Application Module instances removed at the current time.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Pool Checkouts

The number of free Application Module instances checked out at the current time.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Average Creation time(ms)

The average creation time for an ApplicationModule instance since the data was last collected.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Free Instances

The number of free Application Module instances at the current time.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Maximum Creation Time (ms)

The maximum creation time for an Application Module instance since the data was last collected.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Request Count

The number of main Application Module instances since the last request.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Available Instances in last 5 Minutes

For the selected ApplicationModule, the count of available ApplicationModule instances in the pool over the past five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Available Instances in last 1 min

For the selected ApplicationModule, the count of available ApplicationModule instances in the pool over the past one minute.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Unavailable Instances in last 5 Minutes

For the selected ApplicationModule, the number of unavailable ApplicationModule instances in the pool over the past five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Unavailable Instances in last 1 Minute

For the selected ApplicationModule, the count of unavailable ApplicationModule instances in the pool over the past one minute.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Activations

The name of the ApplicationModule to which the following metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Pool check Ins

The number of ApplicationModule instances checked into the ApplicationModule pool since the data was last collected.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Pool Check Outs

The number of ApplicationModule instances checked out of the ApplicationModule pool since the data was last collected.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Pool Check Out Failures

The number of ApplicationModule instance check out failures of the ApplicationModule pool since the data was last collected.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Referenced Modules Reused

This metric provides details on the referenced modules used

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Unreferenced Modules Recycled

This metric provides details on the unreferenced modules recycled.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Datasource Metrics

This category provides information about datasource metrics.

Datasource - Available Connections

For the selected data source, this metric shows the number of database connections currently available (not in use).

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.

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 60 Samples

<

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

Datasource - Connections in Use

For the selected data source, this metric shows the number of JDBC connections currently in use by applications.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

Datasource - Connection Pool Size

For the current data source, this metric shows the current count of JDBC connections in the JDBC connection pool.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

<

Not Defined

Not Defined

-

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

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).

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

Datasource - Connection Requests Waiting

For the selected data source, this metric shows the current number of JDBC connection requests waiting for a database connection.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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

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.

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 60 Samples

<

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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

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.

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 60 Samples

!=

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

<

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

<

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

<

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

<

Not Defined

Not Defined

-

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

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.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

EJB Module Metrics

This category provides information about EJB module metrics.

EJB Module - Cached Beans

This metric shows the total number of beans from this EJB Home that are currently in the EJB cache.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

EJB Module - Cache Hits (%)

This metric shows the percentage of cache accesses that completed successfully in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

EJB Module - Bean Accesses (per minute)

This metric shows the average EJB pool accesses per minute over the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

EJB Module - Bean Access Successes (%)

This metric shows the percentage of EJB pool accesses that were successful in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

EJB Module - Free Bean Instances

This metric shows the current number of available EJB instances in the free pool.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

EJB Module - Beans In Use

This metric shows the number of EJB instances currently being used from the free pool.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

EJB Transaction Metrics

This category provides information about EJB transaction metrics.

EJB Transaction - Bean Transaction Commits (%)

This metric shows the percentage of EJB transactions that were committed during the last five minutes.

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.

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 60 Samples

<

Not Defined

Not Defined

-

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

EJB Transaction - Bean Transaction Commits (per minute)

This metric shows the EJB transaction commits per minute, averaged over the past five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

EJB Transaction - Bean Transaction Rollbacks (per minute)

This metric shows the EJB transaction rollbacks per minute, averaged over the past five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

EJB Transaction - Bean Transaction Timeouts (per minute)

This metric shows the EJB transaction timeouts per minute, averaged over the past five minutes.

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.

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 60 Samples

>

Not Defined

Not Defined

-

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

Overview Metrics

This category provides information about the EJB overview metrics.

Cached Beans

This metric shows the total number of EJBs currently active in the EJB cache.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Cache Hits (%)

This metrics indicates the percentage of cache accesses that completed successfully in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Cache Misses (per minute)

This metric shows the average number of EJB cache misses per minute in this application in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Bean Accesses (per minute)

This metrics shows the average number of Pool accesses per minute for this application in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Free Bean Instances

This metric shows the current number of available EJB instances in the free pool.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Bean Destroys (per minute)

This metric shows the average number of EJB destroys per minute for this application in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Beans In Use

This metric shows the number of EJB instances currently being used from the free pool.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Bean Transaction Commits (%)

This metric shows the percentage of EJB transactions that were committed for this application during the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Active Sessions

This metric shows the number of active sessions for this application.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Work Manager Pending Requests

This metric shows the number of Work Manager requests waiting in the queue.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Servlet/JSP Metrics

This category provides information about servlet/JSP metrics.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Status Metrics

This category provides information about status metrics.

Server Name

This metric shows the name of the current WebLogic server.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Web Module Metrics

This category provides information about Web module metrics.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

Web Module - Active Sessions

This metric shows the number of active sessions for this web module.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No user action.

MDS Metrics

Metrics concerning MDS (Metadata Services)

Metadata Object Gets Per Second

The number of metadata object gets per second.

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.

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.

Metadata Object Get Processing Time (seconds)

The average elapsed time in seconds to get a metadata object.

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.

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 3 Samples

>

Not Defined

Not Defined

2

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.

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.

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.

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 3 Samples

>

Not Defined

Not Defined

2

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.

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.

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.

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 3 Samples

>

Not Defined

Not Defined

2

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.

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.

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.

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 3 Samples

>

Not Defined

Not Defined

2

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.

Metadata Updates Per Second

The average number of metadata objects updated per second.

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.

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.

Metadata Update Processing Time (seconds)

The average elapsed time in seconds taken to update a metadata object.

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.

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 3 Samples

>

Not Defined

Not Defined

2

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).

Response

This category provides information about response metrics

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.

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.

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 J2EE Application is down

13 Oracle Service Bus

This chapter describes Oracle Service Bus (OSB) metrics.

Oracle Service Bus

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.

Flow Component Resource Details Metrics

This category provides information about the resource type FLOW_COMPONENT.

Average Response Time (Flow Component)

This metric shows the average response time of the resource type (FLOW_COMPONENT) since last collection (75 minutes).

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.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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 Thresholds for information on accessing the Edit Thresholds page.

Open Instance Count (FLOW_COMPONENT)

This metric shows the open instance count of the resource type (FLOW_COMPONENT) since last collection (75 minutes).

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.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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 Thresholds for information on accessing the Edit Thresholds page.

Error Instance Count (Flow Component)

This metric shows the error instance count of the resource type (FLOW_COMPONENT) since last collection (75 minutes).

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.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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 Thresholds for information on accessing the Edit Thresholds page.

End Point URI Resource Details Metrics

This category provides information about the resource type URI.

Average Response Time (End Point URI)

This metric shows the average response time of the resource type (URI) since last collection (75 minutes).

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.

This table lists the metric's collection and threshold information.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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 Thresholds for information on accessing the Edit Thresholds page.

Open Instance Count (End Point URI)

This metric shows the open instance count of the resource type(URI) since last collection (75 minutes).

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.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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 Thresholds for information on accessing the Edit Thresholds page.

Error Instance Count (End Point URI)

This metric shows the error instance count of the resource type (URI) since last collection (75 minutes).

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.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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 Thresholds for information on accessing the Edit Thresholds page.

End Point Operation Resource Details Metrics

This category provides information about the resource type WEBSERVICE_OPERATION.

Average Response Time (End Point Operation)

This metric shows the average response time of the resource type (WEBSERVICE_OPERATION) since last collection (75 minutes).

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.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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 Thresholds for information on accessing the Edit Thresholds page.

Open Instance Count (End Point Operation)

This metric shows the open instance count of the resource type (WEBSERVICE_OPERATION) since last collection (75 minutes).

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.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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 Thresholds for information on accessing the Edit Thresholds page.

Error Instance Count (End Point Operation)

This metric shows the error instance count of the resource type (WEBSERVICE_OPERATION) since last collection (75 minutes).

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.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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 Thresholds for information on accessing the Edit Thresholds page.

OSB Service Details Metrics

This category provides metrics related to Oracle Service Bus services. The information is collected every 24 hours.

Contains Sensitive Details

This metric indicates whether or not the service handles sensitive data.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Created User

This metric shows the name of the user who created the service.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Created Time

This metric shows the time when the service was created.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

End Point URI

This metric shows the end point URI of the service.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Last Modified User

This metric shows the name of the user who last modified the service.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Last Modified Time

This metric shows the time when the service was last modified.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Protocol

This metric shows the protocol of the service it operates on.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Status

This metric shows the status of the service. The status can be either Up or Down.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

Version

This metric shows the version of Oracle Service Bus.

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.

Target Version

Collection Frequency

All Versions

Every 24 Hours

OSB Service Metrics

This category provides metrics related to proxy services and business services running on Oracle Service Bus.

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.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Total Average Response Time

This metric shows the total average time taken by the service to respond since the time the server was restarted.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Open Instance Count

This metric shows the number of open instances of the service since last collection. The information is collected every 75 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Total Open Instance Count

This metric shows the total number of messages handled by this service since the time the server was restarted.

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.

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 Thresholds for information on accessing the Edit Thresholds page.

Error Instance Count

This metric shows the number of errored instances for the service since last collection. The information is collected every 75 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Total Error Instance Count

This metric shows the total number of error instances occurred on this service since the time the server was restarted.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Failure Rate

This metric shows the failure rate of messages since last collection.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Maximum Response Time

This metric shows the maximum time taken by this service to respond since the time the server was restarted.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Minimum Response Time

This metric shows the minimum time taken by this service to respond since the time the server was restarted.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Service Name

This metric shows the name of the proxy or business service running on Oracle Service Bus.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Path

This metric shows the current path to the project and resource directory hierarchy in the configuration.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Project Name

This metric shows the name of the project associated with Oracle Service Bus.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Service Type

This metric shows the type of service running on Oracle Service Bus. The service type can be Proxy or Business.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

OSB Proxy Service Metrics

This category provides metrics related to proxy services and business services running on Oracle Service Bus.

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.

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.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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 Thresholds for information on accessing the Edit Thresholds page.

Total Average Response Time

This metric shows the total average time taken by the service to respond since the time the server was restarted.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Open Instance Count

This metric shows the number of open instances of the service since last collection. The information is collected every 75 minutes.

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.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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 Thresholds for information on accessing the Edit Thresholds page.

Total Open Instance Count

This metric shows the total number of messages handled by this service since the time the server was restarted.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Error Instance Count

This metric shows the number of errored instances for the service since last collection. The information is collected every 75 minutes.

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.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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 Thresholds for information on accessing the Edit Thresholds page.

Total Error Instance Count

This metric shows the total number of error instances occurred on this service since the time the server was restarted.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Failure Rate

This metric shows the failure rate of messages since last collection.

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.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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 Thresholds for information on accessing the Edit Thresholds page.

Maximum Response Time

This metric shows the maximum time taken by this service to respond since the time the server was restarted.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Minimum Response Time

This metric shows the minimum time taken by this service to respond since the time the server was restarted.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Service Name

This metric shows the name of the proxy or business service running on Oracle Service Bus.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Path

This metric shows the current path to the project and resource directory hierarchy in the configuration.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Project Name

This metric shows the name of the project associated with Oracle Service Bus.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Service Type

This metric shows the type of service running on Oracle Service Bus. The service type can be Proxy or Business.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

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.

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.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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 Thresholds for information on accessing the Edit Thresholds page.

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.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

OSB Service Dependency Metrics

This category provide metrics related to the services that are dependent on a particular service.

Dependent Service ID

This metric shows the ID of the service that is dependent on this particular service.

Response

This category provides status metrics for Oracle Service Bus.

Status

This metric shows the current status of Oracle Service Bus. The status can be either Up or Down.

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.

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 Sample

=

Not Defined

0

1

ALSB IS DOWN......

SLA Alert Metrics

This category provides information about the SLA alerts generated in the OSB console.

Service Name

This metric shows the name of the service (Proxy/Business).

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Project Name

This metric shows the name of the project.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

SLA Severity Critical Alerts

This metric shows the number of SLA severity alerts since last collection (Severity Level - Critical, interval - 75 minutes).

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.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

Number of OSB Severity critical alerts 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 Thresholds for information on accessing the Edit Thresholds page.

Total SLA Severity Critical Alerts

This metric shows the total number of SLA severity alerts since the time the server restarted(Severity Level - critical).

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

SLA Severity Fatal Alerts

This metric shows the number of SLA severity alerts since last collection (Severity Level - Fatal, interval - 75 minutes).

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.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

Number of OSB Severity fatal alerts 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 Thresholds for information on accessing the Edit Thresholds page.

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).

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

SLA Severity Major Alerts

This metric shows the number of SLA severity alerts since last collection (Severity Level - Major, interval - 75 minutes).

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.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

Number of OSB Severity minor alerts 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 Thresholds for information on accessing the Edit Thresholds page.

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).

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

SLA Severity Minor Alerts

This metric shows the number of SLA severity alerts since last collection (Severity Level - Minor, interval - 75 minutes).

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.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

Number of OSB Severity major alerts 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 Thresholds for information on accessing the Edit Thresholds page.

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).

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

SLA Severity Warning Alerts

This metric shows the number of SLA severity alerts since last collection (Severity Level - Warning, interval - 75 minutes).

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.

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 75 Minutes

After Every Sample

>

Not Defined

Not Defined

1

Number of OSB Severity warning alerts 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 Thresholds for information on accessing the Edit Thresholds page.

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).

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Service Type

This metric shows the type of service either Proxy or Business.

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.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

14 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.

B2B Active Entities Metrics

This category provides information about B2B active entities metrics.

Number of Active Agreements

This metric shows the number of active agreements.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Number of Active Documents

This metric shows the number of active documents.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Number of Active Trading Partners

This metric shows the number of active trading partners.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

B2B Document Metrics Table

This category provides information about B2B Document Metrics Table metrics.

Number of Inbound Messages

This metric shows the number of inbound messages.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Number of inbound message faults

This metric shows the number of inbound message faults.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Inbound Message Size (KB)

This metric shows the inbound message size.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Inbound Messages processing time

This metric shows the processing time for inbound messages.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

B2B Document Name

This metric shows the B2B document name.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Number of Outbound Messages

This metric shows the number of outbound messages.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Number of outbound message faults

This metric shows the number of outbound message faults.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Outbound Message Size (KB)

This metric shows the outbound message size.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Outbound Messages processing time

This metric shows the processing time for outbound messages.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

B2B Inbound Endpoint Metrics

This category provides information about B2B Inbound Endpoint metrics.

B2B Inbound Endpoint Status

This metric shows the status of the B2B inbound endpoint.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

B2B Outbound Endpoint Metrics

This category provides information about B2B Outbound Endpoint metrics.

B2B Outbound Endpoint Status

This metric shows the status of the B2B outbound endpoint.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

B2B Trading Partner Metrics

This category provides information about B2B Trading Partner metrics.

Number of inbound messages

This metric shows the number of inbound messages for B2B trading partners.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Number of inbound message faults

This metric shows the number of inbound message faults for B2B trading partners.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Inbound Message Size (KB)

This metric shows the inbound size of messages for B2B trading partners.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Processing time of Inbound Messages

This metric shows the processing time of inbound messages for B2B trading partners.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Trading partner name

This metric shows the name of the trading partner.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Number of outbound messages

This metric shows the number of outbound messages for B2B trading partners.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Number of outbound message faults

This metric shows the number of outbound message faults for B2B trading partners.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Outbound Message Size (KB)

This metric shows the outbound size of messages for B2B trading partners.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Processing time of outbound messages

This metric shows the processing time of outbound messages for B2B trading partners.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

BPEL Engine Requests Rate Metric Table

Displays the BPEL Engine request related metrics

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Last active request value

This metric shows the value for the last active request in the BPEL service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Last scheduled request value

This metric shows the value for the last scheduled request in the BPEL service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Business Rules Engine Cache Metrics Table

Displays the business rules service engine cache metrics.

Total Access Count since server startup

This metric shows the total access count since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Last value of access count

This metric shows the last value of the access count in the business rules service engine cache.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total Count since server startup

This metric shows the total count of objects in the cache since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Last value of total count

This metric shows the last value of the total count.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Business Rule Engine Request Breakdown Rate Metric Table

Displays the path of a message/request within the service engine.

Request count since server startup

This metric shows the count of objects in the cache since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Throughput of requests in the last 5 minutes

This metric shows the request message throughput in the last five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Last value of request

This metric shows the value of the last request message.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Average request processing time

This metric shows the average request processing time for messages.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Number of completed requests

This metric shows the number of completed instances.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Response

Shows if the SOA server is available or not.

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.

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.

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

SOA Infrastructure Bindings Rate Metric Table

Shows metrics of the SOA Bindings.

Active request throughput in the last 5 minutes

This metric shows the active request throughput in the last five minutes in the binding component.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Number of faults since server startup

This metric shows the number of faults in the binding component since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Average request processing time

This metric shows the average request processing time for the binding component.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total number of processed requests since server startup

This metric shows the total number of processed requests since server startup in the binding component.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

SOA Composite Bindings/References Rate Metric

This category provides information about SOA composite bindings/references rate metrics.

Total number of faults since server start

This metric shows the total number of faults since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Throughput of faults in the last 5 minutes

This metric shows the throughput for faults in the last five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Average Incoming Messages Processing Time

This metric shows the average processing time for incoming messages.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total completed incoming messages since server start

This metric shows total number of completed incoming messages since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Incoming messages throughput in the last 5 minutes

This metric shows the throughput for incoming messages in the last five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total Incoming Messages Processing Time

This metric shows the total processing time for incoming messages.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total Incoming Message processing time

This metric shows the total processing time for incoming message.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total number of incoming messages since server start

This metric shows the total number of incoming messages since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Incoming message throughput in the last 5 minutes

This metric shows the throughput for incoming messages in the last five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Average Outbound Messages Processing Time

This metric shows the average processing time for outbound messages.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total completed outgoing messages since server start

This metric shows the total number of completed, outgoing messages since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Outbound messages throughput in the last 5 minutes

This metric shows the throughput for outbound messages in the last five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total Outbound Messages Processing Time since server start

This metric shows the total processing time for outbound messages since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total Outbound Message processing time

This metric shows the total processing time for outbound messages.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total number of outgoing messages since server start

This metric shows the total number of outgoing messages since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Outbound message events throughput in the last 5 minutes

This metric shows the throughout for outbound message events in the last five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

BPEL Dispatcher Rate Metric Table

Displays throughput metrics related to the BPEL dispatcher.

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Throughput of total messages in the last 5 minutes

This metric shows the total message throughput in the BPEL dispatcher.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Last value of total message

This metric shows the last value of all messages in the BPEL dispatcher.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Last value of average thread allocation time

This metric shows the last value of average thread allocation time in the BPEL dispatcher.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Last value of average thread lifetime

This metric shows the last value for the lifetime of the average thread in the BPEL dispatcher.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Throughput of maximum threads in the last 5 minutes

This metric shows the throughput for maximum threads in the last five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Last value of maximum thread

This metric shows the last value for the maximum thread in the BPEL dispatcher.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Throughput of minimum threads in the last 5 minutes

This metric shows the throughput for minimum threads in the last five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Last value of minimum thread

This metric shows the last value for the minimum thread in the BPEL dispatcher.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Number of active threads since server startup

This metric shows the number of active threads since server startup in the BPEL dispatcher.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Last value of thread count

This metric shows the last thread count value in the BPEL dispatcher.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Number of thread highs since server startup

This metric shows the number of high thread levels in the BPEL dispatcher since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Last value of thread high

This metric shows the last high value of the thread in the BPEL dispatcher.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Number of pending threads since server startup

This metric shows the number of pending threads in the BPEL dispatcher since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Last value of pending thread

This metric shows the last value of the pending thread in the BPEL dispatcher.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total number of threads since server startup

This metric shows the total number of threads in the BPEL dispatcher since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Last value of total thread metric

This metric shows the last value for the total thread metric in the BPEL dispatcher.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

BPMN Dispatcher Rate Metric Table

Throughput of total messages in the last 5 minutes.

Last value of maximum thread

This metric shows the last value for the maximum thread in the BPMN dispatcher

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Number of active threads since server startup

This metric shows the number of active threads since server startup in the BPMN dispatcher.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

SOA Mediator Engine Cache

This category provides information about SOA Mediator Engine Cache metrics.

Last value of metadata cache

This metric shows the last value of the metadata cache in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Last value of transformation cache

This metric shows the last value of transformation cache in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

SOA Mediator Engine Requests

This metric shows the callback requests in the mediator service engine

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Callback Requests

This metric shows the callback requests in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Delay Requests

This metric shows the delayed requests in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Dequeue Requests

This metric shows the dequeued requests in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Timeout Requests

This metric shows the timed out requests in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

SOA Mediator Engine Request Breakdown Rate Metric Table

Displays the path taken by a request in the Mediator Service Engine and the time spent

enqueue-phase.active

This metric shows the active enqueued phases in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Avg Enqueue Time (ms)

This metric shows the average time spent on enqueuing in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Enqueued

This metric shows the completed enqueuing phases in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Throughput of Enqueue phase

This metric shows the throughput for enqueuing in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total Enqueue Time (ms)

This metric shows the total enqueuing time in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

invoke-phase.active

This metric shows the active invocations in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Avg Invoke Time (ms)

This metric shows the average invocation time in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Invoked

This metric shows the completed invocations in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Throughput of Invoke phase

This metric shows the throughput for invocations in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total Invoke Time (ms)

This metric shows the total invocation time in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

invokeOneway-phase.active

This metric shows the active one-way invocations in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Avg Oneway Invoke Processing Time (ms)

This metric shows the average processing time for one-way invocations in milliseconds in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Oneway Invocations

This metric shows the completed one-way invocations in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Throughput of Oneway Invocations

This metric shows the throughput for one-way invocations in the mediator service component.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total Oneway Invocation Time (ms)

This metric shows the total time for one-way invocations in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

publish-phase.active

This metric shows the active publishing phases in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Avg Publication Time (ms)

This metric shows the average publication times in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Publications

This metric shows the completed publishing phases in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Throughput of Publication phase

This metric shows the throughput for publications in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total Publication Time (ms)

This metric shows the total publication times in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

transformation-phase.active

This metric shows the active transformation phases in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Avg Transformation Time (ms)

This metric shows the average time for transformations in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Transformations

This metric shows the completed transformations in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Throughput of Transformations

This metric shows the throughput for transformations in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total Transformation Time (ms)

This metric shows the total time for transformations in the mediator service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

SOA Infra Mesh

Displays the SOA server mesh metrics

Number of active messages in the mesh

This metric displays the number of active messages in the SOA server.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total number of messages in the mesh since server startup

This metric shows the total number of messages in the SOA server since startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Number of faulted messages in the mesh

This metric displays the number of faulted messages in the SOA server.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

SOA Infra Mesh Message Count Table

This metric shows the soa infra mesh message count.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Mesh Name

This metric shows service infrastructure performance.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Number of active asynchronous messages

This metric shows the number of active, asynchronous messages in the SOA server at this time.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Average processing time of asynchronous messages

This metric shows the average processing time for asynchronous messages in the SOA server.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Number of completed asynchronous messages

This metric shows the number of completed asynchronous messages in the SOA server.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total processing time of asynchronous messages

This metric shows the total processing time for asynchronous messages in the SOA server.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Number of active synchronous messages

This metric shows the number of active, synchronous messages in the SOA server.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Average processing time of synchronous messages

This metric shows the average processing time for synchronous messages in the SOA server.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Number of completed synchronous messages

This metric displays the number of completed, synchronous messages in the SOA server.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total processing time of synchronous messages

This metric shows the total processing time for synchronous messages in the SOA server.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

SOA Message Processing Rate Metric Table

Displays the metrics related to message processing in the service engines

Total number of active requests since server startup

This metric shows the total number of active requests since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Throughput of the active requests in the last 5 minutes

This metric shows message processing details in the service engines.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Last value of active request

This metric shows the last value of the active request.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

BPEL Service Engine

Total number of BPEL messages since startup

This metric shows the total number of BPEL messages since startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Engine Name

This metric shows the BPEL service engine name.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Decision Service Engine

Total number of decision service messages since startup

This metric shows the total number of decision service messages since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Engine Name

This metric shows the decision service engine name.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Number of faults since server startup

This metric shows the number of faults occurring since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Throughput of faulted requests in the last 5 minutes

This metric shows the throughput of faulted requests in the last five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Rate of processing faulted requests

This metric shows the processing rate for faulted requests.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Mediator Service Engine

Total number of mediator messages since startup

This metric shows the total number of mediator messages since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Engine Name

This metric shows the mediator service engine name.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total number of messages since server startup

This metric shows the total number of messages since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total number of asynchronous requests since server startup

This metric shows the total number of asynchronous requests since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Throughput of asynchronous invocations in the last 5 minutes

This metric shows the throughput of asynchronous invocations in the last five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Rate of processing asynchronous invocations

This metric shows processing rate for asynchronous invocations.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Average asynchronous message processing time since server startup

This metric shows the average processing time for asynchronous messages since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total number of synchronous requests since server startup

This metric shows the total number of synchronous requests since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Synchronous invocations throughput in the last 5 minutes

This metric shows the throughput for synchronous invocations in the last five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Rate of processing synchronous invocations

This metric shows the processing rate for synchronous invocations.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Average synchronous message processing time since server startup

This metric shows the average processing time for synchronous messages since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Workflow Service Engine

Total number of workflow messages since startup

This metric shows the total number of human workflow messages since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Engine Name

This metric shows the human workflow service engine name.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total Composite Instances

Shows the instance metrics of composites deployed on the SOA server

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.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Domain Name

This metric shows the instance metrics of composites deployed on the SOA server.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Total Composite Faults

Displays the metrics of the composite faults

Total number of faults since server startup

This metric shows the total number of faults across all composite instances since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Workflow Request Breakdown Rate Metrics

Shows the various services used by the Workflow Service Engine and their usage metrics.

Number of invocations since server startup

This metric shows the total number of invocations in the human workflow service engine since server startup.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Service Name

This metric shows the name of the internal service used by the human workflow service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Number of active requests

This metric shows the number of active requests in the human workflow service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Average request processing time

This metric shows the average request processing time in the human workflow service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Number of completed requests

This metric shows the total number of completed requests in the human workflow service engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

15 SOA Composite

This chapter describes Oracle SOA Composite metrics.

SOA Composite B2B Inbound Metrics

Displays the metrics for the Composite B2B Inbound messages.

InBound Message Count

This metric displays the number of inbound messages in B2B trading partners.

Inbound Messages Faults

This metric displays the number of faults in inbound messages in the B2B binding.

Inbound Messages Size

This metric displays the inbound message size in the B2B binding.

Inbound Message Processing Time

This metric displays the time taken to process inbound messages by the B2B binding.

ServerName

This metric shows the name of the server for inbound messages in B2B trading partners.

Total Outbound Messages Count

This metric displays the total number of outbound messages in the B2B binding.

SOA Composite B2B Outbound Metrics

Displays the B2B outbound message metrics.

Name

This metric displays the name

OutBound Message Count

This metric displays the number of outbound messages in the B2B binding.

Outbound Messages Faults

This metric displays the number of faults in outbound messages in the B2B binding.

Outbound Messages Size

This metric displays the size of outbound messages in the B2B binding.

Outbound Message Processing Time

This metric displays the processing time for outbound messages in the B2B binding.

ServerName

This metric shows the name of the server for B2B outbound messages.

Total Outbound Messages Count

This metric displays the total number of outbound messages in the B2B binding.

BPEL Activity Time Distribution

Shows the information related to the BPEL activity-time distribution.

Average Execution Time (ms)

This metric shows the average time it took for this BPEL activity to execute.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Activity Count

This metric shows the number of times this BPEL activity has been invoked.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Activity Name

This metric shows the name of the BPEL activity whose data is being shown.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Server Name

This metric shows the name of the J2EE container in which the SOA composite application is deployed.

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.

Target Version

Collection Frequency

All Versions

Every Minute

SOA Composite - Response Metrics

Indicates whether the SOA composite application is available to accept requests.

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.

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.

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 J2EE Application is down

SOA Composite Bindings/References Rate Metric

Displays metrics about the SOA bindings.

Total number of faults since server start

This metric shows the total number of faulted messages in the binding.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Average Incoming Messages Processing Time

This metric shows the average processing time of incoming messages in the binding.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Total number of incoming messages since server start

This metric shows the total number of incoming messages in the binding.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Incoming message throughput in last 5 minutes

This metric shows the throughput for inbound messages in the binding.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Average Outbound Messages Processing Time

This metric shows the average processing time of outbound messages in the binding.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Total number of outgoing messages since server start

This metric shows the total number of outbound messages in the binding.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Outbound message throughput in last 5 minutes

This metric shows the throughput for outbound messages in the binding.

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.

Target Version

Collection Frequency

All Versions

Every Minute

SOA Component References

Shows the metrics of the SOA component references.

Average Message Processing Time (secs) since server start up

This metric shows the average time taken by the reference to respond to invocations.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Number of Faults

This metric shows the number of faults encountered when this reference was invoked.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Number of Messages

This metric shows the number of times that this reference has been invoked by the SOA component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Average Message Processing Time (secs) in last 5 mins

This metric shows the total time taken by the reference to respond to an invocation.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Reference Name

This metric shows the SOA component whose reference is being shown.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Component References

This metric shows the SOA component reference name.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Component Type

This metric indicates that the current type is a component whose references are being listed.

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.

Target Version

Collection Frequency

All Versions

Every Minute

SOA Component Rollup Metric

Shows all SOA component throughput metrics.

Business faults throughput in the last 5 minutes

This metric shows the throughput for messages with business faults in this SOA component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Number of active faulted instances

This metric shows the number of active, faulted messages in this SOA component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Average processing time for faulted instances

This metric shows the average time spent processing faulted messages in this SOA component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Number of faulted instances

This metric shows the number of faulted messages in this SOA component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Throughput of faulted instances in the last 5 minutes

This metric shows the throughput for faulted messages in this SOA component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Total time spent on processing faulted instances

This metric shows the time spent processing faulted messages in this SOA component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Total average faulted processing time

This metric shows the total time spent processing faulted messages in this SOA component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Instance throughput in the last 5 minutes

This metric shows the throughput for incoming messages in the SOA component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Server Name

This metric shows the SOA component throughput for the server.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Number of active successful instances

This metric shows the number of successful, active messages in this SOA component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Average processing time for successful instances

This metric shows the average time spent processing successful messages in this SOA component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Number of successful instances

This metric shows the number of successfully completed messages in this SOA component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Throughput of successful instances in the last 5 minutes

This metric shows the throughput for successful messages in this SOA component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Total time spent on processing successful instances

This metric shows the time spent processing successful messages in this SOA component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Total average successful processing time

This metric shows the total time spent processing successful messages.

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.

Target Version

Collection Frequency

All Versions

Every Minute

System faults throughput in the last 5 minutes

This metric shows the throughput for messages with system faults in this SOA component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Total faults throughput in the last 5 minutes

This metric shows the throughput for all faulted messages in this SOA component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

SOA Composite - Rate Metrics

Displays the throughput metrics for a SOA composite.

Instance throughput in the last 5 minutes

This metric shows the total throughput for the composite instances.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Asynchronous message event throughput in the last 5 minutes

This metric shows the throughput for asynchronous messages.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Average asynchronous message Processing time

This metric shows the average processing time of asynchronous messages in the SOA composite.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Asynchronous messages throughput in the last 5 minutes

This metric shows the throughput of asynchronous messages in this SOA composite.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Total asynchronous message processing time

This metric shows the total processing time of asynchronous messages in the SOA composite.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Synchronous message event throughput in the last 5 minutes

This metric displays the throughput for requests to the SOA composite.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Average synchronous message processing time

This metric shows the average processing time of synchronous messages in this SOA composite.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Synchronous messages throughput in the last 5 minutes

This metric shows the throughput for all synchronous messages to this composite.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Total synchronous message processing time

This metric shows the total processing time of synchronous messages for this SOA composite.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Server Name

This metric shows the name of the server on which the SOA composite application revision is deployed.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Mediator Case

Displays metrics about the mediator case.

Average processing time of invocations

This metric shows the average processing time of invocations in the mediator component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Invocation throughput in the last 5 minutes

This metric shows the throughput for messages in the mediator case.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Total processing time for invocations

This metric shows the total processing time of invocations in the mediator component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Failed filtered messages throughput in the last 5 minutes

This metric shows the throughput for the failed, filtered message in the mediator case.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Average processing time of faulted cases

This metric shows the average processing time of faulted cases in the mediator component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Number of faulted cases

This metric shows the number of faulted cases in this mediator component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Faulted case throughput in the last 5 minutes

This metric shows the throughput of faulted cases in this mediator component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Total processing time for faulted cases

This metric shows the total processing time for faulted cases in the mediator component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Filtered messages throughput in the last 5 minutes

This metric shows the throughput for the filtered messages of the mediator case.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Invocation Count throughput in the last 5 minutes

This metric shows the throughput for the invocation count of the mediator case.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Component Type

This metric shows the component type, which in this case is always mediator.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Composite Label

This metric shows the label of the SOA composite.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Case Target

This metric shows the case target of the mediator.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Mediator Flow

This metric shows the state of the mediator flow.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Flow Type

This metric shows the flow type of the mediator component case.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Average processing time of successful cases

This metric shows the average processing time of successful cases.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Number of successful cases

This metric shows the number of successful cases in this mediator component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Successful case throughput in the last 5 minutes

This metric shows the throughput for successful cases in this mediator component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Total processing time for successful cases

This metric shows the total processing time for successful cases in this mediator component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Mediator Flow Metric

Displays metrics about the Mediator component's flow.

Deferred message count throughput in last 5 minutes

This metric shows the throughput for the deferred message count in the mediator component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Failed filter case throughput in last 5 minutes

This metric shows the throughput for the failed filter case in the mediator component.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Average faulted instance processing time

This metric shows the average time spent processing faulted messages.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Faulted instances throughput in last 5 minutes

This metric shows the throughput for faulted messages.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Total faulted instance processing time

This metric shows the total time spent processing faulted messages.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Instance throughput in last 5 minutes

This metric shows the throughput for the mediator instances.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Component Type

This metric shows the component type, which in this case is always mediator.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Composite Label

This metric shows the SOA composite label in which the mediator component is packaged.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Flow Type

This metric shows the flow type for the mediator.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Average successful instance processing time

This metric shows the average time spent processing successful messages.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Successful instances throughput in last 5 minutes

This metric shows the successful instance processing time.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Total successful instance processing time

This metric shows the total time spent processing successful messages.

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.

Target Version

Collection Frequency

All Versions

Every Minute

Total Composite Instances

Displays metrics about the total composite instances.

Total number of composite instances since server startup

Domain Name

The domain name

Total Composite Faults

Displays metrics about total composite faults.

Total number of faults since server startup

This is the number of faults recorded since server startup.

Reference Binding Rollup

This provides details on the references exposed by the composite

Average Incoming Messages Processing Time

This metric shows the average incoming messages processing time.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Average Incoming Messages Processing Time (ms)

This metric shows the average incoming messages processing time in milliseconds.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Average Outbound Messages Processing Time

This metric shows the average outbound messages processing time.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Average Outbound Messages Processing Time (ms)

This metric shows the average outbound messages processing time in milliseconds.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Binding - Error rate

This metric shows the binding error rate.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Composite Revision

This metric shows the revision of the composite.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Composite Name

This metric shows the composite name.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Domain Name

This metric shows the domain name.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

End Point URL

This metric shows the end point URL.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Incoming message throughput in last 5 minutes

This metric shows the incoming message throughput in last five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Incoming message throughput in last 5 minutes (sec)

This metric shows the incoming message throughput in last five minutes, expressed in seconds.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Outbound message throughput in last 5 minutes

This metric shows the outbound message throughput in the last five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Outbound message throughput in last 5 minutes (sec)

This metric shows the outbound message throughput in the last five minutes, expressed in seconds.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Reference Name

This metric shows the reference name.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Reference Type

This metric shows the reference type.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Total number of faults since last collection

This metric shows the total number of faults since last collection.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Total number of faults since startup

This metric shows the total number of faults since startup.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Total number of incoming messages Since Last Collection

This metric shows the total number of incoming messages since last collection.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Total number of incoming messages since startup

This metric shows the total number of incoming messages since startup.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Total number of outgoing messages since last collection

This metric shows the total number of outgoing messages since last collection.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Total number of outgoing messages since startup

This metric shows the total number of outgoing messages since startup.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

WSDL Port

This metric shows the WSDL port.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

WSDL URL of the service

This metric shows the WSDL URL of the service.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Service Binding Rollup

This provides details on the services exposed by the composite.

Average Incoming Messages Processing Time

This metric shows the average incoming messages processing time.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Average Incoming Messages Processing Time (ms)

This metric shows the average incoming messages processing time in milliseconds.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Average Outbound Messages Processing Time

This metric shows the average outbound messages processing time.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Average Outbound Messages Processing Time (ms)

This metric shows the average outbound messages processing time in milliseconds.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Binding - Error rate

This metric shows the binding error rate.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Composite Revision

This metric shows the revision of the composite.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Composite Name

This metric shows the composite name.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Domain Name

This metric shows the domain name.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

End Point URL

This metric shows the end point URL.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Incoming message throughput in last 5 minutes

This metric shows the incoming message throughput in last five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Incoming message throughput in last 5 minutes (sec)

This metric shows the incoming message throughput in last five minutes, expressed in seconds.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Outbound message throughput in last 5 minutes

This metric shows the outbound message throughput in the last five minutes.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Outbound message throughput in last 5 minutes (sec)

This metric shows the outbound message throughput in the last five minutes, expressed in seconds.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Reference Name

This metric shows the reference name.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Reference Type

This metric shows the reference type.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Total number of faults since last collection

This metric shows the total number of faults since last collection.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Total number of faults since startup

This metric shows the total number of faults since startup.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Total number of incoming messages Since Last Collection

This metric shows the total number of incoming messages since last collection.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Total number of incoming messages since startup

This metric shows the total number of incoming messages since startup.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Total number of outgoing messages since last collection

This metric shows the total number of outgoing messages since last collection.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Total number of outgoing messages since startup

This metric shows the total number of outgoing messages since startup.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

WSDL Port

This metric shows the WSDL port.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

WSDL URL of the service

This metric shows the WSDL URL of the service.

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.

Target Version

Collection Frequency

All Versions

Every 15 Minutes

16 Forms

This chapter describes Oracle Forms metrics.

Forms Resource Usage

This metric measures the resources consumed by all the Forms sessions.

CPU Usage (%)

This metric specifies the percentage CPU usage of all the Forms sessions.

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.

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 Hours

After Every Sample

>=

80

90

2

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.

Total CPU Time (millisec)

This metric specifies the total CPU Time (in millisec) consumed by all the Forms sessions.

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.

Target Version

Collection Frequency

All Versions

Every 60 Hours

User Action

No user action required.

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).

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.

Target Version

Collection Frequency

All Versions

Every 60 Hours

User Action

No user action required.

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.

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.

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 Hours

After Every Sample

>=

80

90

2

totalprivateMem 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.

JVM Controllers

The JVM Controllers category provides information about all the JVM controllers.

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.

CPU Time (millisec)

This metric specifies the CPU Time (in millisec) consumed by the JVM Controller process including child JVM processes.

Number of JVMs running for this JVM Controller

This metric specifies the number of JVMs running for this JVM Controller.

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.

UP Time (millisec)

This metric specifies the UP Time (in millisec) of the JVM Controller.

Number Of Sessions

The number of sessions category provides information about all the sessions.

Number Of Sessions

This metric measures the total number of Forms sessions of all Forms application deployments deployed in various WebLogic Server instances.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Response

The Response category provides information about the default Forms application deployment 'formsapp' in WebLogic Server WLS_FORMS

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).

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.

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

After Every Sample

>

500

1000

-

The Forms Listener response time is unacceptable..

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.

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.

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

After Every Sample

=

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.

Servlet ResponseTime

Average response time (in millisec) of Forms Servlet.

Average Response Time (millisec)

This metric measure the average response time.

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).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 60 Hours

Servlet Name

This metric specifies the name of the servlet.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 60 Hours

User Action

No user action required.

Response Time (millisec)

This metric measures the average time per task taken by the servlet to serve requests. By default, this metric has a warning threshold of 500 millisec and critical threshold of 1000 millisec indicating that the Forms Listener Response time is unacceptable. A critical alert is generated when the metric value reaches the critical threshold value once. It is recommended that this threshold is left at the default value

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.

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 Hours

After Every Sample

>

500

1000

1

The Forms Listener response time is unacceptable.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Application Deployment Name" and "Server Name" objects.

If warning or critical threshold values are currently set for any unique combination of "Application Deployment Name" and "Server 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 "Application Deployment Name" and "Server Name" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

User Action

No user action required.

Number Of Tasks

This metric specifies the total number of requests served by Forms Servlet.

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.

Target Version

Collection Frequency

All Versions

Every 60 Hours

User Action

No user action required.

Total Time

This metric specifies the total time spent (in millisec) on serving completed requests by Forms Servlet.

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.

Target Version

Collection Frequency

All Versions

Every 60 Hours

User Action

No user action required.

Web Module Name

This metric specifies the name of the Web Module.

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.

Target Version

Collection Frequency

All Versions

Every 60 Hours

User Action

No user action required.

17 Portal

This chapter describes Oracle Portal metrics.

Note:
The current Enterprise Manager release does not support Oracle 10g Portal metrics.

Portlets (All)

This category provides information about portlets metrics.

Cache Hit (%)

This metric specifies the rate of cache hits.

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Average Time (ms)

This metric specifies the average time.

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Requests (per minute)

This metric specifies the rate per minute of requests to the Portal.

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Availability (%)

The percentage availability.

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Producer Type

The producer type

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Portlets (Top 5)

This category provides information about portlets (Top 5) metrics.

Cache Hit (%)

The cache hit percentage

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Average Time (ms)

This is the average time in milliseconds

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Requests (per minute)

This is the number of requests recorded per minute.

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Availability (%)

The percentage availability

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Producer Type

The producer type

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Producers (All)

This category provides information about producers metrics.

Cache Hit (%)

This metric specifies the rate of cache hits from a producer.

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to assess the cache hit ratio for a producer.

Average Time (ms)

This metric specifies the average time in executing portlet calls for a producer.

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.

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.

Requests (per minute)

This metric specifies the rate of requests per minute that are getting serviced from a producer.

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to assess the load on the producer.

Availability (%)

This metric measures the availability of a producer, and measures the percent of requests that got an HTTP-2xx response from a producer.

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.

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.

Producer Type

The producer type

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Producers (Top 5)

This category provides information about producers (Top 5) metrics.

Cache Hit (%)

The cache hit percentage.

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Average Time (ms)

The average time in milliseconds

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Requests (per minute)

The number of requests per minute

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Availability (%)

The percentage availability

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Producer Type

The producer type

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Portal Cache

This category provides information about portal cache metrics.

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".

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to assess the caching statistics of your pages/content.

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.

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.

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.

Ping Hit (%)

This metric specifies the percentage of requests that resulted in successful cache hits for content that requires ping checks.

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to assess the caching statistics of your pages/content.

Requests (per minute)

This metric specifies the rate per minute of requests to the Portal Cache.

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

Use this metric to assess the rate of requests to the Portal Cache.

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.

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.

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.

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.

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.

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.

Database Connection Pool Statistics

This category provides information about database connection pool statistics.

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.

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.

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.

Requests (per minute)

This metric provides the rate of incoming requests that require a database connection

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.

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.

Hit (%)

This metric indicates the effectiveness of the Portal connection pool by measuring the percentage of Portal database connection pool hit rate.

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.

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.

New (%)

This metric indicates the effectiveness of the Portal connection pool by measuring the percentage rate of creating new database connections in Portal.

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.

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.

Stale (%)

This metric indicates the effectiveness of the Portal connection pool by providing the percentage rate of discarding pooled database connections.

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.

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.

Database Repository Response Code Statistics

This category provides information about database repository response code statistic metrics.

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.

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.

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.

Average Processing Time (ms)

This metric provides the average response time for generating a response code.

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.

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.

Page Engine Statistics

This category provides information about page engine statistic metrics.

Average Queue Wait Time (ms)

This metric provides the average time all internal PPE requests spent in the PPE internal request queue.

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.

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.

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

Pages (per minute)

This metric specifies the rate of pages per minute generated by the Parallel Page Engine

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.

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.

Average Page Metadata Fetch Time (ms)

This metric specifies the average time taken to retrieve the page metadata.

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.

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.

Page Metadata Fetches (per minute)

This metric specifies the page metadata throughput per-minute.

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.

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.

Average Page Metadata Wait Time (ms)

This metric specifies the average time spent in the PPE internal request queue waiting for page metadata.

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.

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.

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.

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.

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.

HTTP200-HTTP299 (%)

This metric provides the percentage rate of HTTP-2xx responses generated by the Portal Parallel Page Engine (PPE).

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.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

If this number is low, use the diagnostic logs to investigate.

HTTP300-HTTP399 (%)

This metric provides the percentage rate of HTTP-3xx responses generated by the Portal Parallel Page Engine (PPE).

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.

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.

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.

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.

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.

HTTP500-HTTP599 (%)

This metric provides the percentage rate of HTTP-5xx responses generated by the Portal Parallel Page Engine (PPE).

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.

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.

Timeout (%)

This metric provides the percentage rate of timeout responses generated by the Portal Parallel Page Engine (PPE).

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.

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

WebCache Page Metadata Hits (%)

This metric specifies the percentage of requests that are able to retrieve the cached page metadata content from WebCache.

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.

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.

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.

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.

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.

WebCache Page Metadata Non-Cacheables (%)

This metric specifies the percentage of requests that cannot use WebCache to cache content.

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.

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.

Response

This category provides information about response metrics.

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.

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.

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 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.

18 Reports Bridge

This chapter describes Oracle Reports Bridge metrics.

Log Message Alerts

This category provides information about log message alerts.

Log Monitoring Rules

The log monitoring rules

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.

Target Version

Key

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

odl_message_alert_rule_name: "MSG-110"

Not Defined

After Every Sample

MATCH

YES

Not Defined

1*

[%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

1*

[%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 Thresholds for information on accessing the Edit Thresholds page.

Diagnostic Log Summary

This category provides information about diagnostic log summary metrics.

Log Error Messages (over 15 minutes)

The log error messages over 15 minutes.

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.

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

1

Error message rate is %value%, crossed warning (%warning_threshold%) or critical(%critical_threshold%) threshold.

Log Incident Error Messages (over 15 minutes)

Log incident error messages over 15 minutes

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.

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

1

Incident Error message rate is %value%, crossed warning (%warning_threshold%) or critical(%critical_threshold%) threshold.

Log Notification Messages (over 15 minutes)

Log notification messages over 15 minutes

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.

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

1

Notification message rate is %value%, crossed warning (%warning_threshold%) or critical(%critical_threshold%) threshold.

Log Trace Messages (over 15 minutes)

Log trace messages over 15 minutes

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.

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

1

Trace message rate is %value%, crossed warning (%warning_threshold%) or critical(%critical_threshold%) threshold.

Log Unknown Messages (over 15 minutes)

The log of unknown messages over 15 minutes

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.

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

1

Unknown message rate is %value%, crossed warning (%warning_threshold%) or critical(%critical_threshold%) threshold.

Log Warning Messages (over 15 minutes)

Log warning messages over 15 minutes

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.

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

1

Warning message rate is %value%, crossed warning (%warning_threshold%) or critical(%critical_threshold%) threshold.

Remote Elements Discovered

Provides information on Bridges and Servers discovered.

Host.value

This metric specifies the host name of the machine in which the remote element is located.

Name

This metric specifies the name of the remote element.

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.

Type of Element

This metric specifies the type of the remote element. Type can be "Server" or "Bridge".

Resource Usage

This category provides information about resource usage metrics.

CPU Usage (%)

This metric specifies the percentage of CPU usage.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Memory Usage (MB)

This metric specifies the memory used (in megabytes).

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Memory Usage (%)

This metric specifies the percentage of total memory used.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Response

Provides information about the status of Reports Bridge, Up or Down.

Up or Down Status

This metric specifies the status of Reports Bridge. Status can be Up or Down.

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.

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

%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.

19 Virtual Directory

This chapter describes Oracle Virtual Directory metrics.

Adapter Metrics

The category specifies the metrics about the currently configured Adapters.

Open Connections

This metric specifies the total number connections opened by a particular Adapter since last collection.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total No of Connections Processed

This metric specifies the total number of connections processed by the Adapter.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total No of Connections Reused

This metric specifies the total number of connections reused by the Adapter.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Enabled

This metric specifies if the Adapter is enabled or disabled.

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.

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.

Add Operations

This metric specifies the total number of Add operations performed by a particular Adapter since last collection.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total No of Operation Binds

This metric specifies the total number of bind operations by a particular Adapter.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Operations Count

Specifies the total number of all operations performed by this particular Adapter.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Delete Operations

This metric specifies the total number of delete operations performed by a particular Adapter since last collection.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Operational Version

This metric specifies the operational version of Adapters.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Modify Operations

This metric specifies the total number of Modify operations performed by a particular Adapter since last collection.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total No of Operations Renamed

This metric specifies the total number of operations renamed by a particular Adapter.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Search Operations

This metric specifies the total number of Search operations performed by a particular Adapter since last collection.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Provisioned version

This metric specifies the Processed version of Adapters.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Type

This metric specifies the type of the Adapter.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Connected IPs

This category provides information about distinct IP Address that are connected to Oracle Virtual Directory

Current Connections

This metric specifies the Current Open connections from a particular IP Address.

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.

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

-

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.

Total Connections

This metric specifies the Total number of connections from a particular IP Address.

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.

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

-

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.

getUsers

The category provides information about currently connected users

Current Connections

This metric specifies the number of connections that are currently open for a particular user.

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.

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

-

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.

Total Connections

This metric specifies the total number of connections opened by a particular user.

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.

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

-

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.

Resource Usage

This category provides information about CPU and memory usage.

CPU Usage (%)

This metric specifies the percentage of the CPU that Oracle Virtual Directory is using.

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.

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

-

Error message rate is Total Connections %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

CPU Idle Time (%)

This metric specifies the percentage of the CPU Idle Time on the Oracle Virtual Directory Host.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Other CPU Usage (%)

This metric specifies the percentage of the CPU that components other than Oracle Virtual Directory are using.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Heap Usage (MB)

This metric specifies the JVM Heap Usage of the Oracle Virtual Directory Server.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Memory Usage (MB)

This metric specifies the Memory Consumed (in MB) by Oracle Virtual Directory.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Free Memory (MB)

This metric specifies the amount of Free Memory on the Oracle Virtual Directory Server Host.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Other Memory Usage (MB)

This metric specifies the Memory Consumed (in MB) by components other than Oracle Virtual Directory.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total Memory (MB)

This metric specifies the Total Available Memory on the Oracle Virtual Directory Server Host.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Memory Usage (%)

This metric specifies the percentage of Memory Consumed by the Oracle Virtual Directory Server.

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.

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

-

Error message rate is The Memory utilization is greater than %value%

Free Memory (%)

This metric specifies the percentage of Free Memory on the Oracle Virtual Directory Server Host.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Other Memory Usage (%)

This metric specifies the percentage of Memory Consumed by components other than the Oracle Virtual Directory Server.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Start Time (ms since Epoch)

This metric specifies the start time (milliseconds since Epoch) of the Oracle Virtual Directory Server.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Response

This category shows whether the Oracle Virtual Directory instance is up and running or down and unavailable.

UpDown Status

This metric specifies whether the Oracle Virtual Directory instance is up and running or down and unavailable.

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.

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 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.

Server Latency Metrics

This category defines the Oracle Virtual Directory Server Latency Metrics

Total Operations

This metric specifies the total number of all LDAP operations since the last collection.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

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 Oracle Virtual Directory instance is down

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Number of LDAP Add Requests

This metric specifies the Number of LDAP Add Requests since the last collection.

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.

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 60 Samples

>

Not Defined

Not Defined

-

LDAP Add Requests %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Number of LDAP Binds Requests

This metric specifies the Number of LDAP Bind Requests since the last collection.

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.

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 60 Samples

>

Not Defined

Not Defined

-

LDAP Binds Requests %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Number of LDAP Delete Requests

This metric specifies the Number of LDAP Delete Requests since the last collection.

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.

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 60 Samples

>

Not Defined

Not Defined

-

LDAP Delete Requests %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Number of LDAP Modify Requests

This metric specifies the Number of LDAP Modify Requests since the last collection.

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.

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 60 Samples

>

Not Defined

Not Defined

-

LDAP Modify Requests %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Number of LDAP Rename Requests

This metric specifies the Number of LDAP Rename Requests since the last collection.

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.

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 60 Samples

>

Not Defined

Not Defined

-

LDAP Rename Requests %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Number of LDAP Search Requests

This metric specifies the Number of LDAP Search Requests since the last collection.

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.

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 60 Samples

>

Not Defined

Not Defined

-

LDAP Search Requests %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Server wide Connection Metrics

This category shows the Oracle Virtual Directory operational Metrics.

Total No of IPs Currently Connected

This metric specifies the Total number of distinct IP Addresses that are currently connected to Oracle Virtual Directory.

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.

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 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.

Total No of Users Currently Connected

This metric specifies the Total number of users that are currently connected to Oracle Virtual Directory.

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.

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 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.

Total No of Operations

This metric specifies the Total number of all LDAP operations that have been completed from the last collection.

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.

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 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.

Total No of Open Connections

This metric specifies the Total number of open connections to Oracle Virtual Directory.

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.

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 60 Samples

>

Not Defined

Not Defined

-

Total Open Connections %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

20 Internet Directory

This chapter describes Oracle Internet Directory metrics.

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.

(Resource Statistics) LDAP Server's Active Database Connections

Shows the number of active database connections for the Oracle Internet Directory server.

Active Database Sessions

The number of active database connections for the Oracle Internet Directory server.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

LDAP Active DB Connections %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Closed LDAP Logon Session Statistics

This category provides information about closed LDAP Logon Session statistics.

Total Closed Logon Sessions

Provides information about total closed logon sessions to Oracle Internet Directory servers.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

OID Server Closed TCP conn %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

(Historical Resource Statistics)LDAP Server's Database Usage

This metric provides information about database usage by Oracle Internet Directory servers.

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.

Date and Time Stamp

Shows the date and time stamp (in UTC) of the metric collection.

Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

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.

Failed Bind Operations

The metric value specifies the number of unsuccessful LDAP bind operations performed by a user

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

Failed Bind Operation %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

(Critical Events)General System Resource Events

This category provides information about general system resource events.

Critical General Sys Resource Event Occurrences

Number of occurrences of general system resource events.

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.

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 10 Minutes

After Every Sample

>

Not Defined

0

1

LDAP Server crashed %value% times, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

LDAP Load

This metric provides information about the total number of LDAP operations in progress.

Server Load

The total number of LDAP operations in progress.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

LDAP Server Load %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

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.

Date and Time Stamp

Shows the date and time stamp (in UTC) of the metric collection.

Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

Server Load

Shows the number of LDAP operations in progress in the Oracle Internet Directory server at the end of the metric collection period.

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.

(Resource Statistics)LDAP Server Memory Growth

Provides information about Oracle Internet Directory server memory growth.

Average memory growth (%)

Average Oracle Internet Directory server memory growth.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

OID Average Memory Growth %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

New LDAP Logon Session Statistics

This category provides information about new LDAP logon session statistics.

Total New Logon Sessions

Provides information about total new logon sessions to Oracle Internet Directory servers.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

OID Server New TCP conn %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

(Resource Statistics) LDAP Server's Open Database Connections

Shows the number of open database connections for the Oracle Internet Directory server.

Open Database Sessions

The number of open database connections for the Oracle Internet Directory server.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

LDAP Open DB Connections %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Open LDAP Logon Session Statistics

This category provides information about open LDAP logon session statistics.

Total Open Logon Sessions

Provides information about total logon sessions to Oracle Internet Directory servers.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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.

Historical LDAP Operation Response Time

This category provides information about historical LDAP operation response time metrics.

Bind Operation Response Time

The average server response time for bind operations

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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.

Compare Operation Response Time

The average server response time for compare operations

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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.

Date and Time Stamp

The date and time stamp of this server instance.

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Instance Number

The instance number of this Oracle Internet Directory server instance.

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Messaging Search Operation Response Time

The metric value shows the average messaging search response time

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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.

LDAP Operation Response Time

This category provides information about LDAP operation response time metrics.

Bind Operation Response Time

The metric value shows the response time of LDAP Bind operations

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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.

Compare Operation Response Time

The metric value shows the response time of LDAP compare operations

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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.

Messaging Search Operation Response Time

The metric value shows the average messaging search response time

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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.

LDAP Server Resource Usage

Provides information about system resources used by Oracle Internet Directory servers.

Total CPU Usage (%)

Provides information about the percentage of CPU used by Oracle Internet Directory servers.

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.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

9.0.4.x

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

1

Total CPU Usage %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Total Memory Usage (KB)

Provides information about total virtual memory used by Oracle Internet Directory servers.

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.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

9.0.4.x

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

1

Total Memory Usage %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Total Memory Usage (%)

Provides information about percent total virtual memory used by Oracle Internet Directory servers.

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.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

9.0.4.x

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

1

Total Memory Usage %value% (%%) crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

LDAP Response

This metric provides information about the average LDAP operation response time in Oracle Internet Directory servers.

Server Response

The average LDAP operation response time in Oracle Internet Directory servers.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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.

Running instances of LDAP Server

Provides information about running instances of Oracle Internet Directory servers.

Downtime Count

Shows the number of times the instance has gone down and has been restarted by the Oracle Internet Directory monitor daemon.

Host Name

Shows the host name of a running Oracle Internet Directory instance.

Instance Number

The instance number of this Oracle Internet Directory server instance.

Up Since

Shows the time when the Oracle Internet Directory instance was first started.

Non SSL Port Number

The metric value specifies the non-SSL port that an instance of Oracle Internet Directory server is listening on.

SSL Port Number

The metric value specifies the SSL port that an instance of Oracle Internet Directory server is listening on.

(Historical Resource Statistics)LDAP Server and System Memory

Provides information about system memory and Oracle Internet Directory server memory.

Date and Time Stamp

Shows the date and time stamp (in UTC) of the metric collection.

Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

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.

System's Total Free Physical Memory (KB)

Shows, in kilobytes, the free physical system memory at the end of metric collection period.

(Critical Events)System Resource Events(3113 Errors)

Provides information about ORA-3113 errors that occurred in Oracle Internet Directory servers.

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.

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

User Action

Check for network problems. Check whether database has crashed.

(Critical Events)System Resource Events(3114 Errors)

Provides information about ORA-3114 errors that occurred in Oracle Internet Directory servers.

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.

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

User Action

Check for network problems. Check whether database has crashed.

(Historical Critical Events)System Resource Events

Provides information about critical system resource events that occurred in Oracle Internet Directory servers.

Last Event Time

Shows the date and time stamp (in UTC) of the event occurrence.

Number of Event Occurrence

The number of occurrences of this event

Event Name

Shows the name of the event that occurred.

Instance Number

Shows the instance number of the Oracle Internet Directory server for which this metric is collected.

Process ID

Shows the process identifier of the Oracle Internet Directory server instance for which this metric is collected.

(Critical Events)System Resource Events(Ora Errors)

This category provides information about System Resource Events(Ora Errors) metrics.

Critical Ora Error Occurrences

Number of occurrences of critical ORA Error Code Number.

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.

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 10 Minutes

After Every Sample

CONTAINS

Not Defined

ORA-

1

Ora Error!

Historical LDAP Logon Session Statistics

This metric provides information about login sessions established with Oracle Internet Directory servers.

Date and Time Stamp

Shows the date and time stamp (in UTC) of the metric collection.

Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

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.

Total Memory Usage

Provides information about total virtual memory use by Oracle Internet Directory servers.

Total Mem. Size(in KB)

Shows total virtual memory use by Oracle Internet Directory servers.

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.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

9.0.2.x and 9.0.3.x

Every 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

Memory Usage over %value% KB crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

User Action

Specific to your deployment.

Historical LDAP Operations Profile

This metric provides information about LDAP operations completed by Oracle Internet Directory servers.

Date and Time Stamp

Shows the date and time stamp (in UTC) of the metric collection.

Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

Completed Abandon Operations

The metric value specifies the number of LDAP abandon operations performed by a user

Completed Add Operations

Shows the total number of LDAP add operations completed by the Oracle Internet Directory server instance during the metrics collection period.

Completed Bind Operations

Shows the total number of LDAP bind operations completed by the Oracle Internet Directory server instance during metric collection.

Completed Compare Operations

Shows the total number of LDAP compare operations completed by the Oracle Internet Directory server instance during metric collection.

Completed Delete Operations

Shows the total number of LDAP delete operations completed by the Oracle Internet Directory server instance during metric collection.

Completed Modify Operations

Shows the total number of LDAP modify operations completed by the Oracle Internet Directory server instance during metric collection.

Completed Modrdn Operations

The metric value specifies the number of unsuccessful LDAP modifydn operations performed by a user

Completed Search Operations

Shows the total number of LDAP search operations completed by the Oracle Internet Directory server instance during metric collection.

Completed Unbind Operations

The metric value specifies the number of LDAP unbind operations performed by a user

Failed Bind Operations

The metric value specifies the number of unsuccessful LDAP bind operations performed by a user

LDAP Operations Profile

This metric provides information about LDAP operations completed by Oracle Internet Directory servers.

Completed Abandon Operations

The metric value specifies the number of LDAP abandon operations performed by a user

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Completed Add Operations

Shows the total number of LDAP add operations completed by the Oracle Internet Directory server instance during the metric collection period.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

LDAP Add %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Completed Bind Operations

This metric provides information about Oracle Internet Directory server login sessions.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

LDAP Bind %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Completed Compare Operations

Shows the total number of LDAP compare operations completed by the Oracle Internet Directory server instance during the metric collection period.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

LDAP Compare %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Completed Delete Operations

Shows the total number of LDAP delete operations completed by the Oracle Internet Directory server instance during the metric collection period.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

LDAP Delete %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Completed Modify Operations

Shows the total number of LDAP modify operations completed by the Oracle Internet Directory server instance during the metric collection period.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

LDAP Modify %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Completed Modrdn Operations

The metric value specifies the number of LDAP Modrdn operations performed by a user

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Total Operations

The metric value specifies the total number of LDAP operations performed by a user

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Completed Search Operations

Shows the total number of LDAP search operations completed by the Oracle Internet Directory server instance during the metric collection period.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

LDAP Search %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Completed Unbind Operations

The metric value specifies the number of LDAP unbind operations performed by a user

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

LDAP Server Total User Sessions

Provides information about total LDAP user sessions currently established with Oracle Internet Directory servers.

Total Users Sessions

Shows the total number of user sessions currently established with an Oracle Internet Directory server.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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.

Directory Integration Profiles

Provides basic status information about various Directory Integration Platform profiles configured in the system.

Last Execution Time

Shows the time when the profile was last executed by the Directory Integration Platform server.

Last Applied Change Number

Shows the last changenumber in Oracle Internet Directory that was successfully synchronized and propagated to the other end.

Execution Errors

Shows the last error that was encountered (if any) during the execution of the integration profile.

State

Shows the state of the integration profile (ENABLED / DISABLED).

Execution Status

Shows the current execution status of the integration profile.

Schedule (secs)

Shows the scheduling interval of the integration profiles. The Directory Integration Platform server executes the profiles using this scheduling interval.

Type

Shows the type of the integration profile (synchronization or provisioning).

Directory Integration Server

Provides information about various Directory Integration Platform instances running against this Oracle Internet Directory instance.

Downtime Count

Shows the number of times the Directory Integration Platform server went down unexpectedly.

Directory Integration Server Host

Shows the machine on which this Directory Integration Platform server is running.

Start Time

Shows the time when this Directory Integration Platform server started.

LDAP Server

Shows the Oracle Internet Directory server against which this Directory Integration Platform server is running.

Size of Audit Log Purge Queue

Provides information about the size of the Audit Log purge queue

Total Number of Audit Log Objects in Purge Queue

The metric value specifies the number of objects in the audit log purge queue

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.

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 10 Minutes

After Every Sample

>

10000

100000

1

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.

Size of General Statistics Purge Queue

Provides information about the size of the general statistics purge queue.

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

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.

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 10 Minutes

After Every Sample

>

10000

100000

1

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.

Size of Health Statistics Purge Queue

Provides information about the size of the health statistics purge queue

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

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.

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 10 Minutes

After Every Sample

>

10000

100000

1

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.

Total Number ChangeLogs in Purge Queue

Provides information about the number of objects in local change log purge queue.

Total Number of Local Changelogs in Purge Queue

The metric value specifies the number of objects in local change log purge queue

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.

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 10 Minutes

After Every Sample

>

10000

100000

1

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. (ref tuning chapter)

For more information see the tuning chapter and the replication attributes chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

Total Number Remote ChangeLogs in Purge Queue

Provides information about the number of objects in remote change log purge queue

Total Number of Remote Changelogs in Purge Queue

The metric value specifies the number of objects in remote change log purge queue

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.

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 10 Minutes

After Every Sample

>

10000

100000

1

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.

Total Number of HIQ ChangeLogs

Provides information about the total number of change logs in the Human Intervention Queue.

HIQ Changelog Count

The Metric value specifies the total number of change logs in the Human Intervention Queue.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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. See Editing Thresholds for information on accessing 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.

Replication Server Configuration Set Information

Provides information about the Replication Server configuration set information metrics.

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.

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.

Running instances of LDAP Replication Server

Provides information about running instances of the directory replication server.

Downtime Count

Shows the number of times the instance went down and was restarted by the Oracle Internet Directory monitor daemon.

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.

Start Time

Shows the time when the instance of the directory replication server was first started.

Total Number of Local ChangeLogs

Provides information about the total number of local change logs generated.

Total Number of Local Changelogs

This metric value specifies the total number of local change logs generated.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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.

Total Number of New ChangeLogs

Provides information about the total number of change logs entries created.

New Changelog Count

This count of this metric gives the total number of change logs entries created.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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. See Editing Thresholds for information on accessing 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.

Total number ChangeLogs to be processed

Provides information about the number of change logs that pending.

Total Changelogs to be processed

This metric value specifies the number of change logs that pending.

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.

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 10 Minutes

After Every Sample

>

5000

20000

1

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.

Total Number of Retry ChangeLogs

Provides information about the number of change logs in the retry queue.

Retry Changelog Count

This metric value specifies the number of change logs in the retry queue.

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.

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 10 Minutes

After Every Sample

>

Not Defined

Not Defined

1

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. See Editing Thresholds for information on accessing 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.

OID Replication Server Virtual Memory Size

Provides information about the total memory used by Oracle Internet Directory Replication Server.

Replication Server Memory Size

The metric value specifies the total memory used by Oracle Internet Directory Replication Server

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.

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

1

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.

OID Replication Server Percentage CPU

Provides information about the percentage of CPU used by Oracle Internet Directory Replication Server.

Replication Server Percentage CPU

Provides information about the percentage of CPU used by Oracle Internet Directory Replication Server.

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.

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

1

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.

Replication Supplier Details

Provides information about the replication supplier detail metrics.

Replication Agreement Type

The replication agreement type: multimaster, one-way, or two-way replication agreement.

HIQ Changelog Count

The Metric value specifies the total number of change logs in the Human Intervention 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.

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.

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.

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.

Name of the Supplier Replica

The replica ID of the supplier

Size of Security Refresh events Purge Queue

Provides information about the number of objects in the Oracle Internet Directory Security Refresh event purge queue.

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.

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.

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 10 Minutes

After Every Sample

>

10000

100000

1

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.

Historical 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.

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

Date and Time Stamp

Shows the date and time stamp (in UTC) of the metric collection.

Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

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.

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

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.

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.

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

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.

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.

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 10 Minutes

After Every Sample

Not Defined

Not Defined

1

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.

For information about tuning Oracle Internet Directory, see the tuning chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

OID Server Virtual Memory Size

Provides information about memory used by Oracle Internet Directory Server.

OID Server Memory Size

The metric value specifies the total memory used by Oracle Internet Directory Server.

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.

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

1

Oracle Directory Server Memory size %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Stopped instances of LDAP Server

Provides information about Oracle Internet Directory instances that were started earlier and are stopped now.

Config Set Number

Shows the configuration set associated with the stopped instance.

Host Name

Shows the host name of the stopped instance.

OID Server Percentage CPU Utilization

Provides information about the percentage of CPU used by Oracle Internet Directory servers.

OID Server Percentage CPU

Provides information about the percentage of CPU used by Oracle Internet Directory servers.

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.

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

1

Oracle Directory Server CPU Usage %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

(Historical Critical Events)Security Events

This metric provides information about security events that occurred in Oracle Internet Directory servers.

Event Time

Shows the date and time stamp (in UTC) of the event occurrence.

Event Result

Shows the result (either success or failure) of the event that occurred.

Event Name

Shows the name of the event that occurred.

Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

Process ID

Shows the process identifier for the Oracle Internet Directory server instance for which this metric is collected.

User DN

Shows the identity of the user who logged into Oracle Internet Directory server and performed the operation that triggered the event.

(Critical Event)Super User Failed Logins

This metric provides information about failed super user logins that occurred in Oracle Internet Directory servers.

Failed LDAP Super User Login

The number of successful super user logins that occurred in Oracle Internet Directory servers.

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.

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 10 Minutes

After Every Sample

>

15

20

1

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.

(Critical Event)Super User Successful Logins

This metric provides information about successful super user logins that occurred in Oracle Internet Directory servers.

Successful LDAP Super User Login

The number of successful super user logins that occurred in Oracle Internet Directory servers.

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.

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 10 Minutes

After Every Sample

>

40

50

1

Superuser Login Success count %value% crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold

Size of System Resource events Purge Queue

Provides information about the number of objects in the Oracle Internet Directory System resource event purge queue.

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.

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.

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 10 Minutes

After Every Sample

>

10000

100000

1

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.

Size of Tombstone Purge Queue

The Tombstone purge queue size metrics are described.

Total Number of Tombstone Objects in Purge Queue

The metric value specifies the number of objects in the tombstone purge queue

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.

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 10 Minutes

After Every Sample

>

10000

100000

1

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.

TopProcesses

Provides information about the name of the process.

Process Name

The name of this process.

Resource Usage

Provides information about resource usage metrics.

CPU Usage (%)

Provides information about the percentage of CPU used by Oracle Internet Directory servers.

CPU Idle Time (%)

Percent CPU Idle time on the system where Oracle Internet Directory is running.

Other CPU Usage (%)

Percentage of CPU used by processes other than Oracle Internet Directory.

Memory Usage (MB)

Provides information about total virtual memory used by Oracle Internet Directory servers.

Free Memory (MB)

The metric value shows the system free memory where Oracle Internet Directory server is running.

Other Memory Usage (MB)

Amount of memory used by processes other than Oracle Internet Directory.

Total Memory (MB)

Metric value represents the total memory as used by Oracle Internet Directory Server.

Memory Usage (%)

Provides information about percent total virtual memory used by Oracle Internet Directory servers.

Free Memory (%)

The metric value shows the percentage of system free memory where Oracle Internet Directory server is running.

Other Memory Usage (%)

Percent of memory used by processes other than Oracle Internet Directory.

Start Time (ms since Epoch)

The start time of the Oracle Internet Directory process.

Response

For Oracle internal use only.

Status

Shows whether any Oracle Internet Directory LDAP server is up or not.

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.

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

0

1

The Internet Directory is down

User Action

Specific to your deployment.

Total Number

Shows the total number of Oracle Internet Directory servers that are up and running.

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.

Target Version

Collection Frequency

9.0.2.x and 9.0.3.x

Every 5 Minutes

User Action

None.

User LDAP Operations Stats

Provides information about user LDAP operations stats metrics.

Abandon Operations

The metric value specifies the number of LDAP abandon operations performed by a user

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Failed Add Operations

The metric value specifies the number of unsuccessful LDAP add operations performed by a user.

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Failed Base Search Operations

The metric value specifies the number of unsuccessful LDAP base search operations performed by a user

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Failed Bind Operations

The metric value specifies the number of unsuccessful LDAP bind operations performed by a user

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Failed Compare Operations

The metric value specifies the number of unsuccessful LDAP compare operations performed by a user

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Failed Delete Operations

The metric value specifies the number of unsuccessful LDAP delete operations performed by a user.

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Failed Modify Operations

The metric value specifies the number of unsuccessful LDAP modify operations performed by a user.

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Failed ModRdn Operations

The metric value specifies the number of unsuccessful LDAP ModRdn operations performed by a user.

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Failed OneLevel Search Operations

The metric value specifies the number of unsuccessful LDAP OneLevel Search operations performed by a user.

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Failed Proxy Bind Operations

The metric value specifies the number of unsuccessful LDAP proxy bind operations performed by a user

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Failed Subtree Search Operations

The metric value specifies the number of unsuccessful LDAP Subtree Search operations performed by a user.

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Successful Add Operations

The metric value specifies the number of successful LDAP add operations performed by a user.

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Successful Base Search Operations

The metric value specifies the number of successful LDAP base search operations performed by a user

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Successful Bind Operations

The metric value specifies the number of successful LDAP bind operations performed by a user

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Successful Compare Operations

The metric value specifies the number of successful LDAP compare operations performed by a user

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Successful Delete Operations

The metric value specifies the number of successful LDAP delete operations performed by a user.

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Successful Modify Operations

The metric value specifies the number of successful LDAP modify operations performed by a user.

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Successful ModRdn Operations

The metric value specifies the number of successful LDAP ModRdn operations performed by a user.

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Successful OneLevel Search Operations

The metric value specifies the number of successful LDAP OneLevel Search operations performed by a user.

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Successful Proxy Bind Operations

The metric value specifies the number of successful LDAP proxy bind operations performed by a user

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Successful Subtree Search Operations

The metric value specifies the number of successful LDAP Subtree Search operations performed by a user.

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

Unbind Operations

The metric value specifies the number of LDAP unbind operations performed by a user

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.

Target Version

Collection Frequency

All Versions

Every 10 Minutes

21 Directory Integration Platform

This chapter describes Oracle Directory Integration Platform (DIP) metrics.

DIP Aggregated Metrics

The aggregation of all the values across profile executions

Total Changes Attempted

This metric specifies the total number of changes attempted across all profiles.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Total Successful Changes

This metric specifies the total number of successful changes across all profiles.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Average LDAP Search Time

This metric specifies the average LDAP search time across all profiles.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Average LDAP Write Time

This metric specifies the average LDAP write time across all profiles.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Average Profile Execution Time

This metric specifies the average profile execution time across all profiles.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

DIP All Profiles (Consolidated)

This metric provides a consolidated list of profiles that are currently enabled in DIP

Host

This metric specifies the host where the DIP application is running.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Last Change Number

This metric specifies the last change number that was processed by the profile during the previous execution.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Last Execution Error

This metric specifies the error when the profile was last executed.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Last Execution Time

This metric specifies the time when the profile was last executed.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Last Successful Execution Time

This metric specifies the time when the profile was last executed successfully.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Status of Last Sync Operation

This metric specifies the status of the last operation during profile execution.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

DIP Profile Name

This metric specifies the name of the profile.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

DIP Process

This metric specifies the DIP process name and ID.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Average Processing Time

This metric specifies the average processing time (in milliseconds) of the profile.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Maximum Processing Time

This metric specifies the largest amount of time (in milliseconds) taken to process the profile.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Minimum Processing Time

This metric specifies the least amount of time (in milliseconds) taken to process the profile.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Profile Job Status

This metric specifies the status of the quartz job related to this profile.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

Check if the profile is scheduled, then check if the profile is enabled.

DIP Prov profile runtime operational metrics

This metric provides detailed execution statistics for all the currently enabled provisioning profiles configured in DIP

Failed Add Group operations

This metric specifies the number of failed add group operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Failed Add Identity operations

This metric specifies the number of failed add identity operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Failed Add Subscription operations

This metric specifies the number of failed add subscription operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Failed Add User operations

This metric specifies the number of failed add user operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Failed Delete Group operations

This metric specifies the number of failed delete group operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Failed Delete Identity operations

This metric specifies the number of failed delete identity operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Failed Delete Subscription operations

This metric specifies the number of failed delete subscription operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Failed Delete User operations

This metric specifies the number of failed delete user operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Failed Modify Group operations

This metric specifies the number of failed modify group operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Failed Modify Identity operations

This metric specifies the number of failed modify identity operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Failed Modify User operations

This metric specifies the number of failed modify user operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Profile Name

This metric specifies the provisioning profile name.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Successful Add Group operations

This metric specifies the number of successful add group operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Successful Add Identity operations

This metric specifies the number of successful add identity operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Successful Add Subscription operations

This metric specifies the number of successful add subscription operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Successful Add User operations

This metric specifies the number of successful add user operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Successful Delete Group operations

This metric specifies the number of successful delete group operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Successful Delete Identity operations

This metric specifies the number of successful delete identity operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Successful Delete Subscription operations

This metric specifies the number of successful delete subscription operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Successful Delete User operations

This metric specifies the number of successful delete user operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Successful Modify Group operations

This metric specifies the number of successful modify group operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Successful Modify Identity operations

This metric specifies the number of successful modify identity operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Successful Modify User operations

This metric specifies the number of successful modify user operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

DIP Sync profile runtime operational metrics

This metric provides detailed execution statistics for all the currently enabled synchronization profiles configured in DIP

Skipped Operations

This metric specifies the number of skipped operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Failed Add Operations

This metric specifies the number of failed add operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Failed Delete Operations

This metric specifies the number of failed delete operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Failed Modify Operations

This metric specifies the number of failed modify operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Profile Name

This metric specifies the synchronization profile name.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Successful Add Operations

This metric specifies the number of successful add operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Successful Delete Operations

This metric specifies the number of successful delete operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Successful Modify Operations

This metric specifies the number of successful modify operations.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

DIP Health

This metric provides information on the functional health of the DIP server

Host

This metric specifies the host where the WebLogic server is running.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

MBean Status

This metric specifies the status of the DIP JMX mbeans.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Name

This metric specifies the internal name of the DIP application.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Quartz Scheduler Status

This metric specifies the status of the internal qurtz scheduler.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

WLS Server Name

This metric specifies the WebLogic server name.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

DIP Provisioning Profiles

This metric provides the list of currently enabled Provisioning profiles

DIP Provisioning Profile Name

This metric specifies the name of the provisioning profile.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Host

This metric specifies the host where the DIP application is running.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Name

This metric specifies the name of the profile.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

DIP Synchronization Profiles

This metric provides the list of currently enabled synchronization profiles

DIP Synchronization Profile Name

This metric specifies the name of the synchronization profile.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Host

This metric specifies the host where the DIP application is running.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Name

This metric specifies the name of the profile.

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.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

No action required.

Resource Usage

Provides information about resource usage metrics.

CPU Usage (%)

The percentage CPU utilization.

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.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

11Plus

Every 15 Minutes

After Every Sample

>

75

90

1

The CPU utilization is greater than %value%

User Action

No action required.

Memory Usage (%)

The percentage memory utilization.

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.

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

11Plus

Every 15 Minutes

After Every Sample

>

75

90

1

The Memory utilization is greater than %value%

User Action

No action required.

DIP server status

Provides information about the DIP server status.

Status

The status of the DIP server.

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.

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 Sample

=

Not Defined

0

1

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.

22 WebCenter

This chapter describes Oracle WebCenter metrics.

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.

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.

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.

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.

WebCenter Spaces (Aggregated)

Provides information about the WebCenter Spaces (Aggregated) metrics

Application Name

This metric identifies the WebCenter application to which these Space metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

Service Name

These metrics apply to the WebCenter Space.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter Content Repositories (Aggregated)

Provides information about the WebCenter Content Repositories (Aggregated) metrics.

Application Name

This metric identifies the WebCenter application to which these content repository metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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

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).

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.

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.

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).

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.

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.

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).

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.

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.

Service Name

These metrics apply to content repositories used by the Documents service.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter Events (Aggregated)

Provides information about WebCenter Events (Aggregated).

Application Name

This metric identifies the WebCenter application to which the Events service metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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 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.

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.

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).

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.

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.

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).

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.

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.

Service Name

These metrics apply to events used by the WebCenter application.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter External Applications (Aggregated)

Provides information about the WebCenter External Applications (Aggregated) metrics.

Application Name

This metric identifies the WebCenter application to which these external application metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

Service Name

These metrics apply to the External Applications service.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter Portlets (Aggregated)

Provides information about WebCenter Portlets (Aggregated) metrics.

Application Name

This metric identifies the WebCenter application to which these portlet metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

Service Name

These metrics apply to WebCenter portlets.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter Producers (Aggregated)

Provides information about WebCenter Producers (Aggregated) metrics.

Application Name

This metric identifies the WebCenter application to which these portlet producer metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

Service Name

These metrics apply to the portlet producers used by the WebCenter application.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter Search (Aggregated)

Provides information about WebCenter Search (Aggregated) metrics.

Application Name

This metric identifies the WebCenter application to which these Search service metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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

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).

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.

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.

Service Name

These metrics apply to the Search service.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter Services

Provides information about WebCenter Services metrics.

Application Name

This metric identifies the WebCenter application to which these WebCenter service metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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

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).

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.

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.

WebCenter BPEL Worklists (Aggregated)

Provides information about WebCenter BPEL Worklists (Aggregated) metrics.

Application Name

This metric identifies the WebCenter application to which these Worklists service metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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

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).

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.

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.

Service Name

These metrics apply to the Worklists service.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter Portlets

Provides information about WebCenter Portlet metrics.

Application Name

This metric identifies the WebCenter application to which these portlet metrics apply.

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.

Target Version

Collection Frequency

All versions

Every 300 seconds

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

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.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter Producers

Provides information about the WebCenter Producers metrics.

Application Name

This metric identifies the WebCenter application to which these portlet producer metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

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.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter Announcements

Provides information about the WebCenter Announcements metrics.

Application Name

This metric identifies the WebCenter application to which these Announcements service metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

Service Name

These metrics apply to the Announcements service.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter Spaces

Provides information about WebCenter Spaces metrics.

Application Name

The application name

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

WebCenter Content Repositories

Provides information about WebCenter Content Repository metrics.

Application Name

This metric identifies the WebCenter application to which these content repository metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

WebCenter Events

Provides information about the WebCenter events metrics.

Application Name

This metric identifies the WebCenter application to which the Events service metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

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).

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.

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.

WebCenter External Applications Connections

Provides information about WebCenter External Applications metrics.

Application Name

This metric identifies the WebCenter application to which these External Application metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

WebCenter External Applications

Provides information about the WebCenter external applications metrics.

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.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

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.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

WebCenter Discussion Forum

Provides information about the WebCenter Discussion forum metrics.

Application Name

This metric identifies the WebCenter application to which these Discussions service metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

Service Name

These metrics apply to the Discussions service.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter Pages

Provides information about WebCenter pages metrics.

Application Name

This metric identifies the WebCenter application to which these page metrics apply.

User Action

No action required.

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).

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.

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.

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).

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

WebCenter Import/Export

Provides information about WebCenter Import/Export metrics.

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.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

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.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

WebCenter Lists

Provides information about WebCenter Lists metrics.

Application Name

This metric identifies the WebCenter application to which these Lists service metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

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).

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.

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.

Service Name

These metrics apply to the Lists service.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter Mail

Provides information about the WebCenter Mail metrics.

Application Name

This metric identifies the WebCenter application to which these Mail service metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

Service Name

These metrics apply to the Mail service.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter Notes

Provides information about the WebCenter Notes metrics.

Application Name

This metric identifies the WebCenter application to which these Notes service metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

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).

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.

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.

Service Name

These metrics apply to the Notes service.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter Page Service

Provides information about the WebCenter Page Service metrics.

Application Name

This metric identifies the WebCenter application to which these Page service metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

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).

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.

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.

Service Name

These metrics apply to the Page service.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter People Connections

Provides information about the WebCenter People Connections metrics.

Application name

This metric identifies the WebCenter application to which these People Connections service metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

Service Name

These metrics apply to the People Connections service.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter Polls

Provides information about WebCenter Polls metrics.

Application Name

This metric identifies the WebCenter application to which these Poll service metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

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).

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.

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.

Service Name

These metrics apply to the Polls service.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter Recent Activity

Provides information about the WebCenter Recent Activity metrics.

Application Name

This metric identifies the WebCenter application to which these Recent Activity metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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

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).

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.

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.

Service Name

These metrics apply to the Recent Activities service.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter RSS News Feeds

Provides information about the WebCenter RSS News Feeds metrics.

Application Name

This metric identifies the WebCenter application to which these RSS News Feed metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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

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).

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.

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.

Service Name

These metrics apply to the RSS service.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter Instant Messaging and Presence

Provides information about the WebCenter Instant Messaging and Presence metrics.

Application Name

This metric identifies the WebCenter application to which these Instant Messaging and Presence service metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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.

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).

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.

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.

Service Name

These metrics apply to the Instant Messaging and Presence (IMP) service.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

WebCenter Search

Provides information about WebCenter Search metrics.

Application Name

This metric identifies the WebCenter application to which these Search service metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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).

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.

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.

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

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).

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.

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.

WebCenter BPEL Worklists

Provides information about the WebCenter BPEL worklists metrics.

Application Name

This metric identifies the WebCenter application to which these Worklists service metrics apply.

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.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

No action required.

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).

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.

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.

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

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).

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.

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.

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).

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.

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.

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).

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.

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.

23 Web Cache

This chapter describes Oracle Web Cache metrics.

Performance by Web Cache Instance

Provides information about the performance metrics for the Web Cache instance.

Instance

This category provides performance-request metrics for the cache.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Request Processing Time (milli seconds)

This metric specifies the average number of seconds used to process a request during the current time period.

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.

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.

Request Throughput (per second)

This metric specifies the average number of requests served for each second during the current time period.

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.

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.

Resource Usage

This category of metrics shows the resource usage of the computer with Oracle Web Cache.

CPU Usage (%)

This metric specifies the percentage of the CPU that is being used for Oracle Web Cache. As traffic increases, CPU utilization increases.

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.

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 3 Samples

>

Not Defined

Not Defined

2

CPU Utilization is %value%%%

User Action

If the load is high, then consider upgrading the cache computer.

CPU Idle Time (%)

This metric specifies the percentage of system CPU time that is idle.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

If the load is high, then consider upgrading the cache computer.

Other CPU Usage (%)

The percentage of physical memory usage by applications other than Oracle Web Cache.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

If CPU usage is high, then consider upgrading the cache computer.

Memory Usage (MB)

This metric specifies the total memory used by Oracle Web Cache.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

If the load is high, then consider upgrading the cache computer.

Free Memory (MB)

The metric specifies the amount of free physical memory, in megabytes, for the system.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Other Memory Usage (MB)

Other memory usage in MB

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total Memory (MB)

This metric shows the total memory of the host that has Oracle Web Cache.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Memory Usage (%)

This metric specifies the percentage of total memory that is being utilized for cache memory.

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.

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 3 Samples

>

80

90

2

Memory Utilization is %value%%%

Free Memory (%)

This metric specifies the percentage of total memory that is being utilized for cache memory.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Other Memory Usage (%)

Percent of memory used by processes other than Oracle Web Cache.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Start Time (ms since Epoch)

This metric shows the start time of Oracle Web Cache.

Up Time (ms since Epoch)

This metric shows the total time the Oracle Web Cache has been running.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Response

This category shows the availability of the cache server process, which manages the cache.

Response Admin

This category shows the availability of the admin server process, which provides administrative access to the cache.

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.

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.

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 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.

Response - Status

This metric indicates whether the cache server process for the Oracle Web Cache instance is up (1) or down (0).

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.

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 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.

Performance of each Site with Summary

This category provides performance metrics for each site.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Number of Cached

This metric specifies the number of objects cached.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

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.

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.

Total Number of Requests Denied

This metric specifies the accumulated number of requests denied by request filters.

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.

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.

Total Number of Requests Served

This metric specifies the accumulate number of requests that Oracle Web Cache has served.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

Capacity.value

This informational metric specifies the capacity you specified in the Origin Servers page for this origin server.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Load.value

This metric specifies the current number of connections from Oracle Web Cache that the origin server has open.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

MaxLoad.value

The metric specifies the maximum number of connections that the origin server has had open at one time.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Port.value

The information metric specifies the port number from which the origin server is listening for Oracle Web Cache requests.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

AvgLatency.value

This metric shows the average amount of time for client requests forwarded by Oracle Web Cache to be resolved.

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.

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.

Latency.value

This metric shows the total time for client requests forwarded by Oracle Web Cache to be resolved, since the cache was started.

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.

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.

Request.value

This metric specifies the accumulated number of client requests forwarded by Oracle Web Cache that the origin server has processed.

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.

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.

RequestFailure.value

This metric specifies the accumulated number of client requests forwarded by Oracle Web Cache that resulted in an error.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

24 Business Activity Monitoring

This chapter describes Oracle Business Activity Monitoring metrics.

Report Server Active Data Page

Provides information about the report server active data page metrics.

Open Connections

Number of open connections to the Report Server.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Open Reports

Number of reports open in the Report Server.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Open Viewsets

Number of open viewsets in the Report Server.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Activity Message Rate (per sec)

The activity message rate recorded per second

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Average Time To Open Viewsets (in sec)

Average length of time in seconds to open a viewset. This is purely from the server's perspective and not from the client's perspective.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Response

Shows if the BAM Web is available or not.

UpDown Status

Displays the current status of the Oracle BAM Report Server. A value of 1 indicates that the server is running, and any other value indicates that it is not running.

No action required.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

25 Business Activity Monitoring Server

This chapter describes Oracle Business Activity Monitoring Server metrics.

ADC Client Requests For All DataObjects

Client requests include all of the requests made to the Oracle BAM Server EJBs. There will be a lot of requests made when opening a single report (for permissions, the report metadata, the views data, etc.).

Client Requests In Progress

Client requests include all of the requests made to the Oracle BAM Server EJBs. There are several requests made when opening a single report (for permissions, the report metadata, the views data, and so on).

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Client Requests Total

Client requests include all of the requests made to the Oracle BAM Server EJBs. There are several requests made when opening a single report (for permissions, the report metadata, the views data, and so on).

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

ADC Waiting Threads For All DataObjects

The number of Active Data Cache server threads waiting to access this data object.

Deletes Per Second

Rate of delete operations per second on the data object in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Inserts Per Second

Rate of insert operations per second on the data object in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Updates Per Second

Rate of update operations per second on the data object in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Upserts Per Second

Rate of upsert operations per second on the data object in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Deletes Per Second

Rate of delete operations on the data object in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Inserts Per Second

Rate of insert operations on the data object in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Updates Per Second

Rate of update operations on the data object in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Upserts Per Second

Rate of upsert operations on the data object in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

ADC Waiting Threads For All DataObjects

The number of Active Data Cache server threads waiting to access this data object.

Waiting Threads For All DataObjects

The number of Active Data Cache server threads waiting to access this data object.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

ADC Waiting Threads For All DataObjects

The number of Active Data Cache server threads waiting to access this data object.

Waiting Threads For All DataObjects

The number of Active Data Cache server threads waiting to access this data object.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

ADC Batch Size For All DataObjects

Average number of rows in the given batch.

Current Delete Batch Size

Average number of rows in the delete batch.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Current Insert Batch Size

Average number of rows in the insert batch.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Current Update Batch Size

Average number of rows in the update batch.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Current Upsert Batch Size

Average number of rows in the upsert batch.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Current Update Batch Size

Average number of rows in the update batch.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Current Insert Batch Size

Average number of rows in the insert batch.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Current Delete Batch Size

Average number of rows in the delete batch.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Current Upsert Batch Size

Average number of rows in the upsert batch.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Current Delete Batch Size

Number of active viewsets.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Current Delete Batch Size

Number of all of the active viewsets.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Current Insert Batch Size

Number of all of the open viewsets.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Current Insert Batch Size

Number of open viewsets.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Waiting Threads For All DataObjects

The number of Active Data Cache server threads waiting to access this data object.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Active Data Cache Transaction Information

Transactions shows, number of transactions on BAM Data Objects e.g. if you add a row in BAM DO and save it (commit), its one transaction.

Committed Transactions

Number of transactions on Oracle BAM data objects.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Completed Transactions

Number of completed transactions on Oracle BAM data objects.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Open Transaction

Number of open transactions on Oracle BAM data objects.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Rolledback Transactions

If there is an invalid operation on a data object, the Oracle BAM Server will roll back the transaction.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

EMS Metrics

Provides information about EMS metrics.

Total number of received messages

The total number of messages that have been received by all Oracle BAM Enterprise Message Sources.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Total number of rejected messages

The total number of messages that have been rejected by all Oracle BAM Enterprise Message Sources.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Total delete operations

The total number of successful Delete operations that have been performed by all Oracle BAM Enterprise Message Sources.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Total insert operations

The total number of successful Insert operations that have been performed by all Oracle BAM Enterprise Message Sources.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Total update operations

The total number of successful Update operations that have been performed by all Oracle BAM Enterprise Message Sources.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Total upsert operations

The total number of successful Upsert operations that have been performed by all Oracle BAM Enterprise Message Sources.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Total number of received messages

The total number of messages that have been received by all Oracle BAM Enterprise Message Sources.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Total number of rejected messages

The total number of messages that have been rejected by all Oracle BAM Enterprise Message Sources.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Delete operations rate

Rate of total number of successful Delete operations that have been performed by all Oracle BAM Enterprise Message Sources.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Insert operations rate

Rate of total number of successful Insert operations that have been performed by all Oracle BAM Enterprise Message Sources.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Update operations rate

Rate of total number of successful Update operations that have been performed by all Oracle BAM Enterprise Message Sources.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Upsert operations rate

Rate of total number of successful Upsert operations that have been performed by all Oracle BAM Enterprise Message Sources.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Total received messages

The total number of messages that have been received by the Oracle BAM Enterprise Message Source.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Total rejected messages

The total number of messages that have been rejected by the Oracle BAM Enterprise Message Source.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Delete operations rate

Number of successful delete operations per second in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Insert operations rate

Number of successful insert operations per second in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Update operations rate

Number of successful update operations per second in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Upsert operations rate

Number of successful upsert operations per second in the last 5 minutes.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Total received messages

The total number of messages that have been received by the Oracle BAM Enterprise Message Source.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Total rejected messages

The total number of messages that have been rejected by the Oracle BAM Enterprise Message Source.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Total delete operations

The total number of successful Delete operations that have been performed by the Oracle BAM Enterprise Message Source.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Total insert operations

The total number of successful Insert operations that have been performed by the Oracle BAM Enterprise Message Source.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Total update operations

The total number of successful Update operations that have been performed by the Oracle BAM Enterprise Message Source.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Total upsert operations

The total number of successful Upsert operations that have been performed by the Oracle BAM Enterprise Message Source.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Event Engine General Information

Provides information about event engine general information metrics.

Active Rules

Number of active alert rules in the Event Engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Action Queue Size

Number of Oracle BAM Event Engine actions waiting to be processed.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Alert History Queue Size

Number of alert history items to be saved.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Rule Fire Queue Size

Number of events fired waiting to be processed.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Event Engine Activity Rule Fire Rate

Number of events fired per second in Event Service.

Events Accepted Rate (per sec)

Number of events accepted per second.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Events Fire Rate (per sec)

Number of events fired per second in the Oracle BAM Event Engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Events Rejected Rate (per sec)

Number of events per second rejected by the Oracle BAM Event Engine.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Active Data Reports Information

Total Number of Active ActiveDataReports

Active Data Reports

Total number of active reports containing active data.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Active Data Sessions

Total number of sessions with active data.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Outgoing Message Rate (per sec)

Number of messages delivered per second by the Report Cache to all of its clients.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

File Count

Total number of files currently managed by FileBasedPersistenceManager.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Element Count

Total number of elements currently managed by InMemoryPersistenceManager.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Viewset Average Open Time (in sec)

Average time period in seconds to open a view set.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Independent Viewsets

Number of open independent viewsets. Independent (unshared) viewsets are neither shared or inherited. See Monitoring the Report Cache for more information.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Open Viewsets

Total number of viewsets opened by the Report Cache.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Shared Viewsets

Number of open shared viewsets. Shared viewsets are the parent viewsets (opened first). See Monitoring the Report Cache for more information.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Sharing Viewsets

Number of open sharing viewsets. Sharing (inherited) viewsets are the child viewsets (opened later). See Monitoring the Report Cache for more information.

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.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

User Action

No action required.

Response

Displays the availability of the Oracle BAM Server.

UpDown Status

Displays the current status of the Oracle BAM Server. A value of 1 indicates that the server is running, and any other value indicates that it is not running.

User Action

No action required.

26 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.

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.

Heap High Hits

This is the number of heap high hits based on sampling

Metric Summary for Database Control

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

Heap High Hits (per sec)

This is the number of heap high hits 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 26-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

Heap High Hits (per sec) (since startup)

This is the number of heap high hits per second since startup based on sampling

Metric Summary for Database Control

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

Heap High Hits (since startup)

This is the number of heap high hits since startup based on sampling

Metric Summary for Database Control

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

Heap Low Hits

This is the number of heap low hits based on sampling

Metric Summary for Database Control

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

Heap Low Hits (per sec)

This is the number of heap low hits 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 26-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

Heap Low Hits (per sec) (since startup)

This is the number of heap low hits per second since startup based on sampling

Metric Summary for Database Control

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

Heap Low Hits (since startup)

This is the number of heap low hits since startup based on sampling

Metric Summary for Database Control

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

Compare Operations Elapsed Time Metrics

The compare operation elapsed time represents the elapsed time taken by the compare operations in the directory server.

Average Elapsed Time per Compare Operation (ms)

This is the average elapsed time per compare operation measured in milliseconds.

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 26-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

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

This is the average elapsed time per compare operation since startup measured in milliseconds

Metric Summary for Database Control

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

LDAP Compare operations (since startup)

This is the number of LDAP compare operations since startup based on sampling

Metric Summary for Database Control

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

Total Elapsed Time for all Compare Operations (ms)

This is the total elapsed time for all compare operations measured in milliseconds

Metric Summary for Database Control

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

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

This is the total elapsed time for compare operations since startup measured in milliseconds

Metric Summary for Database Control

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

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

Metric Summary for Database Control

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

Compare Operations Metrics

The compare operations metrics represent the number of compare operations issued by the directory server.

Compare Operations

This is the number of compare operations 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 26-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

Compare Operations (per sec)

This is the number of compare operations 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 26-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

Compare Operations (per sec) (since startup)

This is the number of compare operations per second based on sampling

Metric Summary for Database Control

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

Compare Operations (since startup)

This is the number of compare operations since startup

Metric Summary for Database Control

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

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.

Connections Peak

Highest number of established connections since the start of the Directory Server instance.

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 26-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

Connections Per Sec

The ratio per second based on the sampling of the total number of connections.

Metric Summary for Database Control

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

Connections Per Sec (s start)

The ratio per second based on the number of connections since the start of the instance.

Metric Summary for Database Control

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

Current Connections

Current open connections

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 26-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

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.

Cache Clean Pages

The number of clean pages forced from the cache per second based on the 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 26-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

Cache Dirty Pages

The number of dirty pages forced from the cache per second based on the 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 26-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

Cache Hits

The number of requested pages found in the database per second based on the sampling.

Metric Summary for Database Control

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

Cache Page Reads

The number of pages read into the database cache per second based on the sampling.

Metric Summary for Database Control

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

Cache Page Writes

The number of pages written from the database cache to the backing file per second based on the sampling.

Metric Summary for Database Control

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

Cache Tries

The total number of requested pages found in the database cache per second based on the sampling.

Metric Summary for Database Control

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

Errors Metrics

The errors set of metrics includes security errors as well as operational errors.

Bind Security Errors

The number of bind security errors per second based on the sampling.

Metric Summary for Database Control

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

Bind Security Errors (Since Start)

The number of bind security errors per second calculated since the start of the Directory Server instance.

Metric Summary for Database Control

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

Operational Errors

The number of operational errors per second based on the sampling.

Metric Summary for Database Control

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

Operational Errors (Since Start)

The number of operational errors per second calculated since the start of the Directory Server instance.

Metric Summary for Database Control

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

Security Errors

The number of all security errors per second based on the sampling.

Metric Summary for Database Control

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

Security Errors (Since Start)

The number of all security errors per second calculated since the start of the Directory Server instance

Metric Summary for Database Control

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

Total Errors

The total number of errors per second based on the sampling.

Metric Summary for Database Control

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

Total Errors (Since Start)

The total number of errors per second calculated since the start of the Directory Server instance.

Metric Summary for Database Control

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

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.

Backend

Backend list in the Directory Server instance.

Metric Summary for Database Control

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

Current Time

Current time from the Directory Service instance.

Metric Summary for Database Control

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

Start Time

The start time of the directory server instance.

Metric Summary for Database Control

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

Version

The version of the directory server instance.

Metric Summary for Database Control

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

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.

Hash Elements Traversed

The number of hash elements traversed during hast table lookups based on sampling.

Metric Summary for Database Control

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

Hash Elements Traversed (per sec)

The number of hash elements traversed per second during hast table lookups 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 26-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

Hash Elements Traversed (per sec since startup)

The number of hash elements traversed per second during hast table lookups based on sampling.

Metric Summary for Database Control

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

Hash Elements Traversed (since startup)

The number of hash elements traversed per second during hast table lookups based on sampling.

Metric Summary for Database Control

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

Hash Table Lookups

The number of hash table lookups based on the sampling.

Metric Summary for Database Control

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

Hash Table Lookups (per sec)

The number of hash table lookups per second based on the 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 26-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

Hash Table Lookups (per sec since start)

The number of hash table lookups per second based on the sampling.

Metric Summary for Database Control

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

Hash Table Lookups (since startup)

The number of hash table lookups per second based on the sampling.

Metric Summary for Database Control

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

Longest Chain During Hash Lookups

The longest chain ever encountered in hash table lookups.

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 26-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

In Out Operation

This set of metrics includes the number of LDAP entries, referrals, and bytes returned by the directory server.

Bytes Returned

The number of bytes returned based on sampling.

Metric Summary for Database Control

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

Bytes Returned (per sec)

The number of bytes returned 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 26-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

Bytes Returned (per sec since startup)

The number of bytes returned per second since startup based on sampling.

Metric Summary for Database Control

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

Bytes Returned (since startup)

The number of bytes returned since startup based on sampling.

Metric Summary for Database Control

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

LDAP Entries Returned

The number of LDAP entries returned based on sampling.

Metric Summary for Database Control

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

LDAP Entries Returned (per sec)

The number of LDAP entries returned 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 26-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

LDAP Entries Returned (per sec) (since startup)

The number of LDAP entries returned per second since startup based on sampling.

Metric Summary for Database Control

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

LDAP Entries Returned (since startup)

The number of LDAP entries returned since startup based on sampling.

Metric Summary for Database Control

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

Referrals Returned

The number of referrals returned based on sampling.

Metric Summary for Database Control

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

Referrals Returned (per sec)

The number of referrals returned 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 26-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

Referrals Returned (per sec) (since startup)

The number of referrals returned per second since startup based on sampling.

Metric Summary for Database Control

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

Referrals Returned (since startup)

The number of referrals returned since startup based on sampling.

Metric Summary for Database Control

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

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.

Current Database Locks

The number of current database locks.

Metric Summary for Database Control

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

Current Lockers

The current number of database lockers.

Metric Summary for Database Control

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

Detected Deadlocks

The number of database deadlocks detected based on the sampling.

Metric Summary for Database Control

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

DeadLocks Detected (per sec)

The number of database deadlocks per second based on the sampling.

Metric Summary for Database Control

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

DeadLocks Detected (per sec since startup)

The number of database deadlocks detected per second since startup based on the sampling.

Metric Summary for Database Control

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

DeadLocks Detected (since startup)

The number of database deadlocks detected since startup based on the sampling.

Metric Summary for Database Control

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

Lock Conflicts

The number of database lock conflicts based on the sampling.

Metric Summary for Database Control

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

Lock Conflicts (per sec)

The number of database lock conflicts per second based on the sampling.

Metric Summary for Database Control

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

Lock Conflicts (per sec since startup)

The number of database lock conflicts per second since startup based on the sampling.

Metric Summary for Database Control

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

Lock Conflicts (since startup)

The number of database lock conflicts since startup based on the sampling.

Metric Summary for Database Control

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

Maximum Database Locks

The maximum number of database locks based on the sampling.

Metric Summary for Database Control

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

Total locks Requested

The number of total locks requested based on the sampling.

Metric Summary for Database Control

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

Total locks Requested (per sec)

The number of total locks requested per second based on the sampling.

Metric Summary for Database Control

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

Total locks Requested (per sec) (since startup)

The number of total locks requested per second since startup based on the sampling

Metric Summary for Database Control

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

Total locks Requested (since startup)

The number of total locks requested since startup based on the sampling

Metric Summary for Database Control

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

Waits before Database Lock

The number of times that a thread had to wait for a database lock based on the sampling.

Metric Summary for Database Control

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

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.

Metric Summary for Database Control

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

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.

Metric Summary for Database Control

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

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.

Metric Summary for Database Control

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

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.

Average Elapsed Time per Operation (ms)

This is the average elapsed time per operation in milliseconds based on the sampling.

Metric Summary for Database Control

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

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

The is the average elapsed time per operation since startup in milliseconds based on the sampling .

Metric Summary for Database Control

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

Total Elapsed Time for all Operations (ms)

The is the total elapsed time for all operations in milliseconds based on the sampling.

Metric Summary for Database Control

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

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.

Metric Summary for Database Control

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

Total LDAP Operations Completed

The total number of LDAP operations completed based on the sampling.

Metric Summary for Database Control

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

Total LDAP Operations Completed (per sec)

The total number of LDAP operations completed per second based on the sampling.

Metric Summary for Database Control

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

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

The total number of LDAP operations completed per second since startup based on the sampling.

Metric Summary for Database Control

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

Total LDAP Operations Completed (since startup)

The total number of LDAP operations completed since startup based on the sampling.

Metric Summary for Database Control

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

Total Operations Completed

The total number of operations completed based on the sampling.

Metric Summary for Database Control

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

Total Operations Completed (per sec)

The total number of operations completed per second based on the sampling

Metric Summary for Database Control

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

Total Operations Completed (per sec) (since startup)

The total number of operations completed per second since startup based on the sampling.

Metric Summary for Database Control

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

Total Operations Completed (since startup)

The total number of operations completed since startup based on the sampling.

Metric Summary for Database Control

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

Total Operations Initiated

The total number of operations initiated based on the sampling.

Metric Summary for Database Control

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

Total Operations Initiated (per sec)

The total number of operations initiated per second based on the sampling.

Metric Summary for Database Control

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

Total Operations Initiated (per sec) (since startup)

The total number of operations initiated per second since startup based on sampling.

Metric Summary for Database Control

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

Total Operations Initiated (since startup)

The total number of operations initiated since startup based on sampling.

Metric Summary for Database Control

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

Other Operations

This set of metrics includes the number of searches and referrals

LDAP Referral Operations

The number of LDAP referral operations based on the sampling.

Metric Summary for Database Control

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

LDAP Referral Operations (per sec)

The number of LDAP referral operations per second based on the sampling.

Metric Summary for Database Control

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

LDAP Referral Operations (per sec) (since startup)

The number of LDAP referral operations per second since startup based on the sampling.

Metric Summary for Database Control

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

LDAP Referral Operations (since startup)

The number of LDAP referral operations since startup based on the sampling.

Metric Summary for Database Control

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

Persistent Searches Running

The number of persistent searches running based on the sampling.

Metric Summary for Database Control

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

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.

Operations In Progress

The number of operations being treated by a worker thread.

Metric Summary for Database Control

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

Operations Queue Back Log

The number of requests waiting to be processed by a thread.

Metric Summary for Database Control

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

Read Waiters Queue

The read waiters queue.

Metric Summary for Database Control

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

Read Operations Elapsed Time Metrics

This set of metrics is related with the elapsed time of the read operations: bind operations and search operations.

Average Elapsed Time per Bind Operation (ms)

The average elapsed time per bind operation in milliseconds based on sampling.

Metric Summary for Database Control

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

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

The average elapsed time per bind operation since startup in milliseconds based on sampling.

Metric Summary for Database Control

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

Average Elapsed Time per Search Operation (ms)

The average elapsed time per search operation in milliseconds based on sampling.

Metric Summary for Database Control

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

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

The average elapsed time per search operation since startup in milliseconds based on sampling.

Metric Summary for Database Control

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

Average Elapsed Time per UnBind Operation (ms)

The average elapsed time per unbind operation in milliseconds based on sampling.

Metric Summary for Database Control

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

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

The average elapsed time per unbind operation since startup in milliseconds based on sampling.

Metric Summary for Database Control

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

LDAP Binds (since startup)

The number of LDAP binds since startup based on sampling.

Metric Summary for Database Control

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

LDAP Searches (since startup)

The number of LDAP searches since startup based on sampling.

Metric Summary for Database Control

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

Total Elapsed Time for Bind Operations (ms)

The total elapsed time for bind operations in milliseconds based on sampling.

Metric Summary for Database Control

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

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

The total elapsed time for bind operations since startup in milliseconds based on sampling.

Metric Summary for Database Control

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

Total Elapsed Time for Search Operations (ms)

The total elapsed time for search operations in milliseconds based on sampling.

Metric Summary for Database Control

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

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

The total elapsed time for search operations since startup in milliseconds based on sampling.

Metric Summary for Database Control

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

Total Elapsed Time for UnBind Operations (ms)

The total elapsed time for unbind operations in milliseconds based on sampling.

Metric Summary for Database Control

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

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

The total elapsed time for unbind operations since startup in milliseconds based on sampling.

Metric Summary for Database Control

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

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.

Metric Summary for Database Control

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

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.

Metric Summary for Database Control

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

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.

Metric Summary for Database Control

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

Read Operations Metrics

The read operations metrics includes the number of bind, search, and compare operations.

Anonymous Binds

The number of anonymous binds based on the sampling.

Metric Summary for Database Control

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

Anonymous binds (per sec)

The number of anonymous binds per second based on the sampling.

Metric Summary for Database Control

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

Anonymous Binds (per sec) (since startup)

The number of anonymous binds per second since startup based on the sampling.

Metric Summary for Database Control

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

Anonymous Binds (since startup)

The number of anonymous binds since startup based on the sampling.

Metric Summary for Database Control

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

LDAP Binds

The number of LDAP binds based on the sampling.

Metric Summary for Database Control

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

LDAP Binds (per sec)

The number of LDAP binds per second based on the sampling.

Metric Summary for Database Control

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

LDAP Binds (per sec) (since startup)

The number of LDAP binds per second since startup based on the sampling.

Metric Summary for Database Control

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

LDAP Binds (since startup)

The number of LDAP binds since startup based on the sampling.

Metric Summary for Database Control

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

Simple Authorized Binds (per sec) (since startup)

The number of simple authorized binds per second since startup based on the sampling.

Metric Summary for Database Control

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

Simple Authorized Binds (since startup)

The number of simple authorized binds per second since startup based on the sampling.

Metric Summary for Database Control

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

Simple Binds

The number of simple binds based on the sampling.

Metric Summary for Database Control

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

Simple Binds (per sec)

The number of simple binds per second based on the sampling.

Metric Summary for Database Control

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

Strong Authorized Binds (per sec) (since startup)

The number of strong authorized binds per second since startup based on the sampling.

Metric Summary for Database Control

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

Strong Authorized Binds (since startup)

The number of strong authorized binds since startup based on the sampling.

Metric Summary for Database Control

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

Strong Binds

The strong binds based on the sampling.

Metric Summary for Database Control

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

Strong Binds (per sec)

The number of strong binds per second based on the sampling.

Metric Summary for Database Control

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

Unauthorized Binds

The number of unauthorized binds based on the sampling.

Metric Summary for Database Control

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

Unauthorized Binds (per sec)

The number of unauthorized binds per second based on the sampling.

Metric Summary for Database Control

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

Unauthorized Binds (per sec) (since startup)

The number of unauthorized binds per second since startup based on the sampling.

Metric Summary for Database Control

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

Unauthorized Binds (since startup)

The number of unauthorized binds since startup based on the sampling.

Metric Summary for Database Control

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

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.

CPU Utilization (%)

The percentage CPU utilization based on the 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 26-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

Memory Utilization (KB)

The memory utilization in KB based on the 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 26-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

Memory Utilization (%)

The percentage memory utilization based on the 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 26-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

Response

The

Status

The

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 26-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

Metric Summary for Database Control

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.

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.

Suffix-Backend Entry - Average Cache Size

The average cache size

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 26-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

Suffix-Backend Entry - Cache Count

The cache count

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 26-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

Suffix-Backend Entry - Cache Hit Ratio

The cache hit ratio.

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 26-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

Suffix-Backend Entry - Cache Hits

The number of cache hits.

Metric Summary for Database Control

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

Suffix-Backend Entry - Cache Hits (per sec)

The number of cache hits per second.

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 26-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

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

The number of cache hits per second since startup.

Metric Summary for Database Control

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

Suffix-Backend Entry - Cache Hits (since startup)

The number of cache hits since startup.

Metric Summary for Database Control

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

Suffix-Backend Entry - Cache Size

The cache size

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 26-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

Suffix-Backend Entry - Cache Tries

The number of cache tries.

Metric Summary for Database Control

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

Suffix-Backend Entry - Cache Tries (per sec)

The number of cache tries per second.

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 26-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

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

The number of cache tries per second since startup.

Metric Summary for Database Control

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

Suffix-Backend Entry - Cache Tries (since startup)

The number of cache tries since startup.

Metric Summary for Database Control

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

Suffix-Backend Name

The suffix backend name.

Metric Summary for Database Control

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

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.

Suffix-Backend File - Cache Hit Ratio

The cache hit ratio.

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 26-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%

Metric Summary for Database Control

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

Suffix-Backend File - Cache Hits

The number of cache hits

Metric Summary for Database Control

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

Suffix-Backend File - Cache Hits (per sec)

The number of cache hits per second.

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 26-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

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

The number of cache hits per second since startup.

Metric Summary for Database Control

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

Suffix-Backend File - Cache Hits (since startup)

The number of cache hits since startup.

Metric Summary for Database Control

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

Suffix-Backend File - Cache Misses

The number of cache misses.

Metric Summary for Database Control

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

Suffix-Backend File - Cache Misses (per sec)

The number of cache misses per second.

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 26-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

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

The number of cache misses per second since startup.

Metric Summary for Database Control

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

Suffix-Backend File - Cache Misses (since startup)

The number of cache misses since startup.

Metric Summary for Database Control

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

Suffix-Backend File - Pages in to Cache

The number of pages in the cache.

Metric Summary for Database Control

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

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

The number of pages stored in the cache per second.

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 26-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

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

The number of pages stored in the cache per second since startup.

Metric Summary for Database Control

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

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

The number of pages stored in the cache since startup.

Metric Summary for Database Control

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

Suffix-Backend File - Pages Out to Disk

The number of pages sent to the disk.

Metric Summary for Database Control

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

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

The number of pages sent to the disk per second.

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 26-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

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

The number of pages sent to the disk per second since startup.

Metric Summary for Database Control

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

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

The number of pages sent to the disk since startup.

Metric Summary for Database Control

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

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.

Suffix-Backend Name

The suffix-backend name.

Metric Summary for Database Control

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

Suffix-Backend Next DB entry ID

The next database entry identification number

Metric Summary for Database Control

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

Suffix-Backend State

The status of the suffix backend.

Metric Summary for Database Control

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

Suffix-Backend Total DB Entry Count

The total database entry count.

Metric Summary for Database Control

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

Suffix-Backend LDAP Entry Count

The LDAP entry count

Metric Summary for Database Control

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

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.

Bytes wrote to log

The number of bytes written in this transaction log based on the sampling.

Metric Summary for Database Control

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

Bytes wrote to log (per sec)

The number of bytes per second written in this transaction log based on the 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 26-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

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.

Metric Summary for Database Control

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

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 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 26-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

Log Flushes

The number of number of times that the transaction log was flushed to disk based on the sampling.

Metric Summary for Database Control

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

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 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 26-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

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.

Metric Summary for Database Control

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

Log Flushes (since startup)

The number of times that the transaction log was flushed to disk since startup based on the sampling.

Metric Summary for Database Control

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

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.

Metric Summary for Database Control

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

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 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 26-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

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

Metric Summary for Database Control

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

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.

Metric Summary for Database Control

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

Log Flushes with Commits

The number of times that the transaction log was flushed to disk with commits based on the sampling.

Metric Summary for Database Control

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

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 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 26-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

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

Metric Summary for Database Control

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

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.

Metric Summary for Database Control

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

Log Written to Disk

The number of logs written to disk based on sampling.

Metric Summary for Database Control

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

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 26-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

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

The number of logs written to disk per second since startup based on sampling.

Metric Summary for Database Control

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

Log Written to Disk (since startup)

The number of logs written to disk since startup based on sampling.

Metric Summary for Database Control

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

Maximum Commits in Log Flush

The maximum number of commits in a log flush.

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 26-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

Minimum Commits in Log Flush

The minimum number of commits in a log flush.

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 26-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

Waits before getting the Log Lock

The number of times that a thread had to wait before getting a transaction log lock

Metric Summary for Database Control

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

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 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 26-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

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.

Metric Summary for Database Control

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

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.

Metric Summary for Database Control

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

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.

Aborted Transactions

The number of aborted transactions based on the sampling.

Metric Summary for Database Control

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

Aborted Transactions (per sec)

The number of aborted transactions per second based on the 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 26-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

Aborted Transactions (per sec) (since startup)

The number of aborted transactions per second since startup based on the sampling.

Metric Summary for Database Control

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

Aborted Transactions (since startup)

The number of aborted transactions since startup based on the sampling.

Metric Summary for Database Control

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

Committed Transactions

The number of committed transactions based on the sampling.

Metric Summary for Database Control

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

Committed Transactions (per sec)

The number of committed transactions per second based on the 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 26-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

Committed Transactions (per sec) (since startup)

The number of committed transactions per second since startup based on the sampling.

Metric Summary for Database Control

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

Committed Transactions (since startup)

The number of committed transactions since startup based on the sampling.

Metric Summary for Database Control

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

Current Active Transactions

The number of current active transactions based on the sampling.

Metric Summary for Database Control

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

Maximum Transactions Used

The maximum number of transactions used.

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 26-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

Waits before Transaction Locks

The number of times a transaction had to wait for a transaction lock based on the sampling

Metric Summary for Database Control

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

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 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 26-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

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

Metric Summary for Database Control

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

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

Metric Summary for Database Control

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

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.

Average Elapsed Time per Add Operation (ms)

The average elapsed time per add operation in milliseconds 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 26-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

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

The average elapsed time per add operation since startup in milliseconds based on sampling.

Metric Summary for Database Control

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

Average Elapsed Time per Delete Operation (ms)

The average elapsed time per delete operation in milliseconds 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 26-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

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

The average elapsed time per delete operation since startup in milliseconds based on sampling.

Metric Summary for Database Control

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

Average Elapsed Time per Modify Operation (ms)

The average elapsed time per modify operation in milliseconds 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 26-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

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

The average elapsed time per modify operation since startup in milliseconds based on sampling.

Metric Summary for Database Control

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

Average Elapsed Time per Modify RDN Operation (ms)

The average elapsed time per modify RDN operation in milliseconds 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 26-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

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

Metric Summary for Database Control

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

LDAP Add operations (since startup)

The number of LDAP add operations since startup based on sampling.

Metric Summary for Database Control

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

LDAP Delete operations (since startup)

The number of LDAP delete operations since startup based on sampling

Metric Summary for Database Control

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

LDAP Modify operations (since startup)

The number of LDAP modify operations since startup based on sampling

Metric Summary for Database Control

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

LDAP Modify RDN operations (since startup)

The number of LDAP modify RDN operations since startup based on sampling

Metric Summary for Database Control

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

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

The total elapsed time for add operations since startup in milliseconds based on sampling.

Metric Summary for Database Control

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

Total Elapsed Time for all Add Operations (ms)

The total elapsed time for all add operations in milliseconds based on sampling.

Metric Summary for Database Control

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

Total Elapsed Time for all Delete Operations (ms)

The total elapsed time for all delete operations in milliseconds.

Metric Summary for Database Control

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

Total Elapsed Time for all Modify Operations (ms)

The total elapsed time for all modify operations in milliseconds based on sampling.

Metric Summary for Database Control

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

Total Elapsed Time for all Modify RDN Operations (ms)

The total elapsed time for all modify RDN operations in milliseconds based on sampling.

Metric Summary for Database Control

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

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

The total elapsed time for delete operations in milliseconds since startup based on sampling.

Metric Summary for Database Control

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

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

The total elapsed time for modify operations in milliseconds since startup based on sampling.

Metric Summary for Database Control

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

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.

Metric Summary for Database Control

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

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.

Metric Summary for Database Control

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

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.

Metric Summary for Database Control

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

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.

Metric Summary for Database Control

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

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.

Metric Summary for Database Control

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

Write Operations Metrics

The read operations metrics includes the number of add, delete, modify, and modify RDN operations.

Add Operations

The average elapsed time (etime) of the add operation based on the 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 26-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

Add Operations (per sec)

The number of add operations per second based on the 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 26-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

Add Operations (per sec) (since startup)

The number of add operations per second since startup based on the sampling.

Metric Summary for Database Control

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

Add Operations (since startup)

The number of add operations since startup based on the sampling.

Metric Summary for Database Control

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

Delete Operations

The average elapsed time (etime) of the delete operation based on the 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 26-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

Delete Operations (per sec)

The number of delete operations per second based on the 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 26-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

Delete Operations (per sec) (since startup)

The number of delete operations per second since startup based on the sampling.

Metric Summary for Database Control

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

Delete Operations (since startup)

The number of delete operations per second based on the sampling.

Metric Summary for Database Control

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

Modify Operations

The number of modify operations per second based on the 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 26-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

Modify Operations (per sec)

The number of modify operations per second based on the 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 26-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

Modify Operations (per sec) (since startup)

The number of modify operations per second since startup based on the sampling.

Metric Summary for Database Control

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

Modify Operations (since startup)

The number of modify operations since startup based on the sampling.

Metric Summary for Database Control

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

Modify RDN (since startup)

The number of modify RDN operations since startup based on the sampling.

Metric Summary for Database Control

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

Modify RDN Operations

The number of modify RDN operations based on the 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 26-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

Modify RDN Operations (per sec)

The number of modify RDN operations per second based on the 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 26-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

Modify RDN Operations (per sec) (since startup)

The number of modify RDN operations per second since startup based on the sampling.

Metric Summary for Database Control

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

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