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

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

Adding ASM Instances

The process of adding ASM instances is almost identical to the process of adding Oracle instances as described in:

To add ASM instances go to the ASM tab. Click Monitor more ASM instances at the upper left corner of the Databases table.

If the installer detected that the ASM instance is part of an ASM cluster, a dialog box appears asking you to verify the connection details.

After ASM instances are configured, the ASM tab will provide access to a more detailed ASM Dashboard. For details, see Reviewing ASM Instances

Configuring Multiple Instances for Monitoring using Silent Installation

1
In the navigation panel, under Dashboards, click Administration > Cartridges > Components for Download.
2
Click the Installer icon beside DB_Oracle_CLI_Installer.
oracle_cli_installer.groovy — a groovy script file that runs the silent installation. This file should be copied to the <FMS_HOME>/bin directory.
oracle_silent_installer_input_template.csv — a template file that should serve as the basis for inserting contents into the input CSV file. This file can be copied to any folder of your choice, provided that the path indicated by the <oracle_instances_file_name> parameter (see below) points to the selected path. For details about the contents of this file, see Contents of the input CSV file for Oracle instances
5
Copy the oracle_cli_installer.groovy file to the <FMS_HOME>/bin directory.
<FMS_HOME>: The Foglight Management Server installation directory.
<fms_host_name>: The name of the host where the Management Server is installed.
<fms_url_port>: The Management Server HTTP port.
<fms_user_name>: The user name used for connecting to the Management Server.
<fms_user_password>: The password of the specified user.
<clusters_file_name>: The full path and the name of the input CSV file.
<lockbox_name>: Optional — specifies the name of an existing lockbox that would be used.
<lockbox_password>: Optional — the selected lockbox's password.
A file with the input file's name and _status suffix (for example: if the input file is named input, this file is named input_status).
The _status file includes the name of the monitored Foglight for Oracle agent, the result of the monitoring validation process - MONITORED, FAILED, or AGENT EXISTS - and the error message, in case the agent creation failed.
A file with input file's name and _new suffix (for example: if the input file is named input, this file is named input_new).

Contents of the input CSV file for Oracle instances

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

RAC Agent Name

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

Instance Type

The type of the instance to be monitored. The possible values are: SINGLE, NODE, RAC ONE NODE.

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 Oracle instance or RAC.

Port

The TNS listener port.

Connection Method

The requested connection method. The possible values are either SERVICE_NAME or SID.

SID/Service Name

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

User name

The name of the user to be used for connecting to the instance.

Password

The password of the database user name.

Administrator User Name (Optional)

The user name of a user that can grant privileges to the regular database user; required only if the regular user does not have sufficient privileges.

Administrator Password (Optional)

The password of the database administrator user name mentioned above.

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:

OS User Name (Optional)

The user name required for connecting to the OS.

OS Password (Optional)

The password of the OS user specified above.

SSH Port (Optional)

The port that is used for listening to 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.

Enable VMware Collection (Optional)

Indicates whether to monitor VMware metrics; The possible values are TRUE or FALSE.

VMware Host (Optional)

The VMware host name.

VMware Port (Optional)

The VMware port. If no value is inserted in this field, the port number to be used is the default number 443.

VMware User Name (Optional)

The user name required for connecting to the VMware.

VMware Password (Optional)

The password of the VMware user specified above.

Configuring Multiple Instances for ASM

1
In the navigation panel, under Dashboards, click Administration > Cartridges > Components for Download.
2
Click the Installer icon beside DB_Oracle_ASM_CLI_Installer.
asm_cli_installer.groovy — a groovy script file that runs the silent installation. This file should be copied to the <FMS_HOME>/bin directory.
asm_silent_installer_input_template.csv — a template file that should serve as the basis for inserting contents into the input CSV file. This file can be copied to any folder of your choice, provided that the path indicated by the <asm_instances_file_name> parameter (see below) points to the selected path. For details about the contents of this file, see Contents of the input CSV file for Oracle instances
5
Copy the asm_cli_installer.groovy file to the <FMS_HOME>/bin directory.
<FMS_HOME>: The Foglight Management Server installation directory.
<fms_host_name>: The name of the host where the Management Server is installed.
<fms_url_port>: The Management Server HTTP port.
<fms_user_name>: The user name used for connecting to the Management Server.
<fms_user_password>: The password of the specified user.
<fglam_name>: The name of the selected Foglight Agent Manager where new agents are to be added.
<clusters_file_name>: The full path and the name of the input CSV file.
<lockbox_name>: Optional - specifies the name of an existing lockbox to be used.
<lockbox_password>: Optional - the selected lockbox's password
A file with the input file's name and _status suffix (for example: if the input file is named input, this file is named input_status).
The _status file includes the name of the monitored Foglight for Oracle agent, the result of the monitoring validation process - MONITORED, FAILED, or AGENT EXISTS - and the error message, in case the agent creation failed.
A file with input file's name and _new suffix (for example: if the input file is named input, this file is named input_new).
관련 문서