Foglight for SQL Server (Cartridge) 6.1.0.10

Table 65. Enable or disable email notification settings.
Scope	Procedure
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.

Click Save changes.

Defining email notifications, recipients, and messages

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.

To configure email notifications:

In the Alarms view, click the Settings tab.

Decide on the scope for the change: all alarms, a category of rules, or a selected rule.

Complete the steps for the selected scope:

Table 66. Configure email notification settings:

Scope

Procedure

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.

•

To change the severity level that warrants an email notification, click the link that displays the severities. Select the desired level of severity and click Set.

•

To configure email recipients and the message, select the tab for a severity level, and click Edit. Skip to Step 5.

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.

In the Message Settings dialog box, configure the email recipients and message.

•

To — Type the addresses of the people who need to take action when this alarm triggers.

•

CC — Type the addresses of the people who want to be notified when the alarm triggers.


	NOTE: If a mail server is not found, you are prompted to configure a mail server. For instructions, see Configuring an email server .

You can use registry variables in place of email addresses. Type the variable name between two hash (#) symbols, for example: #EmailTeamName#. For more information, see Defining variables to contain email recipients .

•

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 Prefix — Optional. Add text that should appear above the alarm information in the body of the email.

Figure 32. Message Settings

Click Set to save the message configuration and close the dialog box.

If the Edit Notification Settings dialog box is open, click Set.

Click Save changes.

Defining variables to contain email recipients

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.

To create a registry variable:

On the navigation panel, under Dashboards, click Administration > Rules & Notifications > Manage Registry Variables.

Click Add.

The New Registry Variable Wizard opens.

Select the registry variable type String, and click Next.

In the Name field, enter a name, for example: EmailTeamName

Optional — Add a description.

Click Next.

Select Static Value.

In the Enter desired value box, enter one or more email addresses (separated by commas).


	NOTE: Email groups are not permitted.

Click Finish.

The Edit Registry Variable dashboard displays the newly created registry variable.

To use a registry variable in email notifications, type the variable name between two hash (#) symbols, for example: #EmailTeamName#. For more information, see Defining email notifications, recipients, and messages .

Defining scheduled email notifications

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

To schedule the sending of email notifications for a registry variable:

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.

In the Performance Calendars List table, click Add.

The Performance Calendar Wizard opens.

Select a schedule, for example: End of Day

Click Next.

Select Static Value.

In the Enter desired value box, enter one or more email addresses (separated by commas) that should received email notifications based on the schedule.


	TIP: The addresses may the same as or different from those assigned to the registry variable.

Click Finish.

The Edit Registry Variable dashboard displays the newly created schedule. If desired, repeat to add other schedules.

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:

On the Databases dashboard, select the check box for the agent with the settings you want to clone.

Click Settings and then Administration.

In the Administration dashboard, click Alarms.

Click Set configuration on selected agents.

The Clone Alarm Settings cross Agents dialog box opens.

In the Select the source agent drop-down list, you should see the agent you selected.

In the Select the target agents table, select the check boxes for agents that should inherit settings from the source agent.

Click Apply.

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 SQL Server rules in the Rule Management dashboard. These rules may be modified during regular software updates and your edits will be 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. User-defined rules need to be managed 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:

On the navigation panel, under Homes, click Administration.

In the Administration dashboard, click Rules.

Type DBSS in the Search field to see the list of predefined rules for SQL Server databases.

The Foglight for SQL Server rules are displayed. From here, you can review threshold values, alarm counts, and descriptions.

To see the full rule definition, click a rule and then click View and Edit.

In the Rule Detail dialog box, click Rule Editor.

When you are done your review, click Rule Management in the bread crumbs to return to the dialog box.

Click Cancel to avoid changing the rule unintentionally.

Defining Data Collection and Storage Options

The Foglight for SQL Server’s agent collects and stores data at all times, even when the browser window that displays the data is not active. Use the Collection Frequencies view to specify:

•

Which collections are sampled and stored

•

The data collection values when sampling is carried out in offline, online, and real-time frequency modes

•

The collection frequency

When a user is currently focusing on a screen, the sampling frequency for all of the collections associated with this screen switches to Real-Time. The collection frequency determines the sampling frequencies of the other collections (that is, collections that are not running in Real-Time mode).

The available collection frequencies are as follows:

•

Low — all collections are running in Offline mode, regardless of whether a client is connected.

•

Normal — the collections' running mode (Online/Offline/Real-time) adjusts dynamically to the client's connection status (disconnected/connected/focusing on a screen).

•

High — all collections are running in Online mode, regardless of whether a client is connected.

•

The Query timeout for on-demand collections.

This setting defines the number of seconds that a query for on-demand collections can run before it times out.

On-demand collections are collections whose data is retrieved not by predefined time intervals but upon entering a screen or clicking a button.

The default setting of this parameter is 60 seconds, but it can be modified by clicking the number that indicates the parameter’s value in the field Query timeout for on-demand collections:.


	NOTE: This section displays only SQL Server-related collections. For details about Windows-related collections, see Configuring Performance Counters .

Table 67. The Collections table includes the following columns:


Column	Description
Collection Enabled	Indicates whether the selected collections are sampled and stored.
Collection Name	The name of the collection. This list is sorted in an alphabetical order.
Offline Frequency (Sec)	Allows defining the collection interval, in seconds, in offline mode (for example, 300). Offline frequency refers to the longest interval possible for sampling the monitored instance.
Online Frequency (Sec)	Allows defining the collection interval, in seconds, in online mode (for example, 60).
Real-time Frequency (Sec)	Allows defining the collection interval, in seconds, in real-time mode (for example, 20). Only one collection can be sampled at real-time frequency in any given moment.
Query Timeout (Sec)	The amount of time, in seconds, that elapses before the query times out.


	IMPORTANT: When the browser window that displays Foglight for SQL Server is active, the collection frequency mode in the active screen (for example: the Indexes pane in the Databases drilldown) switches to the fastest frequency possible - once every 20 seconds.

To modify the values of a specific collection:

Select the collection’s row in the table.

Click Edit.

The Edit the Collection dialog box appears.

Select whether to enable the collection and storage of the selected collection.

Set the collection interval, in seconds, in offline frequency mode (if available).

Set the collection interval, in seconds, in online frequency mode (if available).

Set the collection interval, in seconds, in real-time frequency mode.

Set the query timeout, in seconds.

Click Set to apply these settings or Cancel to reject them.

If no more editing is necessary, save the changes before switching to another screen. For details, see Reviewing the Administration Settings .