Chatee ahora con Soporte
Chat con el soporte

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

Defining Connection Details

Use the Connection Details category to define global connection settings, which apply to all instances and hosts selected in the view. You can enable user-defined collections and set VMware connection details.

* 
NOTE: The following sections instructs how to define the connection settings for monitored Oracle instances.

Defining the Connection Settings for the Monitored Oracle Instances

The Connection Details view contains a table that displays all the agents that were selected before entering the Databases Administration dashboard.

To define the connection settings for the requested agents:
1
Select the check boxes to the left of the agents for which uniform credentials are to be set. To cancel the selection, click Select None and select again.
2
Click Set Credentials.
The Edit Instance Credentials dialog box opens.
3
Use the Connection Details section to enter the TNS listener port, or accept the default port (1521).
4
Use the Login Credentials section to type the user name and the password used for connecting to the Oracle instance.
5
Specify Use SSL require you to import database certificate into the FglAM certificate store at first.
All the certificate related command line options require that FglAM be up and running first. More details can be found in the FglAM command document.
* 
NOTE: The SSL connection for Oracle current just support TLS1.2 encryption for server authentication.
6
Select whether to enable OS monitoring, in order to retrieve OS-related data, such as CPU utilization and memory consumption. For instructions about configuring OS monitoring, see Configuring OS monitoring credentials .
* 
IMPORTANT: When enabling OS monitoring, ensure that the selected OS user has the privileges required for monitoring the operating system. For details, see the Foglight for Oracle Release Notes.
7
Select whether to enable and set user-defined collections. For more information, see Enabling and setting credentials for user-defined collections.
8
If the selected agents reside on a VMware virtual host, click Edit VMware connection details to define their connection details. For more information, see Defining the VMware Connection Profile.
9
Click Validate to proceed to the next stage of validating the instance’s connectivity.

Validating Connectivity and Starting to Monitor the Instances

After setting the default credentials for the host, these newly created credentials can now be used by the wizard to attempt to log in to the instances.

To validate the instances’ connectivity:
1
Click Test connection.
The Verifying Connectivity progress bar appears.
At the end of this process, any connectivity issues are listed in the Status column of the instance table. When the connection is successful, the Status column displays the status message Validated, which indicates that the instance connected successfully and the specified Oracle user has the required permissions.
If the connection failed verification, the Status column displays one of several connectivity status messages.
The messages, causes, and appropriate responses are:
•
No valid RAC nodes were detected (for a RAC) — modify the RAC nodes’ credentials.
•
Invalid username/password — check the credentials and try again.
•
Process Error — see the code error under the Details column.
•
Wrong Database Credentials — modify the login credentials.
•
Database Connection Failed — the database to which the instance tries to connect is not running or cannot be accessed. Ensure clearing the check box near the database’s name.
•
Insufficient Privileges — grant the user the privileges required for connecting to the database, by clicking the status Insufficient Privileges.
The Grant Database Privileges dialog box opens.
Use this dialog box to specify a SYSDBA (System Database Administrator) user with sufficient privileges.
Type a SYSDBA user and password, and then click Grant.
If the Sysdba credentials entered were incorrect, the column displays the status Wrong Sysdba credentials.
After correcting the mistakes that resulted in the connectivity failure, click again Validate connectivity.
2
Click Validate connectivity on the status bar.
3
Click Save Changes.
The Applying Modified Settings progress bar appears.
Configuring OS monitoring credentials
To configure the OS monitoring credentials:
1
Use the Host Credentials section to select whether to log in to the monitored host using the existing host connection details or to edit the host connection details.
2
If the option to edit the host connection details is selected, select whether to disable OS monitoring, which is enabled by default.
* 
IMPORTANT: When enabling OS monitoring, ensure that the selected OS user has the privileges required for monitoring the operating system. For details, see the Foglight for Oracle Release Notes.
3
Specify the requested authentication type:
•
Local user — using the same credentials that were used for running the monitoring software (Agent Manager) on the Oracle host.
•
Windows — the user name (in the domain\user name format) and password, used for logging in to a Windows-based monitored host.
•
SSH (DSA) — using the SSH private key, generated via the DSA algorithm.
•
SSH (RSA) — using the SSH private key, generated via the RSA algorithm.
•
SSH (login credentials) — the user name and password used for logging in to a UNIX-based monitored host.
4
If any option other than Agent Manager local user is selected, enter the required credentials.
* 
IMPORTANT: If either of the UNIX authentication types is selected, to run certain commands that require administrative privileges as root, without having to log in as administrator, select the Use sudo check box.
* 
IMPORTANT: It is possible to delete or edit existing credentials by clicking Select from stored credentials and entering the User Credentials dialog box. However, it is highly advisable not to make any changes to existing credentials, as such changes will affect all agents that currently use these credentials.
Enabling and setting credentials for user-defined collections

Use the user-defined collections feature to add customized collections to all of the currently selected agents, thereby providing for queries not included in Foglight for Oracle.

Use the Connection Details view to enable and configure the creation of user-defined collections.

To enable and configure the creation of user-defined collections:
1
Select the requested agents.
2
Click Set UDC credential.
The Edit Credentials for User-defined Collections dialog box opens.
3
Click Edit Credentials for User-defined Collections.
The Edit Credentials for User-defined Collections dialog box opens.
4
Select the check box Enable user-defined collections.
5
Select whether to perform the collection using the existing agent credentials or by creating dedicated credentials.
6
If the user-defined collections are to be enabled using dedicated credentials, type the requested user name and password.
7
Select whether to connect as SYSDBA.
8
Click Set.

To add user-defined collections, go to the User-defined Collections view in the Databases Administration dashboard. For details, see Configuring User-defined Collections .

Defining the VMware Connection Profile

If you have Oracle instances that run on virtual hosts, monitoring such instances requires setting a dedicated connection profile, in order to connect to the requested VMware server.

* 
NOTE: The VMware connection profile can be defined only if OS monitoring is enabled.

Establishing such a connection is necessary in order to retrieve the Virtualization overhead data, that is, the percentage of CPU that is unavailable to this virtual machine because it is being utilized either by other virtual machines or by VMware itself. The Virtualization Overhead indicator is displayed in both the real-time and history summary pages.

To edit the VMWare Connection Profile:
1
Select the requested agents.
2
Click Set credentials.
3
In the Edit Credentials dialog box, click Edit VMWare connection details.
The Edit VMWare Credentials dialog box opens.
4
Select the check box Enable monitoring the VMWare CPU layer.
5
Enter the details required for monitoring the CPU distribution data, that is: vCenter or ESX host name, port, VMware user, and VMware password.
6
Click OK.

Defining the Connection Settings for the Monitored ASM Instances

The Connection Details view contains a table, which displays all of the agents that were selected before entering the Databases Administration dashboard.

To define the connection settings for the requested ASM agents:
1
Go to the ASM tab.
2
Select the check boxes to the left of the requested ASM agents.
3
Click Settings.
4
Click Administration.
5
In the Connection Details view, select the check boxes to the left of the ASM agents for which uniform credentials are to be set. To cancel the selection, click Select None and select again
6
Click Set Credentials.
The dialog box Edit credentials of ASM instance opens.This dialog box is identical to the one used for configuring ASM instances for monitoring.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación