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

Foglight for DB2 (Cartridge) 5.9.4.20 - User Guide

Introduction to Foglight for DB2 LUW Using Foglight for DB2 LUW 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

Introducing the Alarms View

The Alarms view enables you to modify global settings and agent-specific settings for alarms.

2
Click Alarms.

Setting and Modifying Alarm Sensitivity Levels

Foglight for DB2 LUW has four sensitivity levels that control which alarms are reported:

Essential — Store and display only critical or fatal alarms.
Normal — Store and display most alarms — essential and best practices; only critical and fatal statistical alarms.
Tuning — Store and display all SQL Server alarms sent to Foglight.

You can change the sensitivity level assigned to each agent. If a sensitivity level does not include all the alarms you want to track or includes too many alarms, you can view a list of multiple-severity rules and modify the sensitivity level that is mapped to each severity.

Changes made to a sensitivity level affect all agents that are assigned that sensitivity level. If you want to enable or disable alarms for the selected agents, see Enabling or disabling alarms for selected agents .

Each agent has its own sensitivity level setting. The default is Normal.

1
In the Alarms view, click the Sensitivity Level tab.
4
Click Save changes.

You can view a list of multiple severity rules to see which severities are assigned to which sensitivity level. If desired, you can change the assignments. Changes to sensitivity levels affect all agents.

To see descriptions of the rules, follow the steps described in Reviewing Rule Definitions .

1
In the Alarms view, click the Sensitivity Level tab.
2
Click Define sensitivity levels.
3
If you want a record of the existing settings, click View as PDF and export the settings to a PDF file.
5
Click Set level.
7
Click Set.

Modifying Alarm Settings

You can customize how the alarms generated by the default Foglight for DB2 LUW rules are triggered and displayed in the Alarm view’s Settings tab. All changes to alarm settings apply to the selected agents, except for thresholds, which can be customized by agent.

IMPORTANT: Avoid editing Foglight for DB2 LUW rules in the Administration > Rules & Notifications > Rule Management dashboard. Default rules may be modified during regular software updates and your edits are lost. Always use the Alarms view.

The Alarms list controls the contents displayed to the right and the tasks that are available.

All Alarms — Displays all rules with configured alarms and indicates whether alarms are enabled. In this view, you can enable or disable alarms for all the rules at once. You can also set email notifications and define mail server settings.
Category of rules — Displays a set of related rules with configured alarms. In this view, you can enable or disable alarms and also set email notifications for the category of rules.
Rule name — Displays the alarm status for the selected rule. If the rule has multiple severity levels, display the threshold configured for each severity level. In this view, you can enable or disable the alarm, edit the alarm text, and edit severity levels and their thresholds. You can also set email notifications for the alarm.

You can complete the following tasks:

Your changes are saved separately and applied over the default rules. This protects you from software upgrades that may change the underlying default rules.

You can override the global alarm sensitivity level setting for the selected agents. You can enable or disable alarms for all rules, a category of rules, or an individual rule.

To see descriptions of the rules, follow the steps described in Reviewing Rule Definitions .

All alarms

Click All Alarms. In the Alarms Settings tab, click either Enable all or Disable all.

Category of rules

Click a category. Click either Enable all or Disable all.

Selected rule

Click the rule. In the Alarms Settings tab, click the link that displays the alarm status. Select Enabled or Disabled from the list and click Set.

4
Click Save changes.

You can and should modify the thresholds associated with alarms to better suit your environment. If you find that alarms are firing for conditions that you consider to be acceptable, you can change the threshold values that trigger the alarm. You can also enable or disable severity levels to better suit your environment.

When a rule has severity levels, a Threshold section appears in the Alarm Settings tab showing the severity levels and bounds by agent. For an example, see the DBSS - Worker Thread rule. The threshold values corresponds to the lower bounds shown in this table. Many rules, such as Baseline rules, do not have severity levels and thresholds.

When editing thresholds, ensure that the new values make sense in context with the other threshold values. For most metrics, threshold values are set so that Warning < Critical < Fatal. However, in metrics where normal performance has a higher value, such as DBSS - Buffer Cache Hit Rate, the threshold values are reversed: Warning > Critical > Fatal.

TIP: If you want to review the thresholds for all Foglight for DB2 LUW rules in a single view, use the Rule Management dashboard. In the navigation panel, click Homes > Administration, then click Rules. Type DBSS in the Search field to see the list of predefined rules for SQL Server databases. For rules with severity levels, you can see the threshold values set for each level. If you want to edit threshold values, return to the Alarms view. Edits made directly to the default rules may be overwritten during software upgrades.
3
Click the Alarms Settings tab.

