Oracle Enterprise Manager Oracle Fusion Middleware Metric Reference Manual, 11g Release 1 (11.1.0.1)

11g Release 1 (11.1.0.1)

E18807-01

Contents

List of Tables

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

Part I Oracle Fusion Middleware Metrics

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 Metrics

- JMS Connections

- JMS Servers

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

- JDK Vendor

- JDK Version

- JVM Garbage Collectors

- Garbage Collector - Garbage Collection Invocations (since startup)

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

- JVM Memory Pools

- Memory Pool - Current Usage (KB)

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

- Active Threads

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

- JDBC Connection Creates (per minute)

- Open JDBC Connections

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

- Committed JTA Transactions (per minute)

- JTA Transaction Rollbacks (per minute)

- Active JTA Transactions

- MDB Messages (per minute)

- Pending Messages

- Current Messages

- JMS Servers

- Requests (per minute)

- Request Processing Time (ms)

- Active Sessions

- Work Manager Pending Requests

- Work Manager Requests (per minute)

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

- Cache Performance - Aggregated Over Nodes

- Cache Hits Delta Sum

- Cache Hits Millis Delta Sum

- Cache Misses Delta Sum

- CacheMissesMillisDeltaSum

- StoreReadMillisDeltaSum

- StoreReadsDeltaSum

- StoreWriteMillisDeltaSum

- StoreWritesDeltaSum

- Total Gets Delta Sum

- TotalGetsMillisDeltaSum

- TotalPutsDeltaSum

- TotalPutsMillisDeltaSum

- Cache Configuration

- Batch Factor

- Description

- Expiry Delay

- Flush Delay

- High Units

- Low Units

- Persistence Type

- Queue Delay

- Refresh Factor

- Refresh Time

- Requeue Threshold

- Cache Performance

- Average Gets Millis

- Average Get Millis Delta

- Average Hit Millis

- Average Hit Millis Delta

- Average Miss Millis

- Average Miss Millis Delta

- Average Put Millis

- Average Put Millis Delta

- Cache Hits

- Cache Hits Delta

- Cache Hits Millis

- Cache Hits Millis Delta

- Cache Misses

- Cache Misses Delta

- Cache Misses Millis

- Cache Misses Millis Delta

- Hit Probability

- Queue Size

- Size

- Store Average Batch Size

- Store Average Read Millis

- Store Failures

- Store Failures Delta

- StoreRead Millis

- Store Read Millis Delta

- Store Reads

- Store Reads Delta

- Store Write Millis

- Store Write Millis Delta

- Store Writes

- Store Writes Delta

- Total Gets

- Total Gets Delta

- Total Gets Millis

- Total Gets Millis Delta

- Total Puts

- Total Puts Delta

- Total Puts Millis

- Total Puts Millis Delta

- Units

- Cluster

- Cluster Name

- Cluster Size

- License Mode

- Local Member Id

- Members

- Oldest Member ID

- Running

- Cluster Aggegated

- Cache Size

- Cache Size Delta

- Cluster Size

- Cluster Size Delta

- Publisher Success Rate

- Receiver Success Rate

- Cluster Alerts

- Cluster Name

- Cluster Nodes

- Change in No. of Nodes Since Last Collection

- Change in Number of Nodes

- Connection

- Connection Time Millis

- Outgoing Byte Backlog

- Outgoing Message Backlog

- Refresh Time

- Remote Address

- Remote Port

- Timestamp

- Total Bytes Received

- Total Bytes Sent

- Total Messages Received

- Total Messages Sent

- Connection Manager

- Connection Count

- Host IP

- Incoming Buffer Pool Capacity

- Incoming Buffer Pool Size

- Outgoing Buffer Pool Capacity

- Outgoing Buffer Pool Size

- Outgoing Byte Backlog

- Outgoing Message Backlog

- RefreshTime

- Total Bytes Received

- Total Bytes Sent

- Total Messages Received

- Total Messages Sent

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

- Total Gets Sum

- Total Gets Sum Delta

- Total Puts Sum

- Total Puts Sum Delta

- Node Configuration

- Buffer Publish Size

- Buffer Receive Size

- Burst Count

- Burst Delay

- Flow Control Enabled

- 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 (Delta Time)

- Packets Received

- Packets Received (Delta Time)

- Packets Repeated

- Packets Repeated (Delta Time)

- Packets Resent

- Packets Resent (Delta Time)

- Packets Resent Early

- Packets Resent Early (Delta Time)

- Packets Resent Excess

- Packets Resent Excess (Delta Time)

- Packets Sent

- Packets Sent (Delta Time)

- Process Name

- Publisher Success Rate

- Publisher Success Rate (Delta Time)

- Rack Name

- Receiver Success Rate (Delta Time)

- Receiver Success Rate Delta

- RefreshTime

- Role Name

- Send Queue Size

- Site Name

- Tcp Ring Failures

- Tcp Ring Failures (Delta Time)

- Tcp Ring Timeouts

- Tcp Ring TimeOuts (Delta Time)

- Up Since

- Weakest Channel

- Point to Point

- Deferred Packets

- Deferring

- LastIn

- LastOut

- Last Slow

- Outstanding Packets

- Paused

- Pause Rate

- Publisher Success Rate

- Publisher Success Rate Delta

- ReceiverSuccessRate

- ReceiverSuccessRateDelta

- Threshold

- Viewed Member Id

- 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

- Partitions All

- Requests Timeout Millis

- Running

- Statistics

- High Availibility Status

- Storage Enabled

- Task Hung Threshold Millis

- Task Timeout Millis

- Thread Count

- Type

- Service Performance

- Backup Count

- Owned Partitions Backup

- Owned Partitions Primary

- Partitions Endangered

- Partitions Unbalanced

- Partitions Vulnerable

- Refresh Time

- Request Average Duration

- Request Max Duration

- Request Pending Count

- Request Pending Duration

- Request Timedout Count

- Request Timeout Count Delta

- Request Total Count

- Request Total Count Delta

- Status HA

- Storage Enabled Count

- Task Average Duration

- Task Backlog

- Task Count

- Task Count Delta

- Task Hung Count

- Task Hung Duration

- Task Hung Task Id

- Task Max Backlog

- Task Timeout Count

- Task Timeout Count Delta

- Thread Abandoned Count

- Thread Abandoned Count Delta

- Thread Average Active Count

- Thread Count

- Thread Idle Count

- Thread Idle Count Delta

- Eviction Count

- Insert Count

- Listener Filter Count

- Listener Key Count

- Listener Registrations

- Locks Granted

- Locks Pending

- Remove Count

- Service Performance - Aggregated Over Nodes

- Backup Count

- Owned Partitions Backup

- Owned Partitions Primary

- Partitions Endangered

- Partitions Unbalanced

- Partitions Vulnerable

- Request Average Duration

- Request Max Duration

- Request Pending Count

- Request Pending Duration

- Request Timeout Count

- Request Timeout Count Delta

- Request Total Count

- Request Total Count Delta

- Storage Enabled Count

- Task Average Duration

- Task Backlog

- Task Count

- Task Count Delta

- Task Hung Count

- Task Hung Duration

- Task Max Backlog

- Task Timeout Count

- Task Timeout Count Delta

- Thread Abandoned Count

- Thread Abandoned Count Delta

- Thread Average Active Count

- Thread Count

- Thread Idle Count

- Thread Idle Count Delta

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

- Insert Count

- Listener Filter Count Sum

- Listener Key Count Sum

- Listener Registrations Sum

- Locks Granted Sum

- Locks Pending Sum

- Remove Count Sum

- Resource Usage

- Memory Usage (MB)

- Threading

- Node ID

- Thread Count

- Peak Thread Count

3 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

4 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

- Metric Summary

- Pool Checkouts

- Metric Summary

- Average Creation time(ms)

- Metric Summary

- User Action

- Free Instances

- Metric Summary

- Maximum Creation Time (ms)

- Metric Summary

- Request Count

- Metric Summary

- Available Instances in last 5 Minutes

- Metric Summary

- User Action

- Available Instances in last 1 min

- Metric Summary

- User Action

- Unavailable Instances in last 5 Minutes

- Metric Summary

- User Action

- Unavailable Instances in last 1 Minute

- Metric Summary

- User Action

- Activations

- Metric Summary

- User Action

- Pool check Ins

- Metric Summary

- User Action

- Pool Check Outs

- Metric Summary

- User Action

- Pool Check Out Failures

- Metric Summary

- Referenced Modules Reused

- Metric Summary

- Reference Modules Reused

- Metric Summary

- Unreference Modules Recycled

- Metric Summary

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

- UpDown Status

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

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

Part II Oracle Fusion Middleware Metrics

6 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

- 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

- 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

7 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

- BPMN Activity Time Distribution

- Average Execution Time (ms)

- Activity Count

- Activity Name

- Server Name

- SOA Composite - Response Metrics

- ServerName

- Composite Status

- SOA Composite Bindings/References Rate Metric

- Total number of faults since server start

- Fault throughput in last 5 minutes

- Average Incoming Messages Processing Time

- Total Incoming Messages Processing Time

- Total Incoming Message processing time

- Total number of incoming messages since server start

- Incoming message throughput in last 5 minutes

- Average Outbound Messages Processing Time

- Total Outbound Messages Processing Time since server start

- Total Outbound Message 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 Composite Faults

8 Forms

- Forms Resource Usage

- CPU Usage (%)

- Total CPU Time (millisec)

- instname.value

- Total Private Memory (KB)

- Forms Application Deployments

- Forms Application Context Root

- instname.value

- Forms Application Internal Name

- Number of User Sessions

- Application State

- Application status

- Forms Application Version

- FormsUserSessions

- appname.value

- config

- connect.value

- CPU Usage (%)

- CPU Time (millisec)

- dbname.value

- executable.value

- form.value

- instname.value

- ip.value

- jsessionid.value

- Private Memory (KB)

- servername.value

- threadid.value

- tnsentry.value

- tracefile.value

- tracing.value

- user.value

- 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

- instname.value

- Average Response Time (millisec)

- instname.value

- Servlet Name

- Response Time (millisec)

- Number Of Tasks

- Total Time

- Web Module Name

9 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

10 Discoverer

- Discoverer

- Discoverer Components

- Total CPU Time (millisec)

- CPU Usage (%)

- Memory Usage (MB)

- Total Private Memory (MB)

- Number of Sessions

- Discoverer Sessions

- Component Name

- Connection Details

- Total CPU Time (millisec)

- CPU Usage (%)

- Memory Usage (MB)

- Port Number

- Total Private Memory (MB)

- Session ID

- SSO User Name

- Discoverer Application

- CPU Idle (%)

- Total CPU Time (millisec)

- CPU Usage (%)

- Available Physical Memory (MB)

- Host

- Memory Usage (MB)

- Total Private Memory (MB)

- Number of Sessions

- Total Physical Memory (MB)

- Discoverer Components

- CPU Usage (%)

- Memory Usage (MB)

- Number of Sessions

- Total Discoverer CPU Usage

- Total Discoverer CPU Usage (%)

- Total Discoverer Memory Usage

- Total Discoverer Memory Usage (MB)

- Discoverer Plus Sessions

- Component Type

- CPU Usage (%)

- DBUser@DB - EUL

- Memory Usage (MB)

- OS Process ID

- SSO User

- Discoverer Portlet Provider Sessions

- Component Type

- CPU Usage (%)

- DBUser@DB - EUL

- Memory Usage (MB)

- OS Process ID

- SSO User

- Discoverer Sessions

- Component Type

- CPU Usage (%)

- DBUser@DB - EUL

- Memory Usage (MB)

- OS Process ID

- SSO User

- Total Number Of Discoverer Plus Sessions

- Total Number Of Discoverer Plus Sessions

- Total Number Of Discoverer Portlet Provider Sessions

- Total Number Of Discoverer Portlet Provider Sessions

- Total Number Of Discoverer Sessions

- Total Number Of Discoverer Sessions

- Total Number Of Discoverer Viewer Sessions

- Total Number Of Discoverer Viewer Sessions

- Discoverer Viewer Sessions

- Component Type

- CPU Usage (%)

- DBUser@DB - EUL

- Memory Usage (MB)

- OS Process ID

- SSO User

- Response

- UpDown Status

11 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

12 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

13 Internet Directory

- Oracle Internet Directory

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

- Active Database Sessions

- Metric Summary

- Closed LDAP Logon Session Statistics

- Total Closed Logon Sessions

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

- Active Database Sessions

- User Action

- Date and Time Stamp

- User Action

- Instance Number

- User Action

- Open Database Sessions

- User Action

- Failed Bind Operations

- Metric Summary

- (Critical Events)General System Resource Events

- Critical General Sys Resource Event Occurrences

- Critical General Sys Resource Event Type

- LDAP Load

- Server Load

- Metric Summary

- 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

14 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

15 WebCenter

- Response

- UpDown Status

- WebCenter Spaces (Aggregated)

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Page Throughput (per minute)

- Average Page Processing Time (ms)

- Service Name

- WebCenter Content Repositories (Aggregated)

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Login Time (ms)

- Logins (per minute)

- Average Processing Time (ms)

- Service Name

- WebCenter Events (Aggregated)

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Processing Time (ms)

- Service Name

- WebCenter External Applications (Aggregated)

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Page Throughput (per minute)

- Average Processing Time (ms)

- Service Name

- WebCenter Spaces Pages (Aggregated)

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Page Throughput (per minute)

- Average Page Processing Time (ms)

- Service Name

- WebCenter Portlets (Aggregated)

- Application Name

- Successful Invocations (%)

- Average HTTP 2xx Time (ms)

- Invocations (per minute)

- Average Processing Time (ms)

- Service Name

- WebCenter Producers (Aggregated)

- Application Name

- Successful Invocations (%)

- Average HTTP 2xx Time (ms)

- Invocations (per minute)

- Average Processing Time (ms)

- Service Name

- WebCenter Search (Aggregated)

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Processing Time (ms)

- Service Name

- WebCenter Services

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Processing Time (ms)

- WebCenter BPEL Worklists (Aggregated)

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Processing Time (ms)

- Service Name

- WebCenter Portlets

- Application Name

- Successful Invocations (%)

- Average HTTP 2xx Time (ms)

- Invocations (per minute)

- Average Processing Time (ms)

- Producer Type

- WebCenter Portlets (Top 5)

- Application Name

- Successful Invocations (%)

- Average HTTP 2xx Time (ms)

- Invocations (per minute)

- Average Processing Time (ms)

- Producer Type

- WebCenter Producers

- Application Name

- Successful Invocations (%)

- Average HTTP 2xx Time (ms)

- Invocations (per minute)

- Average Processing Time (ms)

- Producer Type

- WebCenter Producers (Top 5)

- Application Name

- Successful Invocations (%)

- Average HTTP 2xx Time (ms)

- Invocations (per minute)

- Average Processing Time (ms)

- Producer Type

- WebCenter Announcements

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Login Time (ms)

- Logins (per minute)

- Average Processing Time (ms)

- Service Name

- WebCenter Spaces

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Page Throughput (per minute)

- Average Page Processing Time (ms)

- WebCenter Spaces (Top 5)

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Page Throughput (per minute)

- Average Page Processing Time (ms)

- WebCenter Content Repositories

- Application Name

- Successful Invocations (%)

- Average Get Item Time (ms)

- Get Item

- Total Get Item Time (ms)

- Invocations (per minute)

- Average List Folder Time (ms)

- List Folder

- Total List Folder Time (ms)

- Average Login Time (ms)

- Logins (per minute)

- Average Processing Time (ms)

- WebCenter Events

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Processing Time (ms)

- WebCenter External Applications

- Application Name

- Invocations (per minute)

- WebCenter External Applications

- Application Name

- Name

- WebCenter Discussion Forum

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Login Time (ms)

- Logins (per minute)

- Average Processing Time (ms)

- Service Name

- WebCenter Spaces Pages

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Page Throughput (per minute)

- Average PPR Processing Time (ms)

- Average Page Processing Time (ms)

- WebCenter Spaces Pages (Top 5)

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Page Throughput (per minute)

- Average Page Processing Time (ms)

- WebCenter Import/Export

- Application Name

- Service Name

- WebCenter Lists

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Processing Time (ms)

- Service Name

- WebCenter Mail

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Login Time (ms)

- Logins (per minute)

- Average Processing Time (ms)

- Service Name

- WebCenter Notes

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Processing Time (ms)

- Service Name

- WebCenter Page Service

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Processing Time (ms)

- Service Name

- WebCenter People Connections

- Application name

- Successful Invocations (%)

- Invocations (per minute)

- Average Processing Time (ms)

- Service Name

- WebCenter Polls

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Processing Time (ms)

- Service Name

- WebCenter Recent Activity

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Processing Time (ms)

- Service Name

- WebCenter RSS News Feeds

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Processing Time (ms)

- Service Name

- WebCenter Instant Messaging and Presence

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Login Time (ms)

- Logins (per minute)

- Average Processing Time (ms)

- Service Name

- WebCenter Search

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Processing Time (ms)

- WebCenter Search (Top 5)

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Processing Time (ms)

- WebCenter BPEL Worklists

- Application Name

- Successful Invocations (%)

- Invocations (per minute)

- Average Processing Time (ms)

16 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

17 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

18 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

Index

List of Tables

- 2-1 Metric Summary Table

- 2-2 Metric Summary Table

- 2-3 Metric Summary Table

- 2-4 Metric Summary Table

- 2-5 Metric Summary Table

- 2-6 Metric Summary Table

- 2-7 Metric Summary Table

- 2-8 Metric Summary Table

- 2-9 Metric Summary Table

- 2-10 Metric Summary Table

- 2-11 Metric Summary Table

- 2-12 Metric Summary Table

- 2-13 Metric Summary Table

- 2-14 Metric Summary Table

- 2-15 Metric Summary Table

- 2-16 Metric Summary Table

- 2-17 Metric Summary Table

- 2-18 Metric Summary Table

- 2-19 Metric Summary Table

- 2-20 Metric Summary Table

- 2-21 Metric Summary Table

- 2-22 Metric Summary Table

- 2-23 Metric Summary Table

- 2-24 Metric Summary Table

- 2-25 Metric Summary Table

- 2-26 Metric Summary Table

- 2-27 Metric Summary Table

- 2-28 Metric Summary Table

- 2-29 Metric Summary Table

- 2-30 Metric Summary Table

- 2-31 Metric Summary Table

- 2-32 Metric Summary Table

- 2-33 Metric Summary Table

- 2-34 Metric Summary Table

- 2-35 Metric Summary Table

- 2-36 Metric Summary Table

- 2-37 Metric Summary Table

- 2-38 Metric Summary Table

- 2-39 Metric Summary Table

- 2-40 Metric Summary Table

- 2-41 Metric Summary Table

- 2-42 Metric Summary Table

- 2-43 Metric Summary Table

- 2-44 Metric Summary Table

- 2-45 Metric Summary Table

- 2-46 Metric Summary Table

- 2-47 Metric Summary Table

- 2-48 Metric Summary Table

- 2-49 Metric Summary Table

- 2-50 Metric Summary Table

- 2-51 Metric Summary Table

- 2-52 Metric Summary Table

- 2-53 Metric Summary Table

- 2-54 Metric Summary Table

- 2-55 Metric Summary Table

- 2-56 Metric Summary Table

- 2-57 Metric Summary Table

- 2-58 Metric Summary Table

- 2-59 Metric Summary Table

- 2-60 Metric Summary Table

- 2-61 Metric Summary Table

- 2-62 Metric Summary Table

- 2-63 Metric Summary Table

- 2-64 Metric Summary Table

- 2-65 Metric Summary Table

- 2-66 Metric Summary Table

- 2-67 Metric Summary Table

- 2-68 Metric Summary Table

- 2-69 Metric Summary Table

- 2-70 Metric Summary Table

- 2-71 Metric Summary Table

Oracle® Enterprise Manager

Oracle Fusion Middleware Metric Reference Manual,

11g Release 1 (11.1.0.1)

E18807-01

February 2011

Oracle Enterprise Manager Oracle Fusion Middleware Metric Reference Manual, 11g Release 1 (11.1.0.1)

E18807-01

Copyright © 2006, 2011, 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 software or related documentation 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 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 which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

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

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.

Related Documents

For more information, see the following manuals in the Oracle Enterprise Manager 11g Release 1 documentation set:

- Oracle Enterprise Manager Grid Control Basic Installation Guide

- Oracle Enterprise Manager Grid Control Advanced Installation and Configuration Guide

- Oracle Enterprise Manager Concepts

- Oracle Enterprise Manager Grid 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 Grid 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 Grid Control Console

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

1. From the Grid 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.

Part I

Oracle Fusion Middleware Metrics

This part provides a compilation of the Oracle Fusion Middleware target metrics provided in Oracle Enterprise Manager.

Part I contains the following chapters:

- Chapter 1, "WebLogic Server"

- Chapter 2, "Oracle Coherence Metrics"

- Chapter 3, "HTTP Server"

- Chapter 4, "Java EE Application"

- Chapter 5, "Oracle Service Bus"

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 EJBs currently in the EJB cache.

Application - Cache Accesses (per minute)

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

Application - Bean Activations (per minute)

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

Application - Cache Hits (%)

For the selected application, the percentage of cache accesses that completed successfully in the last 5 minutes. The value of this metric can range between zero and 100.

Application - Cache Misses (per minute)

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

Application - Bean Accesses (per minute)

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

Application - Bean Access Successes (%)

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

Application - Free Bean Instances

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

Application - Bean Destroys (per minute)

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

Application - Bean Access Failures (per minute)

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

Application - Beans in Use

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

Application - Bean Transaction Commits (%)

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

Application - Bean Transaction Commits (per minute)

For the selected application, the transaction commits per minute for the last 5 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.

Application - Bean Transaction Timeouts (per minute)

For the selected application, the transaction timeouts per minute for the last 5 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 5 minutes.

Application - Requests (per minute)

For the selected application, this metric shows the average number of servlet and/or JSP invocations per minute, averaged over the past five 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.

Application - Active Sessions

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

Application - Work Manager Pending Requests

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

Application - Work Manager Requests (per minute)

For the selected application, the number of requests processed per minute in the last 5 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.

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.

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.

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

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.

Datasource - Connections in Use

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

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.

Datasource - Connection Pool Size

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

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.

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.

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.

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.

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

Datasource - Connection Requests Waiting

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

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.

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

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

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.

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

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.

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.

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.

Datasource - Cached Statements Used (%)

For the selected data source, this metric shows the percentage of statements satisfied by the statement cache during the last 5 minutes.

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.

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.

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.

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

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

EJB Module - EJB Cache Hits (%)

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

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

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

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

EJB Module - Bean Successes (%)

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

EJB Module - Free Bean Instances

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

EJB Module - Bean Destroys (per minute)

For the selected EJB Module, this metric shows the bean destroys per minute in the last 5 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.

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.

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.

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

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

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

EJB Pool - Successful Bean Accesses (%)

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

EJB Pool - Available Beans

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

EJB Pool - Bean Destroys (per minute)

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

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.

EJB Pool - Beans in Use

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

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.

EJB Transaction - Bean Transaction Commits (per minute)

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

EJB Transaction - Bean Transaction Rollbacks (per minute)

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

EJB Transaction - Bean Transaction Timeouts (per minute)

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

JMS Metrics

This category provides information about JMS metrics.

JMS Connections

For the selected server, this metric shows the number of active JMS connections to the server.

JMS Servers

This metric shows the number of JMS servers that are deployed on the selected WebLogic Server instance.

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.

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.

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.

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.

Bytes Received (per minute)

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

Bytes Stored

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

Destinations

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

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.

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.

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.

Messages Received (per minute)

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

Messages Stored

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

Session Pools

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

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.

Committed Transactions (%)

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

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.

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.

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.

Transactions Processed (per minute)

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

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.

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.

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.

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.

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.

Active Transactions

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

JVM Metrics

This category provides information about JVM metrics.

JVM Class Loading

This metric provides information about JVM class loading metrics.

Classes Currently Loaded

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

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.

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.

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.

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.

Active Daemon Threads

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

Heap Usage (MB)

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

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.

JDK Version

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

JVM Garbage Collectors

This category provides information about JVM garbage collectors metrics.

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.

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.

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

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.

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

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

Objects Pending Finalization

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

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.

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

VM Version

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

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.

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.

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.

Lock Name

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

Thread State

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

The state can be any of the states defined here on the Sun Java Web site.

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.

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.

Active Threads

This metric shows the number of Java threads (daemon and non-daemon) that are currently running in the virtual machine across all processors.

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

Deadlocked Threads

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

Peak Threads

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

Active Threads

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

Threads Started (since startup)

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

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

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.

Start Time

This metric shows the time when the server was started.

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.

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.

Server Datasource - Connections Created (per minute)

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

Server Datasource - Connections in Use

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

Server Datasource - Connection Pool Size

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

Server Datasource - Connection Requests (per minute)

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

Server Datasource - Successful Connections (%)

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

Server Datasource - Connection Requests Waiting

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

Server Datasource - Connection Requests that Waited (per minute)

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

Server Datasource - Connection Wait Successes (%)

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

Server Datasource - Connection Wait Successes (per minute)

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

Server Datasource - Statements Added to Cache (per minute)

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

Server Datasource - Cached Statements not Used (per minute)

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

Server Datasource - Cached Statements Used (%)

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

Server Datasource - Cached Statements Used (per minute)

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

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.

Server Overview Metrics

This category provides information about server overview metrics.

JDBC Connection Creates (per minute)

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

Open JDBC Connections

For the selected server, the number of JDBC connections currently open.

Cached Beans

The total number of EJBs currently in the EJB cache.

Cache Accesses (per minute)

The number of EJB cache access attempts per minute in the last 5 minutes on the selected server.

Bean Activations (per minute)

The total number of Java beans per minute that have been activated in the last 5 minutes.

Cache Hits (%)

The percentage of EJB cache accesses that completed successfully in the last 5 minutes.

Cache Misses (per minute)

The number of EJB cache misses per minute in the last 5 minutes.

Bean Accesses (per minute)

EJB pool accesses per minute over 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)

For the selected server, this metric shows the bean destroys per minute in the last 5 minutes.

Bean Access Failures (per minute)

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

Beans in Use

The number of bean instances currently being used from the EJB free pool.

Bean Transaction Commits (%)

For the selected server, this metric shows the percentage of EJB transactions that were committed during 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 specifies the percentage of transactions that were committed during the last 5 minutes.

Bean Transaction Timeouts (per minute)

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

Committed JTA Transactions (per minute)

The total number of JTA transactions committed per minute on this server in the last 5 minutes.

JTA Transaction Rollbacks (per minute)

The number of JTA transactions rolled back per minute in the last 5 minutes on the selected server.

Active JTA Transactions

The number of active JTA transactions on the 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.

Pending Messages

The current number of messages pending (unacknowledged or uncommitted) stored on the JMS servers deployed on this WebLogic Server instance. Pending messages are over and above the current number of messages.

Current Messages

The current number of JMS messages stored on the JMS servers deployed on this WebLogic Server instance. This number does not include the pending messages.

JMS Servers

The number of JMS servers that are deployed on this WebLogic Server instance.

Requests (per minute)

For the selected server, the average number of servlet and/or JSP invocations per minute in the last 5 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)

Active Sessions

The number of active sessions for this server.

Work Manager Pending Requests

This metric shows the number of work manager requests waiting 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.

Server Work Manager Metrics

This category provides information about server work manager metrics.

Server Work Manager - Work Manager Pending Requests

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

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.

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.

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

Servlet/JSP - Requests (per minute)

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

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

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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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

Web Module - Active Sessions

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

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.

Execution Time Total

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

Invocation Count

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

Response Count

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

Response Error Count

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

Response Time Total

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

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.

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.

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.

2 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

Cache Hits Delta Sum

The rough number of cache hits during the last collection interval. A cache hit is a read operation invocation (i.e. get()) for which an entry exists in this map.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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 Millis Delta Sum

The total number of milliseconds (during the last collection interval) for the get() operations for which an entry existed in this map.

Metric Summary

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

Table 2-2 Metric Summary Table

Target Version

Collection Frequency

All Versions

Every 300 Hours

Cache Misses Delta Sum

The rough number of cache misses during the last collection interval.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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.

CacheMissesMillisDeltaSum

The total number of milliseconds (during the last collection interval) for the get() operations for which no entry existed in this map.

Metric Summary

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

Table 2-4 Metric Summary Table

Target Version

Collection Frequency

All Versions

Every 300 Hours

StoreReadMillisDeltaSum

The cummulative time (in millis) spent on load operations during the last collection interval; -1 if persistence type is NONE.

Metric Summary

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

Table 2-5 Metric Summary Table

Target Version

Collection Frequency

All Versions

Every 300 Hours

StoreReadsDeltaSum

The total number of load operations during the last collection interval; -1 if persistence type is NONE.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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.

StoreWriteMillisDeltaSum

The cummulative time (in milliseconds) spent on store and erase operations during the last collection interval; -1 if persistence type is NONE or READ-ONLY.

Metric Summary

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

Table 2-7 Metric Summary Table

Target Version

Collection Frequency

All Versions

Every 300 Hours

StoreWritesDeltaSum

The total number of store and erase operations during the last collection interval; -1 if persistence type is NONE or READ-ONLY.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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 Gets Delta Sum

The total number of get() operations during the last collection interval.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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.

TotalGetsMillisDeltaSum

The total number of milliseconds spent on get() operations during the last collection interval.

Metric Summary

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

Table 2-10 Metric Summary Table

Target Version

Collection Frequency

All Versions

Every 300 Hours

TotalPutsDeltaSum

The total number of put() operations during the last collection interval.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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.

TotalPutsMillisDeltaSum

The total number of milliseconds spent on put() operations during the last collection interval.

Metric Summary

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

Table 2-12 Metric Summary Table

Target Version

Evaluation and Collection Frequency

All Versions

Every 300 Hours

Cache Configuration

This metric addresses the cache configuration

Batch Factor

The BatchFactor attribute 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 (along with all other `ripe` and `soft-ripe` entries). This attribute is only applicable if asynchronous writes are enabled (i.e. the value of the QueueDelay attribute is greater than zero) and the CacheStore implements the storeAll() method. The value of the element is expressed as a percentage of the QueueDelay interval. Valid values are doubles in the interval [0.0, 1.0].

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

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 Hour

Expiry Delay

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 Hour

Flush Delay

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 Hour

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

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

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 Hour

Queue Delay

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 Hour

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 Hour

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 Hour

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 Hour

Cache Performance

The cache performance metrics

Average Gets Millis

The average number of milliseconds per get() invocation since the cache statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Average Get Millis Delta

The average number of milliseconds per get() invocation tduring the last collection interval.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Average Hit Millis

The average number of milliseconds per get() invocation that is a hit.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Average Hit Millis Delta

The average number of milliseconds per get() invocation hat is a hit during the last collection interval.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Average Miss Millis

The average number of milliseconds per get() invocation that is a miss.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Average Miss Millis Delta

The average number of milliseconds per get() invocation that is a miss during the last collection interval.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Average Put Millis

The average number of milliseconds per put() invocation since the cache statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Average Put Millis Delta

The average number of milliseconds per put() invocation since the cache statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Cache Hits

The rough number of cache hits since the cache statistics were last reset. A cache hit is a read operation invocation (i.e. get()) for which an entry exists in this map.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Cache Hits Delta

The rough number of cache hits during the last collection interval. A cache hit is a read operation invocation (i.e. get()) for which an entry exists in this map.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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 Millis

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Cache Hits Millis Delta

The total number of milliseconds (during the last collection interval) for the get() operations for which an entry existed in this map.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Cache Misses

The rough number of cache misses since the cache statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Cache Misses Delta

The rough number of cache misses during the last collection interval.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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 Millis

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Cache Misses Millis Delta

The total number of milliseconds (during the last collection interval) for the get() operations for which no entry existed in this map.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Hit Probability

The rough probability (0 <= p <= 1) that the next invocation will be a hit, based on the statistics collected since the last reset of the cache statistics.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Queue Size

The size of the write-behind queue size. 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 300 Hours

Size

The number of entries in the cache.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Store Average Batch Size

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Store Average Read Millis

The average time (in millis) spent per write operation; -1 if persistence type is NONE.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Store Failures

The total number of CacheStore failures (load, store and erase operations); -1 if persistence type is NONE.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Store Failures Delta

The total number of CacheStore failures (load, store and erase operations) during the last collection interval; -1 if persistence type is NONE.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

StoreRead Millis

The cumulative number of load operations per node; -1 if persistence type is NONE

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Store Read Millis Delta

The cummulative time (in millis) spent on load operations during the last collection interval; -1 if persistence type is NONE.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Store Reads

The total number of load operations; -1 if persistence type is NONE.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Store Reads Delta

The total number of load operations during the last collection interval; -1 if persistence type is NONE.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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.

Store Write Millis

The cummulative time (in milliseconds) spent on store and erase operations; -1 if persistence type is NONE or READ-ONLY.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Store Write Millis Delta

The cummulative time (in milliseconds) spent on store and erase operations during the last collection interval; -1 if persistence type is NONE or READ-ONLY.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Store Writes

The total number of store and erase operations; -1 if persistence type is NONE or READ-ONLY.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Store Writes Delta

The total number of store and erase operations during the last collection interval; -1 if persistence type is NONE or READ-ONLY.

Metric Summary

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

Table 2-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 Hours

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 Gets

The total number of get() operations since the cache statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Total Gets Delta

The total number of get() operations during the last collection interval.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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

The total number of milliseconds spent on get() operations since the cache statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Total Gets Millis Delta

The total number of milliseconds spent on get() operations during the last collection interval.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Total Puts

The total number of put() operations since the cache statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Total Puts Delta

The total number of put() operations during the last collection interval.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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

The total number of milliseconds spent on put() operations since the cache statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Total Puts Millis Delta

The total number of milliseconds spent on put() operations during the last collection interval.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Units

The size of the cache measured in units.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Cluster

This cluster metrics are described.

Cluster Name

The name of the cluster.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Cluster Size

The total number of cluster nodes.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

License Mode

The license mode that this cluster is using. Possible values are Evaluation, Development or Production.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Members

An array of all existing cluster members.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Oldest Member ID

The senior cluster member id; -1 if the cluster service is not running.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Running

Specifies whether the cluster is running.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Cluster Aggegated

The aggregated coherence cluster metrics are descirbed

Cache Size

The number of entries in the cache.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Cache Size Delta

The number of entries present in the cache during the last collection interval.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

After Every Sample

<

Not Defined

Not Defined

1

Cache deleted or new cache added

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.

Cluster Size

The total number of cluster nodes.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Cluster Size Delta

The total number of cluster nodes present during the last collection interval.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

After Every Sample

<

Not Defined

Not Defined

1

Cache deleted or new cache added

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

The publisher success rate from the viewing node to the viewed node since the statistics were last reset.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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

The receiver success rate from the viewing node to the viewed node since the statistics were last reset.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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.

Cluster Alerts

The coherence cluster alert metrics are described.

Cluster Name

The name of the cluster.

Metric Summary

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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 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.

Connection Time Millis

The time duration (in milliseconds) that the client has been connected.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Outgoing Byte Backlog

The backlog (in bytes) of the outgoing queue

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Outgoing Message Backlog

The backlog of the outgoing message queue.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 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 300 Hours

Remote Address

The IP address of the corresponding client.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Remote Port

The port of the corresponding client.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Timestamp

The date/time value (in local time) that the corresponding client connected to the Proxy.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Total Bytes Received

The total number of bytes recieved since the last time the statistics were reset.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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

The total number of bytes sent since the statistics were last reset.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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

The total number of messages received since the statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Total Messages Sent

The total number of messages sent since the last time the statistics were reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Connection Manager

The connection manager metrics are described.

Connection Count

The number of client connections.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Host IP

The IP address of the host.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Incoming Buffer Pool Capacity

The pool capacity (in bytes) of the incoming buffer.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Incoming Buffer Pool Size

The number of buffers in the incoming pool.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Outgoing Buffer Pool Capacity

The pool capacity (in bytes) of the outgoing buffer.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Outgoing Buffer Pool Size

The number of buffers in the outgoing pool.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Outgoing Byte Backlog

The backlog (in bytes) of the outgoing queue.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Outgoing Message Backlog

The backlog of the outgoing message queue.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

RefreshTime

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

Total Bytes Received

The total number of bytes received by the Proxy host since the statistics were last reset.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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

The total number of bytes sent by the Proxy host since the statistics were last reset.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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

The total number of messgaes received by the Proxy host since the statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Total Messages Sent

The total number of messgaes sent by the Proxy host since the statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Garbage Collector after GC

Garbage Collector memory pool metrics after completion of garbage collection per node.

Name

Garbage Collector Name.

Metric Summary

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 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 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 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 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 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 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 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 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 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 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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

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

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 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 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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

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

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 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 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 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 garbagee collected

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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" 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 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 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 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 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 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 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 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 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 Session Cache

The number of non-distributed sessions stored in the local session cache

Metric Summary

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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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" 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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" 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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" 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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" 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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" 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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" 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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" 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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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" 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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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.

Heap Memory Used (bytes)

The amount of heap memory currently in use.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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.

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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.

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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.

Non Heap Memory Used (bytes)

The amount of non-heap memory currently in use.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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.

Object Pending Finalization Count

The approximate number of objects for which finalization is pending.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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.

Verbose

Boolean value indicating whether verbose logging is enabled or not.

Metric Summary

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.

Total Gets Sum

The total number of get() operations since the cache statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Total Gets Sum Delta

The total number of get() operations during the last collection interval.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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

The total number of put() operations since the cache statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Total Puts Sum Delta

The total number of put() operations during the last collection interval.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Hour

Burst Count

The maximum number of packets to send without pausing. Anything less than one (e.g. zero) means no limit.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Burst Delay

The number of milliseconds to pause between bursts. Anything less than one (e.g. zero) is treated as one millisecond.

Metric Summary

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 flow control is enabled for this node.

Metric Summary

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 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 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 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 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 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 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 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 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 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 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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Hour

Nack Enabled

Indicates whether or not the early packet loss detection protocol is enabled.

Metric Summary

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 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), Grid Edition (GE).

Metric Summary

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 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 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 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 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 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 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 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 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 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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Machine Id

The Member`s machine Id.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Member Name

A configured name that must be unique for every Member.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Memory Available (MB)

The total amount of memory in the JVM available for new objects in MB.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Packets Bundled (Delta Time)

The total number of packets which were bundled prior to transmission during the last collection interval. The total number of network transmissions is equal to (PacketsSent - PacketsBundled).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Packets Received

The number of packets received since the node statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Packets Received (Delta Time)

The number of packets received during the last collection interval.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Packets Repeated

The number of duplicate packets received since the node statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Packets Repeated (Delta Time)

The number of duplicate packets received since the node statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Packets Resent (Delta Time)

The number of packets resent during the last collection interval. A packet is resent when there is no ACK received within a timeout period.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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

Multiple Thresholds

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Packets Resent Early (Delta Time)

The total number of packets resent ahead of schedule during the last collection interval. A packet is resent ahead of schedule when there is a NACK indicating that the packet has not been received. .

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Packets Resent Excess

The total number of packet retransmissions which were later proven unnecessary.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Packets Resent Excess (Delta Time)

The total number of packet retransmissions sent during the last collection interval which were later proven unnecessary.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Packets Sent

The number of packets sent since the node statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Packets Sent (Delta Time)

The number of packets sent during the last collection interval.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Publisher Success Rate (Delta Time)

The publisher success rate for this cluster node during the last collection interval. 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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.

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Receiver Success Rate (Delta Time)

The receiver success rate from the viewing node to the viewed node during the last collection interval.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Receiver Success Rate Delta

The receiver success rate from the viewing node to the viewed node during the last collection interval.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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.

RefreshTime

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

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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 (e.g. data center), and different for Members that are on different physical sites.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Tcp Ring Failures (Delta Time)

The number of recovered TcpRing disconnects during the last collection interval. 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Tcp Ring Timeouts

The number of TcpRing timeouts since the node statistics were last reset. A timeout is a normal, but relatively rare event that is registered when the TcpRing peer did not ping this node within a heartbeat interval. This value will be -1 if the TcpRing is disabled.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Tcp Ring TimeOuts (Delta Time)

The number of TcpRing timeouts during the last collection interval. A timeout is a normal, but relatively rare event that is registered when the TcpRing peer did not ping this node within a heartbeat interval. This value will be -1 if the TcpRing is disabled.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Up Since

The date/time value (in cluster time) that this Member joined the cluster.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Point to Point

Point to point metrics.

Deferred Packets

The number of packets addressed to the viewed member that the viewing member is currently deferring to send. The viewing member will delay sending these packets until the number of outstanding packets falls below the value of the Threshold attribute. The value of this attribute is only meaningful if the viewing member has FlowControl enabled.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Deferring

Indicates whether or not the viewing member is currently deferring packets to the viewed member. The value of this attribute is only meaningful if the viewing member has FlowControl enabled.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

LastIn

The number of milliseconds that have elapsed since the viewing member last received an acknowledgment from the viewed member.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

LastOut

The number of milliseconds that have elapsed since the viewing member last sent a packet to the viewed member.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Last Slow

The number of milliseconds that have elapsed since the viewing member declared the viewed member as slow, or -1 if the viewed member has never been declared slow.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Outstanding Packets

The number of packets that the viewing member has sent to the viewed member which have yet to be acknowledged. The value of this attribute is only meaningful if the viewing member has FlowControl enabled.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Paused

Indicates whether or not the viewing member currently considers the viewed member to be unresponsive. The value of this attribute is only meaningful if the viewing member has FlowControl enabled.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Pause Rate

The percentage of time since the last time statistics were reset in which the viewing member considered the viewed member to be unresponsive. Under normal conditions this value should be very close to 0.0. Values near 1.0 would indicate that the viewed node is nearly inoperable, likely due to extremely long GC pauses. The value of this attribute is only meaningful if the viewing member has FlowControl enabled.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Publisher Success Rate

The publisher success rate from the viewing node to the viewed node since the statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Publisher Success Rate Delta

The publisher success rate for this cluster node during the last collection interval. 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Hour

ReceiverSuccessRate

The receiver success rate from the viewing node to the viewed node since the statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

ReceiverSuccessRateDelta

The receiver success rate from the viewing node to the viewed node during the last collection interval.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Threshold

The maximum number of outstanding packets for the viewed member that the viewing member is allowed to accumulate before initiating the deferral algorithm. The value of this attribute is only meaningful if the viewing member has FlowControl enabled.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Viewed Member Id

The ID of the member being viewed.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

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 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 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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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.

Free Physical Memory Size (bytes)

The amount of free physical memory.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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.

Free Swap Space Size (bytes)

The amount of free swap space.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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.

Max File Descriptor Count

Maximum permissible open file descriptor.

Metric Summary

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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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.

Process Cpu Time

The CPU time used by the process on which the Java virtual machine is running.

Metric Summary

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 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 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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Response

Response metrics.

Status

This metric shows the response status.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Minute

After Every Sample

=

Not Defined

0

1

The Coherence Cluster instance is down

Runtime

Coherence Node Runtime metrics

Row ID

Internal key metric

Metric Summary

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

Partitions All

The total number of partitions that each cache storage is divided into.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Requests Timeout Millis

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Hour

Running

Specifies whether or not the service is running.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Statistics

Statistics for this service in human readable format.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

High Availibility 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 stoppped at once without data loss. The value of NODE-SAFE means that any cluster node could be stoppped 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Hour

Storage Enabled

Specifies whether local storage is enabled for this cluster Member.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Task Hung Threshold Millis

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Hour

Task Timeout Millis

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Hour

Thread Count

The number of threads in the service thread pool.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Type

The type identifier of the service.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Service Performance

The service performance metrics are described.

Backup Count

The number of backups for every cache storage.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Owned Partitions Backup

The number of partitions that this Member backs up (responsible for the backup storage).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Owned Partitions Primary

The number of partitions that this Member owns (responsible for the primary storage).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Partitions Endangered

The total number of partitions that are not currently backed up.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Partitions Vulnerable

The total number of partitions that are backed up on the same machine where the primary partition owner resides.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 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 300 Hours

Request Average Duration

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Request Max Duration

The maximum duration (in milliseconds) of a synchronous request issued by the service since the last time the statistics were reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Request Pending Count

The number of pending synchronous requests issued by the service.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Request Pending Duration

The duration (in milliseconds) of the oldest pending synchronous request issued by the service.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Request Timedout Count

The total number of timed-out requests since the last time the statistics were reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Request Timeout Count Delta

The number of timed out requests per node since the last collection interval.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Request Total Count Delta

The total number of synchronous requests issued by the service during the last collection interval.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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.

Status HA

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 stoppped at once without data loss. The value of NODE-SAFE means that any cluster node could be stoppped 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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.

Storage Enabled Count

Specifies the total number of cluster nodes running this Service for which local storage is enabled.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Average Duration

The average duration (in milliseconds) of an individual task execution.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Backlog

The size of the backlog queue that holds tasks scheduled to be executed by one of the service threads.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Count

The total number of executed tasks since the last time the statistics were reset

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Count Delta

The total number of executed tasks during the last collection interval.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Hung Count

The total number of currently executing hung tasks.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Hung Duration

The longest currently executing hung task duration in milliseconds.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Hung Task Id

The ID of the longest currently executing hung task.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Max Backlog

The maximum size of the backlog queue since the last time the statistics were reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Timeout Count

The total number of timed-out tasks since the last time the statistics were reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Timeout Count Delta

The total number of timed out tasks since the last time the statistics were reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Thread Abandoned Count Delta

The number of abandoned threads from the service thread pool during the last collection interval. 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Thread Count

The number of threads in the service thread pool.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Thread Idle Count Delta

The number of threads that became idle in the service thread pool during the last collection interval.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Eviction Count

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.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Insert Count

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

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Listener Filter Count

The number of filter-based listeners currently registered with the StorageManager.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Listener Key Count

The number of filter-based listeners currently registered with the StorageManager.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Listener Registrations

The total number of listener registration requests processed by the StorageManager since the last time the statistics were reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Locks Granted

The number of locks currently granted for the portion of the partitioned cache managed by the StorageManager.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Locks Pending

The number of pending lock requests for the portion of the partitioned cache managed by the StorageManager.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Remove Count

The number of removes from the backing map managed by this StorageManager caused by operations such as clear, remove or invoke.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Service Performance - Aggregated Over Nodes

The service performance metrics aggregated over nodes are described.

Backup Count

The number of backups for every cache storage.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Owned Partitions Backup

The number of partitions that this Member backs up (responsible for the backup storage).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Owned Partitions Primary

The number of partitions that this Member owns (responsible for the primary storage).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Partitions Endangered

The total number of partitions that are not currently backed up.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Partitions Vulnerable

The total number of partitions that are backed up on the same machine where the primary partition owner resides.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Request Average Duration

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Request Max Duration

The maximum duration (in milliseconds) of a synchronous request issued by the service since the last time the statistics were reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Request Pending Count

The number of pending synchronous requests issued by the service.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Request Pending Duration

The duration (in milliseconds) of the oldest pending synchronous request issued by the service.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Request Timeout Count

The total number of timed-out requests since the last time the statistics were reset.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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 "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 Timeout Count Delta

The total number of synchronous requests issued by the service during the last collection interval.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Request Total Count

The total number of synchronous requests issued by the service since the last time the statistics were reset.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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 "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 Total Count Delta

The total number of synchronous requests issued by the service during the last collection interval.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Storage Enabled Count

Specifies the total number of cluster nodes running this service for which local storage is enabled.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Average Duration

The average duration (in milliseconds) of an individual task execution.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Backlog

The size of the backlog queue that holds tasks scheduled to be executed by one of the service pool threads.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Count

The total number of executed tasks since the last time the statistics were reset

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Count Delta

The total number of executed tasks during the last collection interval.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Hung Count

The total number of currently executing hung tasks.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Hung Duration

The longest currently executing hung task duration in milliseconds.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Max Backlog

The maximum size of the backlog queue since the last time the statistics were reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Timeout Count

The total number of timed-out tasks since the last time the statistics were reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Task Timeout Count Delta

The total number of timed-out tasks during the last collection interval.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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

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.

Thread Abandoned Count Delta

The number of abandoned threads from the service thread pool during the last collection interval. 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.l

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Thread Average Active Count

The average number of active (not idle) threads in the service thread pool since the the statistics were last reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Thread Count

The number of threads in the service thread pool.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 Hours

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

Thread Idle Count

The number of currently idle threads in the service thread pool.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Thread Idle Count Delta

The number of threads that became idle in the service thread pool during the last collection interval.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 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 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 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 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 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 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 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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Hour

Store Manager - Aggregated Over Nodes

The storage manager aggregate metrics are described.

Events Dispatched

The total number of events dispatched by the StorageManager since the last time the statistics were reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Eviction Count Sum

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.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Insert Count

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

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Listener Filter Count Sum

The number of filter-based listeners currently registered with the StorageManager.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Listener Key Count Sum

The number of key-based listeners currently registered with the StorageManager.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Listener Registrations Sum

The total number of listener registration requests processed by the StorageManager since the last time the statistics were reset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Locks Granted Sum

The number of locks currently granted for the portion of the partitioned cache managed by the StorageManager.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Locks Pending Sum

The number of pending lock requests for the portion of the partitioned cache managed by the StorageManager.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Remove Count Sum

The number of removes from the backing map managed by this StorageManager caused by operations such as clear, remove, or invoke.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Hour

Resource Usage

This metric shows the memory usage for the Coherence target.

Memory Usage (MB)

This metric shows the total memory used by all nodes in the cluster.

Threading

The threading metrics are described.

Node ID

Coherence Node ID.

Metric Summary

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 2-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.

3 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 Grid Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is 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 OracleHTTP Server metrics.

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

Metric Summary

The rest of the information in this section is only valid for this metric when it appears in Enterprise Manager Grid 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 Grid 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 Grid 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 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 Grid 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 Grid Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is 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 Grid Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 Grid 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 Grid Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is 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 Grid 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 Grid Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 Grid Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 Grid 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 Grid Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is 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 Grid 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 Grid Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is 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 Grid Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is 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 Grid 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 Grid Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is 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 Grid 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 Grid 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 Grid Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is 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 Grid 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 Grid 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 Grid 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 Grid 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 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 Grid 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 Grid 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 Grid 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 Grid 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 Grid Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is 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 Grid 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 Grid 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 Grid 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 Grid Control (if applicable).

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

4 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 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 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 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 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 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 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 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 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 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 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 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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Pool Checkouts

The number of free Application Module instances checked out at the current time.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Average Creation time(ms)

The average creation time for an ApplicationModule instance since the data was last collected.

Metric Summary

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Maximum Creation Time (ms)

The maximum creation time for an Application Module instance since the data was last collected.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Request Count

The number of main Application Module instances since the last request.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Referenced Modules Reused

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Reference Modules Reused

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Unreference Modules Recycled

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Datasource Metrics

This category provides information about datasource metrics.

Datasource - Available Connections

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

Datasource - Connections Created (per minute)

This metric shows the average number of database connections created for this data source per minute in the last 5 minutes.

Datasource - Connections in Use

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

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.

Datasource - Connection Pool Size

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

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.

Datasource - Connection Request Failures (per minute)

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

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

Datasource - Successful Connections (%)

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

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

EJB Module - Cache Hits (%)

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

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

EJB Module - Bean Accesses (per minute)

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

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

EJB Module - Free Bean Instances

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

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

EJB Module - Beans In Use

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

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 for the select EJB over the last 5 minutes.

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

EJB Transaction - Bean Transaction Rollbacks (per minute)

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

EJB Transaction - Bean Transaction Timeouts (per minute)

This metrics shows the average number of transaction timeouts per minute for this EJB over the last 5 minutes.

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Cache Hits (%)

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

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Free Bean Instances

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

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Beans In Use

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

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Active Sessions

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

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Work Manager Pending Requests

This metric shows the number of Work Manager requests waiting in the queue.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Status Metrics

This category provides information about status metrics.

Server Name

This metric shows the name of the current WebLogic server.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Web Module - Active Sessions

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

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

MDS Metrics

Metrics concerning MDS (Metadata Services)

Metadata Object Gets Per Second

The number of metadata object gets per second.

Metric Summary

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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

Metadata Update Processing Time (seconds)

The average elapsed time in seconds taken to update a metadata object.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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

5 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

Contains Sensitive Data

This metric indicates whether or not the service handles sensitive data.

Created User

This metric shows the name of the user who created the service.

Created Time

This metric shows the time when the service was created.

End Point URI

This metric shows the end point URI of the service.

Last Modified User

This metric shows the name of the user who last modified the service.

Last Modified Time

This metric shows the time when the service was last modified time.

Protocol

This metric shows the protocol of the service it operates on.

Status

This metric shows the status of the service. The status can be either Up or Down.

Version

This metric shows the version of Oracle Service Bus.

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 average response time 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.

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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

Failure Rate

This metric shows the failure rate of messages since last collection.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 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 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 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 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 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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 webservice security violation 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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 75 Minutes

Part II

Oracle Fusion Middleware Metrics

This part provides a compilation of the Oracle Fusion Middleware target metrics provided in Oracle Enterprise Manager.

Part II contains the following chapters:

- Chapter 6, "Oracle SOA Infra"

- Chapter 7, "SOA Composite"

- Chapter 8, "Forms"

- Chapter 9, "Portal"

- Chapter 10, "Discoverer"

- Chapter 11, "Reports Bridge"

- Chapter 12, "Virtual Directory"

- Chapter 13, "Internet Directory"

- Chapter 14, "Directory Integration Platform"

- Chapter 15, "WebCenter"

- Chapter 16, "Web Cache"

- Chapter 17, "Business Activity Monitoring"

- Chapter 18, "Business Activity Monitoring Server"

6 Oracle SOA Infra

This chapter describes Oracle SOA Infra metrics.

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 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 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 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 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 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 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 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 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 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 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 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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 following table shows how often the metric's value is collected.

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 following table shows how often the metric's value is collected.

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 following table shows how often the metric's value is collected.

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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

SOA Mediator Engine Requests

Callback Requests

This metric shows the callback requests in the mediator service engine.

Metric Summary

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

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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total number of BPEL messages since startup

This metric shows the total number of BPEL messages since startup.

Metric Summary

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 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 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 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 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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Total number of mediator messages since startup

This metric shows the total number of mediator messages since server startup.

Metric Summary

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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

7 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

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 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 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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

BPMN Activity Time Distribution

Displays the metrics related to the BPMN Activity-Time distribution

Average Execution Time (ms)

The average time that this BPMN activity took to execute.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Minute

Activity Count

Number of times this BPMN activity has been invoked.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Minute

Activity Name

Name of the BPMN Activity whose data are being shown.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Minute

Server Name

Name of the J2EE container where the SOA Composite application is deployed

Metric Summary

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

SOA Composite - Response Metrics

Indicates whether the SOA composite application is available to accept requests.

ServerName

This metric shows the name of the server on which the SOA composite application is deployed.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Minute

Composite 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

Fault throughput in last 5 minutes

This metric shows the throughput for faulted messages in the binding.

Metric Summary

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

Total Incoming Messages Processing Time

This metric shows the total processing time of incoming messages in the binding.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Minute

Total Incoming Message processing time

This metric shows the total processing time of incoming messages in the binding.

Metric Summary

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 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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every Minute

Total Outbound Messages Processing Time since server start

This metric shows the total processing time of outbound messages in the binding.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every Minute

Total Outbound Message processing time

This metric shows the total processing time of outbound messages in the binding.

Metric Summary

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

Displays metrics about total composite faults.

8 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 60 Hours

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

Forms Application Deployments

Shows information about the forms application deployments deployed in various WebLogic Server instances.

Forms Application Context Root

This metric specifies the Context Root of the Forms application deployment.

User Action

No action required.

instname.value

Forms Application Internal Name

This metric provides the Forms application name including the version information.

User Action

No user action required.

Number of User Sessions

This metric indicates the number of forms sessions running per Forms application deployment.

User Action

No user action required.

Application State

This metric describes the current state of an application. An application could be in various states such as Active, Prepared and so on.

User Action

No user action required.

Application status

This metric specifies the status of Forms application deployment.

User Action

Check whether the WebLogic Server instance has been started and if so whether the application formsapp.ear has been deployed successfully.

Forms Application Version

This metric specifies the Forms Application Version.

User Action

No user action required.

FormsUserSessions

This metric provides information such as resource usage, connection time, and so on of individual Forms sessions.

appname.value

This metric specifies the name of the forms application that is deployed in the WebLogic Server instance. This is the deployment name in whose servlet the forms session is running.

User Action

No user action required.

config

This metric specifies the Configuration section the Forms Session is using. The configuration parameters are picked up either from the default section or the selected configuration section of formsweb.cfg.

User Action

No user action required.

connect.value

This metric provide information on the client connection time. This is the time at which the client connected to the Forms Runtime process.

User Action

No user action required.

CPU Usage (%)

This metric specifies the percentage of CPU Usage consumed by individual Forms sessions.

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.

CPU Time (millisec)

This metric specifies the CPU Time (in millisec) consumed by individual Forms session.

User Action

No user action required.

dbname.value

This metric provides the Database name to which the Forms session is connected.

User Action

No user action required.

executable.value

This metric provides the Forms Runtime Engine executable name.

User Action

No user action required.

form.value

This metric specifies the name of the form module that is active.

User Action

No user action required.

instname.value

This metric provides the name of the application server instance where Forms is configured.

User Action

No user action required.

ip.value

This metric specifies the IP Address of the client machine.

User Action

No user action required.

jsessionid.value

This metric provides the Jsession ID that is used by the Forms Servlet for session management.

User Action

No user action required.

Private Memory (KB)

This metric specifies the Private memory consumed by the Forms session. 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.

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.

servername.value

This metric provides the name of the WebLogic Server where Forms servlet is deployed.

User Action

No user action required.

threadid.value

This metric provides the Thread ID of the Forms process that is used for tracing on Windows platforms.

User Action

No user action required.

tnsentry.value

This metric provides the TNS alias that is used by a running form to connect to Database. This is used to get Database specific information to be displayed on the Database Sessions page.

User Action

No user action required.

tracefile.value

This metric provides the name of the Trace file in which the trace statements are written.

User Action

No user action required.

tracing.value

This metric provides information on the trace group that contains the trace events that are being traced. This may not reflect the accurate trace group if dynamic tracing built-ins have been used to enable or disable selective events.

User Action

No user action required.

user.value

This metric specifies the Database user that is connected to the Forms session.

User Action

No user action required.

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.

User Action

No user action required.

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.

User Action

No user action required.

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.

User Action

No user action required.

Response

The Response category provides information about the default Forms application deployment 'formsapp' in WebLogic Server WLS_FORMS

instname.value

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

Target Version

Collection Frequency

All Versions

Every 60 Hours

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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

=

Not Defined

0

1

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.

instname.value

This metric provides the name of the instance where Forms Servlet is configured.

Average Response Time (millisec)

This metric measure the average response time.

instname.value

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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

9 Portal

This chapter describes Oracle Portal metrics.

Portlets (All)

This category provides information about portlets metrics.

Cache Hit (%)

This metric specifies the rate of cache hits.

Metric Summary

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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

Availability (%)

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Producer Type

Metric Summary

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 (%)

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Average Time (ms)

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Requests (per minute)

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Availability (%)

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Producer Type

Metric Summary

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

Metric Summary

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 (%)

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Average Time (ms)

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Requests (per minute)

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Availability (%)

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

Producer Type

Metric Summary

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

Metric Summary

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

Metric Summary

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

Metric Summary

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, 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 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 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 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 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 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 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 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 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 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 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 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 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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

10 Discoverer

This chapter describes Oracle Discoverer metrics.

Discoverer

Oracle Business Intelligence Discoverer is a business intelligence tool for analyzing data. Discoverer provides an integrated business intelligence solution comprising a set of intuitive ad-hoc query, reporting, analysis, and Web-publishing tools. These tools enable nontechnical users to gain immediate access to information from data marts, data warehouses, and online transaction processing systems. Discoverer integrates seamlessly with Oracle Portal, enabling rapid deployment of Discoverer workbooks and worksheets to Web portals.

Discoverer Components

Provides information about the metrics aggregated at the level of each Discoverer component.

Total CPU Time (millisec)

This metric specifies the total CPU usage time (in milliseconds) for all the Discoverer server sessions of the selected component on the host machine.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

CPU Usage (%)

This metric specifies the CPU usage (in percentage) for the Discoverer server sessions of the selected component on the host machine.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Memory Usage (MB)

This metric specifies the memory (in megabytes) used by the Discoverer server sessions of the selected component on the host machine.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Total Private Memory (MB)

This metric specifies the total private memory (in megabytes) used by the Discoverer server sessions of the selected component on the host machine.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Number of Sessions

This metric specifies the total number of Discoverer server sessions that are active for the selected component on the host machine.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Discoverer Sessions

This metric displays information about the Discoverer server sessions that are currently active.

Component Name

This metric indicates the name of the Discoverer component for which the metrics are displayed.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Connection Details

This metric specifies the database user, the database, and the EUL to which the session is connected. The format of this metric value is databaseuser@database - EUL.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Total CPU Time (millisec)

This metric specifies the total CPU usage time (in milliseconds) for the Discoverer server session on the host machine.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

CPU Usage (%)

This metric specifies the CPU usage (in percentage) for the Discoverer server session on the host machine.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Memory Usage (MB)

This metric specifies the amount of memory (in megabytes) used by the Discoverer server session on the host machine.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Port Number

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Total Private Memory (MB)

This metric specifies the amount of total private memory (in megabytes) used by the Discoverer server session on the host machine.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Session ID

This metric indicates the discoverer client session ID.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

SSO User Name

If Single Sign-On (SSO) is enabled for Discoverer, this column identifies the SSO user that is using the current session. Information about the SSO user is meaningful only for Discoverer Plus and Discoverer Viewer because SSO users work in Plus and Viewer sessions interactively. For Discoverer Portlet Provider, information about the SSO user might not be meaningful because Discoverer Portlet Provider runs queries in the background, and a query could run as a given SSO user even when that SSO user is not currently logged in.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Discoverer Application

Provides information about metrics at the Discoverer application level, aggregated for all the server sessions.

CPU Idle (%)

This metric specifies the CPU idle time (in percentage) on the host machine.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Total CPU Time (millisec)

This metric specifies the total CPU usage time (in milliseconds) for all Discoverer server sessions on the host machine.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

CPU Usage (%)

This metric specifies the CPU usage (in percentage) for all Discoverer server sessions on the host machine.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Available Physical Memory (MB)

This metric specifies the amount of free physical memory (in megabytes) on the host machine.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Host

The metric indicates the host name.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Memory Usage (MB)

This metric specifies the memory (in megabytes) used by all the Discoverer server sessions on the host machine.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Total Private Memory (MB)

This metric specifies the total private memory (in megabytes) used by all the Discoverer server sessions on the host machine.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Number of Sessions

This metric specifies the total number of Discoverer server sessions that are active on the host machine.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Total Physical Memory (MB)

This metric specifies the total physical memory (in megabytes) available on the host machine.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Hours

Discoverer Components

This metric displays the total CPU and memory consumption for all current sessions created by each Discoverer component (Discoverer Plus, Discoverer Viewer, or Discoverer Portlet Provider). Note that the total CPU and memory consumption displayed here is only for the sessions and does not include the CPU and memory consumption of the servlets for these components. This metric also displays the total number of sessions created by the component.

CPU Usage (%)

This metric specifies the total CPU usage for the sessions created by each Discoverer UI component. The total CPU usage does not include CPU usage for the servlets of these components. For CPU usage of servlets, see the Discoverer application page under the OC4J_BI_Forms home page.

Memory Usage (MB)

This metric specifies the total memory usage for the sessions spawned by the given UI component. The total memory usage does not include memory usage for the servlets of these components. For memory usage of servlets, see the Discoverer application page under the OC4J_BI_Forms home page.

Number of Sessions

This metric specifies the total number of Discoverer sessions created by the given component.

Total Discoverer CPU Usage

This metric displays the total CPU percentage used by all Discoverer sessions running on the machine at a given time. The total CPU usage does not include the CPU usage of the servlets for Discoverer Plus, Viewer, or Portlet Provider. For the CPU usage of these servlets, see the Discoverer application page from the OC4J_BI_Forms home page in the EM standalone console.

Total Discoverer CPU Usage (%)

This metric specifies the percentage of CPU used by all Discoverer sessions running on the machine at a given time. The total CPU usage does not include the CPU usage of the servlets for Discoverer Plus, Viewer, and Portlet Provider. For the CPU usage of these servlets, see the Discoverer application page from the OC4J_BI_Forms home page in the EM standalone console.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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

CPU Usage is %value%%%

Total Discoverer Memory Usage

This metric displays the total memory used by all Discoverer sessions running on the machine at a given time. The total memory usage does not include the memory usage of the servlets for Discoverer Plus, Viewer, or Portlet Provider. For the memory usage of these servlets, see the Discoverer application page from the OC4J_BI_Forms home page in the EM standalone console.

Total Discoverer Memory Usage (MB)

This metric specifies the total memory usage for all Discoverer sessions.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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

Memory Usage is %value% MB

Discoverer Plus Sessions

This metric displays information about all the Discoverer sessions created by Discoverer Plus. The information included for each session is the session ID, OS Process ID, memory usage of the session, CPU usage for the session, database and EUL to which the session is connected, and, if SSO is enabled, the SSO user using the session.

Component Type

This metric specifies the Discoverer UI component that started the Discoverer Plus, Discoverer Viewer, or Discoverer Portlet Provider session.

CPU Usage (%)

This metric specifies the percentage CPU usage for this session.

DBUser@DB - EUL

This metric specifies the database user, database name, and EUL for this session.

Memory Usage (MB)

This metric specifies the memory used (in megabytes) for this session.

OS Process ID

This metric indicates the operating system process ID for the session.

SSO User

This metric indicates the name of the Single Sign-On (SSO) user for this session.

Discoverer Portlet Provider Sessions

This metric displays information about all the Discoverer sessions created by Discoverer Portlet Provider. The information included for each session is the session ID, OS Process ID, memory usage of the session, CPU usage for the session, database and EUL to which the session is connected, and, if SSO is enabled, the SSO user using the session.

Component Type

This metric specifies the Discoverer UI component that started the Discoverer Plus, Discoverer Viewer or Discoverer Portlet Provider session.

CPU Usage (%)

This metric specifies the percentage CPU usage for this session.

DBUser@DB - EUL

This metric specifies the database user, database name, and EUL for this session.

Memory Usage (MB)

This metric specifies the memory used (in megabytes) for this session.

OS Process ID

This metric specifies the operating system process ID for this session.

SSO User

If Single Sign-On (SSO) is enabled for Discoverer, this column identifies the SSO user that is using the current session. Information about the SSO user is meaningful only for Discoverer Plus and Discoverer Viewer because SSO users work in Plus and Viewer sessions interactively. For Discoverer Portlet Provider, information about the SSO user might not be meaningful because Discoverer Portlet Provider runs queries in the background, and a query could run as a given SSO user even when that SSO user is not currently logged in.

Discoverer Sessions

This metric displays information about all the Discoverer server sessions that are currently running on the server. It includes the following information: session ID, OS Process ID, Discoverer UI component (that is, Discoverer Plus, Discoverer Viewer, or Discoverer Portlet Provider) that created the session, memory usage of the session, CPU usage for the session, database and EUL to which the session is connected, and, if Single Sign-On (SSO) is enabled, the SSO user using the session.

Component Type

This metric indicates the Discoverer UI component that started the Discoverer Plus, Discoverer Viewer or Discoverer Portlet Provider session.

CPU Usage (%)

This metric specifies the percentage of CPU used for all the Discoverer sessions.

DBUser@DB - EUL

This metric specifies the database user, the database, and the EUL to which the session is connected. The format is databaseuser@database - EUL.

Memory Usage (MB)

This metric specifies the memory used (in megabytes) for all the Discoverer sessions.

OS Process ID

This metric indicates the operating system process ID for the given session.

SSO User

If Single Sign-On (SSO) is enabled for Discoverer, this column identifies the SSO user that is using the current session. Information about the SSO user is meaningful only for Discoverer Plus and Discoverer Viewer because SSO users work in Plus and Viewer sessions interactively. For Discoverer Portlet Provider, information about the SSO user might not be meaningful because Discoverer Portlet Provider runs queries in the background, and a query could run as a given SSO user even when that SSO user is not currently logged in.

Total Number Of Discoverer Plus Sessions

This metric displays the total number of sessions created by Discoverer Plus at any given time on the machine.

Total Number Of Discoverer Plus Sessions

This metric specifies the total number of sessions created by Discoverer Plus at any given time on the machine.

Total Number Of Discoverer Portlet Provider Sessions

This metric displays the total number of sessions created by Discoverer Portlet Provider at any given time on the machine.

Total Number Of Discoverer Portlet Provider Sessions

This metric specifies the total number of sessions created by Discoverer Portlet Provider at any given time on the machine.

Total Number Of Discoverer Sessions

This metric displays the total number of Discoverer sessions running on the machine at a given time.

Total Number Of Discoverer Sessions

This metric specifies the total number of Discoverer sessions running on the machine at a given time.

Total Number Of Discoverer Viewer Sessions

This metric displays the total number of sessions created by Discoverer Viewer at any given time on the machine.

Total Number Of Discoverer Viewer Sessions

This metric specifies the total number of sessions created by Discoverer Viewer at any given time on the machine.

Discoverer Viewer Sessions

This metric displays information about all the Discoverer sessions created by Discoverer Viewer. The information included for each session is the session ID, OS Process ID, memory usage of the session, CPU usage for the session, database and EUL to which the session is connected, and, if SSO is enabled, the SSO user using the session.

Component Type

This metric specifies the Discoverer UI component that started the Discoverer Plus, Discoverer Viewer or Discoverer Portlet Provider session.

CPU Usage (%)

This metric specifies the percentage CPU usage for this session.

DBUser@DB - EUL

This metric specifies the database user, database name, and EUL for this session.

Memory Usage (MB)

This metric specifies the memory used (in megabytes) for this session.

OS Process ID

This metric specifies the operating system process ID for this session.

SSO User

If Single Sign-On (SSO) is enabled for Discoverer, this column identifies the SSO user that is using the current session. Information about the SSO user is meaningful only for Discoverer Plus and Discoverer Viewer because SSO users work in Plus and Viewer sessions interactively. For Discoverer Portlet Provider, information about the SSO user might not be meaningful because Discoverer Portlet Provider runs queries in the background, and a query could run as a given SSO user even when that SSO user is not currently logged in.

Response

This metric displays information that indicates whether Discoverer is up or down.

UpDown Status

This metric displays information that indicates whether Discoverer is up or down.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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

0

1

The Discoverer instance is down

11 Reports Bridge

This chapter describes Oracle Reports Bridge metrics.

Log Message Alerts

This category provides information about log message alerts.

Log Monitoring Rules

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

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)

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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)

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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)

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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)

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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)

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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)

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

User Action

No action required.

Name

This metric specifies the name of the remote element.

User Action

No action required.

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

User Action

No action required.

Resource Usage

This category provides information about resource usage metrics.

CPU Usage (%)

This metric specifies the percentage of CPU usage.

Memory Usage (MB)

This metric specifies the memory used (in megabytes).

Memory Usage (%)

This metric specifies the percentage of total memory used.

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

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

User Action

No action required.

Total No of Connections Processed

This metric specifies the total number of connections processed by the Adapter.

User Action

No action required.

Total No of Connections Reused

This metric specifies the total number of connections reused by the Adapter.

User Action

No action required.

Enabled

This metric specifies if the Adapter is enabled or disabled.

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.

User Action

No action required.

Total No of Operation Binds

This metric specifies the total number of bind operations by a particular Adapter.

User Action

No action required.

Operations Count

Specifies the total number of all operations performed by this particular Adapter.

User Action

No action required.

Delete Operations

This metric specifies the total number of delete operations performed by a particular Adapter since last collection.

User Action

No action required.

Operational Version

This metric specifies the operational version of Adapters.

User Action

No action required.

Modify Operations

This metric specifies the total number of Modify operations performed by a particular Adapter since last collection.

User Action

No action required.

Total No of Operations Renamed

This metric specifies the total number of operations renamed by a particular Adapter.

User Action

No action required.

Search Operations

This metric specifies the total number of Search operations performed by a particular Adapter since last collection.

User Action

No action required.

Provisioned version

This metric specifies the Processed version of Adapters.

User Action

No action required.

Type

This metric specifies the type of the Adapter.

User Action

No action required.

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.

User Action

No action required.

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.

User Action

No action required.

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.

User Action

No action required.

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.

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.

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.

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.

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.

User Action

No action required.

CPU Idle Time (%)

This metric specifies the percentage of the CPU Idle Time on the Oracle Virtual Directory Host.

User Action

No action required.

Other CPU Usage (%)

This metric specifies the percentage of the CPU that components other than Oracle Virtual Directory are using.

User Action

No action required.

Heap Usage (MB)

This metric specifies the JVM Heap Usage of the Oracle Virtual Directory Server.

User Action

No action required.

Memory Usage (MB)

This metric specifies the Memory Consumed (in MB) by Oracle Virtual Directory.

User Action

No action required.

Free Memory (MB)

This metric specifies the amount of Free Memory on the Oracle Virtual Directory Server Host.

User Action

No action required.

Other Memory Usage (MB)

This metric specifies the Memory Consumed (in MB) by components other than Oracle Virtual Directory.

User Action

No action required.

Total Memory (MB)

This metric specifies the Total Available Memory on the Oracle Virtual Directory Server Host.

User Action

No action required.

Memory Usage (%)

This metric specifies the percentage of Memory Consumed by the Oracle Virtual Directory Server.

User Action

No action required.

Free Memory (%)

This metric specifies the percentage of Free Memory on the Oracle Virtual Directory Server Host.

User Action

No action required.

Other Memory Usage (%)

This metric specifies the percentage of Memory Consumed by components other than the Oracle Virtual Directory Server.

User Action

No action required.

Start Time (ms since Epoch)

This metric specifies the start time (milliseconds since Epoch) of the Oracle Virtual Directory Server.

User Action

No action required.

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.

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

User Action

No action required.

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.

User Action

No action required.

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.

User Action

No action required.

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.

User Action

No action required.

Number of LDAP Add Requests

This metric specifies the Number of LDAP Add Requests since the last collection.

User Action

No action required.

Number of LDAP Binds Requests

This metric specifies the Number of LDAP Bind Requests since the last collection.

User Action

No action required.

Number of LDAP Delete Requests

This metric specifies the Number of LDAP Delete Requests since the last collection.

User Action

No action required.

Number of LDAP Modify Requests

This metric specifies the Number of LDAP Modify Requests since the last collection.

User Action

No action required.

Number of LDAP Rename Requests

This metric specifies the Number of LDAP Rename Requests since the last collection.

User Action

No action required.

Number of LDAP Search Requests

This metric specifies the Number of LDAP Search Requests since the last collection.

User Action

No action required.

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.

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.

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.

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.

User Action

No action required.

13 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

User Action

Specific to your site.

Date and Time Stamp

Shows the date and time stamp (in UTC) of the metric collection.

User Action

Specific to your site.

Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

User Action

Specific to your site.

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.

User Action

Specific to your site.

Failed Bind Operations

The metric value specifies the number of unsuccessful LDAP bind operations performed by a user

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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

Critical General Sys Resource Event Type

Type of general system resource event.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 10 Minutes

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

User Action

Specific to your site.

Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

User Action

Specific to your site.

Server Load

Shows the number of LDAP operations in progress in the Oracle Internet Directory server at the end of the metric collection period.

User Action

Specific to your site.

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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

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

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.

Instance Number

The instance number of this Oracle Internet Directory server instance.

Messaging Search Operation Response Time

The metric value shows the average messaging search response time

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is 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

User Action

Specific to your site.

Total Memory Usage (KB)

Provides information about total virtual memory used by Oracle Internet Directory servers.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

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

User Action

Specific to your site.

Total Memory Usage (%)

Provides information about percent total virtual memory used by Oracle Internet Directory servers.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

User Action

None.

Host Name

Shows the host name of a running Oracle Internet Directory instance.

User Action

None.

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.

User Action

None.

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.

User Action

Specific to your site.

Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

User Action

Specific to your site.

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.

User Action

Specific to your site.

System's Total Free Physical Memory (KB)

Shows, in kilobytes, the free physical system memory at the end of metric collection period.

User Action

Specific to your site.

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

User Action

Specific to your site.

Number of Event Occurrence

The number of occurrences of this event

Event Name

Shows the name of the event that occurred.

User Action

Specific to your site.

Instance Number

Shows the instance number of the Oracle Internet Directory server for which this metric is collected.

User Action

Specific to your site.

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.

(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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

User Action

Specific to your site.

Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

User Action

Specific to your site.

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.

User Action

Specific to your site.

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is 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.

User Action

Specific to your site.

Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

User Action

Specific to your site.

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.

User Action

Specific to your site.

Completed Bind Operations

Shows the total number of LDAP bind operations completed by the Oracle Internet Directory server instance during metric collection.

User Action

Specific to your site.

Completed Compare Operations

Shows the total number of LDAP compare operations completed by the Oracle Internet Directory server instance during metric collection.

User Action

Specific to your site.

Completed Delete Operations

Shows the total number of LDAP delete operations completed by the Oracle Internet Directory server instance during metric collection.

User Action

Specific to your site.

Completed Modify Operations

Shows the total number of LDAP modify operations completed by the Oracle Internet Directory server instance during metric collection.

User Action

Specific to your site.

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.

User Action

Specific to your site.

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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

User Action

Specific to your site.

Last Applied Change Number

Shows the last changenumber in Oracle Internet Directory that was successfully synchronized and propagated to the other end.

User Action

Specific to your site.

Execution Errors

Shows the last error that was encountered (if any) during the execution of the integration profile.

User Action

Specific to your site.

State

Shows the state of the integration profile (ENABLED / DISABLED).

User Action

Specific to your site.

Execution Status

Shows the current execution status of the integration profile.

User Action

Specific to your site.

Schedule (secs)

Shows the scheduling interval of the integration profiles. The Directory Integration Platform server executes the profiles using this scheduling interval.

User Action

Specific to your site.

Type

Shows the type of the integration profile (synchronization or provisioning).

User Action

Specific to your site.

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.

User Action

Specific to your site.

Directory Integration Server Host

Shows the machine on which this Directory Integration Platform server is running.

User Action

Specific to your site.

Start Time

Shows the time when this Directory Integration Platform server started.

User Action

Specific to your site.

LDAP Server

Shows the Oracle Internet Directory server against which this Directory Integration Platform server is running.

User Action

Specific to your site.

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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

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

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.

User Action

Specific to your site.

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.

User Action

None.

Start Time

Shows the time when the instance of the directory replication server was first started.

User Action

None.

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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:

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

2. 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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:

1. There are many change logs to apply and updateschedule is set to 0 (immediate processing). Consider increasing updateschedule to 1 or 2.

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:

1. The attributes orclreplmaxworkerthread, orclthreadspersupplier;apply, and orclthreadspersupplier;transport are set inappropriately high. Consider decreasing these values. Also consider setting replautotune to 1.

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

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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:

1. There are many change logs to apply and updateschedule is set to 0 (immediate processing). Consider increasing updateschedule to 1 or 2.

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:

1. The attributes orclreplmaxworkerthread, orclthreadspersupplier;apply, and orclthreadspersupplier;transport are set inappropriately high. Consider decreasing these values. Also consider setting replautotune to 1.

2. 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:

1. Change logs are not being retried a sufficient number of times. Consider increasing orclchangeretrycount to 4-10.

2. HIQ change log processing is too slow because orclhiqschedule is set too high. Consider setting orclhiqschedule lower.

3: 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

User Action

Specific to your site.

Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

User Action

Specific to your site.

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

User Action

None.

Host Name

Shows the host name of the stopped instance.

User Action

None.

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 occured in Oracle Internet Directory servers.

Event Time

Shows the date and time stamp (in UTC) of the event occurence.

User Action

Specific to your site.

Event Result

Shows the result--that is, either success or failure--of the event that occured.

User Action

Specific to your site.

Event Name

Shows the name of the event that occured.

User Action

Specific to your site.

Instance Number

Shows the instance number of the Oracle Internet Directory server instance for which this metric is collected.

User Action

Specific to your site.

Process ID

Shows the process identifier for the Oracle Internet Directory server instance for which this metric is collected.

User Action

Specific to your site.

User DN

Shows the identity of the user who logged into Oracle Internet Directory server and performed the operation that triggered the event.

User Action

Specific to your site.

(Critical Event)Super User Failed Logins

This metric provides information about failed super user logins that occured in Oracle Internet Directory servers.

Failed LDAP Super User Login

The number of successful super user logins that occured in Oracle Internet Directory servers.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 occured in Oracle Internet Directory servers.

Successful LDAP Super User Login

The number of successful super user logins that occured in Oracle Internet Directory servers.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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

Total Number of Tombstone Objects in Purge Queue

The metric value specifies the number of objects in the tombstone purge queue

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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

Failed Add Operations

The metric value specifies the number of unsuccessful LDAP add operations performed by a user.

Failed Base Search Operations

The metric value specifies the number of unsuccessful LDAP base search operations performed by a user

Failed Bind Operations

The metric value specifies the number of unsuccessful LDAP bind operations performed by a user

Failed Compare Operations

The metric value specifies the number of unsuccessful LDAP compare operations performed by a user

Failed Delete Operations

The metric value specifies the number of unsuccessful LDAP delete operations performed by a user.

Failed Modify Operations

The metric value specifies the number of unsuccessful LDAP modify operations performed by a user.

Failed ModRdn Operations

The metric value specifies the number of unsuccessful LDAP ModRdn operations performed by a user.

Failed OneLevel Search Operations

The metric value specifies the number of unsuccessful LDAP OneLevel Search operations performed by a user.

Failed Proxy Bind Operations

The metric value specifies the number of unsuccessful LDAP proxy bind operations performed by a user

Failed Subtree Search Operations

The metric value specifies the number of unsuccessful LDAP Subtree Search operations performed by a user.

Successful Add Operations

The metric value specifies the number of successful LDAP add operations performed by a user.

Successful Base Search Operations

The metric value specifies the number of successful LDAP base search operations performed by a user

Successful Bind Operations

The metric value specifies the number of successful LDAP bind operations performed by a user

Successful Compare Operations

The metric value specifies the number of successful LDAP compare operations performed by a user

Successful Delete Operations

The metric value specifies the number of successful LDAP delete operations performed by a user.

Successful Modify Operations

The metric value specifies the number of successful LDAP modify operations performed by a user.

Successful ModRdn Operations

The metric value specifies the number of successful LDAP ModRdn operations performed by a user.

Successful OneLevel Search Operations

The metric value specifies the number of successful LDAP OneLevel Search operations performed by a user.

Successful Proxy Bind Operations

The metric value specifies the number of successful LDAP proxy bind operations performed by a user

Successful Subtree Search Operations

The metric value specifies the number of successful LDAP Subtree Search operations performed by a user.

Unbind Operations

The metric value specifies the number of LDAP unbind operations performed by a user

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

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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

Check if the DIP application has started in the Weblogic server.

Name

This metric specifies the internal name of the DIP application.

Metric Summary

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

11Plus

Every 15 Minutes

User Action

Check if the DIP application has started in the Weblogic server.

WLS Server Name

This metric specifies the WebLogic server name.

Metric Summary

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 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 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 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 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 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 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 (%)

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

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 (%)

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

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

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

15 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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 group space metrics apply.

Metric Summary

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.

Successful Invocations (%)

This metric indicates the percentage of group space invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count. All group 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 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 group space metric page where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Group Space Metrics.

You can also check the diagnostic logs to establish why group space invocations are failing.

Invocations (per minute)

This metric indicates the number of group space invocations per minute.

All group spaces in the WebCenter application are included in this count. The number of invocations per group space is available on application's group 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 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 group spaces is high (compared with other WebCenter services), consider prioritizing troubleshooting efforts in this area.

See also, Analyzing Group Space Metrics.

Page Throughput (per minute)

This metric shows the average number of pages accessed per minute.

All group 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 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 group spaces. You can evaluate when pages are accessed the most, as well as the maximum and minimum usage.

See also, Analyzing Group Space Metrics.

Average Page Processing Time (ms)

This metric indicates the average time (in ms) spent processing group space operations.

All group spaces in the WebCenter application are included in the count. Processing times for individual group 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 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 group space operations.

If this metric is out-of-bounds (the average time for group space operations is increasing or higher than expected), navigate to the application's group space metric page where more detailed metric data for individual group spaces is available.

See also, Analyzing Group Space Metrics.

Service Name

These metrics apply to the WebCenter group space.

Metric Summary

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

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

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

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

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

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 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 content repository-related operations.

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.

Service Name

These metrics apply to content repositories used by the Documents service.

Metric Summary

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 these Group Space and Personal Events service metrics apply.

Metric Summary

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.

Successful Invocations (%)

This metric indicates the percentage of Group Space and Personal 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 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.

Invocations (per minute)

This metric indicates the total number of invocations per minute for the Group Space and Personal Events services.

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 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 Group Space and Personal Events services 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.

Average Processing Time (ms)

This metric indicates the average time the Group Space Events service and the Personal Events service spends processing events operations (in ms).

Group Space Events and Personal 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 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 Group Space Events and Personal Events service operations. If this metric is out-of-bounds (the average time for Group Space Events and Personal 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.

Service Name

These metrics apply to group space events and personal events used by the WebCenter application.

Metric Summary

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

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

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

Page Throughput (per minute)

This metric shows the average number of pages accessed per minute.

All pages in the WebCenter application are included in this count.

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

Service Name

These metrics apply to the External Applications service.

Metric Summary

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 Pages (Aggregated)

Provides information about the WebCenter Spaces Pages (Aggregated) metrics.

Application Name

This metric identifies the WebCenter application to which these portlet metrics apply.

Metric Summary

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.

Successful Invocations (%)

All portlets used in the WebCenter application are included in this count.

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

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

Page Throughput (per minute)

This metric shows the average number of pages accessed per minute.

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

Average Page Processing Time (ms)

This metric indicates the average time (in ms) to display the page.

All pages in the WebCenter application are included in the count. Processing times for individual pages are available on application's main metric page. See Monitoring Page Metrics for Spaces and Monitoring Page Metrics for WebCenter Portal Applications.

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

Service Name

These metrics apply to the WebCenter Spaces page.

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

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

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

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

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

Service Name

These metrics apply to WebCenter portlets.

Metric Summary

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

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

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

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

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

Service Name

These metrics apply to the portlet producers used by the WebCenter application.

Metric Summary

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

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, Group Spaces, Group Space 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 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.

Invocations (per minute)

This metric indicates the total number of Search service invocations per minute across all WebCenter search sources: Announcements, Documents, Discussion Forums, Group Spaces, Group Space 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 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.

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, Group Spaces, Group Space 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 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.

Service Name

These metrics apply to the Search service.

Metric Summary

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

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

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

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

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

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

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

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

Service Name

These metrics apply to the Worklists service.

Metric Summary

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All versions

Every 300 seconds

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

Average HTTP 2xx Time (ms)

This metric indicates the average time the portlet takes to process requests returning a HTTP2xx 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 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 performing 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.

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

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

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 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 (Top 5)

Provides information about the WebCenter Portlets (Top 5) metrics.

Application Name

This metric identifies the WebCenter application to which these portlet metrics apply.

Metric Summary

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.

Successful Invocations (%)

This metric indicates the percentage of portlet invocations that succeeded.

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.

This portlet is one of the top five, most popular portlets 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

User Action

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.

Average HTTP 2xx Time (ms)

This metric indicates the average time the portlet takes to process requests returning a HTTP2xx response code (in ms).

This portlet is one of the top five, most popular portlets in this WebCenter application.

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 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 performance of popular portlets.

If this metric is out-of-bounds, consider prioritizing troubleshooting efforts for the most popular portlets. Navigate to the application's main metric page where additional 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 the portlet.

This portlet is one of the top five, most popular portlets in this WebCenter application. 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 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), start by troubleshooting this portlet.

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 (in ms) spent processing operations for portlet.

This portlet is one of the top five, most popular portlets in this WebCenter application. 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 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 popular portlets.

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.

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

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

Average HTTP 2xx Time (ms)

This metric indicates the average time that all portlets from this producer take to process requests returning a HTTP2xx 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 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 performing 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.

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

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

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 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 (Top 5)

Provides information about the WebCenter Producers (Top 5) metrics.

Application Name

This metric identifies the WebCenter application to which these portlet producer metrics apply.

Metric Summary

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.

Successful Invocations (%)

This metric indicates the percentage of producer invocations that succeeded.

Description

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

This producer is one of the top five, most popular producers in this WebCenter application.

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

Average HTTP 2xx Time (ms)

This metric indicates the average time that all portlets from this producer take to process requests returning a HTTP2xx response code (in ms).

This producer is one of the top five, most popular producers in this WebCenter application.

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 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 performance of popular producers.

If this metric is out-of-bounds, consider prioritizing troubleshooting efforts for the most popular producers. Navigate to the application's main metric page where additional 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 this producer.

This producer is one of the top five, most popular producers in this WebCenter application.

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 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 total number of invocations per minute for this producer is high (compared with other producers), consider prioritizing troubleshooting efforts in this area. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

Average Processing Time (ms)

This metric indicates the average time (in ms) spent processing operations for this producer. Maximum processing times for individual HTTP request types are also available on the application's main metric page. See, Viewing Performance Information.

This producer is one of the top five, most popular producers 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 that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

Metric Summary

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 top five 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.

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

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

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

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

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

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

Service Name

These metrics apply to the Announcements service.

Metric Summary

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

Metric Summary

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.

Successful Invocations (%)

This metric indicates the percentage of group 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 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 group space metric page where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

Invocations (per minute)

This metric indicates the number of group space invocations per minute.

The number of invocations for this group space is available on application's group 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 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 group space is high (compared with other group spaces), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's group space metric page where more detailed metric data is available. See, Monitoring WebCenter Spaces Information</</a>.

See also,Analyzing Group Space Metrics.

Page Throughput (per minute)

This metric shows the average number of pages accessed per minute for the group 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 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 group space. You can evaluate when pages are accessed the most, as well as the maximum and minimum usage.

See also, Analyzing Group Space Metrics.

Average Page Processing Time (ms)

This metric indicates the average time spent processing operations for a particular group 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 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 group space.

If this metric is out-of-bounds (the average time for group 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 Group Space Metrics.

WebCenter Spaces (Top 5)

Provides information about WebCenter Spaces (Top 5) metrics.

Application Name

This metric identifies the WebCenter application to which these group space metrics apply.

Metric Summary

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.

Successful Invocations (%)

This metric indicates the percentage of group space invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

This group space is one of the top five, most popular group spaces 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 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 group space metric page where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Group Space Metrics.

You can also check the diagnostic logs to establish why group space invocations are failing.

Invocations (per minute)

This metric indicates the total number of group space invocations per minute for a single group space. This group space is one of the top five, most popular group spaces in this WebCenter application.

The number of invocations for this group space is available on application's main 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 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 group space is high (compared with other group spaces), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's group space metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Group Space Metrics.

Page Throughput (per minute)

This metric shows the average number of pages accessed per minute for the group space. This group space is one of the top five, most popular group spaces 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 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 group space. You can evaluate when pages are accessed the most, as well as the maximum and minimum usage.

See also, Analyzing Group Space Metrics.

Average Page Processing Time (ms)

This metric indicates the average time (in ms) spent processing operations for the group space.

This group space is one of the top five, most popular group spaces in this WebCenter application. Processing times for all group spaces is available on application's group space 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 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 five most popular group spaces.

If this metric is out-of-bounds (the average time for group space operations is increasing or higher than expected), navigate to the application's group space metric page where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Group 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 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.

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

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 Content Presenter 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.

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.

Total Get Item Time (ms)

This metric indicates the total time spent selecting and displaying items, such as a document or image, in Content Presenter task flows.

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 time spent on 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 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.

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 Content Presenter 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.

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.

Total List Folder Time (ms)

This metric indicates the total time Content Presenter task flows spend listing folders stored in a content repository.

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 time spent listing folders in Content Presenter task flows 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.

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

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

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

WebCenter Events

Provides information about the WebCenter events metrics.

Application Name

This metric identifies the WebCenter application to which these Group Space Events or Personal Events service metrics apply.

Metric Summary

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.

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 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 group space events and personal events. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

Invocations (per minute)

This metric indicates the total number of invocations per minute for the Group Space Events or Personal Events service.

The number of invocations per operation for both group space and personal 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 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 Group Space Events service or the Personal 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.

Average Processing Time (ms)

This metric indicates the average time the Events service spends processing operations (in ms) associated with group space events or personal 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 both group space and personal 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 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 both group space and personal events. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

WebCenter External Applications

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 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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Name

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

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

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

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

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

Service Name

These metrics apply to the Discussions service.

Metric Summary

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 Pages

Provides information about WebCenter spaces pages metrics.

Application Name

This metric identifies the WebCenter application to which these page metrics apply.

User Action

No action required.

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

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 Portal Applications.

You can also check the diagnostic logs to establish why page invocations are failing.

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

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

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 Portal Applications.

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

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

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 Portal Applications.

WebCenter Spaces Pages (Top 5)

Provides information about WebCenter spaces pages (Top 5) metrics

Application Name

This metric identifies the WebCenter application to which these page metrics apply.

User Action

No action required.

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.

This page is one of the top five, most popular pages 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).

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 Portal Applications.

You can also check the diagnostic logs to establish why page invocations are failing.

Invocations (per minute)

This metric indicates the total number of page invocations per minute. This page is one of the top five, most popular pages in this WebCenter application.

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

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 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 Portal Applications.

Page Throughput (per minute)

This metric shows the average number of pages accessed per minute. This page is one of the top five, most popular pages 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).

User Action

Use this metric to monitor typical and peak usage of the page. You can evaluate when pages are accessed the most, as well as the maximum and minimum usage.

Average Page Processing Time (ms)

This metric indicates the average time (in ms) to display the page.

This page is one of the top five, most popular pages in this WebCenter application. Processing times for all pages is available on application's page metric page. See, Monitoring Page Metrics for Spaces and Monitoring Page Metrics for WebCenter Portal Applications.

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

User Action

Use this metric to determine the performance of the five most popular pages.

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 Portal Applications.

WebCenter Import/Export

Provides information about WebCenter Import/Export metrics.

Application Name

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

Target Version

Collection Frequency

All Versions

Every 300 Seconds

Service Name

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

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

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

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

Service Name

These metrics apply to the Lists service.

Metric Summary

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

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

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

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

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

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

Service Name

These metrics apply to the Mail service.

Metric Summary

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

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

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

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

Service Name

These metrics apply to the Notes service.

Metric Summary

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

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

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

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

Service Name

These metrics apply to the Page service.

Metric Summary

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.

User Action

No action required.

Successful Invocations (%)

This metric indicates the percentage of People Connection 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).

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.

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

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.

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

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.

Service Name

These metrics apply to the People Connections service.

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.

User Action

No action required.

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

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

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.

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

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.

Service Name

These metrics apply to the Polls service.

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

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

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

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

Service Name

These metrics apply to the Recent Activities service.

Metric Summary

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

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

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

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

Service Name

These metrics apply to the RSS service.

Metric Summary

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

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

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

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

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

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

Service Name

These metrics apply to the Instant Messaging and Presence (IMP) service.

Metric Summary

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

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 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, Group Spaces, Group Space 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 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.

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, Group Spaces, Group Space 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 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 Search (Top 5)

Provides information about the WebCenter Search (Top 5) metrics.

Application Name

This metric identifies the WebCenter application to which these Search service metrics apply.

Metric Summary

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.

Successful Invocations (%)

This metric indicates the percentage of Search service invocations that succeeded. This search source is one of the top five most popular search sources in this WebCenter application.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

WebCenter search sources include data associated with: Announcements, Documents, Discussion Forums, Group Spaces, Group Space Events, Lists, Notes, Oracle Secure Enterprise Search, Pages, Wikis and Blogs, People Connections, 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 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 the 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.

Invocations (per minute)

This metric indicates the total number of Search service invocations per minute for a single search source. This search source is one of the top five most popular search sources in this WebCenter application.

WebCenter search sources include data associated with: Announcements, Documents, Discussion Forums, Group Spaces, Group Space 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 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.

Average Processing Time (ms)

This metric indicates the average time (in ms) the Search service spends processing search operations for a single search source. This search source is one of the top five, most popular search sources in this WebCenter application.

WebCenter search sources include data associated with: Announcements, Documents, Discussion Forums, Group Spaces, Group Space 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 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 search performance for the five most popular search sources.

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 all search sources 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 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.

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

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

Request Processing Time (milli seconds)

This metric specifies the average number of seconds used to process a request during the current time period.

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.

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 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 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 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Other Memory Usage (MB)

Metric Summary

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

Memory Usage (%)

This metric specifies the percentage of total memory that is being utilized for cache memory.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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

Other Memory Usage (%)

Percent of memory used by processes other than Oracle Web Cache.

Metric Summary

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

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.

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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 following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version

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.

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.

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.

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.

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.

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.

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.

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.

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.

Load.value

This metric specifies the current number of connections from Oracle Web Cache that the origin server has open.

MaxLoad.value

The metric specifies the maximum number of connections that the origin server has had open at one time.

Port.value

The information metric specifies the port number from which the origin server is listening for Oracle Web Cache requests.

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.

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.

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.

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.

17 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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Open Reports

Number of reports open in the Report Server.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Open Viewsets

Number of open viewsets in the Report Server.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Activity Message Rate (per sec)

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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.

User Action

No action required.

18 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, and so on).

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Deletes Per Second

Rate of delete operations on the data object in the last 5 minutes.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Inserts Per Second

Rate of insert operations on the data object in the last 5 minutes.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Updates Per Second

Rate of update operations on the data object in the last 5 minutes.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Upserts Per Second

Rate of upsert operations on the data object in the last 5 minutes.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Current Insert Batch Size

Average number of rows in the insert batch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Current Update Batch Size

Average number of rows in the update batch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Current Upsert Batch Size

Average number of rows in the upsert batch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Current Update Batch Size

Average number of rows in the update batch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Current Insert Batch Size

Average number of rows in the insert batch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Current Delete Batch Size

Average number of rows in the delete batch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Current Upsert Batch Size

Average number of rows in the upsert batch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Current Delete Batch Size

Number of active viewsets.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Current Delete Batch Size

Number of all of the active viewsets.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Current Insert Batch Size

Number of all of the open viewsets.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Current Insert Batch Size

Number of open viewsets.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Completed Transactions

Number of completed transactions on Oracle BAM data objects.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Open Transaction

Number of open transactions on Oracle BAM data objects.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Delete operations rate.

Number of successful delete operations per second in the last 5 minutes.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Insert operations rate.

Number of successful insert operations per second in the last 5 minutes.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Update operations rate.

Number of successful update operations per second in the last 5 minutes.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Upsert operations rate.

Number of successful upsert operations per second in the last 5 minutes.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Action Queue Size

Number of Oracle BAM Event Engine actions waiting to be processed.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Alert History Queue Size

Number of alert history items to be saved.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Rule Fire Queue Size

Number of events fired waiting to be processed.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Active Data Sessions

Total number of sessions with active data.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

File Count

Total number of files currently managed by FileBasedPersistenceManager.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Element Count

Total number of elements currently managed by InMemoryPersistenceManager.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Viewset Average Open Time (in sec)

Average time period in seconds to open a view set.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

User Action

No action required.

Open Viewsets

Total number of viewsets opened by the Report Cache.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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 following table shows how often the metric's value is collected.

Target Version

Collection Frequency

All Versions

Every 300 Hours

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

To start or stop the Oracle BAM Server, use the Start Up and Shut Down controls in the Oracle BAM Server menu.

Index

A  T

A

alerts

as polling-based, Preface

definition, Preface

T

thresholds

defining, Preface

definition of, Preface

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