ca insight database performance monitor for distributed...

CA Insight™ Database Performance Monitor for Distributed Databases

Insight AIM for CA eHealth Integration Guide r11.2.2

This documentation and any related computer software help programs (hereinafter referred to as the “Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the Documentation for their own internal use, and may make one copy of the related software as reasonably required for back-up and disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for the Product are permitted to have access to such copies.

The right to print copies of the Documentation and to make a copy of the related software is limited to the period during which the applicable license for the Product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE.

The use of any product referenced in the Documentation is governed by the end user’s applicable license agreement.

The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Copyright © 2008 CA. All rights reserved.

CA Product References This document references the following CA products:

CA Database Command Center (CA DCC)

CA eHealth Suite

CA Insight™ Database Performance Monitor for Distributed Databases (CA Insight DPM)

Insight AIM for CA eHealth

Contact Technical Support For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Technical Support at http://ca.com/support.

http://www.ca.com/support

http://www.ca.com/support

Contents v

Contents

Chapter 1: Overview and Installation 7 CA Insight DPM and CA eHealth Integration Overview............................................ 8

How You Integrate CA Insight DPM and CA eHealth .......................................... 9 Pre-Installation Tasks ......................................................................... 10 Installation of CA Insight DPM and Insight AIM for CA eHealth ................................... 10 CA Insight DPM Integration to Add Insight AIM for CA eHealth................................... 11

Integration on Windows ................................................................... 11 Integration on UNIX and Linux............................................................. 12

Pre-Configuration Tasks....................................................................... 12 Configuration of CA Insight DPM Knowledge Agents ............................................. 13

Manually Run the Insight AIM for CA eHealth Integration Utility .............................. 13 Post-Configuration Tasks...................................................................... 15 CA eHealth Element Discovery................................................................. 16

Discover CA Insight DPM Elements Using CA eHealth ........................................ 17 Discovering and Saving Application and System Elements ................................... 17

Insight AIM for CA eHealth Upgrades .......................................................... 17 Un-register Insight Knowledge Agents After Removal ........................................... 18 Alternative Database Monitoring Scenarios ..................................................... 19

Configure a Remote CA Insight DPM Knowledge Agent Using CA Database Command Center... 20 Modify IDDMOD.CF for the CA Insight AIM.................................................. 21 CA eHealth Elements...................................................................... 22 CA eHealth At a Glance Report............................................................. 22

Chapter 2: Work with the Insight AIM for CA eHealth 23 Generation of At-a-Glance and Trend Reports .................................................. 23 Display AdvantEDGE View Reports ............................................................. 24 Monitor Alarms Using Live Exceptions .......................................................... 25 Archive Considerations........................................................................ 26 How You Monitor the Embedded CA eHealth Database Using CA Insight DPM ..................... 26

Index 27

Chapter 1: Overview and Installation

This section contains the following topics:

CA Insight DPM and CA eHealth Integration Overview (see page 8) Pre-Installation Tasks (see page 10) Installation of CA Insight DPM and Insight AIM for CA eHealth (see page 10) CA Insight DPM Integration to Add Insight AIM for CA eHealth (see page 11) Pre-Configuration Tasks (see page 12) Configuration of CA Insight DPM Knowledge Agents (see page 13) Post-Configuration Tasks (see page 15) CA eHealth Element Discovery (see page 16) Insight AIM for CA eHealth Upgrades (see page 17) Un-register Insight Knowledge Agents After Removal (see page 18) Alternative Database Monitoring Scenarios (see page 19)

Overview and Installation 7

CA Insight DPM and CA eHealth Integration Overview

CA Insight DPM and CA eHealth Integration Overview CA Insight DPM knowledge agents collect and provide a comprehensive set of database health and performance metrics and threshold alarm conditions. The Insight AIM for CA eHealth enables CA eHealth to display and use this information.

8 Insight AIM for CA eHealth Integration Guide

CA Insight DPM and CA eHealth Integration Overview

How You Integrate CA Insight DPM and CA eHealth

There are several required and optional components for integrating CA Insight DPM with CA eHealth. This section provides a high-level overview of the integration process.

To integrate CA Insight DPM and CA eHealth, follow these steps:

1. Set up CA eHealth.

a. Install CA eHealth (eHealth Server).

b. Install any applicable CA eHealth Service Packs on the eHealth Server.

c. Install any applicable CA eHealth Certification Kits on the eHealth Server.

d. Reboot the eHealth Server.

2. Install the Database Command Center Portal (DCC Portal) on a different computer than the eHealth Server.

3. Set up the systems hosting the databases you plan to monitor using CA Insight DPM and Insight AIM for CA eHealth (targetDB system).

a. Install SystemEDGE SNMP Agent.

SystemEDGE is the SNMP agent that is a prerequisite to installing any AIM for CA eHealth including Insight AIM for CA eHealth.

b. Install CA Insight DPM and Insight AIM for CA eHealth.

CA Insight DPM and Insight AIM for CA eHealth need to be paired on the targetDB system. The Insight AIM for CA eHealth is a bridge between CA eHealth and the Insight knowledge agents and needs to interoperate with Insight knowledge agents on the same system. A single Insight AIM for CA eHealth installation can handle data from multiple configured Insight knowledge agents if needed.

c. Configure Insight knowledge agents on the targetDB system using the DCC Portal (includes configuration of the Insight AIM for CA eHealth in the same knowledge agent configuration job).

d. Register the Insight AIM for CA eHealth with SystemEDGE.

4. In CA eHealth, discover the Insight AIM for CA eHealth elements.


Pre-Installation Tasks

5. Install Live Health clients to access Live Health functionality (by downloading the Live Health application installer from the Live Health tab in the CA eHealth web interface).

Live Health comprises the following applications that connect to and pull information from the eHealth Server.

Trend

Displays statistics graphically over time.

Exception

Displays alarms.

Status

Displays enterprise level health.

Note: For more information about these procedures see the corresponding sections in this chapter.

Pre-Installation Tasks The following pre-installation tasks are required to ensure proper setup for your environment:

Install CA eHealth (eHealth Server)

Install any applicable CA eHealth Service Packs on the eHealth Server

Install any applicable CA eHealth Certification Kits on the eHealth Server

Install the SystemEDGE SNMP agent on the systems hosting the databases you plan to monitor using the Insight AIM for CA eHealth (targetDB systems)

Note: For information about installing and configuring CA eHealth and the SystemEDGE SNMP agent, see the CA eHealth documentation.

Installation of CA Insight DPM and Insight AIM for CA eHealth After completing the pre-installation tasks, use the procedures in the CA Database Command Center Implementation Guide if you are installing Database Command Center and CA Insight DPM in addition to Insight AIM for CA eHealth.


CA Insight DPM Integration to Add Insight AIM for CA eHealth

CA Insight DPM Integration to Add Insight AIM for CA eHealth

Use the information in this section to integrate a new or existing installation of Database Command Center and CA Insight DPM to add Insight AIM for CA eHealth.

Note: If you are upgrading Insight AIM for CA eHealth, rediscover the Insight AIM elements in CA eHealth to update the existing Insight AIM element's MIB information.

Integration on Windows

Use this section to integrate an existing CA DCC and CA Insight DPM installation with the Insight AIM for CA eHealth on Windows.

To add Insight AIM for CA eHealth on Windows

1. Run setup.exe from the installation media.

The welcome and license agreement pages appear.

2. Review and accept the license agreement.

The CA Database Command Center Product Installation Menu appears.

3. Select one of the following installation types to add Insight AIM for CA eHealth and select Next:

Unicenter DCC Agents and Advanced Database Products

Custom

You will be prompted for the features you plan to install.

4. Select the Insight AIM for CA eHealth option and any other features you require.

Note: The Insight AIM for CA eHealth option will only appear if SystemEDGE is installed. Selecting this option will automatically select the Unicenter Insight for Distributed Agents option for a mandatory update of the Insight binaries.

A selection confirmation summary appears.

5. Select Install to continue with the installation.

An installation confirmation appears.

Note: If the options you select require you to enter Management Database (MDB) information, you can check the current MDB settings using Start, Programs, CA, CA Database Command Center, Config Tool, Administration.


Pre-Configuration Tasks

Integration on UNIX and Linux

Use this section to integrate an existing CA DCC and CA Insight DPM installation with the Insight AIM for CA eHealth on UNIX and Linux.

Note: If the explicitly declared path to the SystemEDGE install is different than the default (/opt/EMPsysedge), you must know the location and enter it during the Insight AIM for CA eHealth installation.

To add Insight AIM for CA eHealth on UNIX and Linux

1. Run INSTALL.SH from the installation media.

The license agreement page appears.

2. Review the license agreement, type Y, and press Enter to accept the license agreement.

The installer verifies the CA DCC Common Services, Enterprise Communicator, and CA ODBC components.

The CA Database Command Center Product Installation Menu appears.

3. Type the number that corresponds with the Install Insight AIM for CA eHealth option and press Enter.

The installer prompts for any additional information necessary and confirms the installation.

Pre-Configuration Tasks There are no additional pre-configuration tasks specific to Insight AIM for CA eHealth.

Note: For CA Insight DPM pre-configuration tasks, see the CA Database Command Center Implementation Guide.


Configuration of CA Insight DPM Knowledge Agents

Configuration of CA Insight DPM Knowledge Agents Use the procedures in the CA Database Command Center Implementation Guide to configure your CA Insight DPM knowledge agents by selecting DCC Configuration, Insight Configuration, Knowledge Agent Configuration wizard. If Insight AIM for CA eHealth is installed and ready to be integrated with CA Insight DPM, the Insight knowledge agent configuration job will also configure Insight AIM for CA eHealth, by running the Insight AIM iddmodcfg configuration utility. The configuration utility is a script that updates iddmod.cf in %UVROOT%\bin or $uvroot/bin.

If Insight AIM for CA eHealth is installed, and the Insight knowledge agent configuration job ends with a Product Status of Completed, it indicates that the Insight AIM for CA eHealth configuration also ran successfully. You should see a message such as the following in the log file:

Successfully ran the Insight agent AIM Integration utility... Successfully configured Agent "ora-AIX92@usacaaix516"

If the Insight AIM for CA eHealth configuration failed, even though the Insight knowledge agent job itself was successful, the job ends with a Product Status of Incomplete indicating that the Insight AIM for CA eHealth failed and requires manual intervention.

Manually Run the Insight AIM for CA eHealth Integration Utility

You can run the Insight AIM for CA eHealth integration utility manually if the Insight AIM configuration fails (the Insight knowledge agent job ends as incomplete in this case).

To manually run the integration utility

1. (Windows) Open a command prompt and cd to %uvroot%\bin on the knowledge agent host.

2. (UNIX and Linux) cd to $uvroot/bin on the knowledge agent host.


Configuration of CA Insight DPM Knowledge Agents

3. Execute the following command:

iddmodcfg add|remove knowledge_agent_type port_number knowledge_agent_name host [local]

add|remove

Indicates whether to add or remove the knowledge agent from the list of knowledge agents iddmod manages.

knowledge_agent_type

Indicates db2, ms2005, mssql, ora, or syb as the knowledge agent type.

port_number

Indicates the port number.

knowledge_agent_name

Indicates the full Insight knowledge agent name (for example, ora-ora001@comp001).

host

Indicates the host where the knowledge agent is running (defaults to the local host except when providing the [local] option).

[local]

Indicates to iddmodcfg that the monitored RDBMS is local. Use this keyword if the monitored RDBMS is local and host alias names are involved in the knowledge_agent_name or host arguments. If [local] is not specified, iddmodcfg will consider the monitored RDBMS as remote except if no alias name is involved, and the monitored RDBMS is effectively local. In other words, use of [local] is mandatory only if the monitored RDBMS is local and alias names are involved.


Post-Configuration Tasks

Post-Configuration Tasks The following post-configuration tasks are required to ensure proper setup for your Insight AIM for CA eHealth environment.

Note: For more information about CA Insight DPM post-configuration tasks see the CA Database Management for Distributed Databases Implementation Guide.

(UNIX and Linux only) Set the library path in the root account to point to the PEC library directory. The CA eHealth SystemEDGE agent must be started and stopped by the root user. Insight AIM for CA eHealth requires that the SystemEDGE agent be started with the PEC libraries in the appropriate load library path (Solaris & Linux = $LD_LIBRARY_PATH; AIX = $LIBPATH; HP-UX = $SHLIB_PATH). As root user, source in the rtinit.sh shell script before starting the SystemEDGE agent.

For example, if PEC is installed in /fs1/pec, source in /fs1/pec/bin/rtinit.sh as the root user:

/fs1/pec/bin/rtinit.sh (for bash, borne, and korn shell users) source /fs1/pec/bin/rtinit.sh (for c-shell users)

(UNIX and Linux only) Run the idd_post_install.sh script before starting the CA Insight DPM knowledge agent for UNIX and Linux. The script requires you to set the CA DCC environment. Perform the following tasks:

1. Set the CA DCC environment based on one of the following:

If you did not let the install update your profile, source in $UDCC_HOME/bin/udminit.csh (C-shell users) or $UDCC_HOME/bin/udminit.sh (all other shell users).

If you let the install update your profile, log out and log back in as udcc user.

2. Run the post installation script as root using one of the following commands:

su root; $uvroot/idd_post_install.sh sudo $uvroot/idd_post_install.sh


CA eHealth Element Discovery

Register Insight AIM for CA eHealth with SystemEDGE. To avoid restarting SystemEDGE several times, run the appropriate script after configuring all Insight knowledge agents on a host.

– On Windows, after you configure and launch Insight knowledge agents, perform one of the following tasks:

Stop SystemEDGE, execute iddmodcfg add2sysedge, and start SystemEDGE.

Execute addidd2systemedge.bat (which does everything listed previously).

This must be done as a user with administrative privileges on the host.

– On UNIX and Linux, after you configure and launch Insight knowledge agents; as the root user, source udminit.sh (udminit.csh for C shell) in $UDCC_HOME/bin.

Note: The $UDCC_HOME environment variable will not be set for the root user, so you must use the full path to udminit.sh.

Execute iddmod_register.sh start located in the $uvroot/bin directory. The iddmod_register script stops the SystemEDGE agent, adds the iddmod.so load library module to the /etc/sysedge.cf file as a sysedge_plugin, and restarts the SystemEDGE agent.

Note: To remove iddmod from SystemEDGE, use iddmod_register.sh stop.

CA eHealth Element Discovery The CA eHealth discovery process creates CA eHealth elements for each manageable device and component that it finds in your network, lists these elements, and stores them in the poller configuration. You can run discovery interactively using the CA eHealth console or run the process as a scheduled system job on a regular basis. Each process offers specific benefits. As a best practice, when you run the discovery process for the first time, use an interactive discovery. After you run it once, create a scheduled discovery job to run periodically.

You run the interactive discovery processes from the CA eHealth console whenever you want to discover devices. An interactive discovery process suggests changes for new and updated elements, as well as resolved and unresolved changes. You can edit the discovery results before saving them to resolve those changes and ensure that CA eHealth does not add duplicate elements to the poller configuration.


Insight AIM for CA eHealth Upgrades

You use scheduled discovery jobs to automatically keep the poller configuration up-to-date for any network changes. Scheduled discovery jobs can either update your configuration automatically or inform you of the discovery results without making changes.

Note: For more information on managing the CA eHealth discovery process see the CA eHealth documentation.

Discover CA Insight DPM Elements Using CA eHealth

Run the CA eHealth discovery process to add CA Insight DPM elements to CA eHealth.

To discover CA Insight DPM elements using CA eHealth

1. Select both System and Application from the mode list.

2. Enter the community string that has been configured for the SystemEDGE agent (located in the /etc/sysedge.cf file on UNIX and Linux).

3. Enter the IP address of the computer you want to discover.

4. Click Discover to start the discovery process.

Note: CA Insight DPM element names include an IDD keyword.

Discovering and Saving Application and System Elements

Before discovering and saving any UNIX Insight AIM application elements, make sure that the corresponding system elements have been discovered and saved previously (and separately). Discovering and saving both application and system elements through the same discovery would result in problems with certain variables. For instance, the first page of the At-A-Glance Reports for Oracle and Sybase application service elements will display ‘Variable not supported' for the Physical Memory graph and the rest of the first page would be truncated.

Insight AIM for CA eHealth Upgrades If you upgrade the Insight AIM for CA eHealth component from an existing installation, rediscover your Insight AIM elements from your CA eHealth installation after the upgrade to realize the changes delivered in the new version.


Un-register Insight Knowledge Agents After Removal

Un-register Insight Knowledge Agents After Removal If you remove an Insight knowledge agent, you must manually un-register it from Insight AIM for CA eHealth.

In addition, a step is required specifically for Oracle knowledge agents to avoid a problem with AdvantEDGE View Reports.

To un-register an Insight knowledge agent

1. Execute iddmodcfg with the remove option.

This command removes the knowledge agent from the list of knowledge agents that iddmod manages.

Note: For more information about this command, see the "Manually Run the Insight AIM for CA eHealth Integration Utility“ section of this guide.

2. (Knowledge Agents for Oracle) Complete the following tasks:

a. Look for lines from the iddmod.cf file (located in $uvroot\bin) that begin with the ora token such as the following examples:

ora 1 myhost 5104 ora-sid1@myhost


If there are no lines with the ora token, the deleted instance was the only one. Change the instancehighwater ora counter to instancehighwater ora 0. Delete the CA eHealth elements corresponding to the deleted instance if you plan to configure and register a new Oracle instance of the Insight AIM for CA eHealth.

If there are lines with the ora token and they are numbered consecutively starting with 1, you deleted the last registered Insight knowledge agent. Update the instancehighwater ora counter to the same value as the highest remaining knowledge agent. Delete the CA eHealth elements corresponding to the deleted instance if you plan to configure and register a new Oracle instance of the Insight AIM for CA eHealth.


Alternative Database Monitoring Scenarios

For example if the following lines remain:



Change instancehighwater ora 3 to instancehighwater ora 2.

If there are lines with the ora token but they are not numbered consecutively or do not start with 1, there are holes in the numbering (including cases where there is one instance, but it is not number 1). In this situation, you must delete (in CA eHealth) the Oracle elements corresponding to these entries. If this is not acceptable (for example if you want to keep history data on these element), then do not continue with the next step (renumbering entries). In this case, you may get erroneous or unavailable AdvantEDGE View Reports for the Oracle AIM. Erroneous results most typically include a -1 value for the Service Name.

If it is acceptable for you to delete the CA eHealth elements, and you delete them using CA eHealth, proceed with renumbering (in iddmod.cf) the remaining Oracle instances consecutively starting with 1.

For example, if the following lines remain:



Replace the value ora 3 with ora 2 so that the values are consecutive and start with 1, resulting in the following:



Update the instancehighwater ora counter to the same value as the highest remaining knowledge agent and use CA eHealth to rediscover the Oracle elements.

3. Recycle SystemEDGE.

The knowledge agent is un-registered from Insight AIM for CA eHealth.

Alternative Database Monitoring Scenarios The integration procedure describes one method to make the corresponding data available to CA eHealth, via the Insight AIM for CA eHealth. This method involves having the monitored RDBMS, SystemEDGE, CA Insight DPM, and the Insight AIM for CA eHealth all reside on the same machine. This is the only scenario where the full Insight AIM for CA eHealth functionality is available.



The alternative database monitoring scenarios, described in this section, detail a remote method that you can also use to obtain the required RDBMS metrics. In this configuration, process set metrics from the SystemEDGE agent do not accurately report the respective environment and would then not be applicable.

Note: Remote monitoring is supported in CA Insight DPM version r11.2.2 and later.

Assuming the monitored RDBMS resides on host RDBMSHost, it can be monitored and made available to CA eHealth without CA Insight DPM, the Insight AIM for CA eHealth, or SystemEDGE being present on the same RDBMSHost host, as in the following examples:

One host, with both SystemEDGE and the Insight AIM for CA eHealth must be chosen. This host is the host to be discovered and polled by CA eHealth for monitoring the RDBMS residing on RDBMSHost. It may be different from RDBMSHost, and will be referred to as SystemEDGE-AIM-Host in this scenario.

One host with CA Insight DPM itself must be chosen, where the Insight knowledge agent will be running. It may be different from RDBMSHost and SystemEDGE-AIM-Host, and will be referred to as InsightHost in this scenario.

This section describes the way to monitor the RDBMS if at least one of these three (RDBMSHost, SystemEDGE-AIM-Host, or InsightHost) is different from the others.

Configure a Remote CA Insight DPM Knowledge Agent Using CA Database Command Center

In the scenario where InsightHost and RDBMSHost are different, use the following process to configure the remote CA Insight DPM knowledge agent through the CA Database Command Center (DCC) Web interface:

1. Discover the database instance that will be remotely monitored (should be on RDBMSHost).

2. Connect to the desired database instance via the database console or server tree.

3. Configure a database CA Insight DPM knowledge agent by selecting the database instance to monitor and selecting InsightHost as the system where this knowledge agent will run (that is not the server that contains the database instance being monitored in this case).

4. Refresh the database console tree in the DCC.



5. Start the knowledge agent.

Note: For more information on any of these steps see the CA Database Management for Distributed Databases Implementation Guide or the CA Database Command Center Online Help.

Modify IDDMOD.CF for the CA Insight AIM

Remotely monitoring databases via Insight AIM for CA eHealth is possible by making some necessary modifications to the iddmod.cf file (or iddmodinst.cf file with any patch), located in the %uvroot%\bin (for a windows installation) or $uvroot/bin (for a UNIX/Linux installation) on the SystemEDGE-AIM-Host host.

To modify the iddmod.cf (or iddmodinst.cf) file

1. Cd to %uvroot%\bin or $uvroot/bin.

2. Open the iddmod.cf (or iddmodinst.cf) file using a text editor.

3. Search for monitored instances section.

4. Manually register the Insight agent instances by adding a line using the following format: <dbmstype><number><InsightHost>CA Portal<InsightKnowledgeAgentName>

dbmstype

The database type (ora, syb, ms2005, or mssql).

number

This is the value of the instancehighwater line (in the same file) for the dbmstype.

InsightHost

The name of the host where the CA Insight DPM knowledge agent is running.

port

The remote Insight port number (by default this port is usually 5104).

InsightKnowledgeAgentName

The full (remote) CA Insight DPM knowledge agent name (typically in the format dbmstype-instance@hostname).

5. Update the corresponding instancehighwater value.

Increase the instancehighwater <dmstype> line by each database type you add to remotely monitor that database.

6. Remove the comment (#) from the ACCEPTREMOTE option, if present. If this option is not present, enter it as ACCEPTREMOTE.




7. Save the file.

When you uncomment the ACCEPTREMOTE keyword, functionality is altered. Within a remote monitoring configuration, the following CA eHealth report metrics are no longer applicable and should be disregarded:

CA eHealth Process Footprint metrics

CA eHealth ProcessSet elements metrics

CPU Utilization(%)/Transaction metric (for SQL Server and Oracle databases)

The host name of the remotely monitored database instance will not be reflected in the CA eHealth elements or its aView reports.

Key performance indicator metrics as well as the database quality index continue to accurately represent health and the performance of the remotely monitored databases.

CA eHealth Elements

You must perform a discovery process of the system where the SystemEDGE agent is installed and the remote database has been defined. Use the CA eHealth discovery process via the CA eHealth console.

CA eHealth At a Glance Report

After completing the modifications, you can view an At a Glance report using the CA eHealth portal.

Chapter 2: Work with the Insight AIM for CA eHealth

This chapter provides basic information on using Insight AIM for CA eHealth.

Note: For more information about CA eHealth see the CA eHealth documentation.

This section contains the following topics:

Generation of At-a-Glance and Trend Reports (see page 23) Display AdvantEDGE View Reports (see page 24) Monitor Alarms Using Live Exceptions (see page 25) Archive Considerations (see page 26) How You Monitor the Embedded CA eHealth Database Using CA Insight DPM (see page 26)

Generation of At-a-Glance and Trend Reports An At-a-Glance report is composed of a series of charts that show the performance of critical variables for a specified element during the report period. You typically run these reports for a particular element to obtain immediate, detailed information on the critical performance parameters. The charts that appear in an At-a-Glance report vary, depending on the element type that the report represents.

A Trend report shows the behavior of one or more performance variables for an element or a group of elements, over a specified period of time. Because of its flexibility, you can use a Trend report to reveal traffic patterns over time, as well as relationships between elements and between variables. If it indicates that two variables are correlated, then it suggests a causal relationship between them.

Note: For each RDBMS type, a DB Quality Index variable is available for CA eHealth Reports. This variable provides an overall indication of Database Health; therefore it will often be appropriate to include it in Reports. It is already included (in the first position) in the At-a-Glance reports for DB2, Oracle, SQL Server, and Sybase.

Work with the Insight AIM for CA eHealth 23

Display AdvantEDGE View Reports

Display AdvantEDGE View Reports AdvantEDGE View provides reports for the application-specific data that the CA eHealth AIMs collect.

To display AdvantEDGE View reports

1. Select the Systems & Apps tab in the CA eHealth WEB interface.

The Systems & Apps tab appears.

2. Select the AdvantEDGE View link.

The AdvantEDGE View pane appears.

3. Select the system you want to query from the System list, select the “Insight - <dbmstype>” line of your choice from the Applications list, and click the Applications icon.

You will access the corresponding aView Reports.


Monitor Alarms Using Live Exceptions

Monitor Alarms Using Live Exceptions The Live Exceptions area of Live Health lets you display Insight agent alarm information for the systems you need to monitor.

Note: To view alarm information, you must configure the SystemEDGE agent you are using to send traps to the CA eHealth console node.

To monitor Insight agent alarms using Live Exceptions

1. Define CA eHealth system groups and group lists if you have not already, including the systems you want to monitor.

2. Select Live Exceptions, Setup Menu, Subjects to Monitor.

The Setup Subjects dialog appears.

3. Click New.

The Setup Subjects Editor dialog appears.

4. (CA eHealth 5.7 only) Select System from the technology combo box.

5. Select Subject Type from Groups or Group Lists as appropriate, and select the groups or group lists you want in the Subjects area

6. Select any combination of the following profiles, in the Profiles list:

SystemEDGE Monitor – Insight DB2 Alarms Presence by Type

SystemEDGE Monitor – Insight DB2 Alarms Global Alarms Status

SystemEDGE Monitor – Insight DB2 Individual Alarms

SystemEDGE Monitor – Insight Oracle Alarms Presence by Type

SystemEDGE Monitor – Insight Oracle Global Alarms Status

SystemEDGE Monitor – Insight Oracle Individual Alarms

SystemEDGE Monitor – Insight SQL Server Alarms Presence by Type

SystemEDGE Monitor – Insight SQL Server Global Alarms Status

SystemEDGE Monitor – Insight SQL Server Individual Alarms

SystemEDGE Monitor – Insight Sybase Alarms Presence by Type

SystemEDGE Monitor – Insight Sybase Alarms Global Alarms Status

SystemEDGE Monitor – Insight Sybase Individual Alarms

7. Click OK to validate the changes in the Setup Subjects Editor dialog.

The Setup Subjects dialog appears.

8. Click OK to save your changes

The number of rows in the Alarms Event pane depends on which of the following profiles you apply:

Work with the Insight AIM for CA eHealth 25

Archive Considerations


Presence by Type profiles result in a single row for each alarm type, for the corresponding DBMS type, as soon as there is at least one alarm of that type. Even if there is more than one alarm of that type, only one row will appear for that type.

Global Alarms Status profiles result in a single row if there is any number of Insight agent alarms, of any type, for the corresponding DBMS type

Individual Alarms profiles result in a single row for every individual alarm for the corresponding RDBMS type.

Archive Considerations CA eHealth collects, stores, and manages historical data for Insight AIM for CA eHealth elements the same as it does for any other CA eHealth elements. It does not use data coming from the CA Insight DPM archive process.

Note: For more information about CA eHealth historical data see the CA eHealth documentation.

How You Monitor the Embedded CA eHealth Database Using CA Insight DPM

You can monitor the embedded CA eHealth repository using an Insight AIM for CA eHealth. This section provides an overview of the set-up process.

Note: This process assumes that all prerequisites are complete.

To monitor the embedded repository, follow the same steps as for monitoring an Oracle database.

For CA eHealth 5.7 only, perform the following additional tasks before configuring the Insight knowledge agent for Oracle:

1. Go to Services, select CA DCC Job Administration, right click and select properties.

2. Select the Log On tab and change the Log on to This Account.

3. Enter the user and password for the CA eHealth administrator account created prior to CA eHealth installation.

4. Stop and Start the CA DCC Job Administration service.

Index

A AdvantEDGE View queries • 24 architecture, integration • 8 At-a-Glance reports • 23

C configuration • 13

D DB Quality Index • 23 Discovery, eHealth • 16

E element discovery • 16

I installation • 10 integration

integration, architecture • 8 integration • 9 upgrade, UNIX • 12 upgrade, Windows • 11

L Live Exceptions • 25

M monitor embedded eHealth database • 26

P post-configuration tasks • 15 pre-configuration tasks • 12 pre-installation tasks • 10

R reports

reports, At-a-Glance • 23 Trend • 23

T Trend reports • 23

Index 27

ca insight database performance monitor for distributed...

Documents