Foglight for Oracle (Cartridge) 6.3.0

A concentrator agent, created specifically for Foglight for Oracle, allows controlling the RMI server so that the server is initialized (starts collecting data) when the agent starts, and stops when data retrieval by the agent is brought to an end. The agent, which is created manually by the user, requires configuring the following parameters:

•

A list of the downstream hosts that are connected through the concentrator

•

The RMI port number

Each time the Foglight Management Server sends an RMI request, the list of downstream hosts submitted by the concentrator agent is being searched.

•

Inclusion of the target RMI server host name within this list indicates that a Foglight Agent Manager concentrator exists, in which case a connection is made to the proxy RMI server.

•

If the list does not contain the target host name, the connection is made directly to the target RMI server.

To create the concentrator agent:

Go to Dashboards > Administration > Agents > Agent Status.

Click Create Agent.

Select the agent type DB_Oracle_Concentrator.

Enter a name of your choice in the Instance Name field.

Click Create.

After the creation process is completed successfully, click OK.

To edit the concentrator agent connection details:

Select the newly created concentrator agent.

Click Edit Properties.

Click Modify properties for this agent only.

Enter the number of the proxy RMI server port, or accept the default number.

Enter the concentrator Foglight Agent Manager host name (optional).

Click Edit to edit the list of downstream Agent Managers.

Click Add Row.

Enter the name of the requested Foglight Agent Manager host.


	IMPORTANT: When editing the properties of the Foglight Agent Manager concentrator (Dashboards > Administration > Agents > Agent Status), the name of the Foglight Agent Manager should be entered in the Downstream FglAMs section exactly as it appears in the topology, under Home > Agents > All agents > <Agent name> > RMI data > Fglam host property. The <Agent name> parameter refers to any of the Foglight for Oracle agents that reside on the selected Foglight Agent Manager.

Repeat Step 7 to Step 8 as many times as required.

Click Save Changes.

Click Save at the lower right corner of the screen.

Click Back to Agent Status.

Select the newly created concentrator agent.

Click Activate.

Click OK to complete the process.


	IMPORTANT: In an environment that includes a Foglight Agent Manager concentrator, when upgrading the environment where the concentrator does not contain any regular agents, the concentrator is not upgraded. Therefore, after the upgrade process takes place the Foglight Agent Manager concentrator has to be deployed manually.

Installing and Monitoring a Single Oracle Instance

Enabling the Foglight Management Server to monitor Oracle instances requires the creation of the Foglight agents that monitor these instances and ensuring that these agents communicate properly with the Foglight Management Server.

Foglight for Oracle provides a graphic, intuitive method for creating and configuring multiple agents, which can be used instead of Foglight’s default method for creating agents and editing their properties using the Agent Administration dashboard. Foglight for Oracle allows you to run a wizard that provides a common entry point for adding and discovering all database instances within a user-specified range, and then configuring these instances for monitoring.


	IMPORTANT: When running Foglight for Oracle in a Federation architecture, neither the creation nor the administration of agents can be accomplished from the central Foglight Management Server (the Federation Master). These two tasks should be carried out from the stand-alone Management Servers (the Federated Children).


	NOTE: When the feature multitenant container database (CDB) architecture is enabled, the customer should create the user with "container=all". create user c##cust identified by cust container=all; grant connect to c##cust container=all;

To run the instance installation wizard:

On the navigation panel, click Homes > Databases.

Click Monitor > Oracle in the upper left corner of the Databases View.

The Monitor Oracle Instance dialog box appears.


	NOTE: If a user-defined database group is currently selected, the databases table's title displays the name of this group instead of All; however, all newly discovered or created databases are added to the general (All) group of databases.

Choose the agent manager on which the agent will be running The default is the agent manager with the least agents installed.

Click the Agent Manager Host <agent manager> link located at the top of the Oracle Connection section.

A dialog box appears with a list of all agent managers connected to the Foglight management server.

Select the appropriate host name and click Set.


	IMPORTANT: You have the option set this host as the default for all future installations.

Use the Connection Details section to select the requested method for entering connection details:

•

TNS — used for selecting a database from the tnsnames.ora file by clicking Load file.

•

Host — Manually enter Host, port and either service name or SID.

Use the Login Credentials section to specify the username and password to be used for monitoring the Oracle instance.

Use SSL: Select whether an SSL connection should be used. For details, see Defining the Connection Settings for the Monitored Oracle Instances .

In the Configuration section, select the Alarm Template to use for this instance. The Factory Template will be applied by default. Refer to Viewing, Creating, and Managing Alarm Templates in the Foglight User Guide for more information.

Optional To enable SQL Performance Investigator, select SQL PI in the Monitoring Extension section.
The SQL PI Repository dialog is displayed. Select the Agent Manager on which the SQL PI

repository should be installed. Then click Apply.

If the SQL PI repository existed on the selected Agent Manager, no more action is required for the configuration.

If no SQL PI repository exists on the selected Agent Manager, the SQL PI Repository Settings


	NOTE: To use gMSA authentication for connections to the PI Repository, select Local User in the Authentication drop-down. This requires that your FMS and Agent Manager are configured to run as a Windows Service logged on with the gMSA account. The gMSA account requires access to the SQL instance.

If the given SQL PI repository user does not have sufficient privileges, the Insufficient Privileges
dialog will be displayed. Enter an admin user and password, and then click Grant Privileges.

Optional —In the Monitoring Extensions pane, click the Operating System link.

To configure the extension, choose the connection details of the host on which the Oracle instance is running:

•

Local user — using the same credentials that were used to launch the Agent Manager.

•

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.

To enable OS monitoring using a DSA key (UNIX users only):

Create one or more Oracle agents using the Oracle Monitoring Installer wizard (without OS monitoring).

Navigate to the Foglight Management Server credentials view (Dashboards > Administration > Cartridges > Credentials > Manage Credentials).

Add credential of type DSA key and link this credential to the agents created in Step a. For details, see “Adding and deleting credentials” in the Foglight Administration and Configuration Guide.

Go to Agent Status screen (Administration > Agents > Agent Status)

Select the agent or agents created in Step a.

Click Edit Properties.

Select Modify the private properties for this agent.

Under the Agent Management section, set Enable OS collections to True.

•

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.

Optional — In the Monitoring Extensions pane, click Collect VM statistics.

To configure the extension, select the connection details of the vCenter or ESX on which the Oracle instance is running:

•

The name of IP address of the vCenter server that hosts the Oracle instance virtual machine, or the name of its parent ESX server

•

The port number used by the vCenter server system or by ESX server for listening to the connections from the vSphere Client (default: 43).

•

The name and password of the user that has the privileges required for connecting to the vCenter server or ESX server and retrieving information.

Click Monitor.


	IMPORTANT: If the monitoring verification fails click the message that is displayed on the Status column and resolve the issue according to the instructions that appear in the dialog box. For example, (for example: insufficient privileges, incorrect credentials or an Agent Manager that reached its full monitoring capacity.

When the installation completes successfully, the Monitoring Initialized Successfully dialog box appears. Click Add another Database or Finish to exit.

Discovering Multiple Instances to Monitor

To discover additional instances to monitor:

In the upper left corner of the Databases View, click Monitor > Oracle.

The Monitor Oracle Instance dialog box appears.

Click the Use this option to discover multiple Oracle instances link.

The Select an Agent Manager Dialog box appears.

Choose an Agent Manager host validate and click Next.


	IMPORTANT: At the bottom of the pane you can select a default agent manager for all Future installations.

Click Add instances and select one of the following methods for adding instances:

•

Load a TNS file. See Loading a TNS file

•

Add manually. See Adding CRS Agents for Monitoring Clusterware

Select the check boxes beside the instances whose credentials are to be configured.

Click Set credentials on the toolbar to provide the login credentials of the instances

Follow the steps described in Installing and Monitoring a Single Oracle Instance , beginning with Step 5 to enter the monitoring credentials and enable the monitoring extensions for this instance.


	NOTE: To use stored credentials when enabling the Operating System monitoring extension, click the Operating System > Select from stored credentials link to open the Stored Credentials dialog box. Here you can review the login credentials and authentication methods used for logging in to Foglight. Foglight stores encrypted credentials in lockboxes, which may be password-protected for added security. Database agents store all user login credentials in a default lockbox called DB-Agent Lockbox. If credentials have already been entered in another lockbox, use the Lockbox list to select from that lockbox.

Click Validate.

If during the connectivity validation process several RACs with a single active node are detected, a dialog box appears asking you to identify the RACs that are not RAC One Node.

Select the check boxes near the multi-node RACs and click OK. After the validation process completes, all instances that passed the validation process successfully are displayed in the table with the status Validated.

Select the validated instances and click Next.

Use the Monitor Oracle Instances screen to review the table that displays all instances that passed the connectivity validation successfully.

•

To add other instances or modify the connection details of existing instances, click Previous.

•

To confirm the selection and start monitoring the instances, click Next.

After clicking Next, the table displays all instances that were configured for monitoring.

At the end of this process, the Status column of the instance table displays either the status Monitored, for the instances that connected successfully to the database or a status that indicates failure of the connectivity verification process and the reason for the failure. Click this text to view a dialog box that allows changing the credentials or to grant privileges, depending on the message that appears on the Status column:

•

If the message is Insufficient database privileges, this issue can be resolved using the Insufficient Database Privileges dialog box that appears. For details, go to Step 12.

•

For all other messages, the Database Connection Failed dialog box appears. For details, go to Step 13.

Click Insufficient Database Privileges.

The Insufficient Database Privileges dialog box appears.

This dialog box allows you to specify a SYSAdmin (System Administrator) user with sufficient privileges.

Enter a SYSDBA user and password, and then click Grant Privileges. Alternatively, click the View script link, to the right of the Grant privileges button, to grant privileges manually by means of a script.

Click the message text.

A dialog box that shows the message details appears.

Click Show details to view the error's description.

Click Set credentials to display the dialog box used for entering the credentials, and enter the required changes.