Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Foglight for SQL Azure 5.5.8.6 - User Guide

Introducing Foglight for SQL Azure Adding and Configuring Agents Reviewing SQL Azure Activity Reviewing Database Usage Reviewing the Database Properties Monitoring Estimated Costs Viewing User Metrics Using the Global Administration Options Reviewing Foglight for SQL Azure Alarms Glossary

Adding and Configuring Agents

Enabling Foglight Management Server to monitor SQL Azure instances requires creating the Foglight agents that monitor the databases running on these instances and ensuring that these agents communicate properly with Foglight Management Server.
Foglight for SQL Azure provides a graphic, intuitive method for creating and configuring agents, rather than the default method offered by Foglight for creating agents and editing their properties via the Agent Administration view (see chapter About the Foglight for SQL Azure Agent in the Foglight for SQL Azure Reference Guide). Foglight for SQL Azure’s installation package also installs the Automatic Discovery cartridge, which allows running a database discovery wizard. This wizard provides a common entry point for adding all of the databases running under a specified SQL Azure instance, and then configuring these databases to be monitored.
 
* 
NOTE: The automatic discovery wizard allows specifying a single SQL Azure instance at a time. To add databases that run under other SQL Azure instances, run the discovery wizard again for each instance.
This contains instructions for using the database discovery wizard, as well as the steps that should be taken for monitoring the newly added databases.

Studying the Foglight for SQL Azure Architecture

The communication architecture of Foglight for SQL Azure is presented in the following illustration.
Figure 1. Foglight for SQL Azure Communication Architecture
 

Running the Database Discovery Wizard

This details the steps required for running the Foglight for SQL Azure database discovery wizard, which offers several methods for discovering and adding database instances.

Carrying Out the Automatic Discovery Process

To run the database discovery wizard:
1
On the navigation panel, click Homes > Databases.
•
If no instances are monitored, the Auto Discovery wizard appears; go to Step 3 on page 21.
•
If one or more instances are already monitored, the Databases view appears.
Figure 2. The Databases view appears containing a list of currently monitored instances.
2
Click the Discover more databases link at the upper right corner of the Databases View.
 
* 
IMPORTANT: If a user-defined database group is currently selected, the databases table's title displays the name of this group instead of All; however, all newly discovered or created databases are added to the general (All) group of databases.
Figure 3. The Select Database screen appears.
3
Click SQL Azure.
The Database Discovery wizard appears.
The first screen of this wizard, Agent Manager, provides a drop-down list of the available Foglight Agent Managers (FglAMs).
4
Select the agent manager that is to be used for monitoring the discovered instance.
5
Click Next.
Figure 4. The Instance Connectivity Settings screen appears letting you specify an instance and set credentials.
6
Use the screen’s upper section, Specify a SQL Azure Instance, to either select one of the SQL Azure instances from the list, which displays the monitored instances, or enter the name of a new instance.
7
Use the lower section, Set Instance Credentials, to enter the credentials (instance user and password) required for logging in to the instance and discovering its databases.
 
* 
NOTE: These credentials can also be used for creating the agents and granting privileges for each of the instance’s databases
 
* 
IMPORTANT: It is advisable to enter an instance user name in the format username@servername. For example: if the server name is MyServer.database.windows.net, enter the name MyUser@MyServer.
8
Click Next.
Figure 5. The Database Connectivity Settings screen appears displaying the instance specified along with all databases running on this instance.
 
* 
IMPORTANT: Monitoring the databases requires selecting them first. Therefore, do not click Finish at this stage.
 
* 
NOTE: When running the automatic discovery wizard on an instance that has not yet been monitored, all databases appear with the status Using Default Credentials. If the automatic discovery wizard is only used for discovering newly added databases running on an instance that is already monitored, the currently monitored databases appear with the status Monitored, and all other databases appear with the status Using Default Credentials.
At this stage, all databases whose status is Using Default Credentials use the credentials entered in the previous screen. These credentials can be reviewed using the screen’s upper section, Set Default Login Credentials, which displays the database user name and allows viewing the password by clicking the Set Credentials button.
Proceeding with discovery progress depends on the changes requested, if any, in the Databases table:
•
To accept the current settings and proceeding to validate the databases’ connectivity and privileges, go to Step 13
•
To set new default credentials, go to Step 9
•
To edit the credentials of the master database, namely: the instance’s credentials, go to Step 10
•
To edit the credentials of a specific database agent, go to Step 11
•
To manually add one or more databases to the list, go to Step 12
9
To set new default credentials:
a
Click Set Credentials.
The Set Default Configuration dialog box that appears now contains the credentials provided in the previous screen for logging in to the instance (see Step 7).
b
Select whether to leave these credentials or replace them.
 
* 
IMPORTANT: If replacing the database user name, it is advisable to enter a name that uses the format username@servername. For example: if the server name is MyServer.database.windows.net, enter the name MyUser@MyServer.
c
To override the current master database credentials with the credentials specified in this dialog box (optional), select the check box Apply credentials to master database.
d
Click Apply.
The newly set default credentials are now applied to all databases whose status is Using Default Credentials (as well as to the instance itself, if the check box Apply credentials to master database was selected) when running the discovery wizard for the first time.
10
To edit the credentials of the master database:
a
Click the instance’s name or status.
Figure 6. The Edit Connection Settings dialog box appears.
b
Use the Edit Database Credentials section to enter a different user name, password, or both.
 
* 
IMPORTANT: If replacing the database user name, it is advisable to enter a name that uses the format username@servername. For example: if the server name is MyServer.database.windows.net, enter the name MyUser@MyServer.
c
Click Apply.
The instance now appears on the table with the status Using Custom Credentials.
11
To edit the credentials of a specific database agent:
a
Click the requested database’s name or status.
Figure 7. The Edit Connection Settings dialog box appears.
b
Use the Edit Database Credentials section to enter a different user name, password, or both.
 
* 
IMPORTANT: If replacing the database user name, it is advisable to enter a name that uses the format username@servername. For example: if the server name is MyServer.database.windows.net, enter the name MyUser@MyServer.
c
Click Apply.
The selected database now appears on the table with the status Using Custom Credentials.
d
Repeat Step a to Step c for every agent whose credentials need to be modified.
12
To add one or more database agent:
a
Click Add database.
Figure 8. The Add a New Database dialog box appears.
b
Enter the database name in the Database field.
c
Select whether to use the default credentials defined for the instance’s databases, or enter user-defined credentials.
 
* 
IMPORTANT: If replacing the database user name, it is advisable to enter a name that uses the format username@servername. For example: if the server name is MyServer.database.windows.net, enter the name MyUser@MyServer.
d
Click Add.
e
Repeat Step a to Step d for each database that needs to be added.
 
* 
IMPORTANT: After adding databases to the table, they cannot be deleted. If a database was mistakenly added, leave its check box cleared.
13
Select the check boxes to the left of the databases to be monitored. Alternatively, to select all of the table’s database, click Select All. To cancel the selection, click Select None and select again.
 
* 
IMPORTANT: Upon selecting databases, the instance is automatically selected.
14
Choose whether to:
•
Validate the selected databases’ connectivity—go to Step 15
•
Proceed directly to monitor the databases—go to Step 16
 
* 
IMPORTANT: Dell Software highly recommends performing the connectivity validation check, thereby detecting in advance any connectivity or privileges-related issues. However, if certain agents are known to currently have connectivity issues, skipping the validation process can shorten the discovery process. If you decide to use this method, keep in mind that some agents will initially collect no data, as evident by their N/A status on the Global View > Databases table. The connection settings of these agents can be changed at any time by selecting the agents and entering the Global Administration > Connection Details screen. For details, see Defining the Connection Settings for the Monitored Databases on page 57.
15
Click Validate connectivity.
Figure 9. The Verifying Connectivity progress bar appears.
Upon successful completion of this process, the databases table is populated by a list of newly added databases, and the Status column displays their connectivity status: either Connection 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: Database Connection Failed or Wrong Database Credentials).
 
* 
NOTE: If one or more of the newly added instances are already monitored, they are displayed with the status Monitored
Figure 10. Newly Added Instances Displayed with Status
If the connectivity issue results from faulty login credentials, clicking the error message that appears in the Details column displays the Edit Connection Settings dialog box, which is similar to the Add a New Database dialog box, described in Step 12. Use this dialog box to modify the credentials, and carry out the connection verification process again. If the database still fails to establish connection, clear the check box near its name.
If some of the instances whose verification failed display a status of Insufficient Privileges, Click to Grant, such instances should be granted privileges.
To grant privileges to a single instance, click the instance. To grant privileges to several instances, select the requested instances and click Grant DB Privileges.
Figure 11. The Grant Privileges dialog box appears.
This dialog box allows specifying a SYSAdmin (System Administrator) user with sufficient privileges.
 
* 
IMPORTANT: Enter a SYSAdmin user and password, and then click Grant Privileges. Alternatively, click the View script link, to the right of the Grant privileges button, to grant privileges manually via a script.
16
In the Monitor Selected Instances section, click Monitor.
The Creating agents progress bar appears. This bar indicates the progress that the discovery agent is making in creating new Foglight for SQL Azure agents.
Upon successful completion of this process, the Status column of the instance table displays the icon Monitored for the newly monitored instances.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation