Chat now with support
Chat with Support

Foglight for SQL Server 5.7.5.41 - User Guide

Introduction to this Guide Using Foglight for SQL Server
Viewing the Databases Dashboard Overview Dashboard Advisories Dashboard Monitoring Data Replication Monitoring SQL Performance Reviewing Memory Usage Reviewing the Instance Activity Reviewing Database Usage Reviewing the Services Using the HADR Drilldown Using the Logs Drilldown Reviewing Configuration Settings Viewing User-defined Counters and Collections
Monitoring Business Intelligence Services Administering Foglight for SQL Server
Configuration Settings Viewing User-defined Counters and Collections Managing Foglight for SQL Server Agent Settings Reviewing Foglight for SQL Server Alarms Generating Reports Monitoring SQL Server instances on VMware servers
Glossary
A
Access methods Adhoc SQL Plans Alarm Alert Allow updates Anonymous subscription Authentication AutoClose AutoGrow Automatic Discovery AutoShrink B Batch BCP (Bulk Copy Program) Blocking Books Online Bound trees Buffer Buffer cache Buffer pull Bulk copy Bulkinsert Bulk load C Cache CAL Calibration Cardinality Cartridge Chart Checkpoint process Client network utility CLR Compile Connect Connection Connectivity software CPU Usage Cursors D Data access components Data file Data storage engine Database Database object DataFlow DBCC DBID DBO Deadlock Disk queue length Disk transfer time Disk utilization DiskPerf Distributing instance Distributor DMO Drilldown DTC DTS E Error log Event alert Execution contexts Extended stored procedures Extent External procedures F File Filegroup File cache Foglight Agent Manager Foglight Management Server Foreign key Forwarded records Free buffers Free list Free pages Free potential Free space Freespace scans Full text search G GAM Ghosted records Growth increment GUID H Hash buckets Hashing Heap Hit rate Hit ratio Host name Host process I I/O Index Indid Integrated security Intent Locks J Job K Kernel memory Kernel mode Kill L Latch Lazy writer Licensing Lightweight pooling Lock Lock area Lock escalation Lock mode Log Log cache Log writer Logical I/O LRU LSN M Master MaxSize MDAC Metric Misc.normalized trees Model Monitor page file N Named pipes Net library NIC Null O OBID Object plans OLAP OLAP service OLTP Optimizer Optimizer cache osql P Page life expectancy Paging Panel Parse Parser Per seat licensing Per server licensing Performance alert Physical I/O Physical read Physical write PID Pinned Plan Plan cache Potential growth Prepared SQL plans Primary key Privileged mode Procedure cache Procedure plans Process Profiler Publication database Publisher Publisher databases Publishing server Pull subscription Pulse Push subscription Q Query plan R RAID Random I/O Read ahead Recompile Referential integrity Relational data engine Replication procedure plans Role Rollback S sa Schema locks Sequential I/O Session Severity SGAM Shared locks Show advanced options SMP Sort, Hash, Index Area SPID Spike Spinner SQL Agent Mail SQL Mail SQL Plans SQL Server Agent SQL Server authentication SQL Server books online Standard deviation Stolen pages Stored procedure Support service SYSADMIN role T TDS TempDB Temporary tables and table variables Threshold Torn page detection Transaction Trigger Trigger plans Truncate Trusted U UMS Unused space User connection area User mode V Virtual log file VLF W Waitfor Windows authentication mode Working set
Reference
SQL PI Repository Cold Backup Procedure SQL Performance Investigator Metrics
Active Time All SQL Agents CPU Usage All SQL Agents Resident Memory Usage Availability Average Physical I/O Operations Average SQL Response Time Backup Recovery Wait Blocked Lock Requests Checkpoint Pages CLR Wait CPU Usage CPU Wait Cursor Synchronization Wait Database Replication Wait Deferred Task Worker Wait Degree of Parallelism Disk Utilization DTC CPU Usage DTC Resident Memory Usage Distributed Transaction Wait Executions Ended Executions Started External Procedures Wait Full Scans Full Text Search CPU Usage Full Text Search Resident Memory Usage Full Text Search Wait Free Buffer Wait Hosted Components Wait IO Bulk Load Wait IO Completion Wait IO Data Page Wait IO Wait Latch Buffer Wait Latch Wait Latch Savepoint Wait Lazy Writes Lock Wait Lock Bulk Update Wait Lock Exclusive Wait Lock Intent Wait Lock Requests Lock Schema Wait Lock Shared Wait Lock Update Wait Lock Wait Log Buffer Wait Log Flushes Log Other Wait Log Synchronization Wait Log Wait Log Write Wait Memory Wait Network IO Wait Network IPC Wait Network Mirror Wait Network Wait Non SQL Server CPU Usage Non SQL Resident Memory Usage OLAP CPU Usage OLAP Resident Memory Usage OLEDB Provider Full Text Wait Other CPU Usage Other Miscellaneous Wait Other Wait Overall CPU Page Life Expectancy Page Splits Parallel Coordination Wait Physical I/O Physical Memory Used Physical Page Reads Physical Page Writes Probe Scans Plan Cache Hit Rate Range Scans Rec Ended Duration Remote Provider Wait Run Queue Length Samples Service Broker Wait Session Logons Session Logoffs SQL Agent CPU Usage SQL Agent Resident Memory Usage SQL Executions SQL Mail CPU Usage SQL Mail Resident Memory Usage SQL Recompilations SQL Response Time SQL Server Background CPU Usage SQL Server Cache Memory SQL Server Connections Memory SQL Server Connections Summary SQL Server Foreground CPU Usage SQL Server Resident Memory Usage SQL Server Swap Memory Usage Synchronous Task Wait Table Lock Escalation Target Instance Memory Total CPU Usage Total Instance Memory Virtual Memory Used
Rules Collections and Metrics

Permissions

•
The same user monitoring the SQL Server database engine must be used to monitor the Integration and Reporting Services.
•
The login ID used to monitor the Integration Service must be a user on the SSISDB database. This user ID is created while applying the "Grant permissions" script.
•
The ID used to monitor the Integration Services on the database needs to have:
•
the ssis_admin role in order to gather all needed information for its collections.
•
the db_datareader role on the SSISDB database.
•
Monitoring Analysis Services requires system administrator permissions on the Analysis Services instance.
•
No additional permissions are required to monitor the Reporting Services.

Monitoring Integration Services

Configuring Integration Services Monitoring

Since Foglight for SQL server already monitors the SQL server instance you need only supply the server credentials.

* 
IMPORTANT: A new agent could only be created when the SQL Server instance is already monitored.
To configure IS monitoring:
1
Click Monitor.
2
Select the instance from the list of monitored instances.
3
Select whether you want to generate the name automatically.
The default name of an Integration Service agent is <Instance name>_<Repository name>. The repository name for SSIS is always SSISDB.
4
To enable monitoring the Integration Service, provide the OS relevant credentials under "Integration Service Account":
a
The name of the underlined host on which the service run.
In the case of a clustered SQL server, identify only the primary server. When a failover occurs the event might fail running packages and is treated as an availability alarm.
b
The username and password allowed to view the service activity and performance counters.
Stored credentials could be used instead of supplying username and password manually.
5
Click Monitor.

Configuring Integration Services Monitoring

Monitoring Integration Services

Since Foglight for SQL server already monitors the SQL server instance you need only supply the server credentials.

* 
IMPORTANT: A new agent could only be created when the SQL Server instance is already monitored.
To configure IS monitoring:
1
Click Monitor.
2
Select the instance from the list of monitored instances.
3
Select whether you want to generate the name automatically.
The default name of an Integration Service agent is <Instance name>_<Repository name>. The repository name for SSIS is always SSISDB.
4
To enable monitoring the Integration Service, provide the OS relevant credentials under "Integration Service Account":
a
The name of the underlined host on which the service run.
In the case of a clustered SQL server, identify only the primary server. When a failover occurs the event might fail running packages and is treated as an availability alarm.
b
The username and password allowed to view the service activity and performance counters.
Stored credentials could be used instead of supplying username and password manually.
5
Click Monitor.

Overview dashboard

The Foglight for Integration Server Overview dashboard provides a quick view of the current state of the instance.

The top of the dashboard includes general information on the monitored instance:

•
Schema build - the exact build of the schema on the SSIS catalog.
•
Schema Version - the exact version of the schema version.
•
Retention window - number of days logged operations data is kept in the catalog database before it is deleted.
•
Logging level - the default logging level used for the running packages.
•
Encryption algorithm level - the security encryption algorithm used for storing the packages XML "scripts".
* 
NOTE: Foglight is unable to show the content of packages stored on the catalog since they are encrypted.

The dashboard tiles include a title that states the name of the monitored issue and an aggregation of the alarms relevant to that issue. Tiles are organized by priority:

•
Availability - information and alarms about the availability of the instance. Also includes the monitoring state for that instance.
•
HA/DR - High Availability (HA) & Disaster Recovery (DR) state of the instance. At this stage no HA issues are monitored. DR refers to the backup of the database used for the SSIS catalog.
•
Storage - the space utilization level for the disk with the least free space on the server and the utilization level of the catalog database itself.
•
Infrastructure - general information collected from the server and the service.
•
CPU - the Integration Service CPU level of utilization compared to the general utilization of the Integration Service.
•
Memory - the amount of memory used by the Integration Service compared to other processes and the total memory on the server.
•
Disk I/O - Displays the latency of the slowest disk on the monitored server. A High I/O value might lead to low IO rate for the running ETL processes (packages).
•
Network Utilization - the amount of network pressure experienced by the server.
•
Operational - summary of the packages execution state over time. The panel displays:
•
The number of failed executions.
•
The number of successful executions.
•
Executions that ended in a state other than success or failure.
Additional information is available on the Packages dashboard.
•
Performance - The tile summarizes general information regarding the measurable performance of the packages. For example, total read and written bytes during a time range.
The tile also displays the amount of total packages run during the time period examined and the amount of packages currently running. This number includes packages in running, pending or stopping status.
 

The alarms panel on the right side of the dashboard displays the list of alarms relevant to the monitored Catalog - Service pair. The errors can be organized by Time or Severity.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating