Chat now with support
Chat mit 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

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

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.

Packages Dashboard

The Packages dashboard displays the list of packages and their activity metrics over time. The data is collected directly from the catalog logs.
The dashboard provides information that allows you to:
•
Detect failures during a specific time range.
•
Detect executions that run for longer than normal during the time range selected.
•
View the inactive packages during the time range selected.
•
View the list of packages stored on msdb *.
* 
NOTE: Packages on msdb are not analyzed yet and no log is read for them. Packages on the file system or package store are not monitored in this Foglight version. To analyze the performance of msdb packages, use the Jobs dashboard or the PI for the relevant job step if the step executes SQL statements.
The dashboard is composed of four components:
•
The left pane, used to display information about package, executions and steps run during the time frame selected. This pane shows the last duration (for packages) or the actual duration (for executions or steps) in the given time range. It is also used to discover if there are excessive durations or failures during the time range.
•
The trend graph in the right pane, used to discover executions trends over time, compare execution time to the normal behavior of the package executions and to view final status at a glance.
•
General description of the package, execution, or step also appear in the right pane.
•
Messages relevant to the package, execution, or step appear on a designated tab on the right pane.
This tab can also be used to search the message log for information.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen