サポートと今すぐチャット
サポートとのチャット

Foglight for SQL Server (Cartridge) 5.9.3.10 - 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

Opening the Databases Administration Dashboard

You can edit agent settings for one or more SQL Server instances on the Databases > Administration dashboard.

* 
NOTE: If you attempt to select instances of more than one type of database, such as an SQL Server database and an Oracle database, an error message is displayed.
To open the Databases Administration dashboard:
1
In the navigation panel, under Homes, click Databases > SQL Server.
2
Select the check boxes beside one or more SQL Server instances.
3
Click Settings and then click Administration.
The Administration dashboard opens, containing settings for all the selected agents. Settings are broken down into categories, which are organized under a SQL Server tree.

Reviewing the Administration Settings

The Databases Administration dashboard allows settings options for collecting, storing, and displaying data, which apply to all the currently selected agents. Click a category of settings on the left (for example: Connection Details) to open a view containing related settings on the right.

The metrics defined under the Databases Administration dashboard apply to all of the agents that were selected before opening the Databases Administration dashboard. As a result, the same unit of measure and aggregation value for display are enforced for all currently selected agents.

The SQL Performance Investigator category allows you enable or disable SQL PI for the agents selected. In addition, you can also start or stop change tracking for the agents.

To view the full list of selected agents, click the Selected Agents button at the upper right corner of the screen. To change the list of agents to which the metrics will apply, exit the Databases Administration dashboard, select the requested agents and re-open the view.

If the settings vary between the selected agents (for example: one agent uses the measurement unit kilobyte, while another uses megabyte), the fields that contain non-identical values are displayed as empty and marked with an Inconsistent Values () icon.

Changes made to settings should be saved before selecting another category of settings.

To save changes made in an Administration dashboard view:
1
In the Database Administration dashboard, select a category from the menu.
2
Make changes to settings as necessary.
3
Click Save changes at the bottom of the view.
If you attempt to exit the view without saving changes, a Warning dialog box prompts you to confirm your action.

Defining Connection Details

Use the Connection Details category to define global connection settings, which apply to all instances and hosts selected in the view. You can configure SQL Performance Investigator connectivity, enable user-defined collections, and set VMware connection details.

Defining the Connection Settings for the Monitored Instances

The Connection Details view contains a table that displays all the agents that were selected before entering the Databases Administration dashboard.

To define the connection settings for the requested agents:
1
Select the check boxes to the left of the agents for which uniform credentials are to be set.
2
Click Settings, and then click Administration.
The Administration dashboard opens, containing settings for all the selected agents.
3
Click Connection Details, and then click Set credentials.
The Set dialog box used for editing the credentials of the selected instance appears.
* 
IMPORTANT: If multiple instances were selected before clicking Set credentials, this dialog box is empty (does not display the instances’ names, ports, and connection details). The default options in such a scenario are Windows authentication (for SQL Server connection details) and the use of existing host connection details (for OS monitoring).
4
On the Edit Credentials pane, provide port connection details. This field can be left empty, unless the TCP/IP connection port is not the default port: 1443.
5
Specify the SQL Server login credentials using either of the following authentication methods:
•
Active Directory (AD) Authentication — log in using the Active Directory account running on your agent manager or typing a new AD account. The user name should be typed in the following format: domain\user name.
•
SQL Server Authentication — log in using a SQL Server account
6
Optional — Select whether an SSL connection should be used. The default is set to Off.
•
SSL Connection Off — SSL is not required
•
Optional — SSL is required; if the server doesn't support SSL, a plain connection is used instead (default method)
•
Mandatory — SSL is required
7
In the Monitoring Extensions section you can select and configure which monitoring extension to add to the monitored instance:
•
Operating System — Correlate the SQL Server OS resources with the entire host.
* 
NOTE: Note: Monitoring OS can made also by using stored credentials - Select this link to open the Stored Credentials dialog box, which allows reviewing the login credentials and authentication methods used for logging in to Foglight. Foglight stores encrypted credentials in lockboxes, which may be password-protected for added security. The Credentials dialog box, DB-Agent Lockbox. If credentials have already been entered in another lockbox, use the Lockbox list to select from that lockbox.
•
VMWare — Collect VM statistics.
8
Click Set.
9
On the Connection Details pane, click Test Connection.
* 
NOTE: If the monitoring verification fails click the message that is displayed on the Status column and resolve the issue according to the instructions that appear in the dialog box. For example, insufficient privileges, incorrect credentials or an Agent Manager that reached its full monitoring capacity.
Upon successful completion of the process, the status shows as Verified.
10
The option of enabling and editing credentials for user-defined collections is available also when multiple instances are selected. This option is carried out as follows:
a
Click Set UDC Credentials.
The dialog box Edit Credentials for User-defined Collections appears.
b
Select the check box Enable user-defined collections.
c
Select whether to perform the collection:
•
Using the current agent credentials
•
Manually specifying login credentials.
•
Using Windows authentication and the Windows account that is running Foglight.
d
If the option of manually specifying login credentials was chosen, select the requested authentication method from one of these options:
•
Windows authentication — type a user name and a password in the domain\username format (for example, COLUMBIA\JSmith).
•
SQL Server authentication
* 
IMPORTANT: If the Foglight Agent Manager that runs the instance resides on a UNIX host, the option of using Windows authentication and the Windows account that is running Foglight is unavailable.
e
Click Set to return to the dialog box used for editing the instance’s credentials.
* 
IMPORTANT: To add user-defined collections, go to the User-defined Collections view in the Databases Administration dashboard. For details, see Configuring User-defined Collections .
11
If you have SQL Server instances that run on virtual hosts, such instances require setting a dedicated connection profile, in order to connect to the requested VMware server.
Establishing such a connection is necessary in order to retrieve the Virtualization overhead data, that is, the percentage of CPU that is unavailable to this virtual machine because it is being utilized either by other virtual machines or by VMware itself. The Virtualization Overhead indicator is displayed in both the real-time and history summary pages.
To edit the VMware Connection Profile:
a
Select the requested agents. To select all agents, select the check box on the table’s title column.
b
Click Edit.
The Edit VMWare Credentials dialog box appears.
c
Select the check box Enable collecting VMWare CPU allocation data.
d
Enter the details required for monitoring the CPU distribution data, that is, host, port, VMware user, and VMware password.
e
Click OK.
If multiple agents were selected, the settings will apply to all agents.
12
Ensure that all requested data has been entered. If so, click Validate.
A progress bar appears.
At the end of this process, any connectivity issues are indicated by the Status column of the agents table. This column displays either the status Verified for the instances that connected successfully to the database, or a status that indicates failure of the connectivity verification process, and the reason for the failure (for example, Login failed for user “X”).
If the connectivity issue results from faulty login credentials, modify the credentials and carry out again the connection verification process. If the database to which the instance tries to connect is not running, clear the box near the database’s name.
If some of the instances whose verification failed display a status of either Insufficient privileges, Click to Grant or Wrong sysdba Credentials, such instances should be granted privileges, by clicking the status and using one of the following methods:
•
Manually, using a script (by clicking View script, copying the text and using it to grant privileges
•
By clicking the button Grant privileges.
The Grant Privileges dialog box appears.
If Insufficient Privileges are indicated, this dialog box allows specifying a SYSAdmin (System Administrator) user with sufficient privileges.
Enter a SYSAdmin user and password, and then click Grant Privileges.
13
Click Save Changes.
The Applying Modified Settings progress bar appears.
Upon successful completion of this process, the Status column of the instance table displays the status Changes applied. For instances that failed verification, the status column indicates that changes cannot be saved if the validation did not complete successfully.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択