Converse agora com nosso suporte
Chat com o suporte

Foglight for SQL Server (Cartridge) 5.7.5.50 - 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 Performance Counters and Collections
Monitoring Business Intelligence Services Administering Foglight for SQL Server
Configuration Settings 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

Terminology

Terminology

Standard score - is used to compare the duration of a specific execution in compare to the normal execution.

Standard score is calculated as the current execution minus the average while the result is divided by the standard deviation. This score gives the result while considering the tendency of the execution duration fluctuation.

Step - is used to describe tasks, data flows and other package components. Steps are used to discover which part of the package has failed or exceeded their normal duration.

Monitoring Reporting Services

Configuring Reporting Services Monitoring

 

* 
IMPORTANT: A new agent can only be created when the SQL Server instance is already monitored.
To configure RS 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 a Reporting Service agent is <Instance name>_<Report_DB>.
4
To enable monitoring the Reporting Service, provide:
a
the OS relevant credentials under Reporting Service Account, which is the name of the underlined host on which the service runs.
b
The username and password allowed to view the service activity and performance counters. Stored credentials can be used instead of entering the username and password manually.
5
Click Monitor.

Configuring Reporting Services Monitoring

Monitoring Reporting Services

 

* 
IMPORTANT: A new agent can only be created when the SQL Server instance is already monitored.
To configure RS 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 a Reporting Service agent is <Instance name>_<Report_DB>.
4
To enable monitoring the Reporting Service, provide:
a
the OS relevant credentials under Reporting Service Account, which is the name of the underlined host on which the service runs.
b
The username and password allowed to view the service activity and performance counters. Stored credentials can be used instead of entering the username and password manually.
5
Click Monitor.

Monitoring Reports using the Reporting Services Panel

The metadata of the reporting services is stored in the SQL Server instance. Foglight for SQL Server offers the capability of analyzing the metadata and produces detailed reports of the user's activity.

This panel contains the following components:

•
Reporting Services Databases — allows selecting which metadata database is to be used.
•
Reporting Services Configuration — allows reviewing the configuration of the metadata databases selected in the Reporting Services Databases section. The settings displayed in this section are read-only and cannot be modified.
•
Distribution of Reported Runs — a pie chart displaying the distribution of the report runs between successful and failed runs.
•
Top Users — displays the users who generated the highest number of reports.
•
The Reporting Services Execution Summary table — displays a row for each report, and includes the following columns:
•
Path — the path where the report resides.
•
Report Name — the name of the report.
•
Status — the report’s status, that is: the result of the report’s running; either Failed or Success.
•
Total Time Retrieving Data — the total time required for collecting the report’s data.
•
Total Time Processing — the total time required for processing the data retrieved for the report.
•
Total Time Rendering — the total time required for rendering the data for UI display.
•
Total No. of Rows — the total number of rows displayed in the report.
•
No. of Executions — the total number of times the report was executed.
•
Explore — allows reviewing in-depth data about the report.
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação