Oracle Enterprise Manager Framework, Host, and Services Metric Reference Manual 12c Release 1 (12.1.0.2.0)

12c Release 1 (12.1.0.2.0)

E25162-03

Contents

Title and Copyright Information

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

How to Use This Manual

- Structure of This Manual

- Background Information on Metrics, Thresholds, and Alerts

- Troubleshooting Metrics

1 Agent

- Agent Process Statistics

- Agent Resident Memory Utilization (KB)

- Agent Virtual Memory Utilization (KB)

- CPU Usage (%)

- Number Files Open

- Number Handles Open

- Number Threads Created

- Process ID

- Resident Memory Utilization (%)

- Resident Memory Utilization (KB)

- Schedule Attempts Percentage

- Virtual Memory Utilization (KB)

- Virtual Memory Utilization Growth (%)

- Response

- Nmo Setuid Status

- Status

- Targets not uploading

- Upload Statistics

- Count of targets not uploading data

- Number of Files to Upload

- Size of Files to Upload (MB)

- Upload Rate (KB/sec)

- User Identification

- Group Name

- Location

- Other Groups

- User Name

- User Limit Info

- CoreDump (blocks)

- Data (kbytes)

- File (blocks)

- NoFiles (descriptors)

- Stack (kbytes)

- Time (seconds)

- Virtual Mem (kbytes)

2 Host

- Aggregate Resource Usage Statistics (By Project)

- Cumulative CPU Wait Time (Seconds)

- Cumulative Data Page Fault Sleep Time (Seconds)

- Cumulative Major Page Faults

- Cumulative Minor Page Faults

- Cumulative Number Character IO (bytes) Read and Written

- Cumulative Number Of Blocks Read

- Cumulative Number Of Blocks Written

- Cumulative Number of Involuntary Context Switches

- Cumulative Number Of Messages Received

- Cumulative Number Of Messages Sent

- Cumulative Number of Signals Received

- Cumulative Number of System Calls Made

- Cumulative Number of Voluntary Context Switches

- Cumulative Project Lock-Wait Sleep Time (Seconds)

- Cumulative Project Other Sleep Time (Seconds)

- Cumulative Stop Time (Seconds)

- Cumulative Swap Operations

- Cumulative System Mode Time (seconds)

- Cumulative System Page Fault Sleep Time (Seconds)

- Cumulative System Trap Time (seconds)

- Cumulative Text Page Fault Sleep Time (Seconds)

- Cumulative User Mode Time (seconds)

- Number of Processes Owned by Project

- Project CPU Time (%)

- Project Process Memory Size (%)

- Project's Total Process Heap Size (KiloBytes)

- Project's Total Process Resident Set Size (KiloBytes)

- Project's Total Process Virtual Memory Size (KiloBytes)

- Total Number of Threads in Project's Processes

- Aggregate Resource Usage Statistics (By User)

- Cumulative CPU Wait Time (Seconds)

- Cumulative Data Page Fault Sleep Time (Seconds)

- Cumulative Major Page Faults

- Cumulative Minor Page Faults

- Cumulative Number Character IO (bytes) Read and Written

- Cumulative Number Of Blocks Read

- Cumulative Number Of Blocks Written

- Cumulative Number of Involuntary Context Switches

- Cumulative Number Of Messages Received

- Cumulative Number Of Messages Sent

- Cumulative Number of Signals Received

- Cumulative Number of System Calls Made

- Cumulative Number of Voluntary Context Switches

- Cumulative Stop Time (Seconds)

- Cumulative System Mode Time (seconds)

- Cumulative System Page Fault Sleep Time (Seconds)

- Cumulative System Trap Time (seconds)

- Cumulative Swap Operations

- Cumulative Text Page Fault Sleep Time (Seconds)

- Cumulative User Lock-Wait Sleep Time (Seconds)

- Cumulative User Mode Time (seconds)

- Cumulative User Other Sleep Time (Seconds)

- Number of Processes Owned by User

- Total Number of Threads in User's Processes

- User CPU Time (%)

- User Process Memory Size (%)

- User's Total Process Heap Size (KiloBytes)

- User's Total Process Resident Set Size (KiloBytes)

- User's Total Process Virtual Memory Size (KiloBytes)

- Buffer Activity

- Buffer Cache Read Hit Ratio (%)

- Buffer Cache Reads (per second)

- Buffer Cache Write Hit Ratio (%)

- Buffer Cache Writes (per second)

- Physical I/O Reads (per second)

- Physical I/O Writes (per second)

- Physical Reads (per second)

- Physical Writes (per second)

- CPU Usage

- CPU Idle Time (%)

- CPU Interrupt Time (%)

- CPU System Time (%)

- CPU User Time (%)

- CPU Utilization (%) of a CPU

- CPU Wait Time (%)

- CPUs Details

- ECACHE in MB

- Frequency in MHZ

- Is HyperThread Enabled

- Implementation

- Number of CPUs

- MASK

- Number of Cores per Physical CPU

- Revision

- Number Of Threads Per Physical CPU

- Vendor Name

- Disk Activity

- Average Disk I/O Service Time (ms)

- Average Disk I/O Wait Time (ms)

- Average Outstanding Disk I/O Requests

- Average Run Time (ms)

- Bulk I/O Ticks

- Difference in Number of Reads

- Difference in Number of Writes

- Disk Block Writes (per second)

- Disk Block Reads (per second)

- Disk Device Busy (%)

- Disk Reads (per second)

- Disk Writes (per second)

- Disk Device Errors

- Hard Errors

- Soft Errors

- Total

- Transport Errors

- Fans

- Fan Status

- Location

- File Access System Calls

- Blocks Read by Directory Search Routine (per second)

- iget() Calls (per second)

- lookuppn() Calls (per second)

- File and Directory Monitoring

- File or Directory Attribute Not Found

- File or Directory Permissions

- File or Directory Size (MB)

- File or Directory Size Change Rate (KB/minute)

- Filesystems

- Filesystem

- Filesystem Size (MB)

- Filesystem Space Available (%)

- Filesystem Utilization (MB)

- Kernel Memory

- Failed Requests for Large Kernel Memory

- Failed Requests for Oversize Kernel Memory

- Failed Requests for Small Kernel Memory

- KMA Available for Large Memory Requests (Bytes)

- KMA for Oversize Memory Requests (Bytes)

- KMA for Small Memory Requests

- Memory Allocated for Large Memory Requests (Bytes)

- Memory Allocated for Small Memory Requests (Bytes)

- Load

- CPU in I/O Wait (%)

- CPU in System Mode (%)

- CPU in User Mode (%)

- CPU Interrupt Time (%)

- CPU Queue Length

- CPU Utilization (%)

- Free Logical Memory (%)

- Free Memory (%)

- Longest Service Time (ms)

- Memory Page Scan Rate (per second)

- Memory Utilization (%)

- Page Transfers Rate

- Run Queue Length (1 minute average)

- Run Queue Length (5 minute average)

- Run Queue Length (15 minute average)

- Swap Utilization (%)

- Total Disk I/O Per Second

- Total Processes

- Total Swap, Kilobytes

- Total Users

- Used Swap, Kilobytes

- Log File Monitoring

- Log File Pattern Matched Content

- Log File Pattern Matched Line Count

- Memory Devices

- Bank Location

- Location

- Memory Status

- Size

- Type

- Message and Semaphore Activity

- msgrcv() System Calls (per second)

- semop() System Calls (per second)

- IO Card Details

- Bus Type

- Frequency

- Name

- Revision

- Vendor Name

- Network Interface Count

- BroadCast Address

- Default Gateway

- Description

- Is DHCP Enabled

- Flags

- Hostname Aliases

- IP Address

- IPV6 Addresses

- MAC Address

- NetMask

- Maximum Transfer Unit

- Name

- Network Interface Bonds

- Bond Name

- Mode of the Bond

- Options of the Bond

- Primary Slave

- Secondary Slaves

- Operating System

- Address Length (Bits)

- Base Version

- Is DB Machine Member

- Default OS Run Level

- Distribution Version

- Max Swap Space (MB)

- Name

- Platform ID

- Update Level

- Vendor Name

- Operating System Components

- Description

- Installation Date

- Name

- Type

- Version

- File Systems

- Disk Space (GB)

- Local Drive

- Mount Location

- Mount Options

- Resource Name

- Type

- Operating System Properties

- Name

- Source

- Value

- Operating System Registered Software

- Description

- ID

- Installation Date

- Installed Location

- Media Type

- Name

- Vendor Name

- Vendor Specific Information

- Version

- Virtual Machine

- Parent Product Identifier

- Product Parent Name

- Software Architecture

- Operating System ULIMITS

- CoreDump (blocks)

- Time (seconds)

- Data (kbytes)

- File (blocks)

- NoFiles (descriptors)

- Stack (kbytes)

- Virtual Mem (kbytes)

- Network Interfaces

- Network Interface Collisions (%)

- Network Interface Combined Utilization (%)

- Network Interface Input Errors (%)

- Network Interface Output Errors (%)

- Network Interface Read (MB/s)

- Network Interface Read Utilization (%)

- Network Interface Total Error Rate (%)

- Network Interface Total I/O Rate (MB/sec)

- Network Interface Write (MB/s)

- Network Interface Write Utilization (%)

- Paging Activity

- Address Translation Page Faults (per second)

- Cache Faults (per second)

- Copy-on-write Faults (per second)

- Demand Zero Faults (per second)

- igets with Page Flushes(%)

- Page Faults (per second)

- Page Faults from Software Lock Requests

- Page-in Requests (per second)

- Page-Out Requests (per second)

- Pages Paged-in (per second)

- Pages Paged-out (per second)

- Pages Put on Freelist by Page Stealing Daemon (per second)

- Pages Scanned by Page Stealing Daemon (per second)

- Transition Faults (per second)

- PCI Devices

- Description

- Manufacturer

- PCI Device Status

- Power Supplies

- Location

- Output (Tenths of Watts)

- Power Supply Status

- Processes - Top

- Command and Arguments

- CPU Time for Top Processes

- CPU Utilization for Top Processes (%)

- Memory Utilization for Top Processes (%)

- Physical Memory Utilization (KB)

- Process User ID

- Virtual Memory Utilization (KB)

- Process, Inode, File Tables Statistics

- File Table Overflow Occurrences

- Inode Table Overflow Occurrences

- Maximum Size of Inode Table

- Maximum Size of Process Table

- Maximum Size of System File Table

- Number Of Allocated Disk Quota Entries

- Number Of Queued RT Signals

- Number Of Super Block Handlers Allocated

- Number Of Used File Handles

- Percentage Of Allocated Disk Quota Entries

- Percentage Of Allocated Super Block Handlers

- Percentage Of Queued RT Signals

- Percentage Of Used File Handles

- Process Table Overflow Occurrences

- Size of Inode Table

- Size of Process Table

- Processors

- Family

- Manufacture

- Processor Status

- Speed (MHz)

- Version

- Program Resource Utilization

- List of PIDs

- Program's Max CPU Time Accumulated (Minutes)

- Program's Max CPU Utilization (%)

- Program's Max Process Count

- Program's Max Resident Memory (MB)

- Program's Min Process Count

- Program's Total CPU Time Accumulated (Minutes)

- Program's Total CPU Utilization (%)

- Remote Access Card

- DHCP Settings

- Gateway Address

- IP Address

- LAN Settings

- Network Mask Address

- Product Name

- Remote Access Card State

- Remote Access Card Status

- Version

- Response

- Status

- Storage Summary Metrics

- ASM Storage Allocated (GB)

- ASM Storage Metric Collection Errors

- ASM Storage Overhead (GB)

- ASM Storage Unallocated (GB)

- Databases Storage Free (GB)

- Databases Storage Metric Collection Errors

- Databases Storage Used (GB)

- Disk Storage Allocated (GB)

- Disk Storage Unallocated (GB)

- Host Storage Metric Collection Errors

- Hosts Summarized

- Local File Systems Storage Free (GB)

- Local File Systems Storage Used (GB)

- Number of ASM Instances Summarized

- Number of Databases Summarized

- Other Mapping Errors

- Total Number of ASM Instances

- Total Number of Databases

- Total Storage Allocated (GB)

- Total Storage Free (GB)

- Total Storage Overhead (GB)

- Total Storage Unallocated (GB)

- Total Storage Used (GB)

- Unmonitored NFS Server Mapping Errors

- Volumes Storage Allocated (GB)

- Volumes Storage Overhead (GB)

- Volumes Storage Unallocated (GB)

- Writeable NFS Storage Free (GB)

- Writeable NFS Storage Used (GB)

- Storage Support

- Supported

- Swap Area Status

- Swap Free

- Swap Size

- Switch/Swap Activity

- Process Context Switches (per second)

- Swapins Transfers (per second)

- Swapout Transfers (per second)

- System Swapins (per second)

- System Swapouts (per second)

- System BIOS

- Manufacturer

- Size

- System BIOS Status

- Version

- System Calls

- Characters Transferred by Read System Calls (per second)

- Characters Transferred by Write System Calls (per second)

- exec() System Calls (per second)

- fork() System Calls (per second)

- read() System Calls (per second)

- System Calls (per second)

- write() System Calls (per second)

- Temperature

- Current Temperature

- Location

- Temperature Probe Status

- TTY Activity

- Incoming Character Interrupts (per second)

- Input Characters Processed by canon()

- Modem Interrupt Rate (per second)

- Outgoing Character Interrupts (per second)

- TTY Output Characters (per second)

- TTY Raw Input (chars/s)

- User Defined Metrics

- User Defined Numeric Metric

- User Defined String Metric

- Users

- Number of Logons

- Windows Events Log

- Category

- Date-Time

- Windows Event Log Message

- Event ID

- Windows Event Severity

- Zombie Processes

- % of Processes in Zombie State

- Processes in Zombie State (%)

- Infiniband Network

- Linked Throughput

- Infiniband Switch

- Port Performance

3 OMS and Repository

- Active Loader Status

- Rows Processed in the Last Hour

- Total Loader Runtime in the Last Hour (seconds)

- Active Management Servlets

- Notifications Processed

- Page Hits (per minute)

- Agent Status

- Number of Agent Restarts

- Configuration

- Number of Administrators

- Number of Groups

- Number of Roles

- Number of Targets

- Repository Tablespace Used

- Target Addition Rate (Last Hour)

- Total Repository Tablespace

- User Addition Rate (Last Hour)

- DBMS Job Status

- DBMS Job Invalid Schedule

- DBMS Job Processing Time (% of Last Hour)

- DBMS Job UpDown

- DBMS Job Throughput Per Second

- Incident

- Alert Log Error Trace File

- Alert Log Name

- Diagnostic Incident

- ECID

- Impact

- Incident ID

- Job Dispatcher Performance

- Job Dispatcher Processing Time (% of Last Hour)

- Job Steps Per Second

- Active Agents

- Number of Active Agents

- Repository Collections Performance

- Collection Duration (seconds)

- Collections Processed

- Collections Waiting To Run

- Number of Collection Workers

- Total Throughput Across Collection Workers

- Repository Job Dispatcher

- Job Step Backlog

- Repository Sessions

- Repository Session Count

- Response

- Status

- Service Initialization Errors

- Service Status

4 Oracle Home Metrics

- Bugs Fixed by a Patch

- Bug Number

- Patch ID

- Patch Language

- Patch UPI

- Component Dependency

- Component Name

- Component Version

- Dependee Name

- Dependee Version

- Dependee Home GUID

- Component Install Type

- Component Name

- Component Version

- Name ID

- Description ID

- Install Type Name

- CRS Node list

- Node

- Files affected by a Patch

- Component Name

- Component Version

- File Name

- Patch ID

- Patch Language

- Patch UPI

- Oracle Home Clone Properties

- Property Name

- Property Value

- Oracle Home Components

- Component Name

- Component Version

- Current Version

- Description

- External Name

- Installed Location

- Installer Version

- Install Time

- Is Top Level

- Languages

- Minimum Deinstaller Version

- Oracle Home Dependency

- Dependee Home Location

- Oracle Home Info

- ARU ID

- Home Location

- Home Base

- Home Size

- Home Type

- Inventory

- Is Clonable

- Is CRS

- OH Group

- OH Group ID

- OH Owner

- OH Owner Groups

- OH Owner Groups ID

- OH Owner ID

- Oracle Base

- OUI Home GUID

- OUI Home Name

- OUI Platform ID

- Oracle Patch

- Description

- Install Time

- Installer Version

- Is PSU

- Is Rollbackable

- Patch ID

- Patch Language

- Patch UPI

- Profile

- XML Inventory Location

- Oracle Patchsets

- Description

- External Name

- Installer Version

- Install Time

- Inventory Location

- Minimum Deinstaller Version

- Patchset Name

- Patchset Version

- Oracle Versioned Patch

- Base Component Version

- Description

- External Name

- Installed Location

- Installer Version

- Install Time

- Languages

- Minimum Deinstaller Version

- Patchset Name

- Patchset Version

- VPATCH Name

- VPATCH Version

- Patched Component

- Component Name

- Component Version

- From Version

- Patch ID

- Patch Language

- Patch UPI

- To Version

- Response

- Status

5 Services Metrics

- [CalDAV Metrics]

- Calendar Access Verification Time

- Event Add Time

- Task Add Time

- Connect Time

- Content Listing Time

- Event Delete Time

- Task Delete Time

- DNS Response Metrics

- [DNS] Number of Retries

- [DNS] Number of Results

- [DNS] Status

- [DNS] Total Connect Time (ms)

- [DNS] Total Response Time (ms)

- [DNS] TTL (seconds)

- DNS Results

- Forms Application

- [Forms] Average Time Per Message (ms)

- [Forms] Database Time (ms)

- [Forms] Forms Time (ms)

- FTP Response Metrics

- [FTP] Connect Time (ms)

- [FTP] Download Rate (KB/second)

- [FTP] Download Time (ms)

- [FTP] Login Time (ms)

- [FTP] NOOP Time (ms)

- [FTP] Number of Retries

- [FTP] Status

- [FTP] Status Description

- [FTP] Total Time (ms)

- [FTP] Upload Time (ms)

- [FTP] Upload Rate (ms)

- HTTP Raw Metrics

- HTTP Raw Time Per Connection

- HTTP Raw Broken URL Count

- HTTP Raw Broken URL Details

- HTTP Raw Connect Time (ms)

- HTTP Raw First Byte Time (ms)

- HTTP Transaction DNS Time

- HTTP Raw HTML Time (ms)

- HTTP Raw Non-HTML Time (ms)

- HTTP Raw Perceived Slowest Page / Page Element Time (ms)

- HTTP Raw Perceived Time per Page / Page Element (ms)

- HTTP Raw Perceived Total Time (ms)

- HTTP Raw Redirect Time (ms)

- HTTP Raw Row Type

- HTTP Raw Status

- HTTP Raw Status Description

- HTTP Raw Total Time (ms)

- HTTP Raw Transfer Rate (KB per second)

- HTTP Raw First Byte Time

- HTTP Raw URL

- HTTP Raw DNS Time

- HTTP Step Group Metrics

- [HTTP Step Group] Connect Time (ms)

- [HTTP Step Group] Broken URL Count

- [HTTP Step Group] First Byte Time (ms)

- [HTTP Step Group] Broken URL Details

- [HTTP Step Group] First Byte Time per Page (ms)

- [HTTP Step Group] HTML Time (ms)

- [HTTP Step Group] DNS Time

- [HTTP Step Group] Non-HTML Time (ms)

- [HTTP Step Group] Perceived Slowest Page Time (ms)

- [HTTP Step Group] Perceived Time per Page (ms)

- [HTTP Step Group} Perceived Total Time (ms)

- [HTTP Step Group] Redirect Time (ms)

- [HTTP Step Group] Status

- [HTTP Step Group] Status Description

- [HTTP Step Group] Time per Connection (ms)

- [HTTP Step Group] Transfer Rate (KB per second)

- [HTTP Step Group] Total Time (ms)

- HTTP Transaction Metrics

- [HTTP Transaction] Connect Time (ms)

- [HTTP Transaction] First Byte Time (ms)

- [HTTP Transaction] First Byte Time per Page (ms)

- [HTTP Transaction] Non-HTML Time (ms)

- [HTTP Transaction] HTML Time (ms)

- [HTTP Transaction] Perceived Slowest Page Time (ms)

- [HTTP Transaction] Perceived Time per Page (ms)

- [HTTP Transaction] Perceived Total Time

- [HTTP Transaction] Redirect Time (ms)

- [HTTP Transaction] Status

- [HTTP Transaction] Status Description

- [HTTP Transaction] Time per Connection (ms)

- [HTTP Transaction] Total Time (ms)

- [HTTP Transaction] Transfer Rate (KB per second)

- HTTP User Action Metrics

- [HTTP Step] Connect Time (ms)

- [HTTP Step] Broken URL Count

- [HTTP Step] Broken URL Content

- [HTTP Step] DNS Time

- [HTTP Step] First Byte Time (ms)

- [HTTP Step] First Byte TIme per Page Element (ms)

- [HTTP Step] HTML Time (ms)

- [HTTP Step] Non-HTML Time (ms)

- [HTTP Step] Perceived Slowest Page Element Time (ms)

- [HTTP Step] Perceived Time per Page Element (ms)

- [HTTP Step] Perceived Total Time (ms)

- [HTTP Step] Redirect Time (ms)

- [HTTP Step] Status

- [HTTP] Status Description

- [HTTP Step] Time per Connection (ms)

- [HTTP Step] Total Time (ms)

- [HTTP Step] Transfer Rate (KB per second)

- [HTTP Step] URL

- ICMP Echo Response Metrics

- [ICMP Ping] Last Host

- [ICMP Ping] Number of Hops

- [ICMP Ping] Packets Dropped (%)

- [ICMP Ping] Response Time (ms)

- [ICMP Ping] Status

- IMAP Response Metrics

- [IMAP] Connect Time (ms)

- [IMAP] Login Time (ms)

- [IMAP] Status

- [IMAP] Status Message

- [IMAP] Time to Read Email (ms)

- [IMAP] Time to List Folders (ms)

- [IMAP] Timing (ms)

- Email Undelete Time

- Email Delete Time

- LDAP Response Metric

- [LDAP] Address Search Time (ms)

- [LDAP] Base Search Time (ms)

- [LDAP] Compare Time (ms)

- [LDAP] Connect Time (ms)

- [LDAP] Message Search Time (ms)

- [LDAP] Status

- [LDAP] Status Message

- NNTP Response Metrics

- [NNTP] Connect Time (ms)

- [NNTP] Status

- [NNTP] Status Message

- [NNTP] Time to post news article (ms)

- [NNTP] Time to retrieve news article (ms)

- [NNTP] Total Time

- OS Response Metrics

- [Custom Script] Number of Retries

- [Custom Script] Status

- [Custom Script] Total Time (ms)

- [Custom Script] Custom Metric 1

- [Custom Script] Custom Metric 2

- [Custom Script] Custom Metric 3

- [Custom Script] Custom Metric 4

- [Custom Script] Custom Metric 5

- [Custom Script] Custom Metric 6

- [Custom Script] Custom Metric 7

- [Custom Script] Custom Metric 8

- [Custom Script] Custom Metric 9

- [Custom Script] Custom Metric 10

- POP Response Metrics

- [POP] Connect Time (ms)

- [POP] Login Time (ms)

- [POP] Status

- [POP] Status Message

- [POP] Time to Read Email (ms)

- [POP] Timing (ms)

- Port Checker Metrics

- [Port Checker] Status

- [Port Checker] Unexpectedly Closed Ports

- [Port Checker] Unexpectedly Open Ports

- SMTP Response Metrics

- [SMTP] Connect Time (ms)

- [SMTP] Message Delivery Time

- [SMTP] Status

- [SMTP] Status Message

- [SMTP] Time To Send Email (ms)

- [SMTP] Total Time (ms)

- SOAP Response Metrics

- SOAP Response Time

- SOAP Response Response Time (ms)

- SOAP Response Status

- SOAP Status

- Oracle SQL Response

- [SQL] Close Time (ms)

- [SQL] Connect Time (ms)

- [SQL] Execute Time (ms)

- [SQL] Fetch Time (ms)

- [SQL] Fetch Time per Row (ms)

- [SQL] Number of Rows Fetched

- [SQL] Prepare Time (ms)

- [SQL] Status

- [SQL] Status Description

- [SQL] Total Time (ms)

- [SQL] Total Time per Row (ms)

- TNS Ping Response

- [TNS] Average Response Time (ms)

- [TNS] Pings Dropped (%)

- [TNS] Status

- [Web Transaction] Browser

- [Web Transaction (Browser)] Status

- [Web Transaction (Browser)] Status Description

- [Web Transaction (Browser)] Total Time (ms)

- [Web Transaction (Browser)] Raw

- [Web Transaction (Browser)] Row Type

- [Web Transaction (Browser)] Status

- [Web Transaction (Browser)] Status Description

- [Web Transaction (Browser)] Total Time (ms)

- Web Transaction (Browser) Step

- [Web Transaction (Browser) Step] Status

- [Web Transaction (Browser) Step] Status Description

- [Web Transaction (Browser) Step] Total Time (ms)

- [Web Transaction (Browser)] Step Group

- [Web Transaction (Browser) Step Group] Status

- [Web Transaction (Browser) Step Group] Status Description

- [Web Transaction (Browser) Step Group] Total Time (ms)

6 Web Application Metrics

- HTTP Content

- Average Connect Time

- Average First Byte Time

- Average Response Time

- Beacon Name

- Broken Content

- Broken Count

- Computed Response Time

- Connect Time

- Content Time

- DNS Time

- First Byte TIme

- HTML Bytes

- HTML Content

- HTTP Response

- HTML Time

- Page Content Bytes

- Page Content Count

- Redirect Count

- Redirect Time

- Request Count

- Slowest Response Time

- Status

- Status Description

- Total Bytes

- Total Response TIme

- Transaction Name

- Transfer Rate

- Web Application

- HTTP Step Group

- [HTTP Step Group] Broken URL Count

- [HTTP Step Group] Broken URL Details

- [HTTP Step Group] Connect Time (ms)

- [HTTP Step Group] DNS Time

- [HTTP Step Group] First Byte Time (ms)

- [HTTP Step Group] First Byte TIme per Page (ms)

- [HTTP Step Group] HTML Time (ms)

- [HTTP Step Group] Non-HTML Time (ms)

- [HTTP Step Group] Perceived Slowest Page Time (ms)

- [HTTP Step Group] Perceived Time per Page (ms)

- [HTTP Step Group] Perceived Total Time (ms)

- [HTTP Step Group] Redirect Time (ms)

- [HTTP Step Group] Status

- [HTTP Step Group] Status Description

- [HTTP Step Group] Time per Connection (ms)

- [HTTP Step Group] Total Time (ms)

- [HTTP Step Group] Transfer Rate (KB per second)

- HTTP Transaction

- [HTTP Transaction] Connect Time (ms)

- [HTTP Transaction] DNS Time

- [HTTP Transaction] First Byte Time (ms)

- [HTTP Transaction] First Byte Time per Page (ms)

- [HTTP Transaction] HTML Time (ms)

- [HTTP Transaction] Non-HTML Time (ms)

- [HTTP Transaction] Perceived Slowest Page Time (ms)

- [HTTP Transaction] Perceived Time per Page (ms)

- [HTTP Transaction] Perceived Total Time

- [HTTP Transaction] Redirect Time (ms)

- [HTTP Transaction] Status

- [HTTP Transaction] Status Description

- [HTTP Transaction] Time per Connection (ms)

- [HTTP Transaction] Total Time (ms)

- [HTTP Transaction] Transfer Rate (KB per second)

- HTTP User Action

- [HTTP Step] Broken URL Content

- [HTTP Step] Connect Time (ms)

- [HTTP Step] DNS Time

- [HTTP Step] First Byte Time (ms)

- [HTTP Step] First Byte Time per Page Element (ms)

- [HTTP Step] HTML Time (ms)

- [HTTP Step] Non-HTML Time (ms)

- [HTTP Step] Perceived Slowest Page Element Time (ms)

- [HTTP Step] Perceived Time per Page Element (ms)

- [HTTP Step] Perceived Total Time (ms)

- [HTTP Step] Redirect Time (ms)

- [HTTP Step] Status

- [HTTP Step] Status Description

- [HTTP Step] Time per Connection (ms)

- [HTTP Step] Total Time (ms)

- [HTTP Step] Transfer Rate (KB per second)

- [HTTP Step] URL

- HTTP Raw

- HTTP Raw Broken URL Details

- HTTP Raw Connect Time (ms)

- HTTP Raw DNS Time

- HTTP Raw First Byte Time (ms)

- HTTP Raw HTML Time (ms)

- HTTP Raw Non-HTML Time (ms)

- HTTP Raw Perceived Slowest Page / Page Element Time (ms)

- HTTP Raw Perceived Time per Page / Page Element (ms)

- HTTP Raw Perceived Total Time (ms)

- HTTP Raw Redirect Time (ms)

- HTTP Raw Status

- HTTP Raw Status Description

- HTTP Raw Time Per Connection

- HTTP Raw Transfer Rate (KB per second)

- HTTP Raw Total Time (ms)

- HTTP Raw URL

Oracle® Enterprise Manager

Framework, Host, and Services Metric Reference Manual

12c Release 1 (12.1.0.2.0)

E25162-03

August 2012

Oracle Enterprise Manager Framework, Host, and Services Metric Reference Manual 12c Release 1 (12.1.0.2.0)

E25162-03

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

Primary Author:

Contributing Author:

Contributor:

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

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

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

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

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

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

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

This software or hardware 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 Enterprise Manager framework, host, and services target metrics provided in Oracle Enterprise Manager.

Audience

This document is intended for Oracle Enterprise Manager users interested in Enterprise Manager framework, host, and services target metrics.

Documentation Accessibility

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

Access to Oracle Support

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

Related Documents

For more information, see the following documents in the Oracle Enterprise Manager 12c Release 1 documentation set:

- Oracle Enterprise Manager Cloud Control Basic Installation Guide

- Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide

- Oracle Enterprise Manager Concepts

- Oracle Enterprise Manager Cloud Control Quick Start Guide

- Oracle Enterprise Manager Administration

- Oracle Enterprise Manager Oracle Database and Database-Related 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 Framework, Host, and Services Metric Reference Manual (hereafter referred to as the Framework, Host, and Services Metric Reference Manual) lists all the framework, host, and services target metrics that Enterprise Manager monitors. This manual compiles in one place all the framework, host, and services target metric help available online, eliminating the need to have the Cloud Control Console up and running.

This preface describes:

- Structure of This Manual

- Background Information on Metrics, Thresholds, and Alerts

- Troubleshooting Metrics

Structure of This Manual

This manual contains a chapter for each Enterprise Manager framework, host, and services 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.

- 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 Framework, Host, and Services 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

Management Agent or Agent

Oracle Management Agent

Database

Oracle Database

Management Service or OMS

Oracle Management Service

Management Repository or Repository

Oracle Management Repository

Background Information on Metrics, Thresholds, and Alerts

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

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

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

- A threshold is reached.

- An alert has been cleared.

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

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

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

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

Editing

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

To better suit the monitoring needs of your organization, you can edit the thresholds provided by Enterprise Manager and define new thresholds. When defining thresholds, the key is to choose acceptable values to avoid unnecessary alerts, while still being notified of issues in a timely manner.

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

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

Specifying Multiple Thresholds

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

Accessing Metrics Using the Cloud Control Console

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

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

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

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

Troubleshooting Metrics

In the unlikely situation that a metric does not report a correct value, you need to determine if the problem is related to the:

- Metric providing the wrong values or failing with an error, or

- If the problem is after the Management Agent in the execution flow of the metric, that is, the metric value is correct but, for some reason, the data is not reaching the Oracle Management Service.

To aid you in this determination, Oracle provides the Metric Browser; a troubleshooting tool that can be used with Enterprise Manager to see the raw data being collected by the Management Agent.

Accessing the Metric Browser

When enabled, the Metric Browser can be accessed using a web browser, for example, Netscape, Firefox, and Internet Explorer, using a URL of the form:

http|https://<agent_hostname>:<agent_port>/emd/browser/main

for example

http://myServer.myDomain:3872/emd/browser/main

Note:
You can determine the protocol (http or https), the host name, and the Management Agent port that should be used from the output of the following command (run on the Management Agent host):
<agent_home>/bin/emctl status agent

The Management Agent URL, listed in the output to that command, needs only to have browser placed between emd and main.

By default, the Metric Browser is disabled. When the Metric Browser is disabled, you receive the following error:

HTTP Error 403 - Forbidden if the metric browser has not been enabled.

How to Enable the Metric Browser and the Management Agent Browser for the Oracle Management Agent

Follow these steps to enable the Metric Browser.

1. The Metric Browser is enabled by setting the enableMetricBrowser property in the Management Agent's emd.properties file. The location of that file depends on the type of Management Agent you are working with:

- For the Cloud Control (central|standalone) Management Agent, the file is:
<AGENT_HOME>/sysman/config/emd.properties

- For a clustered (RAC) Management Agent install, the file is:
<AGENT_HOME>/<hostname>/sysman/config/emd.properties

- For the Database Control Management Agent, the file is:
<DATABASE_HOME>/<hostname>_<SID>/sysman/config/emd.properties

- For Application Server Control Management Agent, the file is:
<AS_HOME>/sysman/config/emd.properties

2. Make a backup copy of the emd.properties file.

3. Edit the file and locate the line that reads:

#To enable the metric browser, uncomment the following line
#This is a reloadable parameter
#
#enableMetricBrowser=true

4. Uncomment the line: #enableMetricBrowser=true, so that it reads:
enableMetricBrowser=true

5. Reload the Management Agent Configuration using the command:
<AGENT_HOME>/bin/emctl reload agent

6. After reloading the Management Agent, the Metric Browser will be enabled and therefore accessible using a browser.

Running the Metric Collection Outside the Management Agent

Running the metric collection outside the Management Agent is specific to each metric and requires a firsthand knowledge of each specific metric. Each metric has its own method of collecting its data and some metrics cannot be run standalone because they are calculated from other metrics.

An example of running the metric collection outside the Management Agent is the command line.

1 Agent

The oracle_emd target is a representation of the Oracle Management Agent. The Oracle Management Agent is the Management Agent used by Oracle Enterprise Manager. This target type exposes useful information required to monitor the performance of the Management Agent.

Most of the help topics in this helpset use the term Management Agent to refer to the Oracle Management Agent.

Agent Process Statistics

The EMD Process Statistics provides information about the performance and resource consumption of the Management Agent process. This metric is collected by default on an interval of 1038 seconds. A value that can be changed in the default collection for the oracle_emd target.

Agent Resident Memory Utilization (KB)

The amount of resident memory used by the agent and all of its child processes in KB.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 1038 Seconds

Data Source

Varies. On UNIX platforms this is derived from the ps command.

User Action

The default warning and critical threshold values for this metric are set higher than what is expected to be necessary in many cases. You may give a lesser value for the warning and critical thresholds based on the number and types of targets that are being monitored by the Management Agent.

Agent Virtual Memory Utilization (KB)

The amount of virtual memory used by the agent and all of its child processes in KB.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 1038 Seconds

Data Source

Varies. On UNIX platforms this is derived from the ps command.

User Action

The default warning and critical threshold values for this metric are set higher than what is expected to be necessary in many cases. You may give a lesser value for the warning and critical thresholds based on the number and types of targets that are being monitored by the Management Agent.

CPU Usage (%)

The CPU Usage metric provides the CPU consumption as a percentage of CPU time at any given moment in time. The number is a summation of the CPU consumption of the Management Agent process and any of its child processes (and their child processes and so on). Child processes are sometimes created by the Management Agent in the course of evaluating a metric or running a job.

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 1-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 1038 Seconds

After Every Sample

>

10

20

4

Agent CPU consumption is %value%%%

Data Source

The source for this metric is the UNIX ps command.

User Action

A large CPU consumption will cause the entire system to slow down. The cause could be the Management Agent process itself or any of its child processes. To analyze what is causing the problem, use the Solaris "top" system command and look out for any Perl or Java processes that seem to be consuming excessive CPU (%).

Number Files Open

This metric records the number of files currently opened by the Management Agent process. The file types that constitute this number are: regular files, links, sockets, directories and name pipes.

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 1-2 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 1038 Seconds

After Every Sample

>

800

900

2

Number files opened by Agent is %value%

Data Source

The source of this information is the UNIX pfiles command. On non-UNIX platforms this will not be collected. On Windows platforms, refer to the File Handles Open metric.

Number Handles Open

This metric records the number of file handles currently opened by the Management Agent process.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 1038 Hours

Data Source

This metric is collected on Windows platforms and is not collected on UNIX platforms. For UNIX, use the "Number Files Open" instead. It is gathered by an agent api.

User Action

None.

Number Threads Created

This metric shows the number of threads currently created by the Management Agent process.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 1038 Seconds

Data Source

The source of this metric is the UNIX ps command.

User Action

None

Process ID

The process ID is the process ID of the Management Agent.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 1038 Seconds

Data Source

The source of this is the Perl getppid function.

User Action

None

Resident Memory Utilization (%)

The Resident Memory Utilization is the physical memory usage as a percentage of total memory 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.

Table 1-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 1038 Seconds

After Every Sample

>

20

30

1

Agent resident memory utilization is %value%%%

Data Source

The source of this information is the UNIX ps system command.

User Action

None

Resident Memory Utilization (KB)

This metric represents the amount of physical memory usage by the Management Agent process and all of its child processes in KB.

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 1-4 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 1038 Seconds

After Every Sample

>

128000

256000

1

Agent resident memory utilization in KB is %value%

Data Source

The source of this data is the UNIX ps system command.

User Action

The default warning and critical threshold values for this metric are set higher than what is expected to be necessary in many cases. You will probably want to lower the warning and critical thresholds to values that work well for the number and types of targets that are being monitored by the Management Agent.

Schedule Attempts Percentage

This metric Indicates the percentage of schedule attempts that were delayed beyond their collection intervals.

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 1-5 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 1038 Seconds

After Every Sample

>=

10

50

1

Schedule Attempts Percentage is %value%%%

Data Source

Not applicable.

User Action

An alert on this column implies that either the collection frequency is too high or that the agent is very busy and cannot keep up with the collection schedule of some metrics. You must modify the collection schedules of the affected metrics.

Virtual Memory Utilization (KB)

The Virtual Memory Utilization (VMU) metric provides a sum of the VMU usage of the Management Agent and all of its child processes (and their child processes and so on). Child processes are sometimes created by the Management Agent in the course of evaluating a metric or running a job.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 1038 Seconds

Data Source

The source of this information is the UNIX ps system command.

User Action

Large virtual memory utilization will also slow the system down. On UNIX machines, use the "top" command to see what processes are consuming this memory. Look out for Perl and Java processes as well as the obvious emdaemon process (the Management Agent process itself.)

Virtual Memory Utilization Growth (%)

Virtual memory utilization growth (%) shows the percentage growth of the virtual memory percentage usage of the Management Agent process. For example: if at time t1 (t1 < t2) the usage was a% and at time t2 it was b%, the growth % would be ((b-1)/a)%.

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 1-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 1038 Seconds

After Every Sample

>

.5

2

3

Agent Virtual Memory Growth is %value%%%

Data Source

The source of the raw information is the UNIX ps command. From this, we calculate an average over four interval periods and use this as our comparison percentage (that is, how much has the virtual memory usage grown as a percentage of this average.

User Action

None.

Response

The Response metric reports on the availability of the Management Agent.

Nmo Setuid Status

This metric is Unix specific. The Management Agent checks whether the setuid bit is set on nmo. If it has not been set, an alert is sent.

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 1-7 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Not Defined

After Every Sample

=

Not Defined

0

1

Not Defined

Data Source

Not applicable.

User Action

The setuid bit must be set on nmo.

Status

This metric has a value of 1 if the Management Agent is up and running.

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

On startup

After Every Sample

=

Not Defined

0

1

Not Defined

Data Source

Not applicable.

User Action

If the value of this metric is not 1, the Management Agent is down and contact with the Management Agent will not exist. In such situations, the Management Agent may need to be restarted.

Targets not uploading

This category of metrics provides information on the targets that do not upload data.

Upload Statistics

The Upload Statistics metrics present information on the state of the upload manager and its performance.

Count of targets not uploading data

This metric provides a count of the targets that are not uploading data.

Data Source

The mgmt_targets, mgmt_current_availability tables in the Management Repository.

User Action

Verify the connection between the agent and OMS to which the agent is uploading is working properly. Check for frequent agent restarts, sufficient disk space for the agent upload directory, any severe agent problems logged in agent error logs, severe problems logged in the OMS error log, loader errors logged in the System Errors page.

Number of Files to Upload

This metric shows the number of XML files that are in the $ORACLE_HOME/sysman/emd/upload directory waiting to be uploaded to the repository.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 62 Minutes

Data Source

The source of this information is the Management Agent itself.

User Action

A large number of files in this directory probably indicates that there is a problem uploading files to the repository. Check the emd.trc file for upload errors and act appropriately. The cause may also be a bad network or problems on the repository end.

Size of Files to Upload (MB)

The Size of Files to Upload metric presents the sum of the sizes of all XML files in the upload directory of the Management Agent.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 62 Minutes

Data Source

The source of this information is the Management Agent itself.

User Action

If this metric is large, check the upload directory. If this directory has very few files, it may be they are large. If it has many files, there may be a problem uploading data to the repository. This may be due to a bad network, bad repository or Management Agent. Check the emd.trc file in the log directory for upload error messages.

Upload Rate (KB/sec)

The upload rate is the average rate in KB/sec at which data is uploaded to the repository.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 62 Minutes

Data Source

The source of this information is the Management Agent itself.

User Action

If the rate is zero or close to zero, there may be problems uploading data or collecting data (because if collections stop for some reason, we have nothing to upload). Check the log files for collection and upload messages.

User Identification

These metrics provide information about the user running the Management Agent.

Group Name

The name of the group the Management Agent is running under.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 168 Hours

Data Source

The source of this metric is the UNIX id command.

User Action

None.

Location

The Location metric shows the directory home of the Management Agent.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 168 Hours

Data Source

The source of this information is the ORACLE_HOME environment variable.

Other Groups

This metric lists the other groups the Management Agent user belongs to.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 168 Hours

Data Source

The source of this metric is the UNIX "id" command.

User Action

None.

User Name

The User Name metric provides information on the user that started the Management Agent process.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 168 Hours

Data Source

The source of this data is the UNIX id command.

User Action

None.

User Limit Info

The metrics in the User Limit Info category provide information about the system resources available to the Management Agent.

CoreDump (blocks)

The CoreDump metric shows the maximum size of a core dump file in 512 Kbytes blocks. A value of unlimited means that the only limit is the file system limit.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 168 Hours

Data Source

The source of this information is the UNIX ulimit command.

User Action

This metric shows the maximum size (in 512 Kbyte blocks) of a core dump file. To decrease or increase this limit, use the UNIX ulimit system command.

Data (kbytes)

This metric shows the maximum size of the Management Agent's heap in Kbytes.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 168 Hours

Data Source

The source for this information is the UNIX ulimit system command.

User Action

This metric shows the maximum heap size (in kbytes) made available to the Management Agent. To decrease or increase this limit, use the UNIX ulimit system command.

File (blocks)

The File metric lets you know the size of the largest single file allowed by the system the Management Agent is running on. The unit is 512 Kbyte blocks. A value of "unlimited" means that the limit is the file system limit.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 168 Hours

Data Source

The source for this information is the UNIX ulimit system command.

User Action

This metric shows the maximum file size (in blocks) allowed by the system that the Management Agent is running on. To decrease or increase this limit, use the UNIX ulimit system command.

NoFiles (descriptors)

The NoFiles metric shows the maximum number of file descriptors that the process can have.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 168 Hours

Data Source

The source of this information is the UNIX system call ulimit.

User Action

If this limit is small (compared to the operating system maximum), it can be changed for the Management Agent process.

Stack (kbytes)

This metric displays the maximum size of the Management Agent's stack in Kbytes.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 168 Hours

Data Source

The source for this information is the UNIX ulimit command.

User Action

This metric shows the maximum size (in kbytes) of the Management Agent's stack. To decrease or increase this limit, use the UNIX ulimit system command.

Time (seconds)

The time metric represents, in seconds, the maximum CPU seconds made available to the Management Agent process by the system it is running on. A value of "unlimited" means that the CPU time available to the Management Agent is unrestricted.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 168 Hours

Data Source

This information is obtained using the UNIX ulimit system command.

User Action

This metric shows the maximum CPU time (in seconds) made available to the Management Agent. To decrease or increase this limit, use the UNIX ulimit system command.

Virtual Mem (kbytes)

The Virtual Mem metric shows the maximum virtual memory size that can be occupied by the Management Agent process. If this value is "unlimited" then the only limit is the operating system limit.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 168 Hours

Data Source

The source of this information is the UNIX ulimit system command.

User Action

If the value of the Virtual Mem metric is too high or too low, you can change the restriction on virtual memory use by the Management Agent process using the limit UNIX command.

2 Host

The host metrics provide description, collection statistics, data source, multiple thresholds (where applicable), and user action information for each metric.

Aggregate Resource Usage Statistics (By Project)

This metric provides data on aggregate resource usage on a per project basis. This metric is available only on Solaris version 9 and later.

Cumulative CPU Wait Time (Seconds)

Cumulative number of seconds that this process has spent Waiting for CPU over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Data Page Fault Sleep Time (Seconds)

Cumulative number of seconds that this process has spent sleeping in Data Page Faults over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Major Page Faults

The cumulative number of Major Page Faults engendered by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Minor Page Faults

The cumulative number of Minor Page Faults engendered by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Character IO (bytes) Read and Written

The cumulative number of character I/O bytes Read and Written by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Of Blocks Read

The cumulative number of blocks Read by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Of Blocks Written

The cumulative number of blocks Written by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number of Involuntary Context Switches

The cumulative number of Involuntary Context Switches made by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Of Messages Received

The cumulative number of Messages Received by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Of Messages Sent

The cumulative number of Messages Sent by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number of Signals Received

The cumulative number of Signals taken by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number of System Calls Made

The cumulative number of system calls made by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number of Voluntary Context Switches

The cumulative number of Voluntary Context Switches made by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Project Lock-Wait Sleep Time (Seconds)

The cumulative number of seconds that this process has spent sleeping on User Lock Waits over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Project Other Sleep Time (Seconds)

The cumulative number of seconds that this process has spent sleeping in all other ways over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Stop Time (Seconds)

The cumulative number of seconds that this process has spent Stopped over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Swap Operations

The cumulative number of swap operations engendered by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative System Mode Time (seconds)

The cumulative number of seconds that this process has spent in System mode over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative System Page Fault Sleep Time (Seconds)

The cumulative number of seconds that this process has spent sleeping in System Page Faults over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative System Trap Time (seconds)

The cumulative number of seconds that this process has spent in System Traps over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Text Page Fault Sleep Time (Seconds)

The cumulative number of seconds that this process has spent sleeping in Text Page Faults over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative User Mode Time (seconds)

The cumulative number of seconds that this process has spent in User mode over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Number of Processes Owned by Project

The number of processes owned by the project measured in the aggregate. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Project CPU Time (%)

The percent CPU time used by the process. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Project Process Memory Size (%)

The ratio of the process resident set size to physical memory. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Project's Total Process Heap Size (KiloBytes)

The total number of KiloBytes of memory consumed by the process heap at the time that it is sampled. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Project's Total Process Resident Set Size (KiloBytes)

The resident set size of the process in kilobytes. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Project's Total Process Virtual Memory Size (KiloBytes)

The size of the process virtual address space in kilobytes. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Total Number of Threads in Project's Processes

The number of threads active in the current Process. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Aggregate Resource Usage Statistics (By User)

This metric provides data on aggregate resource usage on a per user basis.

This metric is available only on Solaris version 9 and later.

Cumulative CPU Wait Time (Seconds)

The cumulative number of seconds that this process has spent Waiting for CPU over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Data Page Fault Sleep Time (Seconds)

The cumulative number of seconds that this process has spent sleeping in Data Page Faults over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Major Page Faults

The cumulative number of Major Page Faults engendered by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Minor Page Faults

The cumulative number of Minor Page Faults engendered by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Character IO (bytes) Read and Written

The cumulative number of character I/O bytes Read and Written by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Of Blocks Read

The cumulative number of blocks Read by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Of Blocks Written

The cumulative number of blocks Written by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number of Involuntary Context Switches

The cumulative number of Involuntary Context Switches made by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Of Messages Received

The cumulative number of Messages Received by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number Of Messages Sent

The cumulative number of Messages Sent by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number of Signals Received

The cumulative number of Signals taken by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number of System Calls Made

The cumulative number of system calls made by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Number of Voluntary Context Switches

The cumulative number of Voluntary Context Switches made by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Stop Time (Seconds)

The cumulative number of seconds that this process has spent Stopped over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative System Mode Time (seconds)

The cumulative number of seconds that this process has spent in System mode over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative System Page Fault Sleep Time (Seconds)

The cumulative number of seconds that this process has spent sleeping in System Page Faults over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative System Trap Time (seconds)

The cumulative number of seconds that this process has spent in System Traps over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Swap Operations

The cumulative number of Swap Operations engendered by the process over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative Text Page Fault Sleep Time (Seconds)

The cumulative number of seconds that this process has spent sleeping in Text Page Faults over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative User Lock-Wait Sleep Time (Seconds)

The cumulative number of seconds that this process has spent sleeping on User Lock Waits over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative User Mode Time (seconds)

The cumulative number of seconds that this process has spent in User mode over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Cumulative User Other Sleep Time (Seconds)

The cumulative number of seconds that this process has spent sleeping in all other ways over its lifetime. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Number of Processes Owned by User

The number of processes owned by the user measured in the aggregate. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Total Number of Threads in User's Processes

The number of threads active in the current Process. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

User CPU Time (%)

The percent CPU time used by the process. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

User Process Memory Size (%)

The ratio of the process resident set size to physical memory. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

User's Total Process Heap Size (KiloBytes)

The total number of kilobytes of memory consumed by the process heap at the time that it is sampled. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

User's Total Process Resident Set Size (KiloBytes)

The resident set size of the process in kilobytes. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

User's Total Process Virtual Memory Size (KiloBytes)

The size of the process virtual address space in kilobytes. This metric is available only on Solaris version 9 and later.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The Solaris CIM Object Manager

User Action

Specific to your site.

Buffer Activity

The Buffer Activity metric provides information about OS memory buffer usage. This metric reports buffer activity for transfers, accesses, and cache (kernel block buffer cache) hit ratios per second.

Buffer Cache Read Hit Ratio (%)

Represents the number of reads from block devices to buffer cache as a percentage of all buffer read

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

After Every Sample

>

Not Defined

Not Defined

6

Buffer Cache Read Hit Ratio %value%%% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

User Action

Specific to your site.

Buffer Cache Reads (per second)

Represents the number of reads performed on the buffer cache 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

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

not available

IBM AIX

sar command

Windows

not available

User Action

Specific to your site.

Buffer Cache Write Hit Ratio (%)

Represents the number of writes from block devices to buffer cache as a percentage of all buffer writes.

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

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

6

Buffer Cache Read Hit Ratio %value%%% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

User Action

Specific to your site.

Buffer Cache Writes (per second)

Represents the number of writes performed on the buffer cache 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

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

not available

IBM AIX

sar command

Windows

not available

User Action

Specific to your site.

Physical I/O Reads (per second)

Represents the number of reads per second from character devices using physical I/O mechanisms.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

User Action

An unusually high value may indicate an abnormal situation, so it is important to set thresholds based on the average value observed over a period of time. An abnormally high value may cause performance issues. The user action varies from case to case, observe the running processes to track down any errant process. Placing highly active directories on different disks may help.

Physical I/O Writes (per second)

Represents the number of writes per second from character devices using physical I/O mechanisms.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

User Action

An unusually high value may indicate an abnormal situation, so it is important to set thresholds based on the average value observed over a period of time. An abnormally high value may cause performance issues. The user action varies from case to case, observe the running processes to track down any errant process. Placing highly active directories on different disks may help.

Physical Reads (per second)

Represents the number of physical reads per second from block devices to the system buffer cache.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

User Action

An unusually high value may indicate an abnormal situation, so it is important to set thresholds based on the average value observed over a period of time. An abnormally high value may cause performance issues. The user action varies from case to case, observe the running processes to track down any errant process. Placing highly active directories on different disks may help.

Physical Writes (per second)

Represents the number of physical writes per second from block devices to the system buffer cache.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

User Action

An unusually high value may indicate an abnormal situation, so it is important to set thresholds based on the average value observed over a period of time. An abnormally high value may cause performance issues. The user action varies from case to case, observe the running processes to track down any errant process. Placing highly active directories on different disks may help.

CPU Usage

The CPU Usage metric provides information about the percentage of time the CPU was in various states, for example, idle state and wait state. The metric also provides information about the percentage of CPU time spent in user and system mode. All data is per-CPU in a multi-CPU system.

On HP Tru64, this information is available as the cumulative total for all the CPUs and not for each CPU which is monitored in the Load metric. Hence, this metric is not available on HP Tru64.

CPU Idle Time (%)

Represents the percentage of time that the CPU was idle and the system did not have an outstanding disk I/O request. This metric checks the percentage of processor time in idle mode for the CPU(s) specified by the Host CPU parameter, such as cpu_stat0, CPU0, or * (for all CPUs on the system).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

kernel statistics (class cpu_stat)

HP

pstat_getprocessor() system call

Linux

/proc/stat

HP Tru64

not available

IBM AIX

oracle_kstat() system call

Windows

performance data counters

User Action

An abnormally high value (determined on the basis of historical data) indicates an underutilized cpu. The user action varies from case to case.

CPU Interrupt Time (%)

Represents the percentage of time that the CPU receives and services hardware interruptions during representative intervals. This metric checks the percentage of processor time in interrupt mode for the CPU(s) specified by the Host CPU parameter, such as cpu_stat0, CPU0, or * (for all CPUs on the system).

This metric is available only on Windows.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "CPU Number" object.

If warning or critical threshold values are currently set for any "CPU Number" 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 "CPU Number" object, use the Edit Thresholds page. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.

Data Source

The data sources for this metric are Performance Data counters.

User Action

This indicates the amount of time spent by the processor in handling interrupts. If an unusually high value is observed, there is a possibility of some hardware

CPU System Time (%)

Represents the percentage of time that the CPU is running in system mode (kernel). This metric checks the percentage of processor time in system mode for the CPU(s) specified by the Host CPU parameter, such as cpu_stat0, CPU0, or * (for all CPUs on the system).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

kernel statistics (class cpu_stat)

HP

pstat_getprocessor() system call

Linux

/proc/stat

HP Tru64

not available

IBM AIX

oracle_kstat() system call

Windows

performance data counters

User Action

An abnormally high value (determined on the basis of historical data) indicates that the machine is doing a lot of work at the system (kernel) level. The user action varies from case to case.

CPU User Time (%)

Represents the portion of processor time running in user mode. This metric checks the percentage of processor time in user mode for the CPU(s) specified by the Host CPU parameter, such as cpu_stat0, CPU0, or * (for all CPUs on the system).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

kernel statistics (class cpu_stat)

HP

pstat_getprocessor() system call

Linux

/proc/stat

HP Tru64

not available

IBM AIX

oracle_kstat() system call

Windows

performance data counters

User Action

An abnormally high value (determined on the basis of historical data) indicates the cpu is doing a lot of work at the user (application) level. An examination of the top processes on the system may help identify problematic processes.

CPU Utilization (%) of a CPU

This figure represents the percentage utilization of a CPU

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

kernel statistics (class cpu_stat)

HP

pstat_getprocessor() system call

Linux

/proc/stat

HP Tru64

not available

IBM AIX

oracle_kstat() system call

Windows

performance data counters

User Action

An abnormally high value (determined on the basis of historical data) indicates that the system is under heavy load. If the value is consistently high, consider reducing the load on the system.

CPU Wait Time (%)

Represents the percentage of time that the CPU was idle during which the system had an outstanding disk I/O request. This metric checks the percentage of processor time in wait mode for the CPU(s) specified by the Host CPU parameter, such as cpu_stat0, CPU0, or * (for all CPUs on the system).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

not available

HP

pstat_getprocessor() system call

Linux

not available

HP Tru64

not available

IBM AIX

oracle_kstat() system call

Windows

performance data counters

User Action

A high value indicates that the cpu spends a lot of time waiting for disk i/o to complete. Examine the disk errors and disk activity metrics to see if there are any problems with disk performance. Consider keeping heavily accessed directories on separate disks.

CPUs Details

The metric provides information on the processors of the host.

ECACHE in MB

This is the size of the Cache memory measured in MB.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

Frequency in MHZ

This is the clock frequency of the processor.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

Is HyperThread Enabled

This tells whether hyper threading is enabled for this processor or not.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

Implementation

Implementation type of processor.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

Number of CPUs

This is the count the number rows having the same information in other columns like vendor_name or num_cores. This is added to make at least one key in table.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

MASK

This is Die used to manufacture the CPU. Solaris prtdiag has CPU mask field. This column stores that information.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

Number of Cores per Physical CPU

This represents number of cores per physical CPU. For example. for dual core processors this count will be two and for quad core processor this count will be four.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

Revision

This is the revision.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

Number Of Threads Per Physical CPU

This effectively represents the number of logical processor per physical processors. For example, for one dual core processor with hyper thread enabled, this value will be four.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

Vendor Name

This is vendor who has manufactured the processors. For example Intel and AMD.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/proc/cpuinfo

User Action

None.

Disk Activity

The Disk Activity metric monitors the hard disk activity on the target being monitored. For each device on the system, this metric provides information about access to the device. This information includes: device name, disk utilization, write statistics, and read statistics for the device.

Average Disk I/O Service Time (ms)

Represents the sum of average wait time and average run 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.

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

After Every Sample

>

Not Defined

Not Defined

6

Average service time for disk %keyvalue% is %value% ms, 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 "Disk Device" object.

If warning or critical threshold values are currently set for any "Disk Device" 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 "Disk Device" object, use the Edit Thresholds page.

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

kernel statistics (class kstat_io)

HP

pstat_getdisk system call

Linux

iostat command

HP Tru64

table() system call

IBM AIX

oracle_kstat() system call

Windows

performance data counters

User Action

This number should be low. A high number can indicate a disk that is slow due to excessive load or hardware issues. See also the CPU in IO-Wait (%) metric.

Average Disk I/O Wait Time (ms)

Represents the average time spent by the command waiting on the queue for getting executed.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Disk Device" object.

If warning or critical threshold values are currently set for any "Disk Device" 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 "Disk Device" object, use the Edit Thresholds page.

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

kernel statistics (class kstat_io)

HP

pstat_getdisk system call

Linux

not available

HP Tru64

table() system call

IBM AIX

oracle_kstat() system call

Windows

performance data counters

User Action

A high figure indicates a slow disk. Use the OS iostat -xn command to check wait time and service time for local disks and NFS mounted file systems. See also the CPU in IO-Wait (%) metric.

Average Outstanding Disk I/O Requests

Represents the average number of commands waiting for service (queue length).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

kernel statistics (class kstat_io)

HP

pstat_getdisk system call

Linux

not available

HP Tru64

table() system call

IBM AIX

oracle_kstat() system call

Windows

performance data counters

User Action

Specific to your site.

Average Run Time (ms)

Represents the average time spent by the command on the active queue waiting for its execution to be completed.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

kernel statistics (class kstat_io)

HP

pstat_getdisk system call

Linux

not available

HP Tru64

table() system call

IBM AIX

oracle_kstat() system call

Windows

performance data counters

User Action

Specific to your site.

Bulk I/O Ticks

Represents the time spent in Input/Output operations (ms).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

Linux: /proc/diskstats or /proc/partitions

User Action

Specific to your site.

Difference in Number of Reads

Represents the number of disk reads from the last collection.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

Linux: /proc/diskstats or /proc/partitions

User Action

Specific to your site.

Difference in Number of Writes

Represents the number of disk reads from the last collection.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

Linux: /proc/diskstats or /proc/partitions

User Action

Specific to your site.

Disk Block Writes (per second)

Represents the number of blocks (512 bytes) written per second.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

kernel statistics (class kstat_io)

HP

not available

Linux

iostat command

HP Tru64

table() system call

IBM AIX

oracle_kstat() system call

Windows

performance data counters

User Action

Specific to your site.

Disk Block Reads (per second)

Represents the number of blocks (512 bytes) read per second.

Note: On HPUNIX, this metric is named Disk Blocks Transferred (per second).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

kernel statistics (class kstat_io)

HP

pstat_getdisk system call

Linux

iostat command

HP Tru64

table() system call

IBM AIX

oracle_kstat() system call

Windows

performance data counters

User Action

Specific to your site.

Disk Device Busy (%)

This metric represents disk device busy percentage.

Note: On HPUNIX, this metric is named Device Busy (%).

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-4 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 15 Minutes

After Every Sample

>

80

95

6

Disk Device %keyValue% is %value%%% busy.

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

kernel statistics (class kstat_io)

HP

pstat_getdisk system call

Linux

iostat command

HP Tru64

table() system call

IBM AIX

oracle_kstat() system call

Windows

performance data counters

User Action

Specific to your site.

Disk Reads (per second)

Represents the disk reads per second for the specified disk device.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

kernel statistics (class kstat_io)

HP

not available

Linux

iostat command

HP Tru64

table() system call

IBM AIX

oracle_kstat() system call

Windows

performance data counters

User Action

Specific to your site.

Disk Writes (per second)

Represents the disk writes per second for the specified disk device.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

kernel statistics (class kstat_io)

HP

not available

Linux

iostat command

HP Tru64

table() system call

IBM AIX

oracle_kstat() system call

Windows

performance data counters

User Action

Specific to your site.

Disk Device Errors

The Disk Device Errors metric provides the number of errors on the disk device.

These metrics are available only on Solaris.

Hard Errors

Represents the error count of hard errors encountered while accessing the disk. Hard errors are considered serious and may be traced to misconfigured or bad disk devices.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 72 Hours

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

iostat -e command

HP

not available

Linux

not available

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

Specific to your site.

Soft Errors

Represents the error count of soft errors encountered while accessing the disk. Soft errors are synonymous to warnings.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 72 Hours

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

iostat -e command

HP

not available

Linux

not available

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

Specific to your site.

Total

Represents the sum of all errors on the particular device

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 72 Hours

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

iostat -e command

HP

not available

Linux

not available

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

Specific to your site.

Transport Errors

Represents the error count of network errors encountered. This generally indicates a problem with the network layer

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 72 Hours

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

iostat -e command

HP

not available

Linux

not available

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

Specific to your site.

Fans

The Fans metric monitors the status of various fans present in the system.

This metric is available only on Dell Poweredge Linux Systems.

Fan Status

Represents the status of the fan.

This metric is available only on Dell Poweredge Linux Systems.

The following table lists the possible values for this metric and their meaning.

Metric Value

Meaning (per SNMP MIB)

1

Other (not one of the following)

2

Unknown

3

Normal

4

Warning

5

Critical

6

Non-Recoverable

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-5 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 15 Minutes

Not Uploaded

>=

4

5

1

Status of Fan at device %FanIndex% in chassis %ChassisIndex% is %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 unique combination of "Chassis Index" and "Fan Index" objects.

If warning or critical threshold values are currently set for any unique combination of "Chassis Index" and "Fan Index" 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 "Chassis Index" and "Fan Index" objects, use the Edit Thresholds page.

Data Source

SNMP MIB object: coolingDeviceStatus (1.3.6.1.4.1.674.10892.1.700.12.1.5)

User Action

None.

Location

Provides a description of the location of the fan. Example values are "CPU Fan", "PCI Fan", and "Memory Fan".

This metric is available only on Dell Poweredge Linux Systems.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: coolingDeviceLocationName (1.3.6.1.4.1.674.10892.1.700.12.1.8)

User Action

None.

File Access System Calls

The File Access System Calls metric provides information about the usage of file access system calls.

This metric is available on Solaris, HP, and IBM AIX.

Blocks Read by Directory Search Routine (per second)

Represents the number of file system blocks read per second performing direct lookup.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

not available

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of lookuppn() calls made over this five-second period divided by five.

User Action

None.

iget() Calls (per second)

Represents the number of system iget() calls made per second. iget is a file access system routine.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

kernel memory structure (class cpu_vminfo

HP

sar command

Linux

not available

HP Tru64

not available

IBM AIX

kernel memory structure (class cpu_vminfo

Windows

not available

User Action

This data is obtained using the OS sar command, which is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of iget() calls made over this five-second period divided by five.

lookuppn() Calls (per second)

Represents the number of file system lookuppn() (pathname translation) calls made per second.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

not available

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of lookuppn() calls made over this five-second period divided by five.

User Action

None.

File and Directory Monitoring

The File and Directory Monitoring metric monitors various attributes of specific files and directories. Setting of key value specific thresholds triggers the monitoring of files or directories referred to in the given key value. The operator must specify key value specific thresholds to monitor any file or directory.

File or Directory Attribute Not Found

Reports issues encountered in fetching the attributes of the file or directory. Errors encountered in monitoring the files and directories specified by the key value based thresholds are reported.

Note: This metric is not available on IBM AIX.

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

After Every Sample

!=

Not Defined

0

1

%file_attribute_not_found% .

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "File or Directory Name" object.

If warning or critical threshold values are currently set for any "File or Directory 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 "File or Directory Name" object, use the Edit Thresholds page.

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points

HP

perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points

Linux

perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

Looks for the attributes for file and directories like inode id, user id, and group id. If not found an alert is raised so that user can verify.

File or Directory Permissions

Fetches the octal value of file permissions on the different variations of UNIX operating systems including Linux. Setting a key value specific warning or critical threshold value against this metric would result in the monitoring of a critical file or directory. For example, to monitor the file permissions for file name /etc/passwd, you should set a threshold for /etc/passwd.

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-7 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 15 Minutes

After Every Sample

!=

Not Defined

Not Defined

1

Current permissions for %file_name% are %file_permissions%, different from warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "File or Directory Name" object.

If warning or critical threshold values are currently set for any "File or Directory 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 "File or Directory Name" object, use the Edit Thresholds page.

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points

HP

perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points

Linux

perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points

HP Tru64

not available

IBM AIX

perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points

Windows

not available

User Action

An alert will be raised if the permissions for a file or directory have changed. User may want to verify the change.

File or Directory Size (MB)

Fetches the current size of the given file or directory in megabytes. Setting a key value specific warning or critical threshold value against this metric would result in monitoring of a critical file or directory. For example, to monitor the file permissions for directory /absolute_directory_path, you should set a threshold for /absolute_directory_path.

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

After Every Sample

>

Not Defined

Not Defined

1

Size of %file_name% is %file_size% MB, 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 "File or Directory Name" object.

If warning or critical threshold values are currently set for any "File or Directory 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 "File or Directory Name" object, use the Edit Thresholds page.

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points

HP

perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points

Linux

perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points

HP Tru64

not available

IBM AIX

perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points

Windows

not available

User Action

If a threshold is exceeded, you may need to take action to adjust the file size or the threshold level.

File or Directory Size Change Rate (KB/minute)

Provides the value for the rate at which the file�s size is changing. Setting a key value specific warning or critical threshold value against this metric would result in monitoring of the critical file or directory. For example, to monitor the file change rate for the file name /absolute_file_path, the operator should set a threshold for /absolute_file_path.

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

After Every Sample

>

Not Defined

Not Defined

1

%file_name% is growing at the rate of %file_sizechangerate% (KB/hour), 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 "File or Directory Name" object.

If warning or critical threshold values are currently set for any "File or Directory 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 "File or Directory Name" object, use the Edit Thresholds page.

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points

HP

perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points

Linux

perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points

HP Tru64

not available

IBM AIX

perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points

Windows

not available

User Action

Rate of change of file/directory. An abnormally high value (determined on the basis of historical data) indicates sudden increase in size. Users may want to take some action based on alert.

Filesystems

The Filesystems metrics provide information about local file systems on the computer.

Filesystem

Represents the name of the disk device resource.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

/etc/mnttab file entries

HP

bdf command

Linux

df command

HP Tru64

df command

IBM AIX

/etc/mnttab file entries

Windows

not available

User Action

None.

Filesystem Size (MB)

Represents the total space (in megabytes) allocated in the file system.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

vminfo system

HP

bdf command

Linux

df command

HP Tru64

df command

IBM AIX

stavfs() system call

Windows

Windows API

User Action

None.

Filesystem Space Available (%)

Represents the percentage of free space available in the file system.

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-10 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 15 Minutes

After Every 24 Samples

<

20

5

1

Filesystem %keyValue% has %value%%% available space, fallen below warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Mount Point" object.

If warning or critical threshold values are currently set for any "Mount Point" 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 "Mount Point" object, use the Edit Thresholds page.

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

stavfs() system call

HP

bdf command

Linux

df command

HP Tru64

df command

IBM AIX

stavfs() system call

Windows

Windows API

User Action

Use the OS du -k command to check which directories are taking up the most space (du -k|sort -rn).

Filesystem Utilization (MB)

Represents the total space, expressed in megabytes, allocated in the file system.

This metric is available only on Windows.

Data Source

The data source for this metric is GetDiskFreeSpaceEx.

User Action

A high value indicates that the filesystem has very little free space remaining.User might want to manage the free space.

Kernel Memory

The Kernel Memory metric provides information on kernel memory allocation (KMA) activities.

This metric is available only on Solaris. The data source is the sar command. The data is obtained by sampling system counters once in a five-second interval.

Failed Requests for Large Kernel Memory

This metric represents the Number of requests for large memory that failed, that is, requests that were not satisfied.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command
The data is obtained by sampling system counters once in a five-second interval.

HP

not available

Linux

not available

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

None.

Failed Requests for Oversize Kernel Memory

This metric represents the number of oversized requests made that could not be satisfied. Oversized memory requests are allocated dynamically so there is no pool for such requests.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command
The data is obtained by sampling system counters once in a five-second interval.

HP

not available

Linux

not available

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

None.

Failed Requests for Small Kernel Memory

This metric represents the number of requests for small memory that failed, that is, requests that were not satisfied.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command
The data is obtained by sampling system counters once in a five-second interval.

HP

not available

Linux

not available

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

None.

KMA Available for Large Memory Requests (Bytes)

This metric represents the amount of memory, in bytes, the kernel memory allocation (KMA) has for the large pool; the pool used for allocating and reserving large memory requests.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command
The data is obtained by sampling system counters once in a five-second interval.

HP

not available

Linux

not available

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

None.

KMA for Oversize Memory Requests (Bytes)

This metric represents the amount of memory allocated for oversized memory requests.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command
The data is obtained by sampling system counters once in a five-second interval.

HP

not available

Linux

not available

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

None.

KMA for Small Memory Requests

This metric represents the amount of memory, in bytes, the Kernel Memory Allocation has for the small pool; the pool used for allocating and reserving small memory requests.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command
The data is obtained by sampling system counters once in a five-second interval.

HP

not available

Linux

not available

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

None.

Memory Allocated for Large Memory Requests (Bytes)

This metric represents the amount of memory, in bytes, the kernel allocated to satisfy large memory requests.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command
The data is obtained by sampling system counters once in a five-second interval.

HP

not available

Linux

not available

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

None.

Memory Allocated for Small Memory Requests (Bytes)

This metric represents the amount of memory, in bytes, the kernel allocated to satisfy small memory requests.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Seconds

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command
The data is obtained by sampling system counters once in a five-second interval.

HP

not available

Linux

not available

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

None.

Load

The Load metric provides information about the number of runnable processes on the system run queue. If this is greater than the number of CPU's on the system, then excess load exists.

CPU in I/O Wait (%)

Represents the average number of jobs waiting for I/O in 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.

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

After Every Sample

>

40

80

6

CPU I/O Wait is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

Host

Data Source

Solaris

kernel statistics

HP

pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls

Linux

uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat

HP Tru64

table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands

IBM AIX

oracle_kstat(), getutent(), getproc(), sysconf() system calls

Windows

performance data counters

User Action

A high percentage of I/O wait can indicate a hardware problem, a slow NFS server, or poor load-balancing among local file systems and disks. Check the system messages log for any hardware errors. Use the iostat -xn command or the nfsstat -c (NFS client-side statistics) command or both to determine which disks or file systems are slow to respond. Check to see if the problem is with one or more swap partitions, as lack of swap or poor disk load balancing can cause these to become overloaded. Depending on the specific problem, fixes may include: NFS client or server tuning, hardware replacement, moving applications to other file systems, adding swap space, or restructuring a file system for better performance.

CPU in System Mode (%)

For UNIX-based platforms, this metric represents the amount of CPU being used in SYSTEM mode as a percentage of total CPU processing power.

For Windows, this metric represents the percentage of time the process threads spent executing code in privileged mode.

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-12 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

not defined

not defined

6

CPU in Kernel Mode, %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

Host

Data Source

Solaris

kernel statistics

HP

pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls

Linux

uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat

HP Tru64

table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands

IBM AIX

oracle_kstat(), getutent(), getproc(), sysconf() system calls

Windows

performance data counters

User Action

An abnormally high value (determined on the basis of historical data) indicates that the machine is doing a lot of work at the system (kernel) level. The user action varies from case to case.

CPU in User Mode (%)

For UNIX-based platforms, this metric represents the amount of CPU being used in USER mode as a percentage of total CPU processing power.For Windows, this metric represents the percentage of time the processor spends in the user mode. This metric displays the average busy time as a percentage of the sample 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.

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

After Every Sample

>

not defined

not defined

6

CPU in User Mode, %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

Host

Data Source

Solaris

kernel statistics

HP

pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls

Linux

uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat

HP Tru64

table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands

IBM AIX

oracle_kstat(), getutent(), getproc(), sysconf() system calls

Windows

performance data counters

User Action

An abnormally high value (determined on the basis of historical data) indicates the cpu is doing a lot of work at the user (application) level. An examination of the top processes on the system may help identify problematic processes.

CPU Interrupt Time (%)

Represents the percentage of time the processor spends receiving and servicing hardware interrupts during sample intervals. This value is an indirect indicator of the activity of devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication lines, network interface cards, and other peripheral devices. These devices normally interrupt the processor when they have completed a task or require attention. Normal thread execution is suspended during interrupts. Most system clocks interrupt the processor every 10 milliseconds, creating a background of interrupt activity. Suspends normal thread execution during interrupts.

This metric is available only on Windows.

Data Source

The data sources for this metric are Performance Data counters.

User Action

None.

CPU Queue Length

Processor Queue Length is the number of ready threads in the processor queue. There is a single queue for processor time even on computers with multiple processors. A sustained processor queue of less than 10 threads per processor is normally acceptable, dependent on the workload.

This metric is available only on Windows.

Data Source

The data sources for this metric are Performance Data counters.

User Action

A consistently high value indicates a number of CPU bound tasks. This information should be corelated with other metrics such as Page Transfer Rate. Tuning the system, accompanied with additional memory, should help.

CPU Utilization (%)

For UNIX-based platforms, this metric represents the amount of CPU utilization as a percentage of total CPU processing power available.

For Windows, this metric represents the percentage of time the CPU spends to execute a non-Idle thread. CPU Utilization (%) is the primary indicator of processor activity.

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

After Every Sample

>

80

95

6

CPU Utilization is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

Host

Data Source

Solaris

kernel statistics

HP

pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls

Linux

uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat

HP Tru64

table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands

IBM AIX

oracle_kstat(), getutent(), getproc(), sysconf() system calls

Windows

performance data counters

User Action

An abnormally high value (determined on the basis of historical data) indicates that the system is under heavy load. If the value is consistently high, consider reducing the load on the system.

Free Logical Memory (%)

Represents logical free memory in a system (discounting memory used for filesystem buffers). Note that this memory can potentially be freed, and may not be available immediately.

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

After Every Sample

<

not defined

not defined

6

Logical Free Memory, %value%%%, gone below warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

Linux: /proc/meminfo

AIX: libperfstat

User Action

A very low value (determined on the basis of historical data) indicates that the system is running out of RAM and this could be due to one or more of the following reasons. The first is that there is more than the planned number of processes running on the system. The second is that the processes are taking a lot more memory than expected. The third reason is that a specific process is leaking memory consistently.

Free Memory (%)

Represents logical free memory in a system (discounting memory used for filesystem buffers). Note that this memory can potentially be freed, and may not be available immediately.

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-16 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

<

not defined

not defined

6

Logical Free Memory, %value%%%, gone below warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

Host

Data Source

Solaris

kernel statistics

HP

pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls

Linux

uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat

HP Tru64

table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands

IBM AIX

oracle_kstat(), getutent(), getproc(), sysconf() system calls

Windows

Windows API

User Action

On Linux OS this value might always be close to 0%. Please refer Free logical memory (%) for actual free memory that is available for the users. User should not take any action based on the value of this metric

Longest Service Time (ms)

Represents the maximum of the average service time of all disks. Units are represented in milliseconds.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Seconds

Data Source

Host

Data Source

Solaris

kernel statistics

HP

pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls

Linux

uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat

HP Tru64

table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands

IBM AIX

oracle_kstat(), getutent(), getproc(), sysconf() system calls

Windows

Not available

Memory Page Scan Rate (per second)

For UNIX-based systems, this metric represents the number of pages per second scanned by the page stealing daemon.

For Windows, this metric represents the rate at which pages are read from or written to disk to resolve hard page faults. The metric is a primary indicator of the kinds of faults that cause system-wide delays.

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

After Every Sample

>

Not Defined

Not Defined

6

Page scan rate is %value% /sec, crossed warning (%warning_threshold% /sec) or critical (%critical_threshold% /sec) threshold.

Data Source

Host

Data Source

Solaris

kernel statistics

HP

pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls

Linux

uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat

HP Tru64

table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands

IBM AIX

oracle_kstat(), getutent(), getproc(), sysconf() system calls

Windows

performance data counters

User Action

If this number is zero or close to zero, then you can be sure the system has sufficient memory. If scan rate is always high, then adding memory will definitely help.

Memory Utilization (%)

Represents the amount of free memory as a percentage of total 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-18 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

80

95

6

Memory Utilization is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

Host

Data Source

Solaris

kernel statistics

HP

pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls

Linux

uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat

HP Tru64

table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands

IBM AIX

oracle_kstat(), getutent(), getproc(), sysconf() system calls

Windows

Windows API

User Action

On Linux OS this value might always be close to 100%. Please refer to Free logical memory (%) for actual free memory that is available for the users. User should not take any action based on the value of this metric.

Page Transfers Rate

Indicates the rate at which pages are read from or written to disk to resolve hard page faults. It is a primary indicator of the kinds of faults that cause system wide delays. It is counted in numbers of pages. It includes pages retrieved to satisfy faults in the file system cache (usually requested by applications) non-cached mapped memory files.

This metric is available only on Windows.

Data Source

The data sources for this metric are Windows Performance counters.

User Action

High transfer rates indicate a memory contention. Adding memory would help.

Run Queue Length (1 minute average)

Represents the average number of processes in memory and subject to be run in the last interval. This metric checks the run queue.

This metric is not available on Windows.

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

After Every Sample

>

not defined

not defined

6

CPU Load (Run Queue Length averaged over 1 minute) is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

Host

Data Source

Solaris

kernel statistics

HP

pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls

Linux

uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat

HP Tru64

table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands

IBM AIX

oracle_kstat(), getutent(), getproc(), sysconf() system calls

Windows

not available

User Action

Check the load on the system using the UNIX uptime or top commands. Also, check for processes using too much CPU time by using the top and ps -ef commands. Note that the issue may be a large number of instances of one or more processes, rather than a few processes each taking up a large amount of CPU time. Kill processes using excessive CPU time.

Run Queue Length (5 minute average)

Represents the average number of processes in memory and subject to be run in the last interval. This metric checks the run queue.

This metric is not available on Windows.

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

After Every Sample

>

10

20

6

CPU Load (Run Queue Length averaged over 5 minutes) is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

Host

Data Source

Solaris

kernel statistics

HP

pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls

Linux

uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat

HP Tru64

table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands

IBM AIX

oracle_kstat(), getutent(), getproc(), sysconf() system calls

Windows

not available

User Action

Check the load on the system using the UNIX uptime or top commands. Also, check for processes using too much CPU time by using the top and ps -ef commands. Note that the issue may be a large number of instances of one or more processes, rather than a few processes each taking up a large amount of CPU time. Kill processes using excessive CPU time.

Run Queue Length (15 minute average)

Represents the average number of processes in memory and subject to be run in the last interval. This metric checks the run queue.

This metric is not available on Windows.

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

After Every Sample

>

not defined

not defined

6

CPU Load (Run Queue Length averaged over 5 minutes) is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

Host

Data Source

Solaris

kernel statistics

HP

pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls

Linux

uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat

HP Tru64

table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands

IBM AIX

oracle_kstat(), getutent(), getproc(), sysconf() system calls

Windows

not available

User Action

Check the load on the system using the UNIX uptime or top commands. Also, check for processes using too much CPU time by using the top and ps -ef commands. Note that the issue may be a large number of instances of one or more processes, rather than a few processes each taking up a large amount of CPU time. Kill processes using excessive CPU time.

Swap Utilization (%)

For UNIX-based platforms, this metric represents the percentage of swapped memory in use for the last interval.

For Windows, this metric represents the percentage of page file instance used.

Metric Summary

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

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

After Every Sample

>

80

95

6

Swap Utilization is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

Host

Data Source

Solaris

kernel statistics

HP

pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls

Linux

uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat

HP Tru64

table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands

IBM AIX

oracle_kstat(), getutent(), getproc(), sysconf() system calls

Windows

Windows API and Performance data counters

User Action

For UNIX-based platforms, check the swap usage using the UNIX top command or the Solaris swap -l command. Additional swap can be added to an existing file system by creating a swap file and then adding the file to the system swap pool. (See documentation for your UNIX OS). If swap is mounted on /tmp, space can be freed by removing any junk files in /tmp. If it is not possible to add file system swap or free up enough space, additional swap will have to be added by adding a raw disk partition to the swap pool. See UNIX documentation for procedures.

For Windows, check the page file usage and add an additional page file if current limits are insufficient.

Total Disk I/O Per Second

Represents the rate of I/O (read and write) operations, calculated from all disks.

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

After Every Sample

>

not defined

not defined

6

Disk totIO %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

Host

Data Source

Solaris

kernel statistics

HP

pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls

Linux

uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat

HP Tru64

table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands

IBM AIX

oracle_kstat(), getutent(), getproc(), sysconf() system calls

Windows

not available

Total Processes

Represents the total number of processes currently running on the system. This metric checks the number of processes running on the system.

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

After Every Sample

>

not defined

not defined

6

Number of processes is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

Host

Data Source

Solaris

kernel statistics

HP

pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls

Linux

uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat

HP Tru64

table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands

IBM AIX

oracle_kstat(), getutent(), getproc(), sysconf() system calls

Windows

performance data counters

User Action

An abnormally high value (determined on the basis of historical data) indicates that the system is under heavy load. If the value is consistently high, consider reducing the load on the system by stopping the number of processes.

Total Swap, Kilobytes

Total amount of page file space available to be allocated by processes. Paging files are shared by all processes and the lack of space in paging files can prevent processes from allocating memory.

This metric is available only on Windows.

Data Source

Performance Data counters and Windows API GlobalMemoryStatusEx

User Action

An abnormally high value (determined on the basis of historical data) indicates that the system is doing a lot of swapping by moving data either to or from the disk. This typically will slow down the system because of the relatively slower access to the disk. The reason for this could be one or more of the following:

- There are many processes running on the system competing for a limited RAM and this results in more swapping. User can try to reduce the load by stopping some process

- A process occupying more memory than expected leading to a shortage of available memory

Typically these kinds of problems are solved by adding more RAM.

Total Users

Represents the total number of users currently logged into the system. This metric checks the number of users running on the system.

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

After Every Sample

>

not defined

not defined

6

Number of users is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

Host

Data Source

Solaris

kernel statistics

HP

pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls

Linux

uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat

HP Tru64

table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands

IBM AIX

oracle_kstat(), getutent(), getproc(), sysconf() system calls

Windows

not available

User Action

An abnormally high value (determined on the basis of historical data) indicates that the system is under heavy load. If the value is consistently high, consider reducing the load on the system by restricting or removing active users from the system.

Used Swap, Kilobytes

Represents the size in kilobytes of the page file instance used.

This metric is available only on Windows.

Data Source

Performance Data counters and Windows API GlobalMemoryStatusEx.

User Action

An abnormally high value (determined on the basis of historical data) indicates that the system is doing a lot of swapping by moving data either to or from the disk. This typically will slow down the system because of the relatively slower access to the disk. The reason for this could be one or more of the following:

- There are many processes running on the system competing for a limited RAM and this results in more swapping. User can try to reduce the load by stopping some process

- A process occupying more memory than expected leading to a shortage of available memory

Typically these kinds of problems are solved by adding more RAM.

Log File Monitoring

The Log File Monitoring metric allows the operator to monitor one or more log files for the occurrence of one or more perl patterns in the content. In addition, the operator can specify a perl pattern to be ignored for the log file. Periodic scanning will be performed against new content added since the last scan, lines matching the ignore pattern will be ignored first, then lines matching specified match patterns will result in one record being uploaded to the repository for each pattern. The user can set a threshold against the number of lines matching the given pattern. File rotation will be handled within the given file.

Log File Pattern Matched Content

Returns the actual content if the given file has been specifically registered for content uploading, else it will return the count of lines that matched the pattern specified.

The operator can list the names of files or directories to be never monitored in <EMDROOT>/sysman/config/lfm_efiles file. The operator can list the names of the files or directories whose contents can be uploaded into Oracle Management Repository in <EMDROOT>/sysman/config/lfm_ifiles file.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

Oracle provided perl program that scans files for the occurrence of user specified perl patterns.

User Action

None.

Log File Pattern Matched Line Count

Returns the number of lines matching the pattern specified in the given file. Setting warning or critical thresholds against this column for a specific {log file name, match pattern in perl, ignore pattern in perl} triggers the monitoring of specified criteria against the given log file.

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

After Every Sample

>

0

Not Defined

1*

%log_file_message% Crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

* 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 "Log File Name", "Match Pattern in Perl", "Ignore Pattern in Perl", and "Time Stamp" objects.

If warning or critical threshold values are currently set for any unique combination of "Log File Name", "Match Pattern in Perl", "Ignore Pattern in Perl", and "Time Stamp" 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 "Log File Name", "Match Pattern in Perl", "Ignore Pattern in Perl", and "Time Stamp" objects, use the Edit Thresholds page.

Data Source

Oracle supplied perl program monitors the log files for user specified criteria.

User Action

None.

Memory Devices

The Memory Devices metric monitors the status of memory devices configured in the system.

Bank Location

Represents the bank location name of the memory device, when applicable.

This metric is available only on Dell Poweredge Linux Systems.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: memoryDeviceStatus (1.3.6.1.4.1.674.10892.1.1100.50.1.5)

User Action

None.

Location

Represents the location name of the memory device, for example, "DIMM A".

This metric is available only on Dell Poweredge Linux Systems.

Metric Value

Meaning (per SNMP MIB)

1

Other (not one of the following)

2

Unknown

3

Normal

4

Warning

5

Critical

6

Non-Recoverable

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: memoryDeviceStatus (1.3.6.1.4.1.674.10892.1.1100.50.1.5)

User Action

None.

Memory Status

Represents the status of the memory device.

This metric is available only on Dell Poweredge Linux Systems.

The following table lists the possible values for this metric and their meaning.

Metric Value

Meaning (per SNMP MIB)

1

Other (not one of the following)

2

Unknown

3

Normal

4

Warning

5

Critical

6

Non-Recoverable

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

Not Uploaded

>=

4

5

1

Status of Memory at bank location %MemoryBankLocation% and location %MemoryLocation% is %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 unique combination of "Chassis" and "Index" objects.

If warning or critical threshold values are currently set for any unique combination of "Chassis" and "Index" 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 "Chassis" and "Index" objects, use the Edit Thresholds page.

Data Source

SNMP MIB object: memoryDeviceStatus (1.3.6.1.4.1.674.10892.1.1100.50.1.5)

User Action

None.

Size

Represents the size, in kilobytes, of the memory device.

This metric is available only on Dell Poweredge Linux Systems.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: memoryDeviceSize (1.3.6.1.4.1.674.10892.1.1100.50.1.14)

User Action

None.

Type

Represents the type of the memory device.

This metric is available only on Dell Poweredge Linux Systems.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: memoryDeviceSize (1.3.6.1.4.1.674.10892.1.1100.50.1.14)

User Action

None.

Message and Semaphore Activity

The Message and Semaphore Activity metric provides information about the message and semaphore activity of the host system being monitored.

The following table lists the metrics and their descriptions.

msgrcv() System Calls (per second)

Represents the number of msgrcv system calls made per second. The msgrcv system call reads a message from one queue to another user-defined queue.

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

ipcs command

IBM AIX

sar command

Windows

not available

User Action

None.

semop() System Calls (per second)

Represents the number of semop system calls made per second. The semop system call is used to perform semaphore operations on a set of semaphores.

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

ipcs command

IBM AIX

sar command

Windows

not available

User Action

None.

IO Card Details

The metric holds the information about the IO cards in the host, including pci cards and USBs.

Bus Type

This is the bus type of the IO card.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

lspci

User Action

None.

Frequency

The clock frequency of the IO card.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

lspci

User Action

None.

Name

This represents the name of the IO card.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

lspci

User Action

None.

Revision

This represents the IO card revision.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

lspci

User Action

None.

Vendor Name

This represents the manufacturer name of IO card.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

lspci

User Action

None.

Network Interface Count

This metric relates to network interface cards, both unbonded and bonded interface cards. Slave interface cards have the same information as bonded cards.

BroadCast Address

Broadcast address of the local area network.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

ifconfig

User Action

None.

Default Gateway

Default gateway configured for this host.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

ifconfig

User Action

None.

Description

A description of the Network Interface Card.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

ifconfig

User Action

None.

Is DHCP Enabled

Represents whether this Network Interface Card (NIC) is configured for dynamic or static ip addresses

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

ifconfig

User Action

None.

Flags

Network interface card's Flags

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

ifconfig

User Action

None.

Hostname Aliases

This represents the aliases for the host corresponding to this Network Interface Card.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

arp

User Action

None.

IP Address

IP address associated with this Network Interface Card. This is supposed to be an IPV4 address.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

ifconfig

User Action

None.

IPV6 Addresses

This is comma-separated list of IPV6 addresses.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

ifconfig

User Action

None.

MAC Address

Hardware address of the Network Interface Card.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

ifconfig

User Action

None.

NetMask

This is subnet mask inet address.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

ifconfig

User Action

None.

Maximum Transfer Unit

Maximum packet size that to be sent it from this Network Interface Card. This is in bytes.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

ifconfig

User Action

None.

Name

Network interface card name.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

ifconfig

User Action

None.

Network Interface Bonds

This metric relates to bonded network interface cards. Slave interface cards have the same information as bonded cards.

Bond Name

Name of the bond.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Mode of the Bond

Mode of the bonds. This can be balance-alb.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Options of the Bond

Options/properties of the bond. This can be something like "miimon=100 max_bonds=4."

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Primary Slave

Primary slave of the bond. The Network Interface Card which is the primary slave of the bond.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Secondary Slaves

Comma separated list of secondary slaves.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Operating System

This metric contains the operating summary information. There will be one row per host.

Address Length (Bits)

This is the OS address length. This is either 32 bit or 64 bit.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

uname -a

User Action

None.

Base Version

Base version of the OS

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

uname -a

User Action

None.

Is DB Machine Member

When host is member Database Machine, this columns will have a value of 1.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

uname -a

User Action

None.

Default OS Run Level

Default Run level of the OS running on the host. Whenever the OS is booted, it will be booted to this run level.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

uname -a

User Action

None.

Distribution Version

This is only applicable for Linux. Represents OS distributed version

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

uname -a

User Action

None.

Max Swap Space (MB)

This represents Maximum swap space available for the OS.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

uname -a

User Action

None.

Name

Name of the OS

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/etc/enterprise-release for OEL

/etc/redhat-release for redhat

/etc/UnitedLinux-release

/etc/SuSE-release

User Action

None.

Platform ID

This is the platform id number

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

uname -a

User Action

None.

Update Level

Latest update level of this OS

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

uname -a

User Action

None.

Vendor Name

This represents the OS vendor name.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/etc/enterprise-release for OEL

/etc/redhat-release for redhat

/etc/UnitedLinux-release

User Action

None.

Operating System Components

This metric stores the information about OS components, including Patches, Bundles, and Packages.

Description

Description of the component

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/rpm

User Action

None.

Installation Date

Installation date of the component.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/rpm

User Action

None.

Name

Name of the OS component.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/rpm

User Action

None.

Type

Type of OS components. This can be Patch, Bundle, Package.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/rpm

User Action

None.

Version

Version of the component.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/rpm

User Action

None.

File Systems

This lists all file systems mounted in the host.

Disk Space (GB)

File System capacity in GB.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/etc/mtab

User Action

None.

Local Drive

Applicable NT only.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/etc/mtab

User Action

None.

Mount Location

Mount location of the file system.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/etc/mtab

User Action

None.

Mount Options

This metric contains details about the mount options. These could be similar to "rw,intr,largefiles,logging,xattr,onerror=panic."

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/etc/mtab

User Action

None.

Resource Name

This is the device path of host. This can be /dev/hd10opt, Local Disk (C:)

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/etc/mtab

User Action

None.

Type

This is the file system type. Examples include nfs, ntfs, and jfs.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/etc/mtab

User Action

None.

Operating System Properties

This metric lists some of the OS properties, including OPEN_MAX, Semaphore values, and kernel.pid_max.

Name

Name of configuration variable of the OS, for example OPEN_MAX.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/getconf, ulimit

Source

This is the source of the property info. This can be similar to /sbin/sysctl or /usr/bin/getconf.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/getconf , ulimit

Value

This is the value of the property.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/getconf , ulimit

Operating System Registered Software

This metric contains details of all the OS Registered Software.

Description

Any vendor description for the software.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

ID

ID of Software installed in the host. Only applicable for NT/Windows.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Installation Date

Installation date of the software.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Installed Location

The location where the software is installed.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Media Type

Installation or distribution source of the installed product. For example, the package name, bundling application, or distro.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Name

Name of installed software.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Vendor Name

Vendor who provided the software

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Vendor Specific Information

Anything related to software

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Version

Any vendor description for the software.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Virtual Machine

Represents the Solaris zone name in which the product is installed.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Parent Product Identifier

Parent ID of the installed product. Applicable to the Sun Service Tag product taxonomy

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Product Parent Name

Descriptive parent name of the installed product. Applicable to the Sun Service Tag product taxonomy

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Software Architecture

CPU/OS architecture the application is designed to run on e.g., Solaris SPARC (64bit)

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

/bin/rpm

User Action

Informational only.

Operating System ULIMITS

This metric contains details of the operating system ULIMITS.

CoreDump (blocks)

Limits the size of a "core" file left behind when a process encounters a segmentation fault or other unexpected fatal error.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Time (seconds)

Maximum CPU time a process can use before it get terminated. CPU time is the amount of time the CPU actual spends executing processor instructions and is often much less than the total program "runs time".

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data (kbytes)

Limits the amount of memory that a process can allocate on the heap, as with malloc, calloc, C++ "new," and most object creation in higher-level languages. Specified in kilobytes.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

File (blocks)

Maximum size of the file a process can create. Number will be in 512 bytes (one block).

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

NoFiles (descriptors)

This number represents maximum number of files that can be opened at a time.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Stack (kbytes)

Limits the amount of memory a process can allocate on the stack, as in the case of local variables in C, C++, and many other languages.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Virtual Mem (kbytes)

Maximum memory that can be allocated to a process. This includes all types of memory, including the stack, the heap, and memory-mapped files Attempts to allocate memory in excess of this limit will fail with an out-of-memory error.

Metric Summary

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

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Network Interfaces

The Network Interfaces metric includes input errors and interface collisions on the network interface. The following network interfaces are supported: le, hme, qfe, ge, and fddi.

Network Interface Collisions (%)

Represents the number of collisions per second. This metric checks the rate of collisions on the network interface specified by the network device names parameter, such as le0 or * (for all network interfaces).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

kernel memory structures (kstat)

HP

netstat, lanscan, and lanadmin commands

Linux

netstat command and /proc/net/dev

HP Tru64

netstat command

IBM AIX

oracle_kstat() system call

Windows

not available

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Network Interface Combined Utilization (%)

Represents the percentage of network bandwidth being used by reading and writing from and to the network for full-duplex network connections.

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

After Every Sample

>

Not Defined

Not Defined

6

Network utilization for %keyvalue% is %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 "Network Interface Name" object.

If warning or critical threshold values are currently set for any "Network Interface 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 "Network Interface Name" object, use the Edit Thresholds page.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

kernel memory structures (kstat)

HP

netstat, lanscan, and lanadmin commands

Linux

netstat command and /proc/net/dev

HP Tru64

netstat command

IBM AIX

oracle_kstat() system call

Windows

not available

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Network Interface Input Errors (%)

Represents the number of input errors, per second, encountered on the device for unsuccessful reception due to hardware/network errors. This metric checks the rate of input errors on the network interface specified by the network device names parameter, such as le0 or * (for all network interfaces).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

kernel memory structures (kstat)

HP

netstat, lanscan, and lanadmin commands

Linux

netstat command and /proc/net/dev

HP Tru64

netstat command

IBM AIX

oracle_kstat() system call

Windows

not available

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Network Interface Output Errors (%)

Represents the number of output errors per second. This metric checks the rate of output errors on the network interface specified by the network device names parameter, such as le0 or * (for all network interfaces).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

kernel memory structures (kstat)

HP

netstat, lanscan, and lanadmin commands

Linux

netstat command and /proc/net/dev

HP Tru64

netstat command

IBM AIX

oracle_kstat() system call

Windows

not available

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Network Interface Read (MB/s)

Represents the amount of megabytes per second read from the specific interface.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

kernel memory structures (kstat)

HP

netstat, lanscan, and lanadmin commands

Linux

netstat command and /proc/net/dev

HP Tru64

not available

IBM AIX

perfstat system call

Windows

not available

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Network Interface Read Utilization (%)

Represents the amount of network bandwidth being used for reading from the network as a percentage of total read capacity.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

kernel memory structures (kstat)

HP

netstat, lanscan, and lanadmin commands

Linux

netstat command and /proc/net/dev

HP Tru64

not available

IBM AIX

perfstat system call

Windows

not available

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Network Interface Total Error Rate (%)

Represents the number of total errors per second, encountered on the network interface. It is the rate of read and write errors encountered on the network interface.

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

After Every Sample

>

Not Defined

Not Defined

6

Network Error Rate for %keyvalue% is %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 "Network Interface Name" object.

If warning or critical threshold values are currently set for any "Network Interface 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 "Network Interface Name" object, use the Edit Thresholds page.

Data Source

It is computed as the sum of Network Interface Input Errors (%) and Network Interface Output Errors (%).

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Network Interface Total I/O Rate (MB/sec)

Represents the total I/O rate on the network interface. It is measured as the sum of Network Interface Read (MB/s) and Network Interface Write (MB/s).

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

After Every Sample

>

Not Defined

Not Defined

6

Network I/O Rate for %keyvalue% is %value%MB/Sec, crossed warning (%warning_threshold%MB/Sec) or critical (%critical_threshold%MB/Sec) threshold.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Network Interface Name" object.

If warning or critical threshold values are currently set for any "Network Interface 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 "Network Interface Name" object, use the Edit Thresholds page.

Data Source

It is computed as the sum of Network Interface Read (MB/s) and Network Interface Write (MB/s).

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Network Interface Write (MB/s)

Represents the amount of megabytes per second written to the specific interface.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

kernel memory structures (kstat)

HP

netstat, lanscan, and lanadmin commands

Linux

netstat command and /proc/net/dev

HP Tru64

netstat command

IBM AIX

oracle_kstat() system call

Windows

not available

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Network Interface Write Utilization (%)

Represents the amount of network bandwidth being used for writing to the network as a percentage of total read capacity.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

kernel memory structures (kstat)

HP

netstat, lanscan, and lanadmin commands

Linux

netstat command and /proc/net/dev

HP Tru64

not available

IBM AIX

perfstat system call

Windows

not available

User Action

Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.

Paging Activity

The Paging Activity metric provides the amount of paging activity on the system.

Address Translation Page Faults (per second)

Represents the minor page faults by way of hat_fault() per second. This metric checks the number of faults for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

kernel statistics (class misc cpu_stat)

HP

pstat_getvminfo() system call

Linux

not available

HP Tru64

table() system call and vmstat command

IBM AIX

oracle_kstat() system call

Windows

not available

User Action

Informational only.

Cache Faults (per second)

The Cache Faults/sec is the rate at which faults occur when a page sought in the file system cache is not found and must be retrieved from elsewhere in memory (a soft fault) or from disk (a hard fault). The file system cache is an area of physical memory that stores recently used pages of data for applications. Cache activity is a reliable indicator of most application I/O operations. This metric shows the number of faults, without regard for the number of pages faulted in each operation.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

not available

HP

not available

Linux

not available

HP Tru64

not available

IBM AIX

not available

Windows

Performance Data counters

User Action

Informational only.

Copy-on-write Faults (per second)

Copy-on-Write faults/sec is the rate at which page faults are caused by attempts to write that have been satisfied by coping of the page from elsewhere in physical memory. This is an economical way of sharing data since pages are only copied when they are written to; otherwise, the page is shared. This metric shows the number of copies, without regard for the number of pages copied in each operation.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

not available

HP

not available

Linux

not available

HP Tru64

not available

IBM AIX

not available

Windows

Performance Data counters

User Action

Informational only

Demand Zero Faults (per second)

Demand Zero Faults/sec is the rate at which a zeroed page is required to satisfy the fault. Zeroed pages, pages emptied of previously stored data and filled with zeros, are a security feature of Windows that prevent processes from seeing data stored by earlier processes that used the memory space. Windows maintains a list of zeroed pages to accelerate this process. This metric shows the number of faults, without regard to the number of pages retrieved to satisfy the fault.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

not available

HP

not available

Linux

not available

HP Tru64

not available

IBM AIX

not available

Windows

Performance Data counters

User Action

Informational only.

igets with Page Flushes(%)

Represents the percentage of UFS inodes taken off the freelist by iget which had reusable pages associated with them. These pages are flushed and cannot be reclaimed by processes.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

kernel statistics (class misc cpu_stat)

HP

pstat_getvminfo system call

Linux

not available

HP Tru64

not available

IBM AIX

oracle_kstat() system call

Windows

not available

User Action

Informational only.

Page Faults (per second)

Page Faults/sec is the average number of pages faulted per second. It is measured in number of pages faulted per second because only one page is faulted in each fault operation, hence this is also equal to the number of page fault operations. This metric includes both hard faults (those that require disk access) and soft faults (where the faulted page is found elsewhere in physical memory.) Most processors can handle large numbers of soft faults without significant consequence. However, hard faults, which require disk access, can cause significant delays.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

not available

HP

not available

Linux

not available

HP Tru64

not available

IBM AIX

not available

Windows

Performance Data Counters

User Action

Informational only.

Page Faults from Software Lock Requests

Represents the number of protection faults per second. These faults occur when a program attempts to access memory it should not access, receives a segmentation violation signal, and dumps a core file. This metric checks the number of faults for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

kernel statistics (class misc cpu_stat)

HP

pstat_getvminfo system call

Linux

not available

HP Tru64

table() system call and vmstat command

IBM AIX

perfstat system call

Windows

not available

User Action

Informational only.

Page-in Requests (per second)

For UNIX-based systems, represents the number of page read ins per second (read from disk to resolve fault memory references) by the virtual memory manager. Along with Page Outs, this statistic represents the amount of real I/O initiated by the virtual memory manager. This metric checks the number of page read ins for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).For Windows, this metric is the rate at which the disk was read to resolve hard page faults. It shows the number of reads operations, without regard to the number of pages retrieved in each operation. Hard page faults occur when a process references a page in virtual memory that is not in working set or elsewhere in physical memory, and must be retrieved from disk. This metric is a primary indicator of the kinds of faults that cause system wide delays. It includes read operations to satisfy faults in the file system cache (usually requested by applications) and in non-cached mapped memory files.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

kernel statistics (class misc cpu_stat)

HP

pstat_getvminfo system call

Linux

not available

HP Tru64

table() system call and vmstat command

IBM AIX

oracle_kstat() system call

Windows

performance data counters

User Action

Informational only.

Page-Out Requests (per second)

For UNIX-based systems, represents the number of page write outs to disk per second. This metric checks the number of page write outs for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).For Windows, this metric is the rate at which pages are written to disk to free up space in physical memory. Pages are written to disk only if they are changed while in physical memory, so they are likely to hold data, not code. This metric shows write operations, without regard to the number of pages written in each operation.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

kernel statistics (class misc cpu_stat)

HP

pstat_getvminfo system call

Linux

not available

HP Tru64

vmstat command

IBM AIX

oracle_kstat() system call

Windows

performance data counters

User Action

Informational only.

Pages Paged-in (per second)

For UNIX-based systems, represents the number of pages paged in (read from disk to resolve fault memory references) per second. This metric checks the number of pages paged in for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).For Windows, this metric is the rate at which pages are read from disk to resolve hard page faults. Hard page faults occur when a process refers to a page in virtual memory that is not in its working set or elsewhere in physical memory, and must be retrieved from disk. When a page is faulted, the system tries to read multiple contiguous pages into memory to maximize the benefit of the read operation.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

kernel statistics (class misc cpu_stat)

HP

pstat_getvminfo system call

Linux

sar command

HP Tru64

table() system call and vmstat command

IBM AIX

oracle_kstat() system call

Windows

performance data counters

User Action

Informational only.

Pages Paged-out (per second)

For UNIX-based systems, represents the number of pages written out (per second) by the virtual memory manager. Along with Page Outs, this statistic represents the amount of real I/O initiated by the virtual memory manager. This metric checks the number of pages paged out for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).For Windows, this metric is the rate at which pages are written to disk to free up space in physical memory. Pages are written back to disk only if they are changed in physical memory, so they are likely to hold data, not code. A high rate of pages output might indicate a memory shortage. Windows writes more pages back to disk to free up space when physical memory is in short supply.

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

After Every Sample

>

Not Defined

Not Defined

6

Pages Paged-out (per second) %value%, has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

kernel statistics (class misc cpu_stat)

HP

pstat_getvminfo() system call

Linux

sar command

HP Tru64

vmstat command

IBM AIX

oracle_kstat() system call

Windows

performance data counters

User Action

Informational only.

Pages Put on Freelist by Page Stealing Daemon (per second)

Represents the number of pages that are determined unused, by the pageout daemon (also called the page stealing daemon), and put on the list of free pages.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

kernel statistics (class misc cpu_stat)

HP

pstat_getvminfo system call

Linux

not available

HP Tru64

table() system call and vmstat command

IBM AIX

oracle_kstat() system call

Windows

not available

User Action

Informational only.

Pages Scanned by Page Stealing Daemon (per second)

Represents the scan rate is the number of pages per second scanned by the page stealing daemon.

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

After Every Sample

>

Not Defined

Not Defined

6

Pages Paged-In (per second) %value%, has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

kernel statistics (class misc cpu_stat)

HP

pstat_getvminfo() system call

Linux

not available

HP Tru64

table() system call and vmstat command

IBM AIX

oracle_kstat() system call

Windows

not available

User Action

If this number is zero or closer to zero, then you can be sure the system has sufficient memory. If the number is always high, then adding memory will definitely help.

Transition Faults (per second)

Transition Faults/sec is the rate at which page faults are resolved by recovering pages that were being used by another process sharing the page, or were on the modified page list or the standby list, or were being written to disk at the time of the page fault. The pages were recovered without additional disk activity. Transition faults are counted in numbers of faults; because only one page is faulted in each operation, it is also equal to the number of pages faulted.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

not available

HP

not available

Linux

not available

HP Tru64

not available

IBM AIX

not available

Windows

performance data counters

User Action

Informational only.

PCI Devices

The Peripheral Component Interconnect (PCI) Devices metric monitors the status of PCI devices.

Description

Descriptive name of the Dell Peripheral Component Interconnect (PCI) Device

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: pCIDeviceDescriptionName (1.3.6.1.4.1.674.10892.1.1100.80.1.9)

User Action

None.

Manufacturer

Name of the Dell Peripheral Component Interconnect (PCI) Device

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: pCIDeviceManufacturerName (1.3.6.1.4.1.674.10892.1.1100.80.1.8)

User Action

None.

PCI Device Status

Represents the status of the Dell Peripheral Component Interconnect (PCI) Device.

This metric is available only on Dell Poweredge Linux Systems.

The following table lists the possible values for this metric and their meaning.

Metric Value

Meaning (per SNMP MIB)

1

Other (not one of the following)

2

Unknown

3

Normal

4

Warning

5

Critical

6

Non-Recoverable

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

Not Uploaded

>=

4

5

1

Status of PCIDevice %PCIDeviceIndex% in chassis %ChassisIndex% is %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 unique combination of "Chassis Index", "PCI Device Index", and "System Slot Index" objects.

If warning or critical threshold values are currently set for any unique combination of "Chassis Index", "PCI Device Index", and "System Slot Index" 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 "Chassis Index", "PCI Device Index", and "System Slot Index" objects, use the Edit Thresholds page.

Data Source

SNMP MIB object: pCIDeviceStatus (1.3.6.1.4.1.674.10892.1.1100.80.1.5)

User Action

None.

Power Supplies

The Power Supplies metric monitors the status of various power supplies present in the host system.

This metric is available only on Dell Poweredge Linux Systems.

Location

Represents the location name of the power supply

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: powerSupplyLocationName (1.3.6.1.4.1.674.10892.1.600.12.1.8)

User Action

None.

Output (Tenths of Watts)

Represents the maximum sustained output wattage of the power supply, in tenths of watts.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: powerSupplyOutputWatts (1.3.6.1.4.1.674.10892.1.600.12.1.6)

User Action

None.

Power Supply Status

Represents the status of the power supply.

This metric is available only on Dell Poweredge Linux Systems.

The following table lists the possible values for this metric and their meaning.

Metric Value

Meaning (per SNMP MIB)

1

Other (not one of the following)

2

Unknown

3

Normal

4

Warning

5

Critical

6

Non-Recoverable

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

Not Uploaded

>=

4

5

1

Status of Power Supply %PSIndex% in chassis %ChassisIndex% is %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 unique combination of "Chassis Index" and "Power Supply Index" objects.

If warning or critical threshold values are currently set for any unique combination of "Chassis Index" and "Power Supply Index" 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 "Chassis Index" and "Power Supply Index" objects, use the Edit Thresholds page.

Data Source

SNMP MIB object: powerSupplyStatus (1.3.6.1.4.1.674.10892.1.600.12.1.5)

User Action

None.

Processes - Top

The Top Processes metric is a listing of (up to) 20 processes that include 10 processes consuming the largest percentage of memory and 10 processes consuming the most percentage of CPU time. The processes are listed in the order of memory consumption.

Command and Arguments

Represents the command and all its arguments.

Data Source

Host

Data Source

Solaris

ps command, for example, ps -efo args

HP

ps command, for example, ps -efo args

Linux

ps command, for example, ps -efo args

HP Tru64

ps command, for example, ps -efo args

IBM AIX

ps command, for example, ps -efo args

Windows

performance data counters

User Action

None.

CPU Time for Top Processes

Represents the CPU utilization time in seconds.

Data Source

Host

Data Source

Solaris

ps command, for example, ps -efo time

HP

ps command, for example, ps -efo time

Linux

ps command, for example, ps -efo time

HP Tru64

ps command, for example, ps -efo time

IBM AIX

ps command, for example, ps -efo time

Windows

performance data counters

User Action

None.

CPU Utilization for Top Processes (%)

Represents the percentage of CPU time consumed by the process.

Data Source

Host

Data Source

Solaris

ps command, for example, ps -efo pcpu

HP

ps command, for example, ps -efo pmem

Linux

ps command, for example, ps -efo pcpu

HP Tru64

ps command, for example, ps -efo pcpu

IBM AIX

ps command, for example, ps -efo pcpu

Windows

performance data counters

User Action

None.

Memory Utilization for Top Processes (%)

Represents the percentage of memory consumed by the process.

Data Source

Host

Data Source

Solaris

ps command, for example, ps -efo pmem

HP

ps command, for example, ps -efo pmem

Linux

ps command, for example, ps -efo pmem

HP Tru64

ps command, for example, ps -efo pmem

IBM AIX

ps command, for example, ps -efo pmem

Windows

performance data counters

User Action

None.

Physical Memory Utilization (KB)

Represents the number of kilobytes of physical memory being used.

Data Source

Host

Data Source

Solaris

kernel memory structure (class vminfo)

HP

ps command

Linux

ps command

HP Tru64

ps command

IBM AIX

kernel memory structure (struct vminfo)

Windows

Windows API

User Action

None.

Process User ID

Represents the user name that owns the process, that is, the user ID of the process being reported on.

Data Source

Host

Data Source

Solaris

ps command, for example, ps -efo user

HP

ps command

Linux

ps command, for example, ps -efo user

HP Tru64

ps command, for example, ps -efo user

IBM AIX

ps command, for example, ps -efo user

Windows

Windows API

User Action

None.

Virtual Memory Utilization (KB)

Represents the total size of the process in virtual memory in kilobytes (KB).

Data Source

Host

Data Source

Solaris

ps command, for example, ps -efo vsz

HP

ps command, for example, ps -efo vsz

Linux

ps command, for example, ps -efo vsz

HP Tru64

ps command, for example, ps -efo vsz

IBM AIX

ps command, for example, ps -efo vsz

Windows

Windows API

User Action

None.

Process, Inode, File Tables Statistics

The Process, Inode, File Tables Stats metric provides information about the process, inode, and file tables status.

File Table Overflow Occurrences

Represents the number of times the system file table overflowed, that is, the number of times that the OS could not find any available entries in the table in the sampling period chosen to collect the data.

Metric Summary

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

User Action

None.

Inode Table Overflow Occurrences

Represents the number of times the inode table overflowed, that is, the number of times the OS could not find any available inode table entries.

Metric Summary

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

User Action

None.

Maximum Size of Inode Table

Represents the maximum size of the inode table.

Metric Summary

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

User Action

None.

Maximum Size of Process Table

Represents the maximum size of the process table.

Metric Summary

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

User Action

None.

Maximum Size of System File Table

Represents the maximum size of the system file table.

Metric Summary

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

User Action

None.

Number Of Allocated Disk Quota Entries

Represents the number of allocated disk quota entries.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

not available

HP

not available

Linux

sar command

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

None.

Number Of Queued RT Signals

Provides the number of queued RT signals.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

not available

HP

not available

Linux

sar command

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

None.

Number Of Super Block Handlers Allocated

Provides the number of allocated super block handlers.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

not available

HP

not available

Linux

sar command

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

None.

Number Of Used File Handles

Represents the current size of the system file table.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

not available

HP

not available

Linux

sar command

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

None.

Percentage Of Allocated Disk Quota Entries

Represents the Percentage Of Allocated Disk Quota Entries against the maximum number of cached disk quota entries that can be allocated.

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

After every sample

>

not defined

not defined

6

Allocated Disk Quota Entries %value%%% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

not available

HP

not available

Linux

sar command

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

None.

Percentage Of Allocated Super Block Handlers

Represents the Percentage Of Allocated Super Block Handlers against the maximum number of super block handlers that Linux can allocate.

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

After every sample

>

not defined

not defined

6

Queued RT Signals %value%%% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

not available

HP

not available

Linux

sar command

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

None.

Percentage Of Queued RT Signals

Represents the percentage of queued RT signals.

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

After every sample

>

not defined

not defined

6

Queued RT Signals %value%%% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

not available

HP

not available

Linux

sar command

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

None.

Percentage Of Used File Handles

Represents the percentage of used file handles against the maximum number of file handles that the Linux kernel can allocate.

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

After every sample

>

not defined

not defined

6

Used File Handles %value%%%, has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

not available

HP

not available

Linux

sar command

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

None.

Process Table Overflow Occurrences

Represents the number of times the process table overflowed, that is, the number of times the OS could not find any process table entries in a five-second interval.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

User Action

None.

Size of Inode Table

Represents the current size of the inode table.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

sar command

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

User Action

None.

Size of Process Table

Represents the current size of the process table.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

sar command

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

Processors

The Processors metric monitors the state of each CPU in the host.

This metric is available only on Dell Poweredge Linux Systems.

Family

Represents the family of the Dell processor devices.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: processorDeviceFamily (1.3.6.1.4.1.674.10892.1.1100.30.1.10)

User Action

None.

Manufacture

Represents the name of the manufacturer of the Dell processor.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: processorDeviceManufacturerName (1.3.6.1.4.1.674.10892.1.1100.30.1.8)

User Action

None.

Processor Status

Represents the status of the Dell processor device.

This metric is available only on Dell Poweredge Linux Systems.

The following table lists the possible values for this metric and their meaning.

Metric Value

Meaning (per SNMP MIB)

1

Other (not one of the following)

2

Unknown

3

Normal

4

Warning

5

Critical

6

Non-Recoverable

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

Not Uploaded

>=

4

5

1

Status of Processor %ProcessorIndex% in chassis %ChassisIndex% is %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 unique combination of "Chassis Index" and "Processor Index" objects.

If warning or critical threshold values are currently set for any unique combination of "Chassis Index" and "Processor Index" 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 "Chassis Index" and "Processor Index" objects, use the Edit Thresholds page.

Data Source

SNMP MIB object: processorDeviceStatus (1.3.6.1.4.1.674.10892.1.1100.30.1.5)

User Action

None.

Speed (MHz)

Represents the current speed of the Dell processor device in MegaHertz (MHz). A value of zero indicates the speed is unknown.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: processorDeviceCurrentSpeed (1.3.6.1.4.1.674.10892.1.1100.30.1.12)

User Action

None.

Version

Represents the version of the Dell processor.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: processorDeviceVersionName (1.3.6.1.4.1.674.10892.1.1100.30.1.16)

User Action

None.

Program Resource Utilization

The Program Resource Utilization metric provides flexible resource monitoring functionality. The operator must specify the criteria for the programs to be monitored by specifying key value specific thresholds. Values for the key value columns {program name, owner} define the unique criteria to be monitored for resource utilization in the system.

By default, no programs will be tracked by this metric. Key Values entered as part of a key value specific threshold setting define the criteria for monitoring and tracking.

List of PIDs

This metric is only available on Solaris.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

ps command

HP

ps command

Linux

ps command

HP Tru64

ps command

IBM AIX

ps command

Windows

ps command

User Action

None.

Program's Max CPU Time Accumulated (Minutes)

Represents the maximum CPU time accumulated by the most active process matching the {program name, owner} key value criteria.

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

After Every Sample

>

Not Defined

Not Defined

3

%prog_max_cpu_time_pid% process running program %prog_name% has accumulated %prog_max_cpu_time% minutes of cpu time. This duration 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 unique combination of "Program Name" and "Owner" objects.

If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" 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 "Program Name" and "Owner" objects, use the Edit Thresholds page.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

ps command

HP

ps command

Linux

ps command

HP Tru64

ps command

IBM AIX

ps command

Windows

not available

User Action

None.

Program's Max CPU Utilization (%)

Represents the maximum percentage of CPU utilized by a single process matching the {program name, owner} key value criteria since last scan.

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

After Every Sample

>

Not Defined

Not Defined

3

Process %prog_max_cpu_util_pid% matched by the program name ''%prog_name%'' and owner ''%owner%'' is utilizing %prog_max_cpu_util%%% of the cpu. It has 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 unique combination of "Program Name" and "Owner" objects.

If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" 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 "Program Name" and "Owner" objects, use the Edit Thresholds page.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

ps command

HP

ps command

Linux

ps command

HP Tru64

ps command

IBM AIX

ps command

Windows

not available

User Action

None.

Program's Max Process Count

Fetches the current number of processes matching the {program name, owner} key value criteria. It can be used for setting warning or critical thresholds to monitor for maximum number of processes that a given {program name, owner} key value criteria crosses.

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

After Every Sample

>

Not Defined

Not Defined

3

%prog_max_process_count% processes are matched by the program name ''%prog_name%'' and owner ''%owner%''. They have 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 unique combination of "Program Name" and "Owner" objects.

If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" 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 "Program Name" and "Owner" objects, use the Edit Thresholds page.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

ps command

HP

ps command

Linux

ps command

HP Tru64

ps command

IBM AIX

ps command

Windows

not available

User Action

None.

Program's Max Resident Memory (MB)

Represents the maximum resident memory occupied by a single process matching the {program name, owner} key value criteria. It can be used for setting warning or critical thresholds to monitor for maximum value a given {program name, owner} key value criteria crosses.

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

After Every Sample

>

Not Defined

Not Defined

3

Process %prog_max_rss_pid% matched by the program name ''%prog_name%'' and owner ''%owner%'' is utilizing %prog_max_rss% (MB) of resident memory. It has 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 unique combination of "Program Name" and "Owner" objects.

If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" 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 "Program Name" and "Owner" objects, use the Edit Thresholds page.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

ps command

HP

ps command

Linux

ps command

HP Tru64

ps command

IBM AIX

ps command

Windows

not available

User Action

None.

Program's Min Process Count

Fetches the current number of processes matching the {program name, owner} key value criteria. It can be used for setting warning or critical thresholds to monitor for minimum number of processes that a given {program name, owner} key value criteria should never go under.

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

After Every Sample

<

Not Defined

Not Defined

3

%prog_min_process_count% processes are matched by the program name ''%prog_name%'' and owner ''%owner%''. They have fallen below warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Program Name" and "Owner" objects.

If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" 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 "Program Name" and "Owner" objects, use the Edit Thresholds page.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

ps command

HP

ps command

Linux

ps command

HP Tru64

ps command

IBM AIX

ps command

Windows

not available

User Action

None.

Program's Total CPU Time Accumulated (Minutes)

Represents the total CPU time accumulated by all active process matching the {program name, owner} key value criteria.

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

After Every Sample

>

Not Defined

Not Defined

3

%prog_max_process_count% processes matched by the program name ''%prog_name%'' and owner ''%owner%'' have accumulated %prog_total_cpu_time% minutes of cpu time. This duration has 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 unique combination of "Program Name" and "Owner" objects.

If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" 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 "Program Name" and "Owner" objects, use the Edit Thresholds page.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

ps command

HP

ps command

Linux

ps command

HP Tru64

ps command

IBM AIX

ps command

Windows

not available

User Action

None.

Program's Total CPU Utilization (%)

Represents the percentage of CPU time utilized by all active process matching the {program name, owner} key value criteria 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.

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

After Every Sample

>

Not Defined

Not Defined

3

%prog_max_process_count% processes matched by the program name ''%prog_name%'' and owner ''%owner%'' are utilizing %prog_total_cpu_util%%% of the cpu. It has 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 unique combination of "Program Name" and "Owner" objects.

If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" 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 "Program Name" and "Owner" objects, use the Edit Thresholds page.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

ps command

HP

ps command

Linux

ps command

HP Tru64

ps command

IBM AIX

ps command

Windows

not available

User Action

None.

Remote Access Card

The Remote Access Card metric monitors the status of the Remote Access Card.

This metric is available only on Dell Poweredge Linux Systems.

DHCP Settings

Determines whether the dynamic host configuration protocol (DHCP) was used to obtain the network interface card (NIC) information.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: remoteAccessNICCurrentInfoFromDHCP (1.3.6.1.4.1.674.10892.1.1700.10.1.33)

User Action

None.

Gateway Address

Represents the IP address for the gateway currently being used by the onboard network interface card (NIC) provided by the remote access (RAC) hardware.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: remoteAccessNICCurrentGatewayAddress (1.3.6.1.4.1.674.10892.1.1700.10.1.32)

User Action

None.

IP Address

Provides the internet protocol (IP) address currently being used by the onboard network interface card (NIC) provided by the remote access (RAC) hardware.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: remoteAccessNICCurrentIPAddress (1.3.6.1.4.1.674.10892.1.1700.10.1.30)

User Action

None.

LAN Settings

Represents the local area network (LAN) settings of the remote access hardware.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: remoteAccessLANSettings (1.3.6.1.4.1.674.10892.1.1700.10.1.15)

User Action

None.

Network Mask Address

Represents the subnet mask currently being used by the onboard network interface card (NIC) provided by the remote access (RAC) hardware.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: remoteAccessLANSettings (1.3.6.1.4.1.674.10892.1.1700.10.1.15)

User Action

None.

Product Name

Represents the name of the product providing the remote access (RAC) functionality.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: remoteAccessProductInfoName (1.3.6.1.4.1.674.10892.1.1700.10.1.7)

User Action

None.

Remote Access Card State

Represents the state of the remote access (RAC) hardware.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: remoteAccessStateSettings (1.3.6.1.4.1.674.10892.1.1700.10.1.5)

User Action

None.

Remote Access Card Status

Represents the status of the remote access (RAC) hardware.

This metric is available only on Dell Poweredge Linux Systems.

The following table lists the possible values for this metric and their meaning.

Metric Value

Meaning (per SNMP MIB)

1

Other (not one of the following)

2

Unknown

3

Normal

4

Warning

5

Critical

6

Non-Recoverable

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

Not Uploaded

>=

4

5

1

Status of Remote Access Card is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

SNMP MIB object: remoteAccessStatus (1.3.6.1.4.1.674.10892.1.1700.10.1.6)

User Action

None.

Version

Represents the version of the product providing the remote access (RAC) functionality.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: remoteAccessVersionInfoName (1.3.6.1.4.1.674.10892.1.1700.10.1.9)

User Action

None.

Response

This metric provides the status of the host, that is, whether it is up or down.

Status

The metric indicates whether the host is reachable or not. A host could be unreachable due to various reasons. The network is down or the Management Agent on the host is down (which could be because the host itself is shutdown).

Storage Summary Metrics

The Storage Summary metrics collectively represent the summary of storage data on a host target. These metrics are derived from the various metrics collected and uploaded into the Oracle Management Repository by the Management Agent. They are computed every time the Management Agent populates the Management Repository with storage data. This collection is also triggered automatically whenever the user manually refreshes the host storage data from the Storage Details page.

ASM Storage Allocated (GB)

Represents the total storage allocated to Oracle databases from Automatic Storage Management (ASM) instances on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

ASM Storage Metric Collection Errors

Represents the number of metric collection errors attributed to the storage related metrics of the Automatic Storage Management (ASM) targets on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

ASM Storage Overhead (GB)

Represents the storage overhead of Automatic Storage Management (ASM) targets on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

ASM Storage Unallocated (GB)

Represents the storage available in Automatic Storage Management (ASM) targets on the host for allocating to databases.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Databases Storage Free (GB)

Represents the total free storage available in the databases on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Databases Storage Metric Collection Errors

Represents the metric collection errors of storage related metrics of databases on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Databases Storage Used (GB)

Represents the total free storage available in the databases on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Disk Storage Allocated (GB)

Represents the storage allocated from the total disk storage available on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Disk Storage Unallocated (GB)

Represents the storage that is available for allocation in disks on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Host Storage Metric Collection Errors

Represents the total number of storage related metric collection errors of the host target.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Hosts Summarized

The possible values for this metric are:

- 1 (one) if this host storage was computed successfully (sometimes with partial errors)

- 0 (zero) if the storage computation did not proceed at all due to some reasons (for example, failure to collect critical storage metric data).

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Local File Systems Storage Free (GB)

The total free storage in all distinct local file systems on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Local File Systems Storage Used (GB)

The total used space in all distinct local file systems on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Number of ASM Instances Summarized

Represents the total number of Automatic Storage Management (ASM) instances, the storage data of which was used in computing storage summary of this host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Number of Databases Summarized

Represents the total number of databases, the storage data of which was used in computing storage summary of this host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Other Mapping Errors

Represents the storage metric mapping issues on the host excluding the unmonitored server mapping errors.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Total Number of ASM Instances

Represents the total number of Automatic Storage Management (ASM) instances on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Total Number of Databases

Represents the total number of databases on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Total Storage Allocated (GB)

Represents the total storage allocated from the host-visible storage available on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Total Storage Free (GB)

Represents the free storage available from the total allocated storage on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Total Storage Overhead (GB)

Represents the overhead associated with storage on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Total Storage Unallocated (GB)

Represents the total unallocated storage on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Total Storage Used (GB)

Represents the total storage used in the file systems and databases on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Unmonitored NFS Server Mapping Errors

Represents the total number of storage mapping issues that result from unmonitored Network File Systems (NFS) servers.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Volumes Storage Allocated (GB)

Represents the total storage allocated from the volumes available on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Volumes Storage Overhead (GB)

Represents the storage overhead in the volumes on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Volumes Storage Unallocated (GB)

Represents the storage available for allocation in the volumes on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Writeable NFS Storage Free (GB)

Represents the total free space available in all distinct writeable NFS mounts on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Writeable NFS Storage Used (GB)

Represents the storage used in all writeable NFS mounts on the host.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 24 hours or when the user manually refreshes storage data from the Storage Details page.

Data Source

These metrics are available on the Linux and Solaris hosts.

User Action

For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.

Storage Support

This metric is used to decide if the OS being monitored is supported or not. Its also used to inform the user if the number of Storage entities (Disks / FileSystems /Volumes) being monitored is within the applicable limits so as not to affect the performance of the Management Agent.

Supported

The metric is used to enable/disable the collection, depending on the OS supported or the number of storage entities being monitored.

The operating systems supported are Linux, Solaris, AIX, and HPUX.

The maximum number of storage entities monitored is set to 100 in the configuration file located in EMAgent/sysman/emd/emagent_storage.config. The Disks/Files/Volumes to be monitored can be added in the configuration file. If the storage entities are more than 100, the response time of the Management Agent increases.

Data Source

Not available

User Action

Edit the configuration file (emagent/sysman/emd/emagent_storage.config), and add the Disks, Filesystems, and Volumes to be monitored.

Swap Area Status

The Swap Area Status metric provides the status of the swap memory on the system.

Swap Free

Represents the number of 1K blocks in swap area that is not allocated.

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

After Every Sample

<

Not Defined

Not Defined

1

Swap Free Size %value% has gone below the warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Swap File" object.If warning or critical threshold values are currently set for any "Swap File" 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 "Swap File" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

swap

HP

swapinfo

Linux

/proc/swaps

HP Tru64

swapon

IBM AIX

lsps

Windows

not available

User Action

Check the swap usage using the UNIX top command or the Solaris swap -l command. Additional swap can be added to an existing file system by creating a swap file and then adding the file to the system swap pool. (See documentation for your UNIX OS). If swap is mounted on /tmp, space can be freed by removing any junk files in /tmp. If it is not possible to add file system swap or free up enough space, additional swap will have to be added by adding a raw disk partition to the swap pool. See UNIX documentation for procedures.

Swap Size

Represents the size of the swap file.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

swap

HP

swapinfo

Linux

/proc/swaps

HP Tru64

swapon

IBM AIX

lsps

Windows

not available

User Action

None.

Switch/Swap Activity

The Switch/Swap Activity metric displays the metric reports on the system switching and swapping activity.

Process Context Switches (per second)

Number of process context switches per second

Metric Summary

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

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

After Every Sample

>

Not Defined

Not Defined

6

Process Context Switches (per second) %value% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

not available

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

Swapins Transfers (per second)

Represents the number of 512-byte units transferred for swapins per second.

Metric Summary

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

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

After Every Sample

>

Not Defined

Not Defined

6

Swapins Transfers (per second) %value% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

sar command

HP Tru64

not available

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

Swapout Transfers (per second)

Represents the number of 512-byte units transferred for swapouts per second.

Metric Summary

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

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

After Every Sample

>

Not Defined

Not Defined

6

Swapins Transfers (per second) %value% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

sar command

HP Tru64

not available

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

System Swapins (per second)

Represents the number of process swapins per second.

Metric Summary

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

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

After Every Sample

>

Not Defined

Not Defined

6

System Swapins (per second) %value% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

sar command

HP Tru64

not available

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

System Swapouts (per second)

Represents the number of process swapouts per second.

Metric Summary

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

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

After Every Sample

>

Not Defined

Not Defined

6

System Swapouts (per second) %value% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

sar command

HP Tru64

not available

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

System BIOS

The System BIOS (Basic Input/Output System) metric monitors the BIOS status for Dell Poweredge Linux systems.

Manufacturer

Represents the manufacturer's name of the System BIOS (Basic Input/Output System). This metric is available only on Dell Poweredge Linux Systems.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: systemBIOSManufacturerName (1.3.6.1.4.1.674.10892.1.300.50.1.11)

User Action

None.

Size

Represents the image size of the System BIOS (Basic Input/Output System) in kilobytes. A value of zero indicates that the size is unknown. This metric is available only on Dell Poweredge Linux Systems.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: systemBIOSSize (1.3.6.1.4.1.674.10892.1.300.50.1.6)

User Action

None.

System BIOS Status

Represents the status of the System BIOS (Basic Input/Output System) in this chassis.

This metric is available only on Dell Poweredge Linux Systems.

The following table lists the possible values for this metric and their meaning.

Metric Value

Meaning (per SNMP MIB)

1

Other (not one of the following)

2

Unknown

3

Normal

4

Warning

5

Critical

6

Non-Recoverable

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

Not Uploaded

>=

4

5

1

Status of BIOS %BiosIndex% in chassis %ChassisIndex% is %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 unique combination of "Chassis Index" and "System BIOS Index" objects.

If warning or critical threshold values are currently set for any unique combination of "Chassis Index" and "System BIOS Index" 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 "Chassis Index" and "System BIOS Index" objects, use the Edit Thresholds page.

Data Source

SNMP MIB object: systemBIOSStatus (1.3.6.1.4.1.674.10892.1.300.50.1.5)

User Action

None.

Version

Represents the version name of the System BIOS (Basic Input/Output System). This metric is available only on Dell Poweredge Linux Systems.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: systemBIOSVersionName (1.3.6.1.4.1.674.10892.1.300.50.1.8)

User Action

None.

System Calls

The System Calls metric provides statistics about the system calls made over a five-second interval.

Characters Transferred by Read System Calls (per second)

Represents the number of characters transferred by read system calls (block devices only) per second.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

Characters Transferred by Write System Calls (per second)

Represents the number of characters transferred by write system calls (block devices only) per second.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

exec() System Calls (per second)

Represents the number of exec() system calls made per second.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

fork() System Calls (per second)

Represents the number of fork() system calls made per second.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

read() System Calls (per second)

Represents the number of read() system calls made per second.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

System Calls (per second)

Represents the number of system calls made per second. This includes system calls of all types.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

write() System Calls (per second)

Represents the number of write() system calls made per second.

Data Source

The data sources for the metrics in this category include the following:

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.

User Action

None.

Temperature

The Temperature metric monitors the hotness or coldness of the temperature probe.

This metric is available only on Dell Poweredge Linux Systems.

Current Temperature

Represents the current reading of the temperature probe. The value is representing temperature in tenths of degrees Centigrade.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: temperatureProbeReading (1.3.6.1.4.1.674.10892.1.700.20.1.6)

User Action

An abnormally high value indicates that the system is doing a lot of work and getting overheated. The system could be overheated due to inadequate cooling by the Fan.

Location

Provides a description of the location name of the temperature probe. Examples of values are: "CPU Temp" and "System Temp".

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

SNMP MIB object: temperatureProbeLocationName (1.3.6.1.4.1.674.10892.1.700.20.1.8)

User Action

None.

Temperature Probe Status

Represents the status of the temperature probe.

This metric is available only on Dell Poweredge Linux Systems.

The following table lists the possible values for this metric and their meaning.

Metric Value

Meaning (per SNMP MIB)

1

Other (not one of the following)

2

Unknown

3

Normal

4

Warning

5

Critical

6

Non-Recoverable

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

Not Uploaded

>=

4

5

1

Temperature at probe %ProbeIndex% in chassis %ChassisIndex% is %TemperatureReading% (C). Status is %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 unique combination of "Chassis Index" and "Temperature Probe Index" objects.

If warning or critical threshold values are currently set for any unique combination of "Chassis Index" and "Temperature Probe Index" 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 "Chassis Index" and "Temperature Probe Index" objects, use the Edit Thresholds page.

Data Source

SNMP MIB object: temperatureProbeStatus (1.3.6.1.4.1.674.10892.1.700.20.1.5)

User Action

This describes the status of the temperature probe. A failed probe needs to be physically examined or replaced.

TTY Activity

This metric reports tty device activity.

Incoming Character Interrupts (per second)

Represents the number of received incoming character interrupts per second.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Seconds

Data Source

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

User Action

None.

Input Characters Processed by canon()

Represents the input characters processed by canon() per second.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Seconds

Data Source

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

User Action

None.

Modem Interrupt Rate (per second)

Represents the modem interrupt rate.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Seconds

Data Source

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

User Action

None.

Outgoing Character Interrupts (per second)

Represents the number of transmit outgoing character interrupts per second.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Seconds

Data Source

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

User Action

None.

TTY Output Characters (per second)

Represents the number of output characters per second.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Seconds

Data Source

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

User Action

None.

TTY Raw Input (chars/s)

Represents the raw input characters per second.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Seconds

Data Source

Host

Data Source

Solaris

sar command

HP

sar command

Linux

not available

HP Tru64

table() system call

IBM AIX

sar command

Windows

not available

The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.

User Action

None.

User Defined Metrics

The UDM metric allows you to execute your own scripts. The data returned by these scripts can be compared against thresholds and generate severity alerts similar to alerts in predefined metrics. UDM is similar to the Oracle9i Management Agent's UDE functionality.

User Defined Numeric Metric

Contains a value if the value type is NUMBER. Otherwise, the value is "", if the value is STRING.

Data Source

User defined script.

User Action

None.

User Defined String Metric

Contains a value if the value type is STRING. Otherwise, the value is "", if the value is NUMBER.

Data Source

User defined script.

User Action

None.

Users

The Users metric provides information about the users currently on the system being monitored.

Number of Logons

Represents the number of times a user with a certain user name is logged on to the host target.

Data Source

For Solaris, HP, Linux, HP Tru64, and IBM AIX, the number of times a user is logged on is obtained from the OS w command.

For Windows, the source of information is Windows API.

User Action

None.

Windows Events Log

The purpose of this metric is to collect those entries from all available Windows NT event log files whose type is either Error or Warning. A critical or a warning alert is raised only for System and Security Event log file entries.

Note: Since log files continue to grow, this metric outputs log events which had been written to the log file after the last collection time, that is, only those records are written out whose timeGenerated (time when the event was generated) is after the last collection time until the last record of the log file. If this metric is collected for the first time, only the events generated on the current date are outputted.

This metric is available only on Windows.

Category

List of all categories for the events matching Log Name, Source, and Event ID defined for the monitored object. The actual category of the event can be found in the Windows event log message.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 15 Minutes

Data Source

Windows Management Instrumentation (WMI)

User Action

None.

Date-Time

This is the time at which point the metric scanned through the event logs. This metric is available only on Windows.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 15 Minutes

Data Source

Windows Management Instrumentation (WMI)

User Action

None.

Windows Event Log Message

This metric is a digest of all the events that match the Log Name, Source, and Event ID specified for the monitored object. After the above filtering is done, grouping of these events is done on Log Name, Source, Event ID, Category, and User to get the count of error events and warning events. The column has the details of the events in the following format:

[LogName: Source:Event ID:Category:User : :]

Example: [Application:Symantec AntiVirus:2: : :error=2:] [Application:Symantec AntiVirus:3: : ::warning =1 ]

To get the exact message about the events that satisfied the criteria set on the monitored object, the Event viewer provided by Microsoft Windows must be used.

This metric is available only on Windows.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 15 Minutes

Data Source

Windows Management Instrumentation (WMI)

User Action

None.

Event ID

This is the Perl pattern to match the string defined for the Event ID in the monitored objects. The actual Event ID of the event can be found in the Windows event log message. This metric is available only on Windows.

Metric Summary

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

Target Version

Collection Frequency

3.0 and higher

Every 15 Minutes

Data Source

Windows Management Instrumentation (WMI)

User Action

None.

Windows Event Severity

The seriousness of the event. Possible values are: Warning and Error.

This metric is available only on Windows.

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

Key

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

logfile: "system"

Every 15 Minutes

After Every Sample

=

warning

error

1*

X1User[%user%]:Category[%categorystring%]:Description[%message%]

* 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 "Log Name", "Source", and "Event ID" objects.

If warning or critical threshold values are currently set for any unique combination of "Log Name", "Source", and "Event ID" 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 "Log Name", "Source", and "Event ID" objects, use the Edit Thresholds page.

Data Source

WMI Operating System Classes

User Action

None.

Zombie Processes

The Zombie Processes metric monitors the orphaned processes in the different variations of UNIX systems.

% of Processes in Zombie State

Represents the percentage of all processes running on the system that are currently in zombie state.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

ps command

HP

ps command

Linux

ps command

HP Tru64

ps command

IBM AIX

ps command

Windows

ps command

User Action

None.

Processes in Zombie State (%)

Represents the percentage of all processes running on the system that are currently in zombie state.

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

After Every 60 Samples

>

35

50

1

%value%%% of all processes are in zombie state, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold.

Data Source

The data sources for this metric include the following:

Host

Data Source

Solaris

ps command

HP

ps command

Linux

ps command

HP Tru64

not available

IBM AIX

not available

Windows

not available

User Action

None.

Infiniband Network

These metrics provide details on the throughput performance of each link (port-to-port connection) in the network, an aggregation of performance for Switch-to-Node and Switch-to-Switch link types, and total throughput performance of the network.

Linked Throughput

This is the throughput performance of each link (switch port to node/switch port connection) in the network

Switch GUID

This is the globally unique identifier of the switch in this link (the first switch, if both end points are switches).

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, perfquery

User Action

No user action is required.

Port Number

This is the port number of the switch in this link (the first switch, if both end points are switches).

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, perfquery

User Action

No user action is required.

Link Type

This is either Switch-to-Switch or Switch-to-Node

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, perfquery

User Action

No user action is required.

Throughput

This is the number of GB sent and received over this link in the last collection interval, divided by the duration of the last collection interval (Gbps).

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, perfquery

User Action

No user action is required.

Infiniband Switch

These metrics describe the performance of each port of the switch and the aggregation of performance for Switch-to-Node and Switch-to-Switch link types. They also define whether a switch is a subnet manager for the network or not. Switch statistics are also covered.

Port Performance

Performance of each port of the switch

Port Number

This is the port number of this switch in this link

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Connected to GUID

This is the globally unique identifier to which this port is connected

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Connected to Type

This is the type of the entity to which this port is connected (for example, compute node, cell or switch)

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Connected to GUID Type

f the port is connected to a switch, the GUID in "Connected to GUID" column is the switch GUID, else if the port is connected to a node, the GUID is the port GUID of the port on the node.

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Connected to Port Number

This is the port number of the entity to which this switch port is connected.

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Supported Speed

This is the supported speed of this link (Gbps).

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Supported Width

This is the supported width of this link (for example, 1X or 4X)

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Enabled Speed

This is the enabled speed of this link (Gbps).

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Enabled Width

This is the enabled width of this link (for example, 1X or 4X)

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Active Speed

This is the active speed of this link (Gbps)

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Active Width

This is the active width of this link (for example, 1X or 4X)

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Link Degraded

This is the ink speed or width is less than the enabled speed or width respectively, the link is operating in degraded mode

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

By default, warning alert is issued if the link becomes degraded. User needs to evaluate the impact of this link on the performance of the database machine, and take appropriate steps to restore the link to normal speed/width.

Link State

This shows whether the link is up or down.

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Physical Link State

This shows whether the physical link is up or down.

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Throughput

This shows the number of GB sent and received over this link in the last collection interval, divided by the duration of the last collection interval (Gbps)

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Symbol Errors

This shows the number of errors of this type in the last collection interval.

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Link Recovers

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Link Downed

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Received Errors

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Received Remote Physical Errors

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Received Switch Relay Errors

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Transmitted Packets Discarded

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Transmitted Packets Constraint Errors

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Received Constraint Errors

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Link Integrity Errors

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Excess Buffer Overrun Errors

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

VL15 Dropped Errors

This shows the number of errors of this type in the last collection interval

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

No user action is required.

Total Errors

This is the total number of errors in the last collection interval

Metric Summary for Database Control

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

iblinkinfo.pl, ibportstate, perfquery

User Action

Set some threshold above which the number of errors is deemed high enough to merit scrutiny of potential impact on throughput performance

3 OMS and Repository

The OMS and Repository, Oracle Management Service, OMS Console, and OMS Platform targets expose metrics that are useful for monitoring the Oracle Enterprise Manager Management Service (OMS) and Management Repository.

Active Loader Status

This category provides information on Loader usage and performance, including throughput and rows processed in last hour.

Rows Processed in the Last Hour

This is the number of rows processed.

Data Source

The mgmt_system_performance_log table in the Management Repository.

User Action

If this number continues to rise over time, then the user may want to consider adding another Management Service or increasing the number of loader threads for this Management Service. To increase the number of loader threads, add or change the em.loader.threadPoolSize entry in the emoms.properties file. The default number of threads is 2. Values between 2 and 10 are common.

Total Loader Runtime in the Last Hour (seconds)

This is the amount of time in seconds that the loader thread has been running in the past hour.

Data Source

The mgmt_system_performance_log table in the Management Repository.

User Action

If this number is steadily increasing along with the Loader Throughput (rows per hour) metric, then perform the actions described in the User Action section of the help topic for the Loader Throughput (rows per hour) metric. If this number increases but the loader throughput does not, check for resource constraints, such as high CPU utilization by some process, deadlocks in the Management Repository database, or processor memory problems.

Active Management Servlets

This category of metrics provides information on Active Management Servlets Category.

Notifications Processed

The total number of notifications delivered by the Management Service over the previous 10 minutes. The metric is collected every 10 mins and no alerts will be generated.

Data Source

The mgmt_system_performance_log table in the Management Repository.

User Action

If the number of notifications processed is continually increasing over several days, then you may want to consider adding another Management Service.

Page Hits (per minute)

This indicates average number of EM console accesses in a minute. The metric is collected every 10 mins and alerts will not be generated.

Data Source

This metric is obtained using the following query of the mgmt_oms_parameters table in the Management Repository.

SELECT value FROM mgmt_oms_parameters
where name='loaderOldestFile'

User Action

None.

Agent Status

This category of metrics provides information on the agent status.

Number of Agent Restarts

The number of times the agent has been restarted in the past 24 hrs.

Data Source

Derived by:

(SELECT t.target_name, COUNT(*) down_count
FROM mgmt_availability a, mgmt_targets t
WHERE a.start_collection_timestamp = a.end_collection_timestamp
AND a.target_guid = t.target_guid
AND t.target_type = MGMT_GLOBAL.G_AGENT_TARGET_TYPE
AND a.start_collection_timestamp > SYSDATE-1
GROUP BY t.target_name)

User Action

If this number is high, check the agent logs to see if a system condition exists causing the system to bounce. If an agent is constantly restarting, the Targets Not Uploading Data metric may also be set for targets on the agents with restart problems. Restart problems may be due to system resource constraints or configuration problems.

Configuration

This category of metrics provides information on configuration.

Number of Administrators

The number of administrators defined for Enterprise Manager.

Data Source

The mgmt_created_users table in the Management Repository.

Number of Groups

The number of groups defined for Enterprise Manager.

Data Source

The mgmt_targets table in the Management Repository.

User Action

If you have a problem viewing the All Targets page, you may want to check the number of roles and groups.

Number of Roles

The number of roles defined for Enterprise Manager.

Data Source

The mgmt_roles table in the Management Repository.

User Action

If you have a problem viewing the All Targets page, you may want to check the number of roles and groups.

Number of Targets

The number of targets defined for Enterprise Manager.

Data Source

The mgmt_targets table in the Management Repository.

User Action

This metric is informational only

Repository Tablespace Used

This is the total number of MB that the Management Repository tablespaces are currently using.

Data Source

The dba_data_files table in the Management Repository.

User Action

This metric is informational only.

Target Addition Rate (Last Hour)

The rate at which targets are being created. The target addition rate should be greatest shortly after EM is installed and then should increase briefly whenever a new agent is added. If the rate is increasing abnormally, you should check for abnormal agent or administrator activity and verify that the targets are useful. Check to see that group creation is not being over utilized.

Data Source

The metric is derived from the mgmt_target table, the current target count - target count at last sampling.

User Action

This metric is informational only.

Total Repository Tablespace

The total MB allocated to the Management Repository tablespaces. This will always be greater than or equal to the space used.

Data Source

The dba_free_space table in the Management Repository.

User Action

This metric is informational only.

User Addition Rate (Last Hour)

The rate at which users are being created. The target addition rate should be low. If the rate is increasing abnormally, you should check for abnormal administrator activity.

Data Source

The metric is derived from the mgmt_created_users table, the current user count - user count at last sampling.

User Action

This metric is informational only.

DBMS Job Status

This category of metrics provides information on the DBMS job status.

DBMS Job Invalid Schedule

This metric flags a DBMS job whose schedule is invalid. A schedule is marked 'Invalid' if it is scheduled for more than one hour in the past, or more than one year in the future. An invalid schedule means that the job is in serious trouble.

Data Source

The user_schedule_jobs table in the Management Repository.

User Action

None.

DBMS Job Processing Time (% of Last Hour)

The percentage of the past hour the job has been running.

Data Source

The mgmt_system_performance_log table in the Management Repository.

User Action

If the value of this metric is greater than 50%, then there may be a problem with the job. Check the System Errors page for errors reported by the job. Check the Alerts log for any alerts related to the job.

DBMS Job UpDown

The down condition equates to the dbms_job "broken" state. The Up Arrow means not broken.

Data Source

The broken column is from the all_users table in the Management Repository.

User Action

Determine the reason for the dbms job failure. Once the reason for the failure has been determined and corrected, the job can be restarted through the dbms_job.run command.

To determine the reason the dbms job failed, take the following steps (replacing myjob with the displayed name of the down job):

1. Copy down the DBMS Job Name that is down from the row in the table. This DBMS Job Name is 'yourDBMSjobname' in the following example.

2. Log onto the database as the repository owner.

3. Issue the following SQL statement:

select dbms_jobname
from mgmt_performance_names
where display_name='yourDBMSjobname';

4. If the dbms_jobname is 'myjob', then issue the following SQL statement:

select job
from all_jobs
where what='myjob';

5. Using the job id returned, look for ORA-12012 messages for this jobid in the alerts log and trace files and try to determine and correct the problem.

The job can be manually restarted through the following database command:

execute dbms_job.run (jobid);

DBMS Job Throughput Per Second

The number of notifications delivered per second, averaged over the past hour.

Data Source

The mgmt_system_performance_log table in the Management Repository.

User Action

This metric is informational only.

Incident

This category of metrics provides information on the Incident target

Alert Log Error Trace File

The alert log error trace file is the name of an associated server trace file generated when the problem generating this incident occurred. If no additional trace file was generated, this field will be blank.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 5 Minutes

Data Source

The alert log error trace file name is extracted from the database alert log.

User Action

The alert log error trace file name is provided so that the user can look in this file for more information about the problem that occurred.

Alert Log Name

The fully specified (includes directory path) name of the current XML alert log file.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

This name is retrieved by searching the OMS ADR_HOME/alert directory for the most recent (current) log file.

User Action

The alert log file name is provided so that the user can look in this file for more information about the problem that occurred.

Diagnostic Incident

A diagnostic incident is a single occurrence of a problem (critical error) that occurred in the OMS process while using Enterprise Manager.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

Text describing a diagnostic incident is extracted from the database alert log, which is an XML file stored in the Automatic Diagnostic Repository (ADR) that stores a chronological list of database messages and errors.

User Action

Diagnostic incidents usually indicate software errors and should be reported to Oracle using the Enterprise Manager Support Workbench.

ECID

The Execution Context ID (ECID) tracks requests as they move through the application server. This information is useful for diagnostic purposes because it can be used to correlate related problems encountered by a single user attempting to accomplish a single task.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The ECID is extracted from the database alert log.

User Action

Diagnostic incidents usually indicate software errors and should be reported to Oracle using the Enterprise Manager Support Workbench. When packaging problems using Support Workbench, the ECID will be used by Support Workbench to correlate and include any additional problems in the package.

Impact

An optional field (may be empty) assessing the impact of the problem that occurred.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The impact is extracted from the database alert log.

User Action

This field is purely informational. Diagnostic incidents usually indicate software errors and should be reported to Oracle using the Enterprise Manager Support Workbench.

Incident ID

The Incident ID is a number that uniquely identifies a diagnostic incident (single occurrence of a problem).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 15 Minutes

Data Source

The incident ID is extracted from the database alert log.

User Action

Diagnostic incidents usually indicate software errors and should be reported to Oracle using the Enterprise Manager Support Workbench. Problems are one or more occurrences of the same incident. Using Support Workbench, the incident ID can be used to select the correct Problem to package and send to Oracle. Using the command line tool ADRCI, the incident ID can also be used with the show incident command to get details about the incident.

Job Dispatcher Performance

This category of metrics provides information on the performance of job dispatcher.

Job Dispatcher Processing Time (% of Last Hour)

The job dispatcher is responsible for scheduling jobs as required. It starts up periodically and checks if jobs need to be run. If job dispatcher is running more than the threshold levels, then it is having problems handling the job load.

Data Source

This is the sum of the amount of time the job has run over the last hour from the mgmt_system_performance_log table in the Management Repository divided by one hour, multiplied by 100 to arrive at the percent.

User Action

This metric is informational only.

Job Steps Per Second

The number of job steps processed per second by the job dispatcher, averaged over the past hour and sampled every 10 minutes.

Data Source

The mgmt_job_execution table in the Management Repository.

User Action

This metric is informational only.

Active Agents

This category of metrics provides information on active agents.

Number of Active Agents

The number of active agents in the repository. If this number is 0, then Enterprise Manager is not monitoring any external targets. May be a problem if unexpected.

Data Source

The number of agents whose status is up in the mgmt_current_availability table.

User Action

If no agents are running, determine the reasons they are down, correct if needed and restart. Log files in the agent's $ORACLE_HOME/sysman/log directory can provide information about possible causes of agent shutdown.

Repository Collections Performance

This category of metrics provides information on the performance of repository collections. They are collected by background dbms jobs in the repository database called collection workers. Repository metrics are sub divided into long and short running metrics. These are called task classes (short task class and long task class). Some collection workers (Default 1) process the short task class and some (Default 1) process long task class. Repository collection performance metrics measure the performance data for repository metric collections for each task class. This metric is a repository metric and hence collected by the collection workers.

Collection Duration (seconds)

The total amount of time in seconds the collection workers were running in last 10 minutes. This is an indicator of the load on the repository collection subsystem. This could be due to two reasons, the number of collections have increased or some of the metrics are taking a long time to complete. This needs to be related with collections processed metric to find out if number of collections have increased or metrics are taking a long time.

Data Source

The data for this metrics come from entries in mgmt_system_performance log where job_name=MGMT_COLLECTION.Collection Subsystem.

Collections Processed

The total number of collections that were processed in the last 10 minutes.

Data Source

The data for this metrics come from entries in mgmt_system_performance log where job_name=MGMT_COLLECTION.Collection Subsystem

Collections Waiting To Run

The total number of collections that were waiting to run at the point this metric was collected. An increasing value would mean the collection workers are falling behind and would need to be increased. The collections waiting to run could be high initially on system startup and should ideally go down towards zero.

Data Source

The data for this metrics come from entries in mgmt_collection_tasks table which holds all the list of collections.

User Action

This metric is informational only.

Number of Collection Workers

The total number of workers that were processing the collections.

Data Source

The data for this metric come from entries in mgmt_collection_workers table.

User Action

This metric is informational only.

Total Throughput Across Collection Workers

The total number of collections per second processed by all the collection workers.

Data Source

The data for this metrics come from entries in mgmt_system_performance log where job_name=MGMT_COLLECTION.Collection Subsystem.

User Action

This metric is informational only.

Repository Job Dispatcher

This category of metrics provides information on the Repository Job Dispatcher.

Job Step Backlog

The number of job steps that were ready to be scheduled but could not be because all the dispatchers were busy.

When this number grows steadily, it means the job scheduler is not able to keep up with the workload.

User Action

This is the sum of job steps whose next scheduled time is in the past - job steps eligible to run but not yet running. If the graph of this number increases steadily over time, the user should take one of the following actions:

- Increase the em.jobs.shortPoolSize, em.jobs.longPoolSize and em.jobs.systemPoolSize properties in the web.xml file. The web.xml file specifies the number of threads allocated to process different types of job steps. The short pool size should be larger than the long pool size.

Property

Default Value

Recommended Value

Description

em.jobs.shortPoolSize

10

10 50

Steps taking less than 15 minutes

em.jobs.longPoolSize

8

8 - 30

Stars taking more than 15 minutes

em.jobs.systemPoolSize

8

8 - 20

Internal jobs (e.g. agent ping)

- Add another Management Service on a different host.

Check the job step contents to see if they can be made more efficient.

Repository Sessions

This category of metrics provides information on the Repository sessions.

Repository Session Count

A count of the number of sessions between the Management Service and Management Repository database.

Data Source

The gv$session system view.

User Action

This metric is informational only.

Response

This page indicates whether Enterprise Manager is up or down. It contains historical information for periods in which it was down.

Status

This metric indicates whether Enterprise Manager is up or down. If you have configured the agent monitoring the oracle_emrep target with a valid email address, you will receive an email notification when Enterprise Manager 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.

Table 3-1 Metric Summary Table

Target Version

Evaluation and Collection Frequency

Upload Frequency

Operator

Default Warning Threshold

Default Critical Threshold

Consecutive Number of Occurrences Preceding Notification

Alert Text

All Versions

Every 5 Minutes

Not Uploaded

=

Not Defined

0

1

%Message%

Data Source

sysman/admin/scripts/emrepresp.pl

User Action

This metric checks for the following:

- Is the Management Repository database up and accessible?
If the Management Repository database is down, start it. If 'Invalid Username or Password' error is displayed, verify that the name and password for the oracle_emrep target is the same as the repository owner's name and password.

- Is at least one Management Service running?
If a Management Service is not running, start one.

- Is the Repository Metrics dbms job running?
If the DBMS job is down or has an invalid schedule, it should be restarted by following the instructions in the User Action section of the help topic for the DBMS Job Bad Schedule metric.

Service Initialization Errors

This category provides information on any initialization errors encountered by services like loader or events.

Service Status

This metric is generated if any of the OMS services (such as Loader, Notification, or PingRecorder) failed to get initialized during the OMS startup. At present this metric is used only by Loader service.

This metric has two key columns and one non-key columns:

- The key columns are Management Service and Service Name. The key values uniquely identify the Service instance that has initialization errors.

- The non-key column is Service Status. This column indicates whether the Service is running fine or encountered an error during OMS startup.

4 Oracle Home Metrics

The oracle_home metrics provide description, collection statistics, data source, multiple thresholds (where applicable), and user action information for each metric.

Bugs Fixed by a Patch

A patch consists of one or more bug fixes. This metric collects all the bugs fixed within that patch applied on the Oracle Home.

Bug Number

Bug number in the patch. There can be multiple bugs fixed in a patch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Patch ID

Patch number which contains one or more bug fixes. The patch id may be the same for more that one patch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Patch Language

This is the language of the patch. Generally its "en" (English)

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Patch UPI

This is the Unique Patch Identifier. Some patches may have the same patch ID but different patch identifier. This will be used to issue patch advisories.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Component Dependency

A component within an Oracle Home might be dependent on another component. This metric collects the dependency information between the components within an Oracle Home.

Component Name

This is the internal name of the component installed in Oracle Home.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Component Version

This is the base version of component installed in Oracle Home.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Dependee Name

This is the internal name of the dependent component installed in the same or different Oracle Home.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Dependee Version

This is the base version of the dependent component installed in same or different Oracle Home.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Dependee Home GUID

This is the Home globally unique identifier of the Oracle Home where the dependent component is installed.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Component Install Type

Every component installed has its own install type. This information is created by the product installation and collected by this metric.

Component Name

This is the internal name of the component installed in Oracle Home.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Component Version

This is the base version of component installed in Oracle Home.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Name ID

This is install type Name ID.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Description ID

This is the install type Description ID.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Install Type Name

This is the type of install (Examples - Basic, EE etc)

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

CRS Node list

This metric collects the node information on the nodes that participate in the cluster installation.

Node

Node hostname which constitute the nodes in the CRS cluster

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Files affected by a Patch

Each patch affects one or more components and each component is made up of many files. This metric collects information on various files which are affected by the application of this patch to the Oracle Home.

Component Name

Internal name of the component installed in Oracle Home.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Component Version

Base version of the component installed in Oracle Home.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

File Name

Name of file affected by Patch

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Patch ID

Patch number which contains one or more bug fixes

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Patch Language

Language of patch. Generally its "en" (English).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Patch UPI

Unique Patch Identifier. Some patches may have the same patch id but different patch identifier. This will be used to issue patch advisories.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Oracle Home Clone Properties

This metric collects all the properties which are later used in cloning and provisioning that Oracle Home.

Property Name

This is the name of the property used for cloning

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Property Value

This is the clone property value.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Oracle Home Components

An Oracle Home installation consists of many components. This metric collects details of all the components installed, including their version and installation date.

Component Name

Internal name of the component installed in Oracle Home.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Component Version

This is the base version of component installed in Oracle Home

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Current Version

The current updated version of the component. The version of the component can be updated by "Patchset Updates" or "Patchsets"

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Description

This is a brief description of the component.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

External Name

This is the external name of the component.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Installed Location

This is the location where the component is installed.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Installer Version

This is the version of the installer used at the time of installation.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Install Time

This is the date and time when the installation was done.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Is Top Level

Is that a top level component [0/1]. There is at least one top level component in any Oracle Home.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Languages

This is a list of the languages supported by the component installation.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Minimum Deinstaller Version

The minimum OUI installer to be used to deinstall the component.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Oracle Home Dependency

Earlier versions of OUI (installer) permitted one component within an Oracle Home to be dependent on another component in another Oracle Home. This metric collects that dependency information.

Dependee Home Location

In case of inter dependency between Oracle Home, the location of other Oracle Home.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Oracle Home Info

This metric collects all generic properties for that Oracle Home like ARUID, is Oracle Home clonable?, is the Oracle Home readable? OUI_ID for that Oracle Home.

ARU ID

ARU ID of the Oracle Home installation. This is used to determine the platform and version of Operating System while issuing patch advisories from ARU.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Home Location

This is the complete path to where Oracle Home is installed.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Home Base

This is the middleware home (in the case of fusion app products) and composite home location (in the case of members of composite homes). A composite home is the location where the core and plug-in Oracle Homes are installed.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Home Size

Estimated size of Oracle Home as in inventory measured in kilobytes.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Home Type

This is the Oracle Home type. Its "O" for OUI installed Oracle Homes and "W" for Weblogic homes.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Inventory

This is the Central inventory location where the Oracle Home is registered.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Is Clonable

This shows whether this home is clonable or not. Weblogic Homes are always clonable, OUI installed Oracle Homes are clonable if all the components inside that Oracle Home are clonable.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Is CRS

This shows whether this is a CRS installation [0/1].

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

OH Group

This is the operating system group name of the user who installed the Oracle Home.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

OH Group ID

This is the operating system group ID of the user who installed the Oracle Home.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

OH Owner

This is the operating system owner name of the user who installed the Oracle Home.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

OH Owner Groups

All the operating system group names to which the user belongs.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

OH Owner Groups ID

All the operating system group IDs to which the user belongs.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

OH Owner ID

This is the operating system owner ID of the user who installed the Oracle Home.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Oracle Base

This is the Oracle Base where Oracle Homes are installed.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

OUI Home GUID

This is the OUI Oracle Home Globally unique identifier. This is unique across all Oracle Product Installations.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

OUI Home Name

This is the readable name of Oracle Home.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

OUI Platform ID

This is the Patform ID of an Oracle Home. This was used in releases 10.1 or earlier. This has been replaced with ARU_ID, still useful for older installations.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Oracle Patch

This metric collects all the patches which have been applied to the Oracle Home.

Description

This is a description of a Patch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Install Time

This is the installation time when the patch was installed.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Installer Version

This is the OUI installer used for the installation of the patch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Is PSU

Is it a Patchset Update? Patchset Updates are just like onoffs, but they can change the minor version of the component

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Is Rollbackable

This show whether the patch can be rolled back [0/1].

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Patch ID

This is the Patch number which contains one or more bug fixes. This ID may be the same for more than one patch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Patch Language

Language of patch. Generally its "en" (English)

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Patch UPI

This is the Unique Patch Identifier. Some patches may have the same patch ID, but different patch identifiers. This will be used to issue patch advisories.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Profile

The profile name is only used for fusion app patches

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

XML Inventory Location

This is the patch xml inventory location in the Oracle Home.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Oracle Patchsets

Oracle Patchset consists of many PS_Patches for each component (also called as Versioned Patch). Patchsets are always cumulative; that is all the components within the patchset have the bumped up version number after the application of that patchset. This metric collects that information.

Description

This is a brief description of the Patchset. A patchset contains one of more versioned patches.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

External Name

This is the external name of the Patchset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Installer Version

This is the OUI installer version used for the installation of the patchset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Install Time

This is the installation time of the Patchset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Inventory Location

This is the inventory location of the patchset.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Minimum Deinstaller Version

This is the minimum OUI installer version to be used for deinstalling the versioned patch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Patchset Name

This is the Internal name of the patchset

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Patchset Version

This is the patchset version.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Oracle Versioned Patch

An Oracle Patchset consists of many Versioned Patches corresponding to various components within that Oracle Home. This metric collects information of all the components affected by the patchset and their versions.

Base Component Version

This is the base component version, on which the Versioned Patch is applied.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Description

This is a brief description of the versioned patch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

External Name

This is the external name of the versioned patch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Installed Location

This is the path showing where the versioned patch is installed.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Installer Version

This is the OUI installer version used at the time of installation.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Install Time

This is the time when the versioned patch was installed.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Languages

This lists the languages supported by the versioned patch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Minimum Deinstaller Version

This is the minimum OUI installer to be used in deinstalling the versioned patch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Patchset Name

This is the patchset name which contains this versioned patch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Patchset Version

This is the patchset version which contains this versioned patch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

VPATCH Name

This is the versioned patch name (Should be same as the Component Name, on which the Versioned Patch is applied).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

VPATCH Version

This is the version of the versioned patch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Patched Component

Patch consists of many bug fixes, each of which will have fixes for various components. This metric collects all the information of various components which are fixed by that patch.

Component Name

This is the internal name of the component which is being patched by the One Off.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Component Version

This is the base version of the component which is being patched.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

From Version

This exists only in Patchset Updates and corresponds to the version of the component being patched.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Patch ID

This is the patch ID number. The patch ID may be the same for more than one patch.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Patch Language

This is the patch language. Generally its "en" (English).

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Patch UPI

This is the Unique Patch Identifier. Some patches may have the same patch ID but different patch identifier. This will be used to issue patch advisories.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

To Version

This exists only in Patchset Updates (PSU) and corresponds to the new version of the component after the PSU has been applied.

Metric Summary

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

Target Version

Collection Frequency

All Versions

Every 24 Hours

Data Source

The data is picked up from the inventory.

User Action

None.

Response

This metric collects the availability of Oracle Home, whether an Oracle Home exists, and if its readable or not.

Status

The metric indicates whether Oracle Home is reachable or not.

5 Services Metrics

This chapter describes the Services Metrics.

[CalDAV Metrics]

This metric is a container for a set of metrics you can use to measure the performance of your CALDAV service.

Calendar Access Verification Time

This metric indicates the time taken (in milliseconds) to verify the calendar access of the CalDAV URL.

Event Add Time

This metric indicates the time taken (in milliseconds) to add a calendar event.

Task Add Time

This metric indicates the time taken (in milliseconds) to add a calendar task.

Connect Time

This metric indicates the time taken (in milliseconds) to connect to the CalDAV server.

Content Listing Time

This metric indicates the time taken (in milliseconds) to list the contents of the folder.

Event Delete Time

This metric indicates the time taken (in milliseconds) to delete a calendar task.

Task Delete Time

This metric indicates the time taken (in milliseconds) to delete a calendar task.

DNS Response Metrics

The following sections lists the DNS Response metrics, their descriptions, and user actions.

User Action

If TTL values are low, then you may consider configuring your DNS service to allow caching for longer periods of time.

[DNS] Number of Retries

The total number of retries before a DNS lookup is successful.

User Action

If TTL values are low, then you may consider configuring your DNS service to allow caching for longer periods of time.

[DNS] Number of Results

A response to a DNS request may contain multiple answers. This indicates the number of answers (e.g. the number of IP addresses) in the response from the DNS service.

User Action

If the number of results is not what it should be, then you will need to examine your DNS service's configuration.

[DNS] Status

Indicates whether the query was successful.

User Action

Consult the Results metric for details.

[DNS] Total Connect Time (ms)

Time taken to connect to the DNS service. This metric is collected for queries using the TCP protocol.

User Action

A slow Total Connect Time suggests that network congestion is a problem.

[DNS] Total Response Time (ms)

Total time required to receive a response from the DNS service.

User Action

Unusually slow response times can occur if the DNS server has to perform a lookup before it can respond. If the total response time is consistently slow, then either the network may be slow, or the DNS server may be having trouble generating a response. Try using traceroute to diagnose network issues

[DNS] TTL (seconds)

A response to a DNS request may contain multiple answers. Each answer in a DNS response has a TTL (Time To Live) that indicates the number seconds that the answer may be cached by a client. The TTL value reported here is the minimum TTL of all the answers in the DNS response.

User Action

If TTL values are low, then you may consider configuring your DNS service to allow caching for longer periods of time.

DNS Results

The results of the DNS query. In the event of a status down, the reason for the status down will be displayed here.

Forms Application

This metric is container for a set of metrics you can use to measure the performance of your Forms transaction.

[Forms] Average Time Per Message (ms)

This is the ratio between total time and the length of transaction. A high average time is usually an indication of a slow down on the server side.

User Action

Use this metric to compare transactions running on the same server rather than total time.

[Forms] Database Time (ms)

The database time required to perform certain Forms operations such as Commit, Query, Runform and others.

User Action

A high database time indicates that the database on which the forms server is working has slowed down due to high load or other reasons.

[Forms] Forms Time (ms)

A high Forms Time might indicate network problems or problem with an unusually slow forms server.

User Action

Check the network time in order to further diagnose the problem. A high Forms Time might further be diagnosed if the server is enabled for End-User Performance Monitoring.

FTP Response Metrics

This metric is container for a set of metrics you can use to measure the performance of your FTP service test.

[FTP] Connect Time (ms)

Time taken to establish a connection with the FTP service.

[FTP] Download Rate (KB/second)

The rate at which the data is downloaded from the FTP service.

[FTP] Download Time (ms)

The total time taken to download a file from the service.

[FTP] Login Time (ms)

The time required to login to the FTP service.

[FTP] NOOP Time (ms)

The time required to perform a NOOP. A NOOP (“No Operation”) is a request that the FTP service respond with an “OK” status. A NOOP is similar to network round-trip time because generating a response to a NOOP requires minimal effort.

[FTP] Number of Retries

The number of retries required before the test was successful.

[FTP] Status

Indicates that all requests succeeded and that the downloaded file matched the uploaded file.

[FTP] Status Description

Details on the reason for any service failure.

[FTP] Total Time (ms)

The total time required to test the FTP service.

[FTP] Upload Time (ms)

The time taken to upload a file to the service.

[FTP] Upload Rate (ms)

The rate at which the data is downloaded from the FTP service.

HTTP Raw Metrics

The following sections lists the HTTP Raw metrics, their descriptions, and user actions.

HTTP Raw Time Per Connection

This metric measures the average connect time for all pages in the transaction. This is calculated as: Total Connect Time / Number of Connections Made. The Connect Time is one of the phases of a transaction that can help you isolate and fix response time problems.

User Action

The average connect time, when reviewed over a period of time, can indicate whether network congestion or other connectivity issues are the cause of poor Web application response time.

HTTP Raw Broken URL Count

This metric measures the number of errors encountered when displaying content for the pages accessed by the transaction, step or step group. For example, missing GIF images or style sheets will increase the value of the Broken Count metric.

User Action

Use this metric to measure the quality of the pages being served by your Web application. For example, high values for the Broken Count metric can indicate that files have been moved or that relative links in the application are broken.

HTTP Raw Broken URL Details

This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.

HTTP Raw Connect Time (ms)

Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction, step or step group can help you pinpoint the cause of a slow response time alert. Connect Time is the total time spent in the transaction connecting to the server. There may be multiple connections made during a transaction. Time spent connecting for requests that result in redirects count as Redirect Time rather than Connect Time.

User Action

Significant Connect Time values are usually caused by a slow network or a busy Web server. Significant Connect Time values may also indicate that there are too many connections made during the transaction. Consider enabling HTTP persistent connections if the application does not already have them enabled.

HTTP Raw First Byte Time (ms)

This is the First Byte Time divided by the number of pages in the step, step group, or transaction.

User Action

A high First Byte Time per Page suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.

HTTP Transaction DNS Time

This metric is not supported for this version of Enterprise Manager.

HTTP Raw HTML Time (ms)

Enterprise Manager breaks down each step, step group, or transaction into individual phases. Performance metrics for each phase can help you pinpoint the cause of a slow response time alert. This metric measures the HTML Time, which is the amount of time it takes to transfer the HTML coding of the page to the browser. This metric does not include the time spent transferring images or other page content.

User Action

Slow HTML time could indicate that the application is taking a long time to finish generating each page. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low.

HTTP Raw Non-HTML Time (ms)

This is the amount of time it takes to transfer the non-HTML content such as images to the browser.

User Action

Slow Non-HTML time could indicate that the application is taking a long time to generate images. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low. Consider reducing the number of distinct images in the application.

HTTP Raw Perceived Slowest Page / Page Element Time (ms)

The amount of time that it would take a Web browser to play the slowest page in the step, step group, or transaction. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.

User Action

Use this metric to identify problem pages. After you identify a page or transaction that's slow to response respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

HTTP Raw Perceived Time per Page / Page Element (ms)

The average amount of time that it would take a Web browser to play each page in the step, step group, or transaction. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be. Because it is normalized on a per-page basis, Perceived Time per Page is also a good metric for comparing the relative performance of different transactions.\

User Action

Use this metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

HTTP Raw Perceived Total Time (ms)

Indicates the overall time spent to process the step, step group, or transaction. This includes all the phases of the step / step group / transaction, including Connect Time, Redirect Time, First Byte Time, HTML Time, and Non-HTML Time. This metric calculates total transaction time by assuming all contents of a page are fetched in a serial manner.

User Action

Use the Total Time Metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

HTTP Raw Redirect Time (ms)

Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. Some pages automatically redirect the HTTP request to another page. Redirect time represents the total time of all redirects within a transaction. The time taken to redirect the request can affect the overall response time of the page.

User Action

Significant time taken to redirect the HTTP request. If the redirect is causing the performance problems, consider alternative solutions to sending the user to another HTML page.

HTTP Raw Row Type

Indicates whether the metric is collected for step, step group, or transaction.

HTTP Raw Status

Indicates whether the Web transaction was successful.

HTTP Raw Status Description

If the beacon is unable to run the step, step group, or transaction successfully, this metric returns a description of the error.

HTTP Raw Total Time (ms)

Indicates the overall time spent to process the step, step group, or transaction. This includes all the phases of the transaction, including Connect Time, Redirect Time, First Byte Time, HTML Time, and Non-HTML Time. This metric calculates total transaction time by assuming all contents of a page are fetched in a serial manner.

User Action

Use the Total Time Metric to identify problem transactions. After you identify a transaction that is slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

HTTP Raw Transfer Rate (KB per second)

The transfer rate indicates how quickly data is being transferred from the Web server to the client browser. This is computed as: Total Kilobytes Received / Total Transaction Time.

User Action

Slow transfer rate can be caused by network congestion or other connectivity issues.

HTTP Raw First Byte Time

Enterprise Manager breaks down each transaction, step or step group into individual phases. Performance metrics for each phase can help you pinpoint the cause of a slow response time alert. This metric measures the First Byte Time, which is the total time taken between the last byte of the request sent and the first byte of the response received by the server for all requests made. This includes the network latency and the time for the server to respond.

User Action

As with the Connect Time and Redirect Time, this metric can help you pinpoint whether or not the page content or Web application software is causing the slow response time, as opposed to the actual time it takes to transfer one byte of information to the browser. A high First Byte Time suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.

HTTP Raw URL

This is the URL associated with the step.

HTTP Raw DNS Time

This metric is not supported for this version of Enterprise Manager.

HTTP Step Group Metrics

The following sections lists the HTTP Step Group metrics, their descriptions, and user actions.

[HTTP Step Group] Connect Time (ms)

Enterprise Manager breaks down each step group into individual phases. Performance metrics for each phase of the step group can help you pinpoint the cause of a slow response time alert. Connect Time is the total time spent in the transaction connecting to the server. There may be multiple connections made during a transaction. Time spend connecting for requests that result in redirects count as Redirect Time rather than Connect Time.

User Action

Significant Connect Time values are usually caused by a slow network or a busy Web server. Significant Connect Time values may also indicate that there are too many connections made during the transaction. Consider enabling HTTP persistent connections if the application does not already have them enabled.

[HTTP Step Group] Broken URL Count

This metric measures the number of errors encountered when displaying content for the pages accessed by the step group. For example, missing GIF images or style sheets will increase the value of the Broken Count metric.

User Action

Use this metric to measure the quality of the pages being served by your Web application. For example, high values for the Broken Count metric can indicate that files have been moved or that relative links in the application are broken.

[HTTP Step Group] First Byte Time (ms)

Enterprise Manager breaks down each step group into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the First Byte Time, which is the total time taken between the last byte of the request sent and the first byte of the response received by the server for all requests made. This includes the network latency and the time for the server to respond.

User Action

As with the Connect Time and Redirect Time, this metric can help you pinpoint whether or not the page content or Web application software is causing the slow response time, as opposed to the actual time it takes to transfer one byte of information to the browser. A high First Byte Time suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.

[HTTP Step Group] Broken URL Details

This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.

[HTTP Step Group] First Byte Time per Page (ms)

This is the First Byte Time divided by the number of pages in the step group.

User Action

A high First Byte Time per Page suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.

[HTTP Step Group] HTML Time (ms)

Enterprise Manager breaks down each step group into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the HTML Time, which is the amount of time it takes to transfer the HTML coding of the page to the browser. This metric does not include the time spent transferring images or other page content.

User Action

Slow HTML time could indicate that the application is taking a long time to finish generating each page. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low.

[HTTP Step Group] DNS Time

This metric is not supported for this version of Enterprise Manager.

[HTTP Step Group] Non-HTML Time (ms)

This is the amount of time it takes to transfer the non-HTML content such as images to the browser.

User Action

Slow Non-HTML time could indicate that the application is taking a long time to generate images. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low. Consider reducing the number of distinct images in the application.

[HTTP Step Group] Perceived Slowest Page Time (ms)

The amount of time that it would take a Web browser to play the slowest page in a step group. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.

User Action

Use this metric to identify problem pages. After you identify a page or transaction that's slow to response respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem

[HTTP Step Group] Perceived Time per Page (ms)

The average amount of time that it would take a Web browser to play each page in the step group. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be. Because it is normalized on a per-page basis, Perceived Time per Page is also a good metric for comparing the relative performance of different transactions.

User Action

Use this metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the step group to isolate and repair the problem.

[HTTP Step Group} Perceived Total Time (ms)

The amount of time that it would take a Web browser to play the step group. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.

User Action

Use this metric to identify problem transactions. After you identify a step group that's slow to respond to user requests, you can drill down and analyze each phase of the step group to isolate and repair the problem.

[HTTP Step Group] Redirect Time (ms)

Enterprise Manager breaks down each step group into individual phases. Performance metrics for each phase of the step group can help you pinpoint the cause of a slow response time alert. Some pages automatically redirect the HTTP request to another page. Redirect time represents the total time of all redirects within a step group. The time taken to redirect the request can affect the overall response time of the page.

User Action

Significant time taken to redirect the HTTP request. If the redirect is causing the performance problems, consider alternative solutions to sending the user to another HTML page.

[HTTP Step Group] Status

Indicates whether the Web transaction was successful.

[HTTP Step Group] Status Description

If the beacon is unable to run the step group successfully, this metric returns a description of the error that prevented the step group from running.

[HTTP Step Group] Time per Connection (ms)

This is the Connect Time divided by the number of connections made while playing a step group.

User Action

Slow Time per Connection has nothing to do with the content of the page itself. It is likely caused by a slow network or a busy Web server, which prevents the request from getting to the Web server in a timely manner. Transactions that use HTTPS will typically have a much higher Time per Connection than transactions that use HTTP.

[HTTP Step Group] Transfer Rate (KB per second)

The transfer rate indicates how quickly data is being transferred from the Web server to the client browser. This is computed as: Total Kilobytes Received / Total Transaction Time.

User Action

Slow transfer rate can be caused by network congestion or other connectivity issues.

[HTTP Step Group] Total Time (ms)

Indicates the overall time spent in processing the step group. This includes all the phases of the transaction, including Connect Time, Redirect Time, First Byte Time, HTML Time, and Non-HTML Time. This metric calculates total transaction time by assuming all contents of a page are fetched in a serial manner.

User Action

Use the Total Time Metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

HTTP Transaction Metrics

The following sections lists the HTTP Transaction metrics, their descriptions, and user actions.

[HTTP Transaction] Connect Time (ms)

Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. Connect Time is the total time spent in the transaction connecting to the server. There may be multiple connections made during a transaction. Time spend connecting for requests that result in redirects count as Redirect Time rather than Connect Time.

User Action

Significant Connect Time values are usually caused by a slow network or a busy Web server. Significant Connect Time values may also indicate that there are too many connections made during the transaction. Consider enabling HTTP persistent connections if the application does not already have them enabled.

[HTTP Transaction] First Byte Time (ms)

Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the First Byte Time, which is the total time taken between the last byte of the request sent and the first byte of the response received by the server for all requests made. This includes the network latency and the time for the server to respond.

User Action

As with the Connect Time and Redirect Time, this metric can help you pinpoint whether or not the page content or Web application software is causing the slow response time, as opposed to the actual time it takes to transfer one byte of information to the browser. A high First Byte Time suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.

[HTTP Transaction] First Byte Time per Page (ms)

This is the First Byte Time divided by the number of pages in the transaction.

User Action

A high First Byte Time per Page suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.

[HTTP Transaction] Non-HTML Time (ms)

This is the amount of time it takes to transfer the non-HTML content such as images to the browser.

User Action

Slow Non-HTML time could indicate that the application is taking a long time to generate images. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low. Consider reducing the number of distinct images in the application.

[HTTP Transaction] HTML Time (ms)

Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the HTML Time, which is the amount of time it takes to transfer the HTML coding of the page to the browser. This metric does not include the time spent transferring images or other page content.

User Action

Slow HTML time could indicate that the application is taking a long time to finish generating each page. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low.

[HTTP Transaction] Perceived Slowest Page Time (ms)

The amount of time that it would take a Web browser to play the slowest page in the transaction. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.

User Action

Use this metric to identify problem pages. After you identify a page or transaction that is slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

[HTTP Transaction] Perceived Time per Page (ms)

The average amount of time that it would take a Web browser to play each page in the transaction. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be. Because it is normalized on a per-page basis, Perceived Time per Page is also a good metric for comparing the relative performance of different transactions.

User Action

Use this metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

[HTTP Transaction] Perceived Total Time

The amount of time that it would take a Web browser to play the transaction. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.

User Action

Use this metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

[HTTP Transaction] Redirect Time (ms)

Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. Some pages automatically redirect the HTTP request to another page. Redirect time represents the total time of all redirects within a transaction. The time taken to redirect the request can affect the overall response time of the page.

User Action

Significant time taken to redirect the HTTP request. If the redirect is causing the performance problems, consider alternative solutions to sending the user to another HTML page.

[HTTP Transaction] Status

Indicates whether the Web transaction was successful.

[HTTP Transaction] Status Description

If the beacon is unable to run the transaction successfully, this metric returns a description of the error that prevented the transaction from running.

[HTTP Transaction] Time per Connection (ms)

This is the Connect Time divided by the number of connections made while playing a transaction.

User Action

Slow Time per Connection has nothing to do with the content of the page itself. It is likely caused by a slow network or a busy Web server, which prevents the request from getting to the Web server in a timely manner. Transactions that use HTTPS will typically have a much higher Time per Connection than transactions that use HTTP.

[HTTP Transaction] Total Time (ms)

Indicates the overall time spent to process the transaction. This includes all the phases of the transaction, including Connect Time, Redirect Time, First Byte Time, HTML Time, and Non-HTML Time. This metric calculates total transaction time by assuming all contents of a page are fetched in a serial manner.

User Action

Use the Total Time Metric to identify problem transactions. After you identify a r transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

[HTTP Transaction] Transfer Rate (KB per second)

The transfer rate indicates how quickly data is being transferred from the Web server to the client browser. This is computed as: Total Kilobytes Received / Total Transaction Time.

User Action

Slow transfer rate can be caused by network congestion or other connectivity issues.

HTTP User Action Metrics

The following sections lists the HTTP User Action metrics, their descriptions, and user actions.

[HTTP Step] Connect Time (ms)

Enterprise Manager breaks down each step into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. Connect Time is the total time spent in the transaction connecting to the server. There may be multiple connections made during a transaction. Time spend connecting for requests that result in redirects count as Redirect Time rather than Connect Time.

User Action

Significant Connect Time values are usually caused by a slow network or a busy Web server. Significant Connect Time values may also indicate that there are too many connections made during the transaction. Consider enabling HTTP persistent connections if the application does not already have them enabled.

[HTTP Step] Broken URL Count

This metric measures the number of errors encountered when displaying content for the pages accessed by the step. For example, missing GIF images or style sheets will increase the value of the Broken Count metric.

User Action

Use this metric to measure the quality of the pages being served by your Web application. For example, high values for the Broken Count metric can indicate that files have been moved or that relative links in the application are broken.

[HTTP Step] Broken URL Content

This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.

[HTTP Step] DNS Time

This metric is not supported for this version of Enterprise Manager.

[HTTP Step] First Byte Time (ms)

Enterprise Manager breaks down each step element. Performance metrics for each step element can help you pinpoint the cause of a slow response time alert. This metric measures the First Byte Time, which is the total time taken between the last byte of the request sent and the first byte of the response received by the server for all requests made. This includes the network latency and the time for the server to respond.

User Action

As with the Connect Time and Redirect Time, this metric can help you pinpoint whether or not the page content or Web application software is causing the slow response time, as opposed to the actual time it takes to transfer one byte of information to the browser. A high First Byte Time suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.

[HTTP Step] First Byte TIme per Page Element (ms)

This is the First Byte Time divided by the number of step elements.

User Action

A high First Byte Time per Page suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.

[HTTP Step] HTML Time (ms)

Enterprise Manager breaks down each step. Performance metrics for each step element can help you pinpoint the cause of a slow response time alert. This metric measures the HTML Time, which is the amount of time it takes to transfer the HTML coding of the page to the browser. This metric does not include the time spent transferring images or other page content.

User Action

Slow HTML time could indicate that the application is taking a long time to finish generating each page. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low.

[HTTP Step] Non-HTML Time (ms)

This is the amount of time it takes to transfer the non-HTML content such as images to the browser.

User Action

Slow Non-HTML time could indicate that the application is taking a long time to generate images. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low. Consider reducing the number of distinct images in the application.

[HTTP Step] Perceived Slowest Page Element Time (ms)

The amount of time that it would take a Web browser to play the slowest step element. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.

User Action

Use this metric to identify problem pages. After you identify a page or a step that is slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

[HTTP Step] Perceived Time per Page Element (ms)

The average amount of time that it would take a Web browser to play each step element. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be. Because it is normalized on a per-page basis, Perceived Time per Page is also a good metric for comparing the relative performance of different transactions.

User Action

Use this metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the step group to isolate and repair the problem.

[HTTP Step] Perceived Total Time (ms)

The amount of time that it would take a Web browser to play the step element. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.

User Action

Use this metric to identify problem transactions. After you identify a step group that's slow to respond to user requests, you can drill down and analyze each phase of the step to isolate and repair the problem.

[HTTP Step] Redirect Time (ms)

Enterprise Manager breaks down each step into individual phases. Performance metrics for each phase of the step can help you pinpoint the cause of a slow response time alert. Some pages automatically redirect the HTTP request to another page. Redirect time represents the total time of all redirects within a step. The time taken to redirect the request can affect the overall response time of the page.

User Action

Significant time taken to redirect the HTTP request. If the redirect is causing the performance problems, consider alternative solutions to sending the user to another HTML page.

[HTTP Step] Status

Indicates whether the Web transaction was successful.

[HTTP] Status Description

If the beacon is unable to run the transaction successfully, this metric returns a description of the error that prevented the transaction from running.

[HTTP Step] Time per Connection (ms)

This is the Connect Time divided by the number of connections made while playing a step.

User Action

Slow Time per Connection has nothing to do with the content of the page itself. It is likely caused by a slow network or a busy Web server, which prevents the request from getting to the Web server in a timely manner. Transactions that use HTTPS will typically have a much higher Time per Connection than transactions that use HTTP.

[HTTP Step] Total Time (ms)

Indicates the overall time spent in processing the step. This includes all the phases of the transaction, including Connect Time, Redirect Time, First Byte Time, HTML Time, and Non-HTML Time. This metric calculates total transaction time by assuming all contents of a page are fetched in a serial manner.

User Action

Use the Total Time Metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

[HTTP Step] Transfer Rate (KB per second)

The transfer rate indicates how quickly data is being transferred from the Web server to the client browser. This is computed as: Total Kilobytes Received / Total Transaction Time.

User Action

Slow transfer rate can be caused by network congestion or other connectivity issues.

[HTTP Step] URL

This is the URL associated with the step.

ICMP Echo Response Metrics

The following sections lists the ICMP Echo Response metrics, their descriptions, and user actions.

[ICMP Ping] Last Host

Indicates the last node that was reached successfully while traversing to the final destination.

User Action

If the last host is not your destination node, there may be an indication that network problems exist between the last host and the destination node. Validate that the host is up and that none of your routers are down.

[ICMP Ping] Number of Hops

Indicates the number of network nodes traversed to reach the host.

User Action

If this number is higher than you think it should be, examine your network configuration. Your routers may be routing packets improperly.

[ICMP Ping] Packets Dropped (%)

Indicates the percentage of packets that could not reach their destination.

User Action

Packets are usually dropped due to a congested network. Remove the source of the congestion or upgrade your network bandwidth.

[ICMP Ping] Response Time (ms)

Indicates the average amount of time that the agent waited before receiving a response for each "ping" sent to the host.

User Action

Slow response time could indicate that there is some network congestion or that a packet takes a long time to reach the host. Investigate your network configuration. When Response Time is high, the Number of Hops is usually also high.

[ICMP Ping] Status

Indicates that the host is reachable from the agent.

IMAP Response Metrics

This metric is a container for a set of metrics you can use to measure the performance of the IMAP service test.

[IMAP] Connect Time (ms)

This value is the time it took (in milliseconds) to open an IMAP connection.

[IMAP] Login Time (ms)

This value is the time it took (in milliseconds) to log into an IMAP Service.

[IMAP] Status

Shows the current status of the IMAP service, either Up, Down, Status Pending, or Agent Unreachable.

[IMAP] Status Message

Shows the current status of the IMAP service, either Up, Down, Status Pending, or Agent Unreachable.

[IMAP] Time to Read Email (ms)

This value is the time it took (in milliseconds) to read an e-mail message.

[IMAP] Time to List Folders (ms)

This value is the time it took (in milliseconds) to list the e-mail folders.

[IMAP] Timing (ms)

This value is the total time it took (in milliseconds) to open an IMAP connection, log into the IMAP service, list the e-mail folders, and read an e-mail message.

Email Undelete Time

This metric indicates the total time taken (in milliseconds) to undelete an email.

Email Delete Time

This metric indicates the total time taken (in milliseconds) to delete an email.

LDAP Response Metric

This metric is a container for a set of metrics you can use to measure the performance of your LDAP service test.

[LDAP] Address Search Time (ms)

This value is the time it took (in milliseconds) to perform an e-mail addressing search against an LDAP server.

[LDAP] Base Search Time (ms)

This value is the time it took (in milliseconds) to perform a base search against an LDAP server.

[LDAP] Compare Time (ms)

This value is the time it took (in milliseconds) to perform a compare operation against an LDAP server. This operation simulates logging in LDAP activity.

[LDAP] Connect Time (ms)

This value is the time it took (in milliseconds) to open an LDAP connection.

[LDAP] Message Search Time (ms)

This value is the time it took (in milliseconds) to perform an e-mail message search against an LDAP server.

[LDAP] Status

Shows the current status of the LDAP service, either Up, Down, Status Pending, or Agent Unreachable.

[LDAP] Status Message

Provides a detailed description of the status of the LDAP service when the service status is down.

NNTP Response Metrics

The following table lists the NNTP Response metrics and their descriptions.

[NNTP] Connect Time (ms)

This value is the time it took (in milliseconds) to open an NNTP connection.

[NNTP] Status

Shows the current status of the NNTP service, either Up, Down, Status Pending, or Agent Unreachable.

[NNTP] Status Message

Provides a detailed description of the status of the NNTP service when the service status is down.

[NNTP] Time to post news article (ms)

This value is the time it took (in milliseconds) to post a message to the news group through the NNTP service.

[NNTP] Time to retrieve news article (ms)

This value is the time it took (in milliseconds) to retrieve a message from the NNTP service.

[NNTP] Total Time

This value is the total time it took (in milliseconds) to open an NNTP connection, log in, retrieve a message and post a message to the news group.

OS Response Metrics

This metric is a container for a set of metrics you can use to measure the performance of the custom script.

[Custom Script] Number of Retries

The total number of retries before the script is successfully executed.

[Custom Script] Status

Indicates the status of the service test. The test is successful of the return code of the script is 0.

[Custom Script] Total Time (ms)

Indicates the total time required to run the script.

[Custom Script] Custom Metric 1

A numeric value should be generated for each line of the custom script. This column corresponds to the first line generated by the script.

[Custom Script] Custom Metric 2

A numeric value should be generated for each line of the custom script. This column corresponds to the second line generated by the script.

[Custom Script] Custom Metric 3

A numeric value should be generated for each line of the custom script. This column corresponds to the third line generated by the script.

[Custom Script] Custom Metric 4

A numeric value should be generated for each line of the custom script. This column corresponds to the fourth line generated by the script.

[Custom Script] Custom Metric 5

A numeric value should be generated for each line of the custom script. This column corresponds to the fifth line generated by the script.

[Custom Script] Custom Metric 6

A numeric value should be generated for each line of the custom script. This column corresponds to the sixth line generated by the script.

[Custom Script] Custom Metric 7

A numeric value should be generated for each line of the custom script. This column corresponds to the seventh line generated by the script.

[Custom Script] Custom Metric 8

A numeric value should be generated for each line of the custom script. This column corresponds to the eighth line generated by the script.

[Custom Script] Custom Metric 9

A numeric value should be generated for each line of the custom script. This column corresponds to the ninth line generated by the script.

[Custom Script] Custom Metric 10

A numeric value should be generated for each line of the custom script. This column corresponds to the last line generated by the script.

POP Response Metrics

This metric is a container for a set of metrics you can use to measure the performance of the POP service test.

[POP] Connect Time (ms)

This value is the time it took (in milliseconds) to open a POP connection.

[POP] Login Time (ms)

This value is the time it took (in milliseconds) to log into the POP service.

[POP] Status

Shows the current status of the POP service, either Up, Down, Status Pending, or Agent Unreachable.

[POP] Status Message

Provides a detailed description of the status of the POP service when the service status is down.

[POP] Time to Read Email (ms)

This value is the time it took (in milliseconds) to read a short e-mail message.

[POP] Timing (ms)

This value is the total time it took (in milliseconds) to open a POP connection, log in, and read a short e-mail message.

Port Checker Metrics

The following sections list the Port Checker metrics, their descriptions, and user actions.

[Port Checker] Status

Indicates whether agent could successfully connect to the Expected Open Ports or it could not connect to the Expected Closed Ports.

[Port Checker] Unexpectedly Closed Ports

Set of ports that were unexpectedly closed.

User Action

Check that there is no firewall blocking these ports. Check that the server listening on these ports is up.

[Port Checker] Unexpectedly Open Ports

Set of ports that were unexpectedly open.

User Action

If you have a firewall blocking these ports, check your firewall configuration.

SMTP Response Metrics

This metric is a container for a set of metrics you can use to measure the performance of the SMTP service test.

[SMTP] Connect Time (ms)

This value is the time it took (in milliseconds) to open an SMTP connection.

[SMTP] Message Delivery Time

This metric is the time it took (in milliseconds) to deliver the email. This includes the time at which the email was initiated by the sender till the time it was delivered to the receiver's email account.

[SMTP] Status

Shows the current status of the SMTP service, either Up, Down, Status Pending, or Agent Unreachable.

[SMTP] Status Message

Provides a detailed description of the status of the SMTP service when the service status is down.

[SMTP] Time To Send Email (ms)

This value is the time it took (in milliseconds) to send a short e-mail message.

[SMTP] Total Time (ms)

This value is the total time it took (in milliseconds) to open an SMTP connection and send a short e-mail message.

SOAP Response Metrics

The following sections list the SOAP Response metrics and their descriptions.

SOAP Response Time

Time taken by the beacon to complete the entire operation. This includes the time taken to send the HTTP request and receive the response.

SOAP Response Response Time (ms)

Time taken by the beacon to complete the entire operation. This includes the time taken to send the HTTP request and receive the response.

SOAP Response Status

This can be 0 (status down) or 1 (status up). The status is down when there is any error detected by beacon while performing the operation. The Status may be down in following cases:

- Due to any HTTP error

- No HTTP errors but due to a SOAP fault in the response

SOAP Status

This can be 0 (status down) or 1 (status up). The status is down when there is any error detected by beacon while performing the operation. The Status may be down in following cases:

- Due to any HTTP error

- No HTTP errors but due to a SOAP fault in the response

Oracle SQL Response

The following sections list the SQL Response metrics, their descriptions, and user actions.

[SQL] Close Time (ms)

Time taken to close the connection.

User Action

Close Time might be slow if the network performance is slow. Examine your network configuration.

[SQL] Connect Time (ms)

Total time taken to connect to the database.

User Action

Connect Time might be slow if the network is congested, if the database is having trouble authenticating the user, or if the database is having trouble allocating connections. If you have an Enterprise Manager target instance for the database, you should consult the homepage for the database.

[SQL] Execute Time (ms)

Time taken to execute the SQL statement.

User Action

Execute Time will be slow if the database performance is slow. If you have an Enterprise Manager target instance for the database, you should consult the homepage for the database.

[SQL] Fetch Time (ms)

Time taken to retrieve data from the server.

User Action

Fetch Time might be slow if the network bandwidth is low or if database performance is slow. If you have an Enterprise Manager target instance for the database, you should consult the homepage for the database.

[SQL] Fetch Time per Row (ms)

Time taken to fetch each row (Fetch Time / Number of Rows Fetched). Fetch Time per Row is a good metric to use for setting thresholds and for comparing the performance of different Oracle SQL Timing tests.

User Action

Use the Fetch Time per Row metric to identify data transfer problems. If the value of this metric is high, then the data-transfer bandwidth between the client and the database is poor. If you have an Enterprise Manager target instance for the database, you should consult the homepage for the database.

[SQL] Number of Rows Fetched

The total number of rows fetched during a query.

User Action

If the Number of Rows Fetched is not what you expected, then examine the contents of your database. Unexpected rows in the result could affect Fetch Time and Total Time.

[SQL] Prepare Time (ms)

Time taken to prepare the SQL statement. This usually includes fetching metadata for the object types in the query.

User Action

Prepare Time might be slow if the network performance is slow or if database performance is slow. If you have an Enterprise Manager target instance for the database, you should consult the homepage for the database.

[SQL] Status

Indicates whether the SQL or PL/SQL statement could be successfully executed.

[SQL] Status Description

Provides a description of the status.

[SQL] Total Time (ms)

The total time taken to connect to the database and run the query. It is the sum of Connect Time, Prepare Time, Execute Time, Fetch Time and Close Time.

User Action

Use the Total Time metric to identify database connectivity problems. Examine the other metrics to isolate and repair the problem. If you have an Enterprise Manager target instance for the database, you should consult the homepage for the database.

[SQL] Total Time per Row (ms)

Time taken to perform the entire test divided by the number of rows fetched (Total Time / Number of Rows Fetched). Total Time per Row is a good metric to use for setting thresholds and for comparing the performance of different Oracle SQL Timing tests.

User Action

Use the Total Time per Row metric to identify database connectivity problems. As with the Total Time metric, you should examine the other metrics to isolate and repair the problem. If you have an Enterprise Manager target instance for the database, you should consult the homepage for the database.

TNS Ping Response

The following sections list the TNS Ping Response metrics, their descriptions, and user actions.

[TNS] Average Response Time (ms)

This metric for a listener shows response time in milli sec . It is calculated using the tnsping "<address>"utility. For example:

tnsping "( ADDRESS= ( PROTOCOL=TCP ) ( HOST=adc2100827.us.oracle.com ) ( PORT=15045 ) )"

TNS Ping Utility for Linux: Version 11.2.0.2.0 - Production on 09-SEP-2011 06:43:16

Copyright (c) 1997, 2010, Oracle.  All rights reserved.

Attempting to contact ( ADDRESS= ( PROTOCOL=TCP ) ( HOST=adc2100827.us.oracle.com ) ( PORT=15045 ) )
OK (2 msec)

[TNS] Pings Dropped (%)

Indicates the percentage of pings that did not receive a response.

User Action

Check that the network is not congested and that the database is not under heavy load. If you have an Enterprise Manager target instance for the database, you should consult the homepage for the database

[TNS] Status

Indicates whether the database responds to the pings.

[Web Transaction] Browser

This metric is a container for a set of metrics you can use to measure the performance of your Web transaction.

[Web Transaction (Browser)] Status

Indicates whether the Web transaction was successful.

[Web Transaction (Browser)] Status Description

If the beacon is unable to run the transaction successfully, this metric returns a description of the error that prevented the transaction from running.

[Web Transaction (Browser)] Total Time (ms)

The amount of time that it would take a Web browser to play the transaction. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.

User Action

Use this metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

[Web Transaction (Browser)] Raw

This metric is container for a set of metrics you can use to measure the performance of your Web transaction service test and its associated steps and steps groups.

[Web Transaction (Browser)] Row Type

Indicates whether the metric is collected for step, step group or transaction.

[Web Transaction (Browser)] Status

Indicates whether the Web transaction was successful.

[Web Transaction (Browser)] Status Description

If the beacon is unable to run the step, step group, or transaction successfully, this metric returns a description of the error.

[Web Transaction (Browser)] Total Time (ms)

Indicates the overall time spent to process the step, step group, or transaction. This includes all the phases of the step / step group / transaction, including Connect Time, Redirect Time, First Byte Time, HTML Time, and Non-HTML Time. This metric calculates total transaction time by assuming all contents of a page are fetched in a serial manner.

User Action

Use the Total Time Metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

Web Transaction (Browser) Step

This metric is a container for a set of metrics you can use to measure the performance each step in the transaction.

[Web Transaction (Browser) Step] Status

Indicates whether the Web transaction was successful.

[Web Transaction (Browser) Step] Status Description

If the beacon is unable to run the transaction successfully, this metric returns a description of the error that prevented the transaction from running.

[Web Transaction (Browser) Step] Total Time (ms)

The amount of time that it would take a Web browser to play the step element. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.

User Action

Use this metric to identify problem transactions. After you identify a step group that's slow to respond to user requests, you can drill down and analyze each phase of the step to isolate and repair the problem.

[Web Transaction (Browser)] Step Group

This metric is container for a set of metrics you can use to measure the performance of all the steps in the step group.

[Web Transaction (Browser) Step Group] Status

Indicates whether the Web transaction was successful.

[Web Transaction (Browser) Step Group] Status Description

If the beacon is unable to run the step group successfully, this metric returns a description of the error that prevented the step group from running.

[Web Transaction (Browser) Step Group] Total Time (ms)

The amount of time that it would take a Web browser to play the step group. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.

User Action

Use this metric to identify problem transactions. After you identify a step group that's slow to respond to user requests, you can drill down and analyze each phase of the step group to isolate and repair the problem.

6 Web Application Metrics

This chapter describes the Web Application metrics.

HTTP Content

The following sections lists the HTTP Content metrics, their descriptions, and user actions.

Average Connect Time

This metric measures the average connect time for all pages in the transaction. This is calculated as: Total Connect Time / Number of Connections Made. The Connect Time is one of the phases of a transaction that can help you isolate and fix response time problems.

User Action

The average connect time, when reviewed over a period of time, can indicate whether network congestion or other connectivity issues are the cause of poor Web application response time.

Average First Byte Time

This metric measures the average First Byte Time for all pages in the transaction. This metric is computed as: Total First Byte Time / Number of Requests Made (either to fetch HTML or content). The First Byte time is one of the phases of a transaction that can help you isolate and fix response time problems.

User Action

The average First Byte Time, when reviewed over a period of time, can indicate whether network congestion or other connectivity issues are the cause of poor Web application response time.

Average Response Time

A single transaction often accesses multiple Web pages. The Average Page Response metric calculates the average response time of the pages within a single transaction. This metric is calculated as: Total Transaction Time / Number of Pages in the Transaction. For example, if the transaction connects to four different Web pages, this metric will calculate the average response time for the four pages each time the transaction is run.

User Action

If a particular transaction continuously exceeds the Average Page Response threshold, use the Beacon Data page to test the transaction from other beacons and over a specific time period. Use this data to pinpoint any trends or specific beacons that generate the alerts. Display the Beacon Data page by clicking the value of a metric on the Transaction Performance Page.

Beacon Name

The beacon name if the name of the beacon for which the current metric data is being collected.

Broken Content

This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.

Broken Count

This metric measures the number of errors encountered when displaying content for the pages accessed by the transaction. For example, missing GIF images or style sheets will increase the value of the Broken Count metric.

User Action

Use this metric to measure the quality of the pages being served by your Web application. For example, high values for the Broken Count metric can indicate that files have been moved or that relative links in the application are broken.

Computed Response Time

This metric represents the estimated response time for a client such as a browser, to fetch all the pages in a transaction. The computed response time is calculated as if the contents of every page (such as images and HTML style sheets) were fetched in parallel using multiple threads.

User Action

Use the Calculated Response Time to predict the response time that will be experienced by your average end user.

Connect Time

Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. Connect Time is the first phase of a transaction and represents the time it takes for a connection to the Web server to be established for all requests.

User Action

Slow connect time has nothing to do with the content of the page itself. It is likely caused by a slow network or a busy Web server, which prevents the request from getting to the Web server in a timely manner.

Content Time

Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the Content Time, which is the amount of time taken to transfer page content to the browser. Page content includes images and style sheets, as opposed to the HTML coding for the page.

User Action

Consider reducing the size of images or other contents of the page

DNS Time

This metric is not supported for this version of Enterprise Manager

First Byte TIme

Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the First Byte Time, which is the total time taken between the last byte of the request sent and the first byte of the response received by the server for all requests made. This includes the network latency and the time for the server to respond.

User Action

As with the Connect Time and Redirect Time, this metric can help you pinpoint whether or not the page content or Web application software is causing the slow response time, as opposed to the actual time it takes to transfer one byte of information to the browser.

HTML Bytes

This metric provides information about the amount of data transferred during the selected transaction. For each transaction, this metric provides the total bytes of HTML code transferred from all the Web pages accessed by the transaction.

User Action

This metric can help you isolate the cause of any performance problems identified by this transaction. Be sure to consider the number of HTML bytes when you compare the response time of your Web Application transactions.

HTML Content

This metric serves as a container for a set of metrics that provide you with information about the content of the Web pages you are monitoring, as well as response time information.

HTTP Response

This metric is a container for a set of metrics you can use to measure the performance of your Web Application transactions. It indicates how quickly the pages respond to user requests.

HTML Time

Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the HTML Time, which is the amount of time it takes to transfer the HTML coding of the page to the browser. This metric does not include the time spent transferring images or other page content, for example.

User Action

Slow HTML time could indicate problems with your HTML coding. Check the source code for your Web Application page to see if there are ways to streamline or improve the logic of the HTML code.

Page Content Bytes

This metric provides information about the amount of data transferred during the selected transaction. For each transaction, this metric provides the number of bytes that represent page content such as images and style sheets.

User Action

This metric can help you isolate the cause of any performance problems identified by this transaction. Be sure to consider the total number of bytes when you compare the response time of your Web Application transactions. Pages with many images or complex style sheets will return a high value for the Page Content Bytes metric.

Page Content Count

This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.

Redirect Count

This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.

Redirect Time

Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. Some pages automatically redirect the HTTP request to another page. Redirect time represents the total time of all redirects within a transaction. The time taken to redirect the request can affect the overall response time of the page.

User Action

Significant time taken to redirect the HTTP request removes the possibility that the page content or the Web application software is causing a slow response time alert. If the redirect is causing the performance problems, consider alternative solutions to sending the user to another HTML page.

Request Count

This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.

Slowest Response Time

A single transaction often accesses multiple Web pages. This metric indicates the maximum response time measured for a particular page within a transaction. The slowest page response time can be monitored for a specific transaction and from a specific beacon over a period of time.

You can set a threshold for this metric so that Enterprise Manager will generate an alert if the slowest page response for a particular transaction exceeds a value you specify when it is run from a specific beacon.

Status

This metric returns a value of 1 if the selected beacon was successfully able to run the transaction for this Web application target.

User Action

There are several possible causes to a failed transaction. First, check the availability of the Web application and host for the Web application target.

Second, check the availability of the Oracle Agent for this beacon.

Status Description

If the beacon is unable to run the transaction successfully, this metric returns a description of the error that prevented the transaction from running.

User Action

If you are reviewing the metric results from the All Metrics page, review the Value column of the Status Description table. The error description should offer clues about why the transaction failed.

Total Bytes

This metric provides information about the amount of data transferred during the selected transaction. For each transaction, this metric provides the total number of bytes transferred from all the Web pages accessed by the transaction.

User Action

This metric can help you isolate the cause of any performance problems identified by this transaction. Be sure to consider the total number of bytes when you compare the response time of your Web Application transactions.

Total Response TIme

Total transaction time indicates the overall time spent to process the transaction. This includes all the phases of the transaction, including Connect Time, Redirect Time, First Byte Time, HTML Time, and Content Time. This metric calculates total transaction time by assuming all contents of a page are fetched in a serial manner.

User Action

Use the total response time metric to identify problem pages. After you identify a page or transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

Transaction Name

The transaction name is the name of the transaction for which the current metric data is collected.

Transfer Rate

The transfer rate indicates how quickly data is being transferred from the Web server to the client browser. This is computed as: Total Kilobytes Received / Total Transaction Time.

User Action

Slow transfer rate can be caused by network congestion or other connectivity issues.

Web Application

You can use Oracle Enterprise Manager to view performance and availability metrics for your Web applications.

HTTP Step Group

The following sections lists the HTTP Step Group metrics, their descriptions, and user actions.

[HTTP Step Group] Broken URL Count

This metric measures the number of errors encountered when displaying content for the pages accessed by the step group. For example, missing GIF images or style sheets will increase the value of the Broken Count metric.

User Action

Use this metric to measure the quality of the pages being served by your Web application. For example, high values for the Broken Count metric can indicate that files have been moved or that relative links in the application are broken.

[HTTP Step Group] Broken URL Details

This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.

[HTTP Step Group] Connect Time (ms)

Enterprise Manager breaks down each step group into individual phases. Performance metrics for each phase of the step group can help you pinpoint the cause of a slow response time alert. Connect Time is the total time spent in the transaction connecting to the server. There may be multiple connections made during a transaction. Time spend connecting for requests that result in redirects count as Redirect Time rather than Connect Time.

User Action

Significant Connect Time values are usually caused by a slow network or a busy Web server. Significant Connect Time values may also indicate that there are too many connections made during the transaction. Consider enabling HTTP persistent connections if the application does not already have them enabled.

[HTTP Step Group] DNS Time

This metric is not supported for this version of Enterprise Manager.

[HTTP Step Group] First Byte Time (ms)

Enterprise Manager breaks down each step group into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the First Byte Time, which is the total time taken between the last byte of the request sent and the first byte of the response received by the server for all requests made. This includes the network latency and the time for the server to respond.

User Action

As with the Connect Time and Redirect Time, this metric can help you pinpoint whether or not the page content or Web application software is causing the slow response time, as opposed to the actual time it takes to transfer one byte of information to the browser. A high First Byte Time suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.

[HTTP Step Group] First Byte TIme per Page (ms)

This is the First Byte Time divided by the number of pages in the step group.

User Action

A high First Byte Time per Page suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.

[HTTP Step Group] HTML Time (ms)

Enterprise Manager breaks down each step group into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the HTML Time, which is the amount of time it takes to transfer the HTML coding of the page to the browser. This metric does not include the time spent transferring images or other page content.

User Action

Slow HTML time could indicate that the application is taking a long time to finish generating each page. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low.

[HTTP Step Group] Non-HTML Time (ms)

This is the amount of time it takes to transfer the non-HTML content such as images to the browser.

User Action

Slow Non-HTML time could indicate that the application is taking a long time to generate images. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low. Consider reducing the number of distinct images in the application.

[HTTP Step Group] Perceived Slowest Page Time (ms)

The amount of time that it would take a Web browser to play the slowest page in a step group. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.

User Action

Use this metric to identify problem pages. After you identify a page or transaction that's slow to response respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem

[HTTP Step Group] Perceived Time per Page (ms)

The average amount of time that it would take a Web browser to play each page in the step group. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be. Because it is normalized on a per-page basis, Perceived Time per Page is also a good metric for comparing the relative performance of different transactions.

User Action

Use this metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the step group to isolate and repair the problem.

[HTTP Step Group] Perceived Total Time (ms)

The amount of time that it would take a Web browser to play the step group. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.

User Action

Use this metric to identify problem transactions. After you identify a step group that's slow to respond to user requests, you can drill down and analyze each phase of the step group to isolate and repair the problem.

[HTTP Step Group] Redirect Time (ms)

Enterprise Manager breaks down each step group into individual phases. Performance metrics for each phase of the step group can help you pinpoint the cause of a slow response time alert. Some pages automatically redirect the HTTP request to another page. Redirect time represents the total time of all redirects within a step group. The time taken to redirect the request can affect the overall response time of the page.

User Action

Significant time taken to redirect the HTTP request. If the redirect is causing the performance problems, consider alternative solutions to sending the user to another HTML page.

[HTTP Step Group] Status

Indicates whether the Web transaction was successful.

[HTTP Step Group] Status Description

If the beacon is unable to run the transaction successfully, this metric returns a description of the error that prevented the transaction from running.

[HTTP Step Group] Time per Connection (ms)

This is the Connect Time divided by the number of connections made while playing a step group.

User Action

Slow Time per Connection has nothing to do with the content of the page itself. It is likely caused by a slow network or a busy Web server, which prevents the request from getting to the Web server in a timely manner. Transactions that use HTTPS will typically have a much higher Time per Connection than transactions that use HTTP.

[HTTP Step Group] Total Time (ms)

Indicates the overall time spent in processing the step group. This includes all the phases of the transaction, including Connect Time, Redirect Time, First Byte Time, HTML Time, and Non-HTML Time. This metric calculates total transaction time by assuming all contents of a page are fetched in a serial manner.

User Action

Use the Total Time Metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

[HTTP Step Group] Transfer Rate (KB per second)

The transfer rate indicates how quickly data is being transferred from the Web server to the client browser. This is computed as: Total Kilobytes Received / Total Transaction Time.

User Action

Slow transfer rate can be caused by network congestion or other connectivity issues.

HTTP Transaction

The following sections lists the HTTP Transaction metrics, their descriptions, and user actions.

[HTTP Transaction] Connect Time (ms)

Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. Connect Time is the total time spent in the transaction connecting to the server. There may be multiple connections made during a transaction. Time spend connecting for requests that result in redirects count as Redirect Time rather than Connect Time.

User Action

Significant Connect Time values are usually caused by a slow network or a busy Web server. Significant Connect Time values may also indicate that there are too many connections made during the transaction. Consider enabling HTTP persistent connections if the application does not already have them enabled.

[HTTP Transaction] DNS Time

This metric is not supported for this version of Enterprise Manager.

[HTTP Transaction] First Byte Time (ms)

Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the First Byte Time, which is the total time taken between the last byte of the request sent and the first byte of the response received by the server for all requests made. This includes the network latency and the time for the server to respond.

User Action

As with the Connect Time and Redirect Time, this metric can help you pinpoint whether or not the page content or Web application software is causing the slow response time, as opposed to the actual time it takes to transfer one byte of information to the browser. A high First Byte Time suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.

[HTTP Transaction] First Byte Time per Page (ms)

This is the First Byte Time divided by the number of pages in the transaction.

User Action

A high First Byte Time per Page suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.

[HTTP Transaction] HTML Time (ms)

Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the HTML Time, which is the amount of time it takes to transfer the HTML coding of the page to the browser. This metric does not include the time spent transferring images or other page content.

User Action

Slow HTML time could indicate that the application is taking a long time to finish generating each page. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low.

[HTTP Transaction] Non-HTML Time (ms)

This is the amount of time it takes to transfer the non-HTML content such as images to the browser.

User Action

Slow Non-HTML time could indicate that the application is taking a long time to generate images. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low. Consider reducing the number of distinct images in the application.

[HTTP Transaction] Perceived Slowest Page Time (ms)

The amount of time that it would take a web browser to play the slowest page in the transaction. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.

User Action

Use this metric to identify problem pages. After you identify a page or transaction that's slow to response respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

[HTTP Transaction] Perceived Time per Page (ms)

The average amount of time that it would take a Web browser to play each page in the transaction. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be. Because it is normalized on a per-page basis, Perceived Time per Page is also a good metric for comparing the relative performance of different transactions.

User Action

Use this metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

[HTTP Transaction] Perceived Total Time

The amount of time that it would take a web browser to play the transaction. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.

User Action

Use this metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

[HTTP Transaction] Redirect Time (ms)

Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. Some pages automatically redirect the HTTP request to another page. Redirect time represents the total time of all redirects within a transaction. The time taken to redirect the request can affect the overall response time of the page.

User Action

Significant time taken to redirect the HTTP request. If the redirect is causing the performance problems, consider alternative solutions to sending the user to another HTML page.

[HTTP Transaction] Status

Indicates whether the Web transaction was successful.

[HTTP Transaction] Status Description

If the beacon is unable to run the transaction successfully, this metric returns a description of the error that prevented the transaction from running.

[HTTP Transaction] Time per Connection (ms)

This is the Connect Time divided by the number of connections made while playing a transaction.

User Action

Slow Time per Connection has nothing to do with the content of the page itself. It is likely caused by a slow network or a busy Web server, which prevents the request from getting to the Web server in a timely manner. Transactions that use HTTPS will typically have a much higher Time per Connection than transactions that use HTTP.

[HTTP Transaction] Total Time (ms)

Indicates the overall time spent to process the transaction. This includes all the phases of the transaction, including Connect Time, Redirect Time, First Byte Time, HTML Time, and Non-HTML Time. This metric calculates total transaction time by assuming all contents of a page are fetched in a serial manner.

User Action

Use the Total Time Metric to identify problem transactions. After you identify a r transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

[HTTP Transaction] Transfer Rate (KB per second)

The transfer rate indicates how quickly data is being transferred from the Web server to the client browser. This is computed as: Total Kilobytes Received / Total Transaction Time.

User Action

Slow transfer rate can be caused by network congestion or other connectivity issues.

HTTP User Action

The following sections lists the HTTP User Action metrics, their descriptions, and user actions.

[HTTP Step] Broken URL Content

This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.

[HTTP Step] Connect Time (ms)

Enterprise Manager breaks down each step element. Performance metrics for each step element can help you pinpoint the cause of a slow response time alert. Connect Time is the total time spent in the transaction connecting to the server. There may be multiple connections made during a transaction. Time spend connecting for requests that result in redirects count as Redirect Time rather than Connect Time.

User Action

Significant Connect Time values are usually caused by a slow network or a busy Web server. Significant Connect Time values may also indicate that there are too many connections made during the transaction. Consider enabling HTTP persistent connections if the application does not already have them enabled.

[HTTP Step] DNS Time

This metric is not supported for this version of Enterprise Manager.

[HTTP Step] First Byte Time (ms)

Enterprise Manager breaks down each step into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the First Byte Time, which is the total time taken between the last byte of the request sent and the first byte of the response received by the server for all requests made. This includes the network latency and the time for the server to respond.

User Action

As with the Connect Time and Redirect Time, this metric can help you pinpoint whether or not the page content or Web application software is causing the slow response time, as opposed to the actual time it takes to transfer one byte of information to the browser. A high First Byte Time suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.

[HTTP Step] First Byte Time per Page Element (ms)

This is the First Byte Time divided by the number of step elements.

User Action

A high First Byte Time per Page suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.

[HTTP Step] HTML Time (ms)

Enterprise Manager breaks down each step element. Performance metrics for each step element can help you pinpoint the cause of a slow response time alert. This metric measures the HTML Time, which is the amount of time it takes to transfer the HTML coding of the page to the browser. This metric does not include the time spent transferring images or other page content.

User Action

Slow HTML time could indicate that the application is taking a long time to finish generating each page. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low.

[HTTP Step] Non-HTML Time (ms)

This is the amount of time it takes to transfer the non-HTML content such as images to the browser.

User Action

Slow Non-HTML time could indicate that the application is taking a long time to generate images. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low. Consider reducing the number of distinct images in the application.

[HTTP Step] Perceived Slowest Page Element Time (ms)

The amount of time that it would take a Web browser to play the slowest step element. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.

User Action

Use this metric to identify problem pages. After you identify a page or transaction that's slow to response respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem

[HTTP Step] Perceived Time per Page Element (ms)

The average amount of time that it would take a Web browser to play each page in a step. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be. Because it is normalized on a per-page basis, Perceived Time per Page is also a good metric for comparing the relative performance of different transactions.

User Action

Use this metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the step group to isolate and repair the problem.

[HTTP Step] Perceived Total Time (ms)

The amount of time that it would take a Web browser to play the step element. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.

User Action

Use this metric to identify problem transactions. After you identify a step group that's slow to respond to user requests, you can drill down and analyze each phase of the step to isolate and repair the problem.

[HTTP Step] Redirect Time (ms)

Enterprise Manager breaks down each step element. Performance metrics for each step element can help you pinpoint the cause of a slow response time alert. Some pages automatically redirect the HTTP request to another page. Redirect time represents the total time of all redirects within a step. The time taken to redirect the request can affect the overall response time of the page.

User Action

Significant time taken to redirect the HTTP request. If the redirect is causing the performance problems, consider alternative solutions to sending the user to another HTML page.

[HTTP Step] Status

Indicates whether the Web transaction was successful.

[HTTP Step] Status Description

If the beacon is unable to run the transaction successfully, this metric returns a description of the error that prevented the transaction from running.

[HTTP Step] Time per Connection (ms)

This is the Connect Time divided by the number of connections made while playing a step element.

User Action

Slow Time per Connection has nothing to do with the content of the page itself. It is likely caused by a slow network or a busy Web server, which prevents the request from getting to the Web server in a timely manner. Transactions that use HTTPS will typically have a much higher Time per Connection than transactions that use HTTP.

[HTTP Step] Total Time (ms)

Indicates the overall time spent in processing the step. This includes all the phases of the transaction, including Connect Time, Redirect Time, First Byte Time, HTML Time, and Non-HTML Time. This metric calculates total transaction time by assuming all contents of a page are fetched in a serial manner.

User Action

Use the Total Time Metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

[HTTP Step] Transfer Rate (KB per second)

The transfer rate indicates how quickly data is being transferred from the Web server to the client browser. This is computed as: Total Kilobytes Received / Total Transaction Time.

User Action

Slow transfer rate can be caused by network congestion or other connectivity issues.

[HTTP Step] URL

This is the URL associated with the step.

HTTP Raw

The following sections lists the HTTP Raw metrics, their descriptions, and user actions.

HTTP Raw Broken URL Details

This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.

HTTP Raw Connect Time (ms)

Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction, step or step group can help you pinpoint the cause of a slow response time alert. Connect Time is the total time spent in the transaction connecting to the server. There may be multiple connections made during a transaction. Time spent connecting for requests that result in redirects count as Redirect Time rather than Connect Time.

User Action

Significant Connect Time values are usually caused by a slow network or a busy Web server. Significant Connect Time values may also indicate that there are too many connections made during the transaction. Consider enabling HTTP persistent connections if the application does not already have them enabled.

HTTP Raw DNS Time

This metric is not supported for this version of Enterprise Manager.

HTTP Raw First Byte Time (ms)

This is the First Byte Time divided by the number of pages in the step, step group, or transaction.

User Action

A high First Byte Time per Page suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.

HTTP Raw HTML Time (ms)

Enterprise Manager breaks down each step, step group, or transaction into individual phases. Performance metrics for each phase can help you pinpoint the cause of a slow response time alert. This metric measures the HTML Time, which is the amount of time it takes to transfer the HTML coding of the page to the browser. This metric does not include the time spent transferring images or other page content.

User Action

Slow HTML time could indicate that the application is taking a long time to finish generating each page. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low.

HTTP Raw Non-HTML Time (ms)

This is the amount of time it takes to transfer the non-HTML content such as images to the browser.

User Action

Slow Non-HTML time could indicate that the application is taking a long time to generate images. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low. Consider reducing the number of distinct images in the application.

HTTP Raw Perceived Slowest Page / Page Element Time (ms)

The amount of time that it would take a web browser to play the slowest page in the step, step group, or transaction. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.

User Action

Use this metric to identify problem pages. After you identify a page or transaction that's slow to response respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

HTTP Raw Perceived Time per Page / Page Element (ms)

The average amount of time that it would take a Web browser to play each page in the step, step group, or transaction. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be. Because it is normalized on a per-page basis, Perceived Time per Page is also a good metric for comparing the relative performance of different transactions.

User Action

Use this metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

HTTP Raw Perceived Total Time (ms)

Indicates the overall time spent to process the step, step group, or transaction. This includes all the phases of the step / step group / transaction, including Connect Time, Redirect Time, First Byte Time, HTML Time, and Non-HTML Time. This metric calculates total transaction time by assuming all contents of a page are fetched in a serial manner.

User Action

Use the Total Time Metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

HTTP Raw Redirect Time (ms)

Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. Some pages automatically redirect the HTTP request to another page. Redirect time represents the total time of all redirects within a transaction. The time taken to redirect the request can affect the overall response time of the page.

User Action

Significant time taken to redirect the HTTP request. If the redirect is causing the performance problems, consider alternative solutions to sending the user to another HTML page.

HTTP Raw Status

Indicates whether the Web transaction was successful.

HTTP Raw Status Description

If the beacon is unable to run the step, step group, or transaction successfully, this metric returns a description of the error that prevented the transaction from running.

HTTP Raw Time Per Connection

This metric measures the average connect time for all pages in the transaction. This is calculated as: Total Connect Time / Number of Connections Made. The Connect Time is one of the phases of a transaction that can help you isolate and fix response time problems.

User Action

The average connect time, when reviewed over a period of time, can indicate whether network congestion or other connectivity issues are the cause of poor Web application response time.

HTTP Raw Transfer Rate (KB per second)

The transfer rate indicates how quickly data is being transferred from the Web server to the client browser. This is computed as: Total Kilobytes Received / Total Transaction Time.

User Action

Slow transfer rate can be caused by network congestion or other connectivity issues.

HTTP Raw Total Time (ms)

Indicates the overall time spent to process the step, step group, or transaction. This includes all the phases of the transaction, including Connect Time, Redirect Time, First Byte Time, HTML Time, and Non-HTML Time. This metric calculates total transaction time by assuming all contents of a page are fetched in a serial manner.

User Action

Use the Total Time Metric to identify problem transactions. After you identify a r transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

HTTP Raw URL

This is the URL associated with the step.

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