Chatta subito con l'assistenza
Chat con il supporto

Foglight for SQL Server 5.7.5.1 - Foglight for SQL Server 5.7.5.1 Getting Started Guide

Installing Foglight for SQL Server and Foglight Management Server Together

A single executable file allows installing Foglight Management Server together with Foglight for SQL Server.
To run the combined installation file:
1
Copy the installation file suitable for the operating system and the bit level (32-bit or 64-bit) to a temporary directory on the requested host.
* 
IMPORTANT: The combined installation file is named using the following convention: Foglight-<version_number>_FoglightForSQL-Server--<version_number>_<operating system>-<bit level><.exe/.bin> For example: Foglight-5_7_5-FoglightForSQL-Server-5_7_5_1_windows-x86_64.exe
2
If planning to use an external database for the Foglight Management Server Installation, ensure that this database is running.
3
Follow the on-screen installation instructions.

Installing the Cartridge by Adding it to a Cartridge Inventory of an Existing Foglight Management Server

To install Foglight for SQL Server as a cartridge:
1
Copy the cartridge’s car file (DB_SQL_Server-VersionNumber.car; for example, DB_SQL_Server-5_7_5_1.car), which is included in the installation media, to your local computer.
2
Log in to the Foglight browser interface.
3
In the browser interface, on the navigation panel, click Dashboards > Administration > Cartridges > Cartridge Inventory.
4
On the Cartridge Inventory dashboard, click Browse to find the car file on your local computer.
5
Click Install Cartridge.

Configuring Foglight for SQL Server

After successful installation of Foglight for SQL Server, when entering the Foglight Management Server, no instances are displayed.
The Foglight for SQL Server agent (DB_SQL_Server) allows you to monitor the database performance on each server where the application is installed. The agent installer allows monitoring of existing and running instances for Foglight monitoring.
To discover database instances, when no instance is monitored:
1
On the navigation panel, under Homes, click Databases.
A blank screen appears, with a message indicating that the agent installer should be used for setting up the monitored environment.
2
Click Monitor > SQL Server in the upper left corner of the Databases View.
The Monitor SQL Server Instance dialog box apears.
3
Choose the agent manager on which the agent will be running The default is the agent manager with the least agents installed.
a
Click the Monitoring agent will run from host <agent manager> link located in the bottom left corner of the dialog box.
A dialog box appears with a list of all agent managers connected to the Foglight management server.
b
Select the appropriate host name and click Set.
* 
IMPORTANT: You have the option set this host as the default for all future installations.
4
On the Monitor SQL Server Instance pane, provide connection details by typing:
•
Server name — for the default instance, specify the host name. If you have more than one instance on the server you must name the instances using the format: domain\user name.
•
Port — Optional. This field can be left empty, unless the TCP/IP connection port is not the default port: 1443.
5
Specify the SQL Server credentials using one of the following authentication methods:
•
Windows Authentication — log in using a Windows user account. The user name should be typed in the following format: domain\user name
•
SQL Server Authentication — log in using a SQL Server account
•
Use the Windows account running your agent.
6
Select an Alarm Sensitivity Level to determine what level of alarms the system will store and display for this instance. The default is Normal. Alarm levels include:
•
Essential — Store and display only critical or fatal alarms.
•
Normal — Store and display most alarms — essential and best practices; only critical and fatal statistical alarms.
•
Tuning — Store and display all SQL Server alarms sent to Foglight.
•
Performance — Store and display only availability and SQL PI related alarms.
7
Optional — In the Monitoring Extensions pane, click the SQL PI monitoring extension. You are prompted to choose the Agent Manager on which the SQL PI repository will be installed.
8
Optional —In the Monitoring Extensions pane, click the Operating System link.
To configure the extension, choose the connection details of the host on which the SQL Server instance is running:
•
Log in to the host using the same account used for monitoring SQL Server — This option is set by default when the SQL Server connection details are of types: Windows Authentication or Using the Windows account running your agent manager.
•
Log in to the host using different login credentials - logging in through a Windows user account. The user name should be entered in the domain\username format (for example, COLUMBIA\JSmith).
9
Optional — In the Monitoring Extensions pane, click Collect VM statistics.
To configure the extension, choose the connection details of the vCenter or ESX on which the SQL Server instance is running:
•
The name of IP address of the vCenter server that hosts the SQL Server instance virtual machine, or the name of its parent ESX server
•
The port number used by the vCenter server system or by ESX server for listening to the connections from the vSphere Client (default: 43).
•
The name and password of the user that has the privileges required for connecting to the vCenter server or ESX server and retrieving information.
10
Click Monitor.
* 
IMPORTANT: 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, (for example: insufficient privileges, incorrect credentials or an Agent Manager that reached its full monitoring capacity.
11
When the installation completes successfully, the Monitoring Initialized Successfully dialog box appears. Click Add another Database or Finish to exit.
* 
NOTE: The Use this option to discover your SQL-Server instances link is for discovering and enabling several instances in one monitoring process. By searching and discovering the Instances on the network through an IP range, Host's or specific IP's or by importing from SQL Server predefined Regserv file.

SQL Performance Investigator Extension

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:
•
Monitor real-time SQL Server database performance at a glance
•
Gather and diagnose historical views
•
Identify and ananticipate performance issues
•
Analyze and optimize execution plan changes
•
Compare day-to-day values to identify anomalies and application changes
* 
NOTE: SQL Performance Investigator requires a license. If you are using a trial version and would like to request pricing, contact https://quest.com/register/57891
SQL PI requires a repository database that is installed automatically on the Agent Manager.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione