Chat now with support
Chat with Support

Foglight for SQL Server (Cartridge) 5.7.5.30 - User Guide

Managing SQL Server Database Systems Introduction to this Guide Using Foglight for SQL Server Monitoring Business Intelligence Services Administering Foglight for SQL Server Glossary Reference

Configuring the Database to be Excluded

Monitoring all of the databases within all of the agents can unnecessarily load the system, as not all databases require such monitoring, due to being either non-mission critical or less significant. The Exclude Databases from Monitoring view allows excluding such databases from monitoring. Use this view to select the agents from which databases are to be excluded from monitoring, and then specify, either manually or by selecting from a list, which databases to exclude.
The On-demand Data Settings view in the Databases Administration dashboard allows defining a port for each Foglight Agent Manager (FglAM) to be used for retrieving data and integrating with Foglight SQL PI.
To exclude databases from monitoring:
1
Click Exclude databases.
* 
NOTE: Selecting a specific agent from which databases are to be excluded is done using the dialog box that opens upon clicking this button.
The dialog box Specify Databases for Exclusion appears.
2
Use the list Select specific agent or all agents to select an agent from which databases are to be excluded. Alternatively, select the option All selected agents.
3
Specify which databases to exclude from monitoring, either by adding their names manually or by selecting them from the list and clicking to move them to the list of excluded agents.
4
Click OK.

Reviewing Foglight for SQL Server Alarms

Alarms are the warnings that Foglight for SQL Server raises when a metric falls outside its “normal” range of values, which is defined by setting thresholds and severities for the metric within the Metric editor. A new alarm is raised whenever the severity for a metric changes. When the severity returns to normal, the alarm is canceled.
* 
IMPORTANT: Only several alarm types are invoked for instances monitored using the vFoglight for SQL Server Add-on mode. For details, see Viewing Data Displayed on vmExplorer.
* 
NOTE: For a complete list of alarms invoked by Foglight for SQL Server, including replication-related alarms, see Foglight for SQL Server Alarms in the Foglight for SQL Server Reference Guide.
Alarms Displayed in the Sessions Pane
Several alarms can be investigated using the home page’s Sessions pane and network packet flows, as follows:
•
Response Time Alarm
•
Packet Errors Alarm
Response Time Alarm
The Response Time alarm becomes active when the execution time of the Response Time SQL exceeds a threshold.
Response time is the full time (in milliseconds) it has taken a query (select 1, by default) to get from the application to SQL Server and back. Every time a real-time sampled interval starts (by default: 20 seconds), a query is sent and its response time value is displayed. Any value higher than 20 ms may indicate a performance issue, which should then be investigated to detect its source, identify the possible bottleneck, and take correcting measures.
The Response Time SQL is a user-defined Transact-SQL batch that can be used for indicating application response time.
To change the query used for determining response time, edit the Response time section in the Agent properties.
* 
NOTE: Only members of the Foglight Administrator group can change the SQL query used for measuring SQL Server response time.
Packet Errors Alarm
The Packet Errors alarm becomes active when the rate at which SQL Server is encountering network packet errors exceeds a threshold.
When this alarm is fired, investigate what is causing the packet errors on the network.

Alarms Displayed in the Sessions Pane

Alarms are the warnings that Foglight for SQL Server raises when a metric falls outside its “normal” range of values, which is defined by setting thresholds and severities for the metric within the Metric editor. A new alarm is raised whenever the severity for a metric changes. When the severity returns to normal, the alarm is canceled.
* 
IMPORTANT: Only several alarm types are invoked for instances monitored using the vFoglight for SQL Server Add-on mode. For details, see Viewing Data Displayed on vmExplorer.
* 
NOTE: For a complete list of alarms invoked by Foglight for SQL Server, including replication-related alarms, see Foglight for SQL Server Alarms in the Foglight for SQL Server Reference Guide.
Several alarms can be investigated using the home page’s Sessions pane and network packet flows, as follows:
•
Response Time Alarm
•
Packet Errors Alarm
Response Time Alarm
The Response Time alarm becomes active when the execution time of the Response Time SQL exceeds a threshold.
Response time is the full time (in milliseconds) it has taken a query (select 1, by default) to get from the application to SQL Server and back. Every time a real-time sampled interval starts (by default: 20 seconds), a query is sent and its response time value is displayed. Any value higher than 20 ms may indicate a performance issue, which should then be investigated to detect its source, identify the possible bottleneck, and take correcting measures.
The Response Time SQL is a user-defined Transact-SQL batch that can be used for indicating application response time.
To change the query used for determining response time, edit the Response time section in the Agent properties.
* 
NOTE: Only members of the Foglight Administrator group can change the SQL query used for measuring SQL Server response time.
Packet Errors Alarm
The Packet Errors alarm becomes active when the rate at which SQL Server is encountering network packet errors exceeds a threshold.
When this alarm is fired, investigate what is causing the packet errors on the network.

Response Time Alarm

Alarms are the warnings that Foglight for SQL Server raises when a metric falls outside its “normal” range of values, which is defined by setting thresholds and severities for the metric within the Metric editor. A new alarm is raised whenever the severity for a metric changes. When the severity returns to normal, the alarm is canceled.
* 
IMPORTANT: Only several alarm types are invoked for instances monitored using the vFoglight for SQL Server Add-on mode. For details, see Viewing Data Displayed on vmExplorer.
* 
NOTE: For a complete list of alarms invoked by Foglight for SQL Server, including replication-related alarms, see Foglight for SQL Server Alarms in the Foglight for SQL Server Reference Guide.
Alarms Displayed in the Sessions Pane
Several alarms can be investigated using the home page’s Sessions pane and network packet flows, as follows:
•
Response Time Alarm
•
Packet Errors Alarm
The Response Time alarm becomes active when the execution time of the Response Time SQL exceeds a threshold.
Response time is the full time (in milliseconds) it has taken a query (select 1, by default) to get from the application to SQL Server and back. Every time a real-time sampled interval starts (by default: 20 seconds), a query is sent and its response time value is displayed. Any value higher than 20 ms may indicate a performance issue, which should then be investigated to detect its source, identify the possible bottleneck, and take correcting measures.
The Response Time SQL is a user-defined Transact-SQL batch that can be used for indicating application response time.
To change the query used for determining response time, edit the Response time section in the Agent properties.
* 
NOTE: Only members of the Foglight Administrator group can change the SQL query used for measuring SQL Server response time.
Packet Errors Alarm
The Packet Errors alarm becomes active when the rate at which SQL Server is encountering network packet errors exceeds a threshold.
When this alarm is fired, investigate what is causing the packet errors on the network.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating