Chat now with support
Chat with Support

Foglight for DB2 (Cartridge) 6.1.0.10 - Getting Started Guide

Configuring Monitoring Agents

A wizard guides you through the process of configuring agents. You are prompted to specify connection details for the DB2 host, instances, and databases. As you go, you can validate log in credentials, database and instance connectivity, and host connectivity. You can correct issues by granting database permissions, setting monitoring switches, and configuring parameters.

To monitor DB2 instances:
1
In the navigation panel, under Homes, click Databases.
On a fresh installation, no instances are listed for DB2 in the Databases dashboard.
2
In the instances table, click Monitor more instances and select Add one DB2.
The Monitor DB2 Instance wizard opens.
3
Follow the online prompts to configure an agent to monitor the DB2 host, instance, and databases. For help with options, click .

Monitoring DB2 HADR Environments

A DB2 high availability disaster recovery (HADR) environment has two or more databases:

•
Primary Database — This is the active database.
•
Standby Database — Data from the primary database is propagated to standby databases.

A standby database can be opened in read-only mode and used for reporting. Running the standby database in reporting mode eases the load on the primary (production) database.

 
* 
NOTE: The HADR read on Standby option is available in DB2 version 9.7.1 or later and is subject to licensing. As of version 10, you can have more than one standby database for each primary database.

We recommend creating agents to monitor each of the instances with databases that participate in the HADR environment. This approach ensures that there is no loss of monitoring in a failover scenario.

For the primary database and for the standby databases that are in read-only mode, you create agents as usual to monitor their DB2 instances. For standby databases that are not in read-only mode, you can define the settings for its DB2 instance, but the wizard is unable to verify database connectivity. To resolve this issue, run the Grant Permissions script for the monitoring user on the standby database.

To monitor databases in a DB2 HADR environment:
1
Configure agents to monitor the instances that host the primary database and standby databases. See Configuring Monitoring Agents .
2
When selecting a standby database that is not in read-only mode, the wizard’s validate database connectivity step shows a message indicating the connection could not be verified. Installation can proceed but it is recommended that you click View grant script and make sure that the Foglight user has the required permissions on the standby database.

Monitoring IBM DB2 pureScale Environments

IBM DB2 pureScale® offers high availability and scalability through clustering technology. To monitor instances in a pureScale environment, ensure that the Permissions for DB2 pureScale Environments are set and then configure monitoring agents as usual. Foglight automatically reports on the pureScale cluster cache facility (CF) component, buffer pools and caches, locks, and request time breakdown.

The following pages and views contain monitoring data for pureScale:

•
Databases dashboard — The instance’s Host is identified as pureScale.
•
Instances home page — See the Additional Information and PureScale CF panes.
•
Instances home page > Memory — See the Primary CF and Backup CF tabs.
•
Database home page — See the Balance Criterion and Memory panes.
•
Database home page > Activity > Locks — See the PureScale Lock Time tab.
•
Database home page > Memory > Buffer Pools — See the GBP Hit Ratio tab.
•
Member (History) home page — See the Request Time Breakdown pane.
•
Member (Real Time) home page — See the Request Time Breakdown pane.
•
Member (either) home page > Activity > Locks — See the PureScale Lock Time tab.
•
Member (either) home page > Memory > Buffer Pools — See the GBP Hit Ratio tab.

 

Permissions

Permissions

Foglight monitoring agents use DB2 LUW user accounts to access monitored DB2 instances. The user accounts need to have the privilege and permission listed in Required DB2 LUW User Account Privileges . When these conditions are met, the Monitor DB2 Instance wizard checks that the rest of the required permissions exist and, if not, enables you to run the Grant Permissions script to grant missing permissions.

The Grant Permissions script verifies and sets the following general and pureScale-specific permissions.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating