立即与支持人员聊天
与支持团队交流

Foglight for Oracle (Cartridge) 5.7.5.41 - 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) Reviewing Overall Activity Reviewing RAC Historic Activity Oracle Activity Drilldown Pluggable Databases Drilldown Storage Drilldown Reviewing Configuration Settings Reviewing the Alert and Error Logs Reviewing ASM Instances Reviewing Exadata-related Information
Administering Foglight for Oracle Reporting Reference Glossary

Generating Reports

The Reports section can be used for generating the following types of reports:

•
Reports about various aspects of the selected instance or RAC performance. These are identical to the reports generated using the Dashboards > Report command. For information on how to generate the various reports, as well as a brief description of each report, see .
•
Executive summary report — a one-click report-generating feature, designed to deliver the critical parameters displayed on the Overview Page in a useful configurable format to key decision-makers. If the monitored instance is part of a multitenant architecture, this report displays a grid showing data for each pluggable database.

Reviewing RAC Historic Activity

The History Summary page in Whole Cluster view contains the following panes:

•
Cluster Overview — see Monitoring the Cluster’s Usability and Load Balance
•
Interconnect/GCS — see Monitoring Interconnect, Cluster, and Global Cache
•
Storage — see Monitoring Disk Storage
•
I/O Activity — see Monitoring the Cluster’s I/O Activity
•
Resource Utilization — see Monitoring Resource Utilization
•
Sessions — see Monitoring Session Activity

Monitoring the Cluster's Usability and Load Balance

Monitoring the Cluster’s Usability and Load Balance

The Cluster Overview pane displays the cluster’s overall functioning and load balance.

Cluster Section
•
Availability — the percentage of RAC nodes that are available (up) and running.
Clicking the number on the icon displays a popup that shows the percentage of cluster nodes that were available (up) during the specified time range, plotted over time.
Click this indicator to drill down to the Activity > Cluster Usability panel. For details, see Reviewing Cluster Usability .
•
Response Time — the maximum (slowest) response time among all of the cluster nodes, in milliseconds.
Holding the cursor over the number on the icon displays a dwell that shows the average response time, that is, the average time (in milliseconds) that elapses from the moment a dummy query (either select 1 from dual or a user-defined query) is submitted, until the application indicates that the query was executed. This value is plotted over time.
Click this indicator to drill down to the Activity > Cluster Usability panel. For details, see Reviewing Cluster Usability .
Balance Criterion Section

The Balance Criterion section contains the following charts:

•
Values aggregated to the cluster level
•
Bar chart values for each cluster node

These charts display data according to the value selected from the Balance Criterion list.

The available values are:

•
Workload — in average active sessions
•
Availability — average availability, in percent
•
Response Time — maximum response time, in milliseconds
•
Logical Reads — average number of logical reads, in blocks
•
CPU Load — average CPU load, in percent
•
Interconnect Load — average interconnect load, in blocks
•
Cluster Wait Time — average cluster wait time
Balance Section

The Balance section contains the balance bars listed below, which display the balance rate of RAC nodes for each metric.

•
Workload (%) — the extent, in percent, to which workload (average active sessions) is balanced across all RAC nodes.
Ideally, all instances should equally share the wait time caused by active sessions workload; however, this metric can indicate a situation where a specific instance takes a much larger share, thereby possibly overloading the system.
•
I/C Load (%) — the extent, in percent, to which the Interconnect workload-related wait events are balanced across all RAC nodes.
Ideally, all instances should equally share the wait time caused by Interconnect workload; however, this metric can indicate a situation where a specific instance takes a much larger share, thereby possibly overloading the system.
•
Cluster Wait (%) — the extent, in percent, to which Cluster wait is balanced across all RAC nodes.
Ideally, all instances should equally share the wait time caused by cluster wait; however, this metric can indicate a situation where a specific instance takes a much larger share, thereby possibly overloading the system
Click the number on the icon to display a popup that shows the percentage of cluster balance between all cluster instances. This value is plotted over time.
•
Logical Reads (%) — the extent, in percent, to which Logical Reads are balanced across all RAC nodes.
Ideally, all instances should equally share the wait time caused by logical reads; however, this metric can indicate a situation where a specific instance takes a much larger share, thereby possibly overloading the system.
•
CPU Load (%) — the extent, in percent, to which CPU usage is balanced across all RAC nodes.
Ideally, all instances should equally share the wait time caused by CPU usage; however, an overly low value of this metric can indicate a situation where a specific instance takes a much larger share, thereby possibly overloading the system

Monitoring Interconnect, Cluster, and Global Cache

The Interconnect/GCS pane contains the indicators listed below, which are used for monitoring the global cache functioning. These indicators also demonstrate the effect of the global cache functioning over the interconnect load and the cluster latency and overhead.

•
Cluster Latency — the average cluster latency value, in milliseconds.
Cluster latency is the time that has elapsed since the request for the block was submitted until the block was received by the requesting instance.
•
Cluster Overhead — the percentage of cluster wait events within the overall active time. This value summarizes the cluster-related activity of all cluster instances.
•
Global Cache — the total amount of global cache in megabytes. This value represents the amount of space allocated to Global Cache across all instances in the cluster.
•
Cache Miss Rate — the maximum cache miss rate in percent. This value represents the frequency at which a data block is requested from a remote instance, after the user session failed to find this block in the buffer cache.
•
I/C Load — the total Interconnect Load across all cluster nodes, that is, the aggregated number of requests for blocks that were not satisfied from the local instance, and therefore had to make a request for the block from the remote instance.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级