Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

Invalid Objects Filtering

Invalid Objects Filtering

Use the Exclude List pane to excluding specific schemas from being monitored by the Invalid Objects collection.

To exclude a schema from being monitored:
1
Select the agent that monitors the instance where the schema resides.
* 
IMPORTANT: If the selected agent is a RAC node, changes made will apply to RAC agent, thereby affecting the entire RAC.
2
Click Add a Schema to the Exclude List.
3
Use the dialog box that appears to enter the name of the requested schema.
4
Click Add.
5
Repeat this procedure for all of the schemas that are to be excluded.
To remove schemas from the table, select the schema’s row and click Delete.
6
At the bottom of the view, click Save changes.

Configuring the Alert Log Filtering Panel Display

Use the Alert Log Filtering view to configure the retrieval and display settings for the Alerts > Alert Log panel. In addition, this view is used to define default settings for invoking alarms based on the collected alerts.

* 
IMPORTANT: While alerts whose severity type is Informational are collected and displayed on the Alert Log panel, alarms are invoked only for alerts whose severity type is Warning or higher.

Use this view to define the following settings:

•
Minimal severity for invoking summary alarms — can be either turned off or set to one of the defined severity values, that is: Warning, Critical or Fatal.
* 
IMPORTANT: By default, the value of this parameter is Critical.
•
Minimal severity for invoking alarms — can be either turned off (the default setting) or set to one of the defined severity values: Warning, Critical or Fatal.
•
Number of rows to collect from logs — the maximum number of rows that would be retrieved from the alert logs.
•
Display under a pre-defined name in the Alert Log panel — using the Match List pane. This pane contains a default list of expressions within the alert logs that are to be retrieved and displayed in the Alert Log panel under a pre-defined name, category and severity.
•
Exclusion from the Alert Log panel display — using the Ignore List pane, which contains a default list of alerts that are to be excluded when setting the alert logs display.
* 
IMPORTANT: Only messages that are explicitly defined in the Ignore List will not be displayed. Messages that were not added to either the Match or Ignore lists appear under name Other, type Oracle alert messages and severity Informational. Therefore, ensure that messages that need not be displayed are added to the Ignore List.

Both the Match List and the Ignore List panes can be customized by adding, editing or removing alert logs. Each filter can be enabled or disabled separately by clicking Edit and selecting or clearing the Enabled check box. Alternatively, to enable or disable all of the filters, click the Enable All or Disable All button.

To add an alert to the Match List:
1
Click Add.
The Add an Alert to the Match List dialog box opens.
Use this dialog box to configure the alert filter by means of the following fields:
•
Filter Name — used for assigning a name to the filter.
•
Severity — used for assigning a severity for the alert. Use this field to set the type of the alarm that is invoked as a result of the alert, or to define that the alert is informational and therefore invokes no alerts.
•
Type — used for entering a filter type, either one of the predefined types or a new type.
•
Expression — identifies the text that is to be extracted as a message from the alert log and displayed in the Message column of the Alert Log panel > Alert Log Messages table. This text usually contains the beginning of the message and a wildcard (for example: ORA-12012.*).
* 
IMPORTANT: Alert filters are enabled automatically upon addition. To disable a filter, use the Edit button.
2
Click Add to save your settings.
Each newly added alert filter is enabled by default. To disable the filter, click Edit and then clear the Enabled check box.
To edit an alert:
1
Click the requested alert log.
2
Click Edit.
The Edit the Selected Alert dialog box opens.
3
Use this dialog box to configure the alert by means of the same fields used for adding it: Filter Name, Severity, Type, and Expression.
4
To disable the filter, clear the Enabled check box.
5
Click Set to save your settings.
6
At the bottom of the view, click Save changes.

Configuring the List of Listeners per Instance

Use the Listeners Monitoring view in the Databases Administration dashboard to edit the list of monitored listeners per instance, by adding or removing listeners from the list.

To add listeners to an instance:
1
Open the drop-down list below the title Please select an agent:, to display the entire list of selected agents.
* 
IMPORTANT: As RAC agents whose version is earlier than 11G2 have no listeners, they are not included in the list, even if such agents appear in the list of selected agents.
2
Select a single agent from the list.
3
Click Add Listener.
The contents of the Add a Listener dialog box that appears now vary between Windows and UNIX. For instructions for Windows-based agent, go to Step 4.
In UNIX, enter a listener service name in the designated field.
4
For a Windows-based agent, type data in the following fields:
•
Listener name — the name of the listener
•
TNS Admin — the path of the $TNS_ADMIN directory (usually $ORACLE_HOME/network/admin)
5
Click Add.
The newly added listener appears in the Listeners table.
To edit the properties of a single listener:
1
Select the requested listener from the table.
2
Click Edit Listener.
3
In the Edit a Listener dialog box, edit the existing data in the various fields (see Step 4 of the procedure for adding a listener).
4
Click Set to apply the changes or Cancel to revert to the previous settings.
To stop monitoring a listener:
1
Select the requested listener from the table.
2
Click Delete Listener.
The Stop Monitoring a Listener dialog box opens.
3
Click Yes to confirm the deletion or Cancel to keep monitoring the listener.
4
At the bottom of the view, click Save changes.

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 34. 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.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation