지금 지원 담당자와 채팅
지원 담당자와 채팅

Foglight for Azure SQL Database (Cartridge) 6.3.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

Installing and Configuring Agents

This guide provides configuration instructions, conceptual information and instructions on how to use the Foglight for Azure SQL Database cartridge. It describes the dashboards included with the cartridge and how they are used for collecting monitoring data from the entire relational database management system, as well as the cartridge’s interaction with and support of additional services and modules, such as replication and virtualization.

This guide is intended for Azure SQL Database administrators and for any users who want to know more about monitoring Azure SQL Databases through Foglight for Azure SQL Database, and the steps required for discovering and configuring the Azure SQL agent. It is also meant for those users who want to learn about the methods used for configuring and applying user-defined settings.

This section provides information about installing the cartridge and configuring the agents for monitoring Azure SQL Database systems:

Installation

For installation pre-requisites, permissions, and information necessary to determine your environment’s hardware requirements, see the Foglight for Databases Deployment Guide.

Foglight for Azure SQL Database monitors the Azure SQL Database activity by connecting to and querying the Azure SQL Database. The agents provided monitor the Azure SQL Database system. The dashboards included with the cartridge provide a visual representation of the status of the major components of the Azure SQL agents. They allow you to determine any potential bottleneck in database performance.

Starting to work with a Foglight for Azure SQL Database cartridge requires upgrading to the current version of both the cartridge and the Foglight Agent Manager that runs the cartridge.

2
Navigate to the Cartridge Inventory dashboard and install the cartridge file, DB_Azure-6_3_0.car.
3
Navigate to the Agent Status dashboard and deploy the Azure SQL agent package to the existing Foglight Agent Manager hosts.

About Monitoring Extensions

During the installation process you can choose to install and configure one or more of the monitoring extensions. The monitoring extensions provide a more in-depth analysis of the monitored database and the environment it is running on, creating a whole and unified status.

SQL Performance Investigator allows you to rapidly identify bottlenecks, anomalies, and application trends by focusing on top resource consumers and providing multi-dimensional SQL domain drilldowns. SQL PI allows you to:

Installing and Monitoring a Single Azure SQL Database

Enabling the Foglight Management Server to monitor Azure SQL Databases requires the creation of the Foglight agents that monitor these databases and ensuring that these agents communicate properly with the Foglight Management Server.

Foglight for Azure SQL Database provides a graphic, intuitive method for creating and configuring multiple agents, which can be used instead of Foglight’s default method for creating agents and editing their properties using the Agent Administration dashboard.

IMPORTANT: When running Foglight for Azure SQL in a Federation architecture, neither the creation nor the administration of agents can be accomplished from the central Foglight Management Server (the Federation Master). These two tasks should be carried out from the stand-alone Management Servers (the Federated Children).
1
2
Click Monitor > Azure SQL in the upper left corner of the Databases View.
The Monitor Azure SQL Database dialog box appears.
a
Click the Agent Manager Host <agent manager> link located at the top of the Azure Database Connection section.
a
Server Name — Specify the host name.
b
Database Name — Specify SQL database name.
c
Port (optional) — It is required only when the TCP/IP connection port of the Azure SQL Database is other than the default port (1433). If it is not specified, the default port (1433) will be used.
5
Select between SQL Server Authentication and Azure Active Directory (AD) Authentication. Specify the username and password to be used for monitoring the Azure SQL Database in the Login Credentials section.
8
Optional To enable SQL Performance Investigator, select SQL PI in the Monitoring Extension section.
The SQL PI Repository dialog is displayed. Select the Agent Manager on which the SQL PI
NOTE: To use gMSA authentication for connections to the PI Repository, select Local User in the Authentication drop-down. This requires that your FMS and Agent Manager are configured to run as a Windows Service logged on with the gMSA account. The gMSA account requires access to the SQL instance.
d
If the given SQL PI repository user does not have sufficient privileges, the Insufficient Privileges
dialog will be displayed. Enter an admin user and password, and then click Grant Privileges.
9
Click Monitor.
10
When the installation completes successfully, the Monitoring Initialized Successfully dialog box appears. Click Add another Database or Finish to exit.
셀프 서비스 도구
지식 기반
공지 및 알림
제품 지원
소프트웨어 다운로드
기술 설명서
사용자 포럼
비디오 자습서
RSS 피드
문의처
라이센싱 지원가져오기
기술 지원
모두 보기
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택