サポートと今すぐチャット
サポートとのチャット

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

Configuring User-defined Collections

Use the User-defined Collections view in the Databases Administration dashboard to add user-defined collections to all of the currently selected agents, in order to provide for queries not included in Foglight for Oracle.

After collections are added, this view displays all user-defined collections for all of the agents; for example, if a collection was added to 12 agents during its addition, the view will display 12 rows, showing the collection for each agent.

This view is also used for configuring the sampling frequency for each collection.

The available sampling frequencies are:

•
Real-Time - When a user is currently focusing on a screen, the sampling frequency for all of the collections associated with this screen switches to Real-Time.
•
Online - When at least one user is connected, the sampling frequency for all of the collections that are not currently running at Real-Time frequency switches to Online.
•
Offline - when no user is currently connected to the application
To add user-defined collections:
1
Select the requested agents.
2
Click Add.
If the user-defined collections are enabled for the selected agent, the Add a User-defined Collection dialog box opens. Proceed to Step 3.
If user-defined collections are not enabled, the User-defined Collections Not Enabled dialog box opens.
* 
IMPORTANT: Agents can also enabled for user-defined collections through the Connection Details view. For details, see Enabling and setting credentials for user-defined collections .
To enable and configure the creation of user-defined collections:
c
Click Edit credentials.
The Edit Credentials for User-defined Collections dialog box opens.
d
Select whether to perform the collection using the existing agent credentials or by creating dedicated credentials.
e
If the user-defined collections are to be enabled using dedicated credentials, type the requested user name and password.
f
Select whether to connect as SYSDBA.
g
Click OK.
h
The Applying modified settings progress bar is displayed. If the modified settings are su cess fully applied, the Add a User-defined Collection dialog box opens.
3
Click Set details.
The Set Collection Details dialog box opens.
4
Enter a name in the Collection name field.
5
Enter a brief description of the collection in the Collection description field (optional).
6
Paste the query’s SQL text in the Query Text field.
* 
IMPORTANT: This field can hold up to 4096 characters. Any PL-SQL Functions (that are not getting input) can be written by wrapping the PL-SQL “Select <pl_sql_func> From dual” statement.
7
Type a value, in seconds, in the Query Timeout field.
8
Use the Start Time field to define the time when the collection starts running (optional).
* 
IMPORTANT: If this field is left empty, the collection starts working immediately. The start time can only be defined using the wizard. After the collection starts working, at the time defined using the Start Time field, it will continue to run according to its defined frequency and can only be disabled.
9
Click Verify.
The collection is verified by running the query on each of the currently selected agents.
After the verification process is complete, the Verification Results pop-up appears, indicating whether the collection was verified successfully. In case the collection verification failed, the relevant error message is displayed.
If the verification succeeded on at least one agent, the collection’s details are displayed on the table described below.
 
Table 33. Collections details
Section
Field
Description
Database
ID

The collections’ ID

Column Name

The name of the column

Column Type

The field type, as retrieved by the query (String, Integer and so on)

Data Storage
Display Name

The column’s display name

 
Type

The topology type for storage purposes. This type can be one of the following:

•
String
•
Integer
•
Double
•
Boolean
•
Date
NOTE: When the Frequently modified check box is selected (the default state), the field’s change history is kept, including use of optional functionality such as use of the IntelliProfile mechanism and aggregation type selection. Clearing this check box is recommended only for fields whose values change infrequently, such as IP address of a specific host, as storing the change history of such fields is highly CPU-intensive and may degrade the FMS performance.
 
Unit of Measurement

The metric’s unit of measurement.

The possible measurement unit values are: Percent, Count, Millisecond, Second, Minute, Hour, Day, Byte, Kilobyte, Megabyte and Gigabyte.

 
Aggregation

Used for defining the value that is displayed in this metric, out of several values that were returned in the relevant time range.

The available aggregation values are:

•
As is — value of the last sample taken during the selected time range
•
Sum — summarized value of all samples taken during the selected time range
•
Average — average value of all samples taken during the selected time range
 
Is Key

Indicates whether the field is the query’s key for retrieval.

NOTE: Fields that are indicated as keys should correspond with the database result set unique values. Selecting a field which has frequently changing and repeating results as key is allowed, but may result in unexpected behavior from the defined collection.
 
Configured to use IntelliProfile

Select True in this column to enable the collection of baseline statistics for this metric.

 
Except for the Column Name and Column Type fields, whose values are retrieved by the query and cannot be changed, all other fields can be edited by clicking any of them.
The Edit Collection Properties dialog box appears, allowing you to edit the values of the following parameters:
•
Display name
•
Type
•
Unit of measurement
•
Aggregation
In addition, the collection’s sampling frequencies are displayed on the table at the bottom of the screen, and can be edited by clicking any of them.
10
Ensure that all settings are appropriate, and click OK to finish the collection creation process.
The newly created collection now appears on the table.
* 
IMPORTANT: After adding the requested user-defined collections, they can only be deleted or cloned to other agents. If one or more queries need to be modified, delete them and create new ones.

Configuring the On-demand Data Port

Use the On-demand Data Settings view in the Databases Administration dashboard to define a port for each Foglight Agent Manager to be used by for retrieving data and integrating with Performance Analysis.

To configure a port for the collection of on-demand data:
1
Select the check box near the names of the requested Foglight Agent Managers.
2
Click Set port.
The Set On-demand Data Port dialog box opens.
3
Type the name of the requested port.
4
Click Set.
5
Click Validate connectivity.
The Validate connectivity progress bar appears. At the end of the validation process, the connection status appears on the Status column.
If the connection failed, take the requested correction measures and try again.
* 
IMPORTANT: Changes to the On-demand Data Port view take effect immediately and do not need to be saved.

Changing the Monitoring Mode of the RAC One Node Agents

Use the RAC One Node view in the Databases Administration dashboard to change the monitoring mode of agents configured as RAC One Node, enabling the monitoring of such agents as regular RACs.

* 
NOTE: The RAC One Node view is only relevant for agents configured as RAC One Node. If no such agent was selected before entering the Databases Administration dashboard, this view will be empty.
To change the monitoring mode of a RAC One Node agent:
1
Click anywhere on the row of the RAC One Node agent (the root).
The Convert to Regular RAC dialog box appears, displaying one or more hosts.
2
Click the row of the RAC that is to be converted to regular RAC.
The Convert to Regular RAC dialog box opens.
3
From the list of hosts that appear in the dialog box, select the host that is to be converted to a physical RAC.
4
Click Validate to verify the selected host’s connectivity.
5
After the connectivity validation completes successfully, click Set.
* 
IMPORTANT: Converting a RAC One Node to a regular RAC is an irreversible process. The Save changes button is disabled on the RAC One Node view, and after clicking Set, the selected host is immediately converted to a physical RAC. Therefore, ensure that the requested host is selected before clicking Set.

After the selected host was converted to a physical RAC, use the Oracle Monitoring Installer wizard to add the other hosts monitored through this agent as nodes to the newly created RAC. For further details, see Using Foglight for Oracle on page 27.

Administering SQL Performance Investigator

The SQL Performance Investigator view in the Administration dashboard allows you to enable and disable SQL PI monitoring for selected agents. In addition, you can start and stop the collection of change tracking data.

In the SQL PI view, select one or more agents to enable or disable or for which to modify the change tracking status.

 

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択