Edit severity levels and set threshold (lower bound) values for all agents.

Click Enhance alarm. Select the check boxes for the severity levels you want enabled and set the threshold values. Click Set.

Change the threshold (lower bound) values for one agent.

Click Edit beside the agent name. Set the new threshold values and click Set.

Copy the changes made to one agent’s threshold values to all other agents.

Click Edit beside the agent name that has the values you want to copy. Select Set for all agents in table and click Set.

6
Click Save changes.

For individual rules, you can change the message displayed when an alarm fires. You cannot add or remove the variables used in the message. This is a global setting that affects all agents.

3
Click the Alarm Settings tab.
4
Click Enhance alarm.
6
Click Set.
7
Click Save changes.

Configuring Email Notifications

We recommend that you set email notifications for the alarms you are most interested in tracking closely. For example, you may want email notifications of any Critical or Fatal situation. Or you may want to be informed whenever a key metric, such as CPU usage, is no longer operating within acceptable boundaries.

You can set up email notifications that are generated when an alarm fires or on a defined schedule, as described in the following topics:

You need to define the global mail server variables (connection details) to be used for sending email notifications. The setting of the email should be configured in Foglight Administration > Email configuration.

You can define a default email address to be used by every new agent created in the future, by selecting the Default email button when configuring email notification.

The Email addresses entered are applied to all monitored agents not only for the agents that were selected to enter the Alarm administration.

You can enable or disable email notifications for all alarms, a category of alarms, or a selected rule. Email notifications are sent only if all the following conditions are met:

All alarms

Click All Alarms. In the Alarms Settings tab, click the Define Email Settings button. Select either Enabled or Disabled from the Alarms notification status list. Click Set.

Category of rules

Click a category. Click the Define Email Settings button. Select either Enabled or Disabled from the Alarms notification status list. Click Set.

Selected rule

Click a rule. In the Alarms Settings tab, click the Define Email Settings tab. Click the link that displays the alarm notification status. Select Enabled or Disabled and click Set.

4
Click Save changes.

You control who receives email messages, the subject line, and some text in the body of the email. The body of the email always contains information about the alarm. This information is not editable. You can also control whether an email is sent based on severity levels. You can set different distribution lists for different rules and different severity levels, or set the same notification policy for all rules.

All alarms

Click All Alarms. In the Alarms Settings tab, click the Define Email Settings button. Continue to Step 4.

Category of rules

Click a category. Click the Define Email Settings button. Continue to Step 4.

Selected rule

Click a rule. Click the Define Email Settings tab.

4
If you selected All Alarms or a category, in the Email Notification Settings dialog box, do one of the following:
To change the severity levels that warrant an email notification, from the Messages will be enabled for severities box, select the desired levels of severity.
To configure the same email recipients and message for all severity levels, click Configure mail recipients for all Severities and then click All severities.
To configure different email recipients and messages for each of the severity levels, click Configure mail recipients for the following options and then click a severity level.
To — Type the addresses of the people who need to act when this alarm triggers.
CC — Type the addresses of the people who want to be notified when the alarm triggers.
Subject — Optional. Edit the text of the subject line to better suit your environment. Avoid editing the variables, which are identified with the @ symbol.
Body PrefixOptional. Add text that should appear preceding the alarm information in the body of the email.
6
Click Set to save the message configuration and close the dialog box.
8
Click Save changes.

You can create registry variables that contain one or more email addresses and (optionally) their scheduled notifications, and use these registry variables when defining email notifications. This procedure describes how to create a registry value. For schedules, see Defining scheduled email notifications.

1
On the navigation panel, under Dashboards, click Administration > Rules & Notifications > Manage Registry Variables.
2
Click Add.
3
Select the registry variable type String, and click Next.
5
Click Next.
6
Select Static Value.
8
Click Finish.

If someone wants to receive an email about an alarm regularly, such as once a day, you use a registry variable schedule to set up the notification.

1
If you are continuing from Defining variables to contain email recipients, the registry variable is already open for editing in the Edit Registry Variable dashboard.
TIP: To edit a different variable, navigate to the Administration > Rules & Notifications > Manage Registry Variables dashboard, click the variable name, and select View and Edit Details.
4
Click Next.
5
Select Static Value.
7
Click Finish.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation