Chat now with support
Chat with Support

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

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

Viewing Execution Plans

This view presents the execution plan of a selected SQL and the cost of it. A Historical execution plan can be generated and will present any two views of the execution plan.
There are two ways to access the Execution Plan History dialog:
•
From a Change Tracking pane by clicking on a row that displays Execution Plan change.
•
From History by selecting the statement or batch and by clicking Analyze in the top of the table.
The execution plan dashboard displays the following content.
Top Bar
Resolving Date — Displays all the execution date and time of the selected statement.
Type — Displays the type of the execution plan.
Plan Hash Value — Displays the plan hash value of the execution plan
Plan analysis section
The execution plan is contains 3 tabs:
•
Plan details — Displays details of each operation in the execution plan.
•
Operation Analysis — Displays statistics aggregated per each operation in the execution plan.
•
Object Analysis - Displays statistics aggregated per each object in the execution plan. Each object is clickable and displays a popup with important performance-related information.
By clicking the Generate Plan button the execution plan is generated and can be viewed. By clicking on the Compare Plan button a pop up will appear that allows comparing all available execution plans of the selected SQL statement.

Comparing Performance

Use the SQL PI Compare where differences in period activity illustrate underlying performance and monitoring issues. It helps you determine whether a comparison occurrence is an isolated incident or a sign of a potentially significant performance problem.
Compare can be access from the Performance tree.
The comparison can be of whole instances or selected dimension breakdowns (such as user or SQL). Use Compare to address questions such as:
•
What caused a specific activity?
•
What were the resource and load demands of today's instance activity compared with that of a previous day?
•
Is an instance imposing different load levels now than previously?
•
How do we explain the difference in a SQL performance compared with a previous period?
•
What are the differences in program characteristics over two periods that caused different performance?
•
After identifying the different resource usage, you can use compare to identify what caused this difference: Usage pattern? Different SQL behavior? Environmental problem?
The upper panes graphically displays the Workload or any other selected resource.
The middle Activity section displays the dimensions which were significant elements of the difference. Expanding the individual lines displays the dimension members which caused the difference and the composing metrics whose differences exceed the specified threshold.
Use the set of performance related metrics (defined by the chosen resource) to help you explain the difference in resource consumption; for example, a rise in I/O Wait might be explained by a rise in the quantity of physical reads.
Use the Comparison Parameters section in order to enter all the desired information for the cooperation. For example, time range, instance, dimension, time frames, resource.

Reviewing Overall Activity

The Oracle Overview page provides an overall view of the RAC or instance status for the selected time range, through the views and tools listed below.
* 
NOTE: The ASM (Automatic Storage Management) and archiving components are enabled only when being used by the monitored instances. Monitoring the ASM-related data is possible only when the ASM instance is installed and configured. For details, see Using Foglight for Oracle .
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating