Chat now with support
Chat with Support

Foglight for Oracle (Cartridge) - User Guide

Installing and Configuring Agents Using Foglight for Oracle
Viewing the Databases Dashboard Assigning Instances to Users Selecting an Instance to Monitor Foglight for Oracle Overview Dashboard Overview view Advisories view SQL Performance Investigator (SQL PI) Oracle Activity Drilldown Pluggable Databases Drilldown Storage Drilldown Reviewing Configuration Settings Reviewing the Alert Log Reviewing Monitored Data Guard Environments Reviewing ASM Instances Reviewing Exadata-related Information
Administering Foglight for Oracle Reporting Reference Glossary


Cartridges extend the functionality of Foglight and are installed on the Foglight Management Server. A cartridge contains one or more components, such as agents for deployment, communication capabilities, and modifications to the way that data is transformed or handled, as well as rules, reports, and views. When a cartridge is installed and enabled, its components become part of the Management Server. Adding cartridges allows users to monitor additional parts of their environment. For further details about managing cartridges, See the Foglight Administration and Configuration Guide.

Cluster Wait

Cluster wait events take place when the session waits for all types of cluster resources, such as Interconnect hardware, shared disks, and Oracle instances.

CPU Usage

When SQL statements and other types of calls are made to Oracle, processing the calls requires spending a certain amount of CPU time. Whereas processing average calls requires a small amount of CPU time, a SQL statement involving a large amount of data or a runaway query can consume a much larger amount, thereby reducing the CPU time available for other processing.

CPU utilization is a key operating system statistic in the tuning process. Excessive CPU usage can result from an inadequately-sized system, untuned SQL statements, or inefficient application programs.

CPU Wait

CPU wait events take place when the session is waiting in the system's run queue to be granted for CPU cycles. The length of these wait events (the amount of time spent) depends upon the number of concurrent processes and threads requesting CPU time.

This metric’s value should be inspected in conjunction with the value of the Run Queue Length.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating