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

Discovering instances by host name

Searching by host is the most efficient search method for discovering instances over a specified, small number of hosts.
To search by host:
1
Click Add instances.
2
Select the Discover SQL Server Instances by Hosts dialog box appears.
3
Type the host names in the field below the first check box. To specify multiple host names, separate the values by comma.
 
* 
IMPORTANT: Ensure typing host names and not IP addresses. IP addresses are supported only when searching by IP range, as detailed in section .
Alternatively, if Foglight already monitors one or more hosts in the selected environment, select the requested host from the table of hosts currently known to Foglight.
 
* 
IMPORTANT: The table lists all the hosts known to Foglight, regardless of the cartridge type, and including virtual hosts if the VMware cartridge is installed and configured.
4
Click Discover.
At the end of this process a table appears, displaying the newly discovered instances within the selected hosts.
5
Select the instances to be monitored.
6
Click Finish.
The newly added instance now appears on the table, with the status Set credentials.
7
Proceed with the wizard, starting from Step 5.

Discovering instances by IP range

Searching by IP range is the recommended search method for discovering database instances over many hosts, by that means saving the need to specify the host names and ports.
To search by IP range:
1
Click Add instances.
2
Click Discover by IP.
The dialog box Discover SQL Server Instance by IP Range appears.
The IP range displayed by default is determined by the IP address and the subnet mask on the selected Foglight server.
3
In the From box, type the IP Range.
 
* 
IMPORTANT: Ensure that the numbers entered are within the range of 0 to 255.
4
In the To box, type the requested IP Range.
 
* 
IMPORTANT: Ensure that the numbers entered are greater than those entered in the From box, and that the address range does not exceed 1000 addresses.
5
Click Discover.
At the end of this process a table appears, displaying the newly discovered instances within the selected hosts.
6
Select the instances to be monitored.
7
Click Finish.
The newly added instance now appears on the table, with the status Set credentials.
8
Proceed with the wizard, starting from Step 5.

Importing Instances from a File

Foglight for SQL Server supports importing an unlimited number of existing SQL Server instances that need to be monitored, using a predefined Regserv file that includes the properties of these instances.
* 
IMPORTANT: The Regserv file can also be created by exporting the list of registered servers in SQL Server Management Studio. To do that follow the instructions at: https://msdn.microsoft.com/en-us/library/ms190246.aspx
To import the '<NAME>.regsrvr' file:
1
Select the Import from file option.
2
Import the <NAME>.regsrvr file
3
The instances listed in the file is presented in the SQL Instances list.
4
Select the instance you want to monitor and proceed with the validation step.

Configuring Multiple Instances for Monitoring using Silent Installation

To add multiple agents using the silent installation through a command line interface:
1
Navigate to Administration > Cartridges > Components for downloads.
2
Click the DB_SQL_Server_CLi_Installer name to download the installer.
The Download Message dialog box appears.
3
Review the details in this dialog box, and click Download.
The downloaded ZIP file contains the following files:
•
README.txt file
•
mssql_cli_installer.groovy — a groovy script file that runs the silent installation. This file should be copied to the <FMS_HOME>/bin directory.
•
silent_installer_input_template.csv — a template file that should serve as the basis for inserting contents into the input CSV file. This file can be copied to any folder of your choice, if the path indicated by the <csv_instances_file_name> parameter (see below) points to the selected path. For details about the contents of this file, see Contents of the Input CSV File.
•
MSSQLPermissionsCheck.sql — this file contains the SQL th.at the user should run on the monitored instance to check permissions needed for monitoring
•
MSSQLPermissionsGrant.sql — this file contains the SQL that the user should run on the monitored instance in order to grant the instance the required permissions for monitoring.
4
Extract the ZIP file to a directory of your choice.
5
Copy the mssql_cli_installer.groovy file to the <FMS_HOME>/bin directory.
6
Go to the command line and run the command: <FMS_HOME>/bin/fglcmd -srv <fms_host_name> -port <fms_url_port> -usr <fms_user_name> -pwd <fms_user_password> -cmd script:run -f mssql_cli_installer.groovy fglam_name <fglam_name> instances_file_name <csv_instances_file_name> lockbox_name <lockbox_name> lockbox_password <lockbox_password>
The descriptions of the flags and parameters in this command are as follows:
•
<FMS_HOME>: The Foglight Management Server installation directory.
•
<fms_host_name>: Name of the host where the Foglight Management Server is installed.
•
<fms_url_port>: The Foglight Management Server port.
•
<fms_user_name>: The user name used for connecting to the Foglight Management Server.
•
<fms_user_password>: The password of the specified user.
•
<clusters_file_name>: The full path and the name of the input CSV file.
•
<lockbox_name>: Optional — specifies the name of an existing lockbox to be used.
•
<lockbox_password>: Optional — the selected lockbox's password.
7
After the installation process completes, review the CSV files that are created in the same folder where the input file resides:
•
A file with the input file's name and _status suffix (for example: if the input file is named input, this file is named input_status).
This file indicates the monitoring situation of all SQL Server instances listed in the input CSV file. If monitoring failed for one or more of the instances, the file specifies the error message.
The _status file includes the name of the monitored Foglight for SQL Server agent, the result of the monitoring validation process — MONITORED, FAILED, or AGENT EXISTS — and the error message, in case the agent creation failed.
 
* 
IMPORTANT: If all instances listed in the input CSV file passed the monitoring validation successfully, no additional file is created.
•
A file with input file's name and _new suffix (for example: if the input file is named input, this file is named input_status).
This file, which is only created if one or more instances failed the monitoring validation, contains all details about these instances.
Using this CSV file, the user only needs to fix the errors and re-run the script, this time by specifying this file as the input file, that is: the original filename with suffix _new. In the example used here, the new file should be named input_new.csv.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen