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

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

Viewing User-Defined Collections

The User-defined Collections panel allows viewing the customized collections, which were created via the User-defined Collections screen in the Global Administration view, either during the last sample (Last Snapshot) or plotted over the specified time range (Selected Period).
This panel comprises the following sections:
•
The Collections column, on the left of the panel—displays all of the names of the existing user-defined collections.
•
SQL text grid—displays the name and full SQL text of the user-defined collection selected in the Collections column.
•
The collection details table—displays all of the fields contained in the query.
Each of the table’s columns shows the field’s display name, while each row represents the records taken at each sample.
 
* 
NOTE: The User-defined Collections panel is used only for displaying the user-defined collections; any creation or management operation of these collections is carried out via the User-defined Collections screen in the Global Administration view.
 

Using the Global Administration Options

The Global Administration view allows setting options for collecting, storing, and displaying data. To open the Global Administration view, select one or more agents in the Databases table and click the button at the top of the screen.
Using the Global Administration view, it is possible to define customized metrics and thresholds, as well as cost configuration, user account, data collection and storage options.
 
* 
NOTE: Global administration settings can be applied to multiple agents, but cannot be applied simultaneously to more than one database type. For example: selecting agents of both the SQL Server and Oracle type and clicking Administer Agents results in an error message.
 
* 
IMPORTANT: Administration functionality is available only when administering agents that are active and collecting data. Ensure only active agents are selected before trying to access Global Administration.

Reviewing the Global Administration Settings

The Global Administration view allows settings options for collecting, storing, and displaying data, which apply to all of the currently selected agents. Use the menu command on the left pane (Connection Details, Collection Frequencies and so on) to select the options to be applied.
The metrics defined under Global Administration apply to all of the agents that were selected before opening the Global Administration view. As a result, the same unit of measure and aggregation value for display are enforced for all currently selected 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 Global Administration view, 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 in each of the Global Administration screens should be saved before switching to another screen.
To implement or cancel the changes made in a specific Global Administration screen:
1
Click Save changes at the bottom of the screen. Alternatively, to exit the screen without implementing the changes, select another screen without clicking first Save changes.
Figure 1. The Warning dialog box appears.
2
Click Yes to exit without saving the changes, or No to proceed with editing and applying the modifications.

Defining the Connection Settings for the Monitored Databases

The Connection Details screen contains a table, which displays all of the agents that were selected before entering Global Administration.
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. Alternatively, to select all of the table’s databases, click Select All. To cancel the selection, click Select None and select again.
2
Click Set credentials to the selected agents.
The Set Login Credentials dialog box appears.
 
* 
IMPORTANT: The dialog box shown below appears if at least one database agent is selected. As user-defined collection can be created only at the database level, the section that allows editing credentials for such collections is not displayed if only instance agents are selected.
Use this dialog box to enter the SQL Azure user name and password to be used as default login 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.
If planning to edit user-defined collections for the selected agents, proceed to Step 3. Otherwise, go to Step 6.
3
Click the arrow near the title Edit Credentials for User-defined Collections.
Figure 2. The Enable user-defined collection check box is displayed.
4
Select the check box Enable user-defined collections
5
Use this dialog box to specify which credentials are to be used for enabling user-defined collections for this agent:
•
Current agent credentials—the credentials that were defined during the creation of the agent and are currently used for monitoring the SQL Azure instance or database.
•
Dedicated credentials—user-specified credentials, to be used exclusively for user-defined collections. If using this credentials, enter the user name and password in the relevant fields.
 
* 
IMPORTANT: For security purposes, it is advisable to enter dedicated credentials with the minimum privileges required for running the user-defined collection (SQL query).
6
Click Set.
7
Ensure that all of the currently selected instances have credentials and are not already monitored, to avoid connection verification error. The status that should appear in the Status column is Using Modified Credentials.
8
Click Validate connectivity.
Figure 3. The Verifying connectivity progress bar appears.
At the end of this process, any connectivity issues are reported via the Status column of the agents table. This column displays either the status 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 Credentials Entered).
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, using one of the following methods:
•
Manually via a script (by clicking the link View script, copying the text and using it to grant privileges.
•
By clicking the button Grant privileges.
Figure 4. The Grant Privileges dialog box appears.
 
* 
IMPORTANT: The Grant Privileges dialog box can also be invoked by clicking the status Insufficient Privileges, click to grant. This method is suitable only when granting privileges to a single agent; for multiple agents, it is advisable to select the requested agents and click the Grant Privileges button.
This dialog box allows specifying a SYSAdmin (System Administrator) user with sufficient privileges required for providing a login with appropriate credentials.
Enter a SYSAdmin user and password, and then click Grant Privileges.
9
Click Save Changes.
The Applying Modified Settings progress bar appears.
Upon successful completion of this process, the Status column of the instance table is left blank.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択