지금 지원 담당자와 채팅
지원 담당자와 채팅

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

Contents of the input CSV file for ASM instances

The input CSV file contains the following fields, which are used as columns in the resulting file.

 
Table 2. Contents of the input CSV file for ASM instances
Name
Description

RAC Agent Name

The name of the RAC agent. This name must be unique per agent.

•
If the instance belongs to a RAC, this field has to contain the name of the RAC agent.
•
If this RAC runs multiple nodes, all instances must have the same RAC agent name.
•
If the instance does not belong to a RAC, leave this field empty.

Agent Name

The requested agent name. This name must be unique per agent. If an agent with the given name already exists, the newly provided agent will not be created.

Host

The host that is serving the ASM instance.

Port

The TNS listener port.

SID

The name of the SID used for establishing connection to the instance.

NOTE: The SID name must be preceded by \\. For example: \\+ASM1.

User name

The name of the user to be used for connecting to the ASM instance. Can be either ASMSNMP or SYS.

User Type

Connection privileges level to be used for monitoring the ASM instance. The possible values are either “SYSASM” or “SYSDBA”.

Password

The password of the database user name.

Enable OS Monitoring

Specifies whether to create an Infrastructure Cartridge agent for the given host name; the possible values are True or False.

OS Platform (Optional)

The type of the OS platform where the Oracle instance runs; the possible values are either UNIX or WINDOWS.

Authentication (Optional)

OS authentication type. This field can have one of the following values:

•
LOGIN_PASSWORD: user/password authentication
•
RSA_KEY: RSA-based public key authentication
•
DSA_KEY: DSA-based public key authentication
•
CLIENT_LOGIN: uses the Foglight Agent Manager's login
•
WINDOWS_ACCOUNT: Windows authentication, in the domain\user and password convention

OS User Name (Optional)

The user name to be used for connecting to the OS and monitoring it.

OS Password (Optional)

The password of the OS user name specified above.

SSH Port (Optional)

The port that is used for listening to incoming SSH connections on the monitored hosts; if the monitored host is Windows-based, leave this field empty.

Private Key File Path (Optional)

The full path of the private key file; relevant only to the following credential types: RSA_KEY, DSA_KEY.

Passphrase (Optional)

The passphrase of the OS user that is used in public key authentication; relevant only to the following credential types: RSA_KEY, DSA_KEY.

Use sudo (Optional)

Used for indicating that the OS user specified above is not an administrator user, but can run certain commands that require administrative privileges as root.

The possible values are TRUE or FALSE. if the monitored host is Windows-based, leave this field empty to indicate FALSE.

Use SSL (String - true/false)

Specifies whether an SSL connection should be used; the possible values are TRUE or FALSE.

If no value is inserted in this field, it will use the default value FALSE.

 

Using Foglight for Oracle

Using Foglight for Oracle

Foglight for Oracle monitors the Oracle database activity by connecting to and querying the Oracle database. The agents provided monitor the Oracle database system. The dashboards included with the cartridge provide a visual representation of the status of the major components of the Oracle agents. They allow you to determine any potential bottleneck in database performance.

This section provides agent configuration instructions and information on investigating Oracle database performance. It covers the entire monitoring process, starting with the discovery of the database instances and the connection with these instances, and proceeding with the use of the various drilldowns and the Global Administration options.

Viewing the Databases Dashboard

Viewing the Databases Dashboard
 
* 
NOTE: The following section describes the various components of the Databases dashboard. To learn how to customize this dashboard’s display and focus on a requested instance, see Selecting an Instance to Monitor.

The Instance home page is launched by accessing the Databases dashboard.

To access the Databases dashboard:
1
Ensure that the navigation panel on the left is open.
To open the navigation panel, click the right-facing arrow on the left.
2
On the navigation panel, click Homes > Databases.

The Databases dashboard provides an at-a-glance view of the monitored environment, with all of the currently monitored database types.

The Databases dashboard includes these sections:

•
Database cartridge type tiles — each tile represents a database type (SQL Server, SQL Server BI, Oracle, Sybase, DB2, MongoDB, Cassandra, or All Instances) and displays the number of instances for each database type, along with a breakdown according to the instance health state severity (Normal, Warning, Critical, Fatal).
When selecting the Oracle Tile the following advanced monitoring can be performed and reviewed:
•
Oracle Instances — This is the default tab, used for displaying the “regular” Oracle instances.
•
Data Guard — used for configuring the monitoring of the Data Guard environment. The Data Guard environment information is presented after Data Guard environments are configured. For details about configuring and running the Data Guard environment, see Adding Data Guard Environment . For details about the monitoring information displayed on the Data Guard tab, see Reviewing Monitored Data Guard Environments .
•
ASM — ASM-related data, which was previously retrieved through the Foglight for Oracle agent, is only enabled if the Foglight ASM instance is configured and running. For details about configuring and running this instance, see Adding ASM Instances . For details about the monitoring information displayed on the ASM tab, see Reviewing ASM Instances .
•
CRS — used for configuring the monitoring of the Clusterware software that manages the oracle RACs. For details about configuring Clusterware for monitoring, see Adding CRS Agents for Monitoring Clusterware .
•
Exadata — used for configuring the monitoring of the Exadata environment. After the Exadata agents are added, data retrieved from Exadata is displayed on this tab, as well as on the Exadata drilldown.
•
For details about configuring the Exadata environment for monitoring, see Adding Agents for Monitoring Exadata Environments .
•
For details about the monitoring information displayed on the Exadata tab, see Viewing Data about the Exadata Cells .
•
For details about the drilldown that displays data retrieved from Exadata, see Reviewing Exadata-related Information
•
Status section — includes the following components:
•
Status summary — a color-coded bar, which provides a visual representation of the summarized health condition of all instances listed in the Database Group table.
The status summary bar provides a graphic representation of the monitored environment’s current state, broken down to the number of instances and their current health state: Fatal, Critical, Warning, Normal or Unknown.
•
Database-specific health summary — when the database group All is selected, this section displays all of the currently monitored instances for each database type, divided by their health state (for example: four Oracle instances, three of which have the health state Warning and one is indicated with the health state Fatal). When a user-defined database group is selected, this section displays data only about the agents included within the selected group.
* 
NOTE: The Status Indicators section can be used for filtering the Databases Group table to display only instances that meet a criterion set in this section. For details, see Filtering the Display by Severity .
•
The Monitor button — Use this button to add instances to be monitored.
•
The Configure Alarms button — Takes you directly to the Administration > Alarms page. On the Alarms page you can configure alarm settings and specify alarm sensitivity levels. Sensitivity levels control which alarms are enabled by default.
•
The Settings button — Use this button to do one of the following:
•
Access the User Management settings, allowing you to restrict which instances specific users are allowed to view. This makes it easier to for users to find information about only the instances they are interested in. For details, see Assigning Instances to Users .
•
After selecting one or more instances of the same database type, use this button to set options for collecting, storing, and displaying data for the selected instances, as well as configuring the connection to SQL Performance Investigator (if installed). For details, see Administering Foglight for Oracle .
•
Currently selected database group table — a list of all monitored databases within the database group that is currently selected in the Databases section. For details, see Using the Currently Selected Database Group Table .
•
The Show Quick View button — provides the ability to open a quick view of the instance at the bottom of the screen.
•
The Select dashboards () button — provides direct link to several drilldowns and panels, thereby saving the need to navigate to these locations through the Overview drilldown.
 
* 
IMPORTANT: If the display is filtered to show only Oracle instances the Databases table is renamed to Oracle Instances, and a new tab titled Reporting Services is shown. For details about this tab, see the following section.

Assigning Instances to Users

The User Level Access screen allows you to assign specific instances to users. As a result, when users view their Database dashboard, they will only see the instances which have been assigned to them. This makes it easier to find the data which is relevant to them.

The User Level Access screen only displays users who are not Administrative users.

To assign instances to a specific user:
1
On the main Database dashboard, click Settings and select Users Level Access from the menu.
The User Management pane appears.
2
Click Users. The table will display user names of non-Administrative users only, log in information, and instance information.
3
To assign one or more instances to a specific user, locate the user’s name in the table, click Configure, and then select Manage in the right-hand column.
4
In the Assign Instances view, select the instances which should be assigned to this user and click the > button to add the selected instances to the Assigned Instances column.
5
Click Set and Close to save your choices and exit.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택