Chatta subito con l'assistenza
Chat con il supporto

Foglight for Oracle (Cartridge) 5.9.3.10 - 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

Viewing Historical Metrics

The History section view is divided into two sections that are correlated to each other:

•
Resource consumption charts — This section displays data in five different charts:
•
Workload chart — Displays the instance resource activity over the selected time frame by emphasizing the resources by colors.
•
Baseline chart — Displays the instance workload compared to the baseline over time.
•
Breakdown chart — Activity of the instance by second.
•
Resource Breakdown Pie chart — Displays the resource breakdown usage by % of the total instance activity.
•
All wait events pop up — Displays details of the wait events that the instance is waiting on during the selected time range.
•
Overview section- Displays a graphical representation of the metrics highlighted in the Workload related Metrics table below.
•
Workload related Metrics - A table that displays a variety of resource consumption metrics which can give an in-depth of the instance activity, each resource holds its default metrics.

Selecting each dimension in the performance tree together with a specific resource effects the data displayed for each Level.

•
For example, by selecting the Lock resource the Instance view dimension will present only locks related data, the SQL Statements dimension will present only the statements that were experiencing locks and DB users the were experiencing locks and so on through all the dimensions and resources.

Blocking History

The Lock Analysis displays all locks that took place within the selected time range.

The lock analysis feature is integrated as part of the performance tree and it displays all the lock trees including further details for both the blocker and the blocked session including:

•
Lock event start date
•
Session Identifier – [Sid,SERIAL#]
•
Session Identifier of the blocker
•
Locked Object Name
•
Status
•
Lock Duration
•
Program
•
DB User
•
SQL Text
•
Client Machine

Activity Highlights

The Activity Highlights are provided for fast performance analysis and allow users focus on the most significant dimensions that are relevant for the resource selected in the selected time range.

This pane comprises the following elements:

•
Summary — Summarizes the instance consumption time by % of the total instance activity.
•
Activity Highlights table — Displays the activity highlights, resource breakdown usage, and the top wait event that the instance is waiting on within the selected time range.

Viewing Change Tracking

The change tracking tool is an integrated monitoring mechanism. It periodically tracks changes in environments and activity that can potentially influence system performance and enables the user to view correlation between occurrences of changes and Oracle’s activity and behavior patterns.

Use the Categories filter mechanism to refine the set of displayed change tracking occurrences. These categories are displayed on the right hand side of the pane and include:

•
Execution plan — SQL statements whose execution plans have changed. Unsuitable execution plans can result in SQL performance degradation.
•
Oracle configuration — instance-level configuration, such as init.ora parameters, location of files (data, log, and control), size and status
•
Oracle schema — any schema object, such as tables and indexes and their partitions, clusters, constraints, views, and materialized views.
•
System configuration — hardware and operating system configuration, such as OS global parameters, amount of RAM, and number of CPU units.
•
User-defined — used for documenting changes inserted manually by the user, which can affect performance. Recording this activity can assist in determining whether a change in performance can be directly associated with this event
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione