Chat now with support
Chat with Support

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

Adding CRS Agents for Monitoring Clusterware

Receiving alarms about the CRS software, which is used for monitoring Oracle Clusterware, requires creating CRS agents.

1
Click the Oracle tile.
2
Go to the CRS tab.
3
Click Monitor more Clusterwares at the upper left corner above of the Databases table.
4
In the Configure CRS Agent screen, use the CRS agent name field to set a user-defined name for the agent. Alternatively, accept the default name provided for the CRS agent.
6
Click Next.
7
Use the Configure Nodes for Monitoring screen to add the requested CRS nodes, using either of the following methods:
8
Click Add Nodes, and from the menu select Discover by cluster node.
16
Click Add nodes.
17
Select the option Add manually.
18
Follow Step 9 to Step 13, then proceed to Step 19.
19
Click Next.
After the agent’s creation completes, monitoring starts automatically, and the Summary screen appears, displaying the newly created agent with all its components.
20
Click Finish to return to the Databases dashboard.

After the CRS agents have been configured for monitoring, their monitoring settings can be modified using the Agent Settings button.

IMPORTANT: Unlike Foglight for Oracle instances, the agent properties of CRS agents cannot be modified using the Databases Administration dashboard, but only through the default Foglight tools (see Foglight Administration and Configuration Guide). Clicking Agent settings and selecting the Administration option only allows re-running the wizard used for configuring the instances for monitoring, and changing the options defined using this wizard.
2
Click Settings.
3
Select Configure CRS agent to re-run the wizard used for configuring the agents for monitoring, and change the options defined using this wizard.

Adding Agents for Monitoring Exadata Environments

2
Go to the Exadata tab.
3
Click Monitor at the upper left corner above of the Databases table.
On the first screen of this wizard, Monitor Exadata, use the Exadata agent name field to set a user-defined name for the agent. Alternatively, accept the default name provided for the Exadata agent.
4
Click Next.
Use the next screen, Monitor InifiniBand Switches, to configure the InfiniBand switches for monitoring, either by adding the switches manually or by discovering by switch name. Configuring the switches for monitoring allows retrieving InfiniBand topology information, as well as automatically detecting the Exadata cells.
5
Click Add switches.
7
Select the option Add manually.
To add switches that would be monitored by a different credentials set, click Apply and repeat the process with the other credentials.
For a single switch, click Set credentials on the switch’s Status row.
9
Select the option Discover by switch name.
11
After adding all requested details, click Apply and then click Next to proceed to Step 12.
12
The following screen, Monitor Exadata Cells, contains a table that lists all of the Exadata Cells that were automatically discovered when the InfiniBand switches were configured for monitoring. If the stage of configuring InfiniBand switches was skipped, this table is empty and cells need to be added manually.
13
Click Add cells.
To add cells that would be monitored by a different credentials set, click Apply and repeat the process with the other credentials.
14
Click Apply.
15
Click Next.
After the agent’s creation completes, monitoring starts automatically, and the Summary screen appears, displaying the newly created agent with all its components.
16
Click Finish to return to the Databases dashboard.

Modifying the Exadata Monitoring Settings

After the Exadata agents have been configured for monitoring, their monitoring settings can be modified using the Agent Settings button.

IMPORTANT: Unlike Foglight for Oracle instances, the agent properties of ASM instances cannot be modified using the Databases Administration dashboard, but only through the default Foglight tools (see Foglight Administration and Configuration Guide). Clicking Agent settings and selecting the Administration option only allows re-running the wizard used for configuring the agents for monitoring, and changing the options defined using this wizard.
2
Click Settings.
3
Select Configure Exadata agent to re-run the wizard used for configuring the agents for monitoring, and change the options defined using this wizard.

Adding Data Guard Environment

IMPORTANT: Before configuring a new complete Data Guard environment via the Data Guard tab, you should add to monitoring its Primary database and Standby database using the Oracle Instances > Monitor dashboard; otherwise you will not be able to add these databases to the configured Data Guard environment. Creating a new Data Guard environment via the Data Guard tab is an optional feature which provides detailed visibility into your data guard environments performance and stability. For more information about how to add the Primary database and Standby database, refer to Installing and Monitoring a Single Oracle Instance .
1
On the Databases dashboard, click the Data Guard tab, and then click Monitor.
The Configure Data Guard Environment wizard appears.
2
Configure Data Guard Environment: specify the Data Guard environment name or use a default name, and then click Next.
1
Click Add database. The Add New Primary Database dialog box appears.
2
Choose a database from the Choose Primary Database drop-down list.
Specify login credentials with sysdba privileges checkbox is not checked: The monitoring of the Primary database will be with already defined db user.
Specify login credentials with sysdba privileges checkbox is checked: The monitoring of the Primary database will be with a new user that has SYSDBA privileges. In this case the SYSDBA credentials will be saved in the agent.
NOTE: We recommend to monitor the primary database with sysdba system privilege for better supporting during switchover.
When data guard switch over between primary and standby, standby database agent will be able to connect to the database with sysdba system privilege and retrieve data.
Specify login credentials with sysdba privileges checkbox is not checked: Monitoring the Standby database with already defined db user. You still need to provide an user with SYSDBA privileges for verification. The SYSDBA credentials will not be saved in the agent.
Specify login credentials with sysdba privileges checkbox is checked: Monitoring the Standby database with a new user that has SYSDBA privileges. In this case the SYSDBA credentials will be saved in the agent.
NOTE: We recommend to monitor the standby database with sysdba system privilege to enable retrieving data when the standby is in mount mode. Monitoring with a normal user (unchecked sysdba), the agent will not be able to retrieve any data when the standby is in mount mode.
5
Summary: find the list of all databases that were configured for a new Data Guard environment. If all details are correct click Finish.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating