Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Foglight for DB2 (Cartridge) 6.3.0 - User Guide

Introduction to Foglight for DB2 LUW Using Reference
Dashboards and Views Collections and Metrics
CF Locks Collection CF Memory Pools Collection CF Resource Usage Collection Current Agents Details Collection Agents Summary Collection Current Locks Wait Collection Database Bufferpools Summary PS Collection Database Configuration Collection Database Tablespaces Collection Database Tablespaces Summary Collection Database Usability Collection Database Parameters Collection Database Instance Parameters Collection Database Instance Registry Variables Collection Database Tablespaces BP Collection FCM Activity Collection FS DB Storage Collection FS DB Storage Summary Collection FS Instance Storage Collection FS Storage Collection FS Storage Summary Collection General Activity Collection HADR Activity Collection Host Properties Collection OS General Collection Instance Activity Collection Instance General Collection Instance Nodes Collection Instance Usability Collection IO Activity Collection License Details Collection Log Activity Collection Log File Collection Log Message Collection Messages Count Collection Monitor Switches Collection OS DB2 General Process Collection Partition Tablespaces Summary Collection Partition Usability Collection pureScale Alerts Collection Top SQLs Collection Query Agents Details Collection Database Partition Activity Collection DB2 Partition Subcategories Wait Collection History Locks Wait Collection History Locks Summary Collection Instance Memory Collection Instance Memory Pool Collection Instance Memory Summary Collection Instance Memory Total Collection Database Memory Collection Database Memory Pool Collection Database Memory Pool DB Collection Database Memory Summary Collection Database Memory Total Collection Database Buffer Pools Collection Database Tables Collection Database Partition Backup Collection Database Tables Global Collection Database Applications Collection

Cloning Agent Settings

You may want an agent to have the same settings as another agent. For example, if you add new agents, you may want them to use the same settings as an existing agent. In this case, you can clone the settings from one agent to other agents.

This process does not link the agents; in the future if you update the source agent, you also need to update the target agents.

This procedure walks you through selecting the source agent from the Databases dashboard. However, you can also open the Administration dashboard with multiple agents selected. In this case, you select the source agent in Clone Alarm-related Settings to Other Agents dialog box.

To clone alarm-related settings:
1
On the Databases dashboard, select the check box for the agent with the settings you want to clone.
2
Click Settings and then Administration.
3
In the Administration dashboard, click Alarms.
4
Click Set configuration on selected agents.
The Clone Alarm settings cross agents dialog box opens.
5
In the Select the source agent drop-down list, you should see the agent you selected.
6
In the Select the target agents table, select the check boxes for agents that should inherit settings from the source agent.
7
Click Apply.
8
When prompted for confirmation, click Yes.

Reviewing Rule Definitions

If you want to review the conditions of a rule, open the rule in the Rule Management dashboard.

* 
IMPORTANT: Avoid editing Foglight for DB2 LUW rules in the Rule Management dashboard. These rules may be modified during regular software updates and your edits are lost. Always use the alarm templates to modify rules.

You can create user-defined rules from the Rule Management dashboard. If you want to modify a rule, we recommend copying the rule and creating a user-defined rule. Manage user-defined rules from the Rule Management dashboard; these rules are not displayed in the Alarms view of the Databases Administration dashboard. For help creating rules, open the online help from the Rule Management dashboard.

To open the Rule Management dashboard:
1
On the navigation panel, under Homes, click Administration.
2
In the Rules & Notifications dashboard, click Rules.
3
Type DB2 in the Search field to see the list of predefined rules for DB2 databases.
The Foglight for DB2 LUW rules are displayed. From here, you can review threshold values, alarm counts, and descriptions.
4
To see the full rule definition, click a rule and then click View and Edit.
5
In the Rule Detail dialog box, click Rule Editor.
6
When you are done your review, click Rule Management in the breadcrumbs to return to the dialog box.
7
Click Cancel to avoid changing the rule unintentionally.

Adding User-defined Collections

This page allows you to add user-defined collections to all the currently selected agents and to provide for queries not included in Foglight for DB2.

* 
IMPORTANT: Agents must be enabled for user-defined collections. If the requested agent is not enabled for such collections, go to the Connection Details page and click the agent to edit it.

After collections are added, this page displays all the user-defined collections for all the agents. For example, if a collection was added to 12 agents during its addition, the page displays 12 rows, showing the collection for each agent.

This page is also used for configuring the sampling frequency for each collection. The available sampling frequencies are as follows:

•
Real — a user is focusing on a page, the sampling frequency for all the collections associated with this page switches to Real-Time.
•
Online — when at least one user is connected, the sampling frequency for all the collections that are not currently running at Real-Time frequency switches to Online.
•
Offline — when no user is connected to the application
To add user-defined collections:
1
Click Add.
The Add a User-defined Collection dialog box appears.
2
Click Set details.
The Set Collection Details dialog box appears.
3
Enter a name in the Collection name field.
4
Enter a brief description of the collection in the Collection description field.
5
Paste the query’s SQL text in the Query Text field.
* 
NOTE: This field can hold up to 4096 characters.
6
Type a value, in seconds, in the Query Timeout field.
7
Click Verify.
The collection is verified by running the query on each of the currently selected agents. After the verification process is complete, the Verification Results pop-up appears, indicating whether the collection was verified successfully. In case the collection verification failed, the relevant error message is displayed. If the verification succeeded on at least one agent, the collection’s details are displayed.
Table 4. Collection details
Section
Field
Description
Database
ID

The collections’ ID

 
Column Name

The name of the column

Column Type

The field type.(String, Integer, etc.)

Data Storage
Display Name

The column’s display name

 
Type

The topology type for storage purposes. This type can be one of the following:

•
String
•
Integer
•
Double
•
Boolean
•
Date
NOTE: When the Frequently modified check box is selected (the default), the field’s change history is kept. This includes use of optional functionality such as use of the IntelliProfile mechanism and aggregation type selection. Clearing this check box is recommended only for fields whose values change infrequently, such as IP address of a specific host. Storing the change history of such fields is highly CPU-intensive and may degrade the FMS performance.
 
Unit of Measurement

The metric’s unit of measurement. The possible measurement unit values are: Percent, Count, Millisecond, Second, Minute, Hour, Day, Byte, Kilobyte, Megabyte and Gigabyte.

 
Aggregation

Allows defining the value that is displayed in this metric, out of several values that were returned in the relevant time range.

The available aggregation values are:

•
As is — value of the last sample taken during the selected time range.
•
Sum — summarized value of all samples taken during the selected time range.
•
Average — average value of all samples taken during the selected time range.
 
Is Key

Indicates whether the field is the query’s key for retrieval.

NOTE: Fields that are indicated as keys should correspond with the database result set unique values. While a field whose results are frequently changing and repeating can be selected as key, such a selection may result in unexpected behavior from the defined collection.
 
Configured to use IntelliProfile

Select True in this column to enable the collection of baseline statistics for this metric.

8
The Edit Sampling Frequencies section allows you to change sampling frequencies. Click the required frequency.
The Edit Frequencies for the Collection dialog box appears.
9
Enter the required changes.
10
Click Set.
11
Click OK.
* 
IMPORTANT: After adding the collection by clicking OK, you will not be able to make changes except to modify the collection frequencies and enable or disable the collection.

On-demand Data Port

The On-demand Data Settings page allows you to define a port for each Foglight Agent Manager. Foglight for DB2 uses this port to retrieve data and for integration with StealthCollect. By default, the collection of on-demand data is carried out using the same port used for connecting to the Performance Analysis middleware. Use this page to collect on-demand data through a different port, or if another port was allocated to the Performance Analysis middleware.

To configure a port for the collection of on-demand data:
1
Select the check box near the names of the requested Foglight Agent Managers.
2
Click Set port.
The Set On-demand Data Port dialog box appears.
3
Type the number of the requested port.
4
Click Set.
5
Click Validate connectivity.
The Validate connectivity progress bar appears. At the end of the validation process, the connection status appears on the Status column.
* 
IMPORTANT: Changes to the On-demand Data Port page take effect immediately and do not need to be saved.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation