Chat now with support
Chat with Support

Foglight for Azure SQL Database (Cartridge) 6.0.0 - User Guide

Installing and Configuring Agents Using Foglight for Azure SQL Database Administering Foglight for Azure SQL Database Reporting Reference
Overview of Collections SQL Performance Investigator Metrics
Active Connections Active Time Active Time per Execution Active Time Rate Always On Average CPU Percent Average DTU Percent Average Memory Usage Percent Average SQL Response Time Average XTP Storage Percent Average Data IO Percent Average Log Write Percent Backup Recovery Blocked Sessions Connections CPU Limit CLR Wait CLR Wait per Execution CLR Wait Rate CPU Time CPU Time per Execution CPU Time Rate CPU Wait CPU Wait per Execution CPU Wait Rate Cursor Synchronization Database Replication Deferred Task Worker Distributed Transaction DTU Limit Elapsed Time Executions External Procedure Full Text Search Governor Wait Governor Wait per Execution Governor Wait Rate Granted Memory Hosted Component Inactive User Connections I/O Bulk Load I/O Completion I/O Data Page I/O Wait I/O Wait per Execution I/O Wait Rate Idle Time Internal Cache Latch Latch Buffer Latch Savepoint Latch Wait Latch Wait per Execution Latch Wait Rate Lead Blockers Lock Bulk Update Lock Exclusive Lock Intent Lock Schema Lock Shared Lock Update Lock Wait Lock Wait Rate Lock Wait per Execution Log Buffer Log Other Log Synchronization Log Wait Log Wait per Execution Log Wait Rate Log Write Logical Reads Logical Reads per Execution Max Degree of parallelism Max DTU Percent Max Session Percent Max Workers Percent Memory Wait Memory Wait per Execution Memory Wait Rate Network HTTP Network I/O Network IPC Network Mirror Network Wait Network Wait per Execution Network Wait Rate OLEDB Provider Full Text Other Miscellaneous Other Wait Other Wait per Execution Other Wait Rate Parallelism Wait Percent of Total Plan Recompilations Physical Reads Physical reads per Execution Preemptive Wait Preemptive wait per Execution Preemptive Wait Rate Remote Provider Wait Remote Provider wait per Execution Remote Provider Wait Rate Row count Service Broker Synchronous Task Wait Time Percent Writes Writes per Execution XTP Log write Wait XTP Miscellaneous Wait XTP Procedure Wait XTP Transaction Wait XTP Wait XTP Wait per Execution XTP Wait Rate
Glossary

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 to be notified by email 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 and/or on a defined schedule, as described in the following topics:

•
Configuring an email server
•
Defining Default Email settings
•
Defining email notifications, recipients, and messages
•
Defining variables to contain email recipients
•
Defining scheduled email notifications
Configuring an email server

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.

Defining Default Email settings

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.

Enabling or disabling email notifications

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:

•
The alarm email notification setting is enabled for the affected rule.
•
The alarm is triggered by changes in the monitored environment.
•
Alarm notification is enabled at the triggered severity level. See Defining email notifications, recipients, and messages .
To enable or disable email notifications:
1
In the Alarms view, click the Settings tab.
2
Decide on the scope for the change: all alarms, a category of rules, or a selected rule.
3
Complete the steps for the selected scope:
 
Table 4. 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.

4
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:
1
In the Alarms view, click the Settings tab.
2
Decide on the scope for the change: all alarms, a category of rules, or a selected rule.
3
Complete the steps for the selected scope:
 
Table 5. Configure email notification settings
Scope
Procedure

All alarms

Click All Alarms. In the All Alarms 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 Email Notification 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.
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.
5
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.
6
Click Set to save the message configuration and close the dialog box.
7
If the Edit Notification Settings dialog box is open, click Set.
8
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:
1
On the navigation panel, under Dashboards, click Administration > Rules & Notifications > Manage Registry Variables.
2
Click Add.
The New Registry Variable Wizard opens.
3
Select the registry variable type String, and click Next.
4
In the Name field, enter a name, for example: EmailTeamName
Optional — Add a description.
5
Click Next.
6
Select Static Value.
7
In the Enter desired value box, enter one or more email addresses (separated by commas).
* 
NOTE: Email groups are not permitted.
8
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:
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.
2
In the Performance Calendars List table, click Add.
The Performance Calendar Wizard opens.
3
Select a schedule, for example: End of Day
4
Click Next.
5
Select Static Value.
6
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.
7
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:
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 Azure SQL Database 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, it is recommended to copy the rule and create 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, refer to 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 Azure in the Search field to see the list of predefined rules for Azure SQL databases.
The Foglight for Azure SQL Database 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.

Defining Connection Details

Use the Connection Details category to define global connection settings, which apply to all instances and hosts selected in the view. You can enable user-defined collections and set VMware connection details.

* 
NOTE: The following sections instructs how to define the connection settings for monitored Azure SQL databases.
Defining the Connection Settings for the Monitored Azure SQL databases

The Connection Details view contains a table that displays all the agents that were selected before entering the Databases Administration dashboard.

To define the connection settings for the requested agents:
1
Select the check boxes to the left of the agents for which uniform credentials are to be set. To cancel the selection, click Select None and select again.
2
Click Set Credentials.
The Edit Instance Credentials dialog box opens.
3
Use the Connection Details section to enter or accept the default port (1433).
4
Use the Specify Login Credentials section to select the type of authentication, specify the user name and the password used for connecting to the Azure SQL Database.
5
Click Set to proceed to the next stage of validating the database’s connectivity.
Validating Connectivity and Starting to Monitor the databases

After setting the default credentials for the host, these newly created credentials can now be used by the wizard to attempt to log in to the databases.

To validate the databases’ connectivity:
1
Click Test connection.
The Verifying Connectivity progress bar appears.
At the end of this process, any connectivity issues are listed in the Status column of the database table. When the connection is successful, the Status column displays the status message Validated, which indicates that the database connected successfully and the specified Azure SQL user has the required permissions.
If the connection failed verification, the Status column displays one of several connectivity status messages.
The messages, causes, and appropriate responses are:
•
Invalid username/password — check the credentials and try again.
•
Incorrect port— check if the SQL Azure port is correct and try again.
•
Wrong Database Credentials — modify the login credentials.
•
Insufficient Privileges — grant the user the privileges required for connecting to the database, by clicking the status Insufficient Privileges.
The Insufficient Privileges dialog box opens.
Use this dialog box to specify a Server Admin user with sufficient privileges.
Select the type of authentication. Type a Server Admin user and password, and then click Grant privileges.
If the Server Admin credentials entered were incorrect, the column displays the status Wrong Sysadmin credentials.
After correcting the mistakes that resulted in the connectivity failure, click again Validate connectivity.
2
Click Validate connectivity on the status bar.
3
Click Save Changes.
The Applying Modified Settings progress bar appears.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating