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

Reviewing the Estimated Costs

The Estimated Cost section details the bandwidth usage and storage costs for the specified time range.
The costs are based on the cost model (pricing plan) specified in the Cost global administration screen, and are calculated as follows:
•
Bandwidth usage—the bandwidth usage cost, for both internal and external traffic, is calculated 120 minutes after the transaction took place, thereby taking into account transactions that ended after the default time range of 60 minutes.
•
Storage—the estimated storage cost is calculated on a daily basis, charging by the maximum storage consumption recorded within a 24 hours period. To view the estimated storage cost, change the time range to 24 hours.
For further details regarding the pricing plan definition, see Configuring Usage Costs on page 71. For details about using the Cost drilldown for in-depth investigation of the database estimated costs compared with the currently used cost model, see Monitoring Estimated Costs on page 51.

Tracking the Instance Data Flow

As SQL Azure users are charged by the data traffic to and from the database, tracking the scope of data transfers is essential for monitoring the database costs.
The Foglight for SQL Azure instance home page allows tracking incoming and outgoing data flows of both types described in the following :
•
External traffic—traffic between external applications running on-premise (that is, on the customer’s site) and the monitored database
•
Internal traffic—traffic flow within the cloud, between monitored databases and applications running on the cloud
 
* 
IMPORTANT: While Azure is always set to work by GMT time zone, the data flow details are updated by Foglight—namely, on-premise—time zone, and are displayed two hours after the actual operation took place. For example: if the on-premise time zone is GMT+2, and the current on-premise hour is 1 PM, the data flows appearing on the screen represent flows that took place on 11 AM.

Monitoring the Database Activity and Storage

The Database pane displays the main indicators of the database activity, as well as the database’s space utilization.
Using this pane allows viewing the response time compared with the instance’s level of activity. A high response time value may result from a long queue, that is: an overly high percentage of active users.
The Database pane displays the following parameters:
 
Table 4. Parameters and Parameter descriptions
Parameter
Description
Availability
The monitored database’s availability during the specified time range.
NOTE: The database's availability is checked only in regards to its connectivity, and not as a service. Therefore, any value less than 100% can indicate connectivity issues.
Response time
The time (in milliseconds) that elapses from the moment a dummy query is submitted, until the application indicates that the query was executed. High response time can indicate system overload.
Avg. Blocked (Sessions)
The average number of sessions that were either waiting on locks held by others, or causing others to wait, during the specified time range.
Foglight for SQL Azure displays information about all blocked sessions and lock conflicts, including the connections and resources involved in these conflicts, either for currently blocked processes or for all processes whose block time exceeded a predefined threshold during the specified time range. For details, see Tracking Current Lock Conflicts on page 27 and Tracking Historical Lock Conflicts on page 29.
Avg. Active (Sessions)
The average number of sessions that are actively processing in SQL Azure or that are waiting on locks (blocked).
Avg. Total (Sessions)
The workload (namely, the sum of all active sessions) for the SQL Azure instance, plotted over the specified time range. The sessions' behavior is compared with the typical observed behavior (baseline), which can be investigated via the Activity > Sessions panel. For details, see Viewing Detailed Sessions Data on page 30.
Storage Section
Used Space
The total size of the disk space used by the currently monitored SQL Azure database.
Curr. Limit
The storage limit currently defined for the database, before the database needs to be resized within the limits of the used database edition.
Max. Limit
The maximum storage limit allocated to the database.
While exceeding the maximum storage limit in the Web edition can be resolved by switching to Business edition, exceeding the maximum storage limit in Business edition requires coordination with Microsoft.
Free
The amount of free disk space, displayed both in size (MB) and as a percentage of the database’s total allocated space.

Reviewing frequently requested statistics

The SQL Azure FAQts section allows viewing various aspects of the database’s resource consumption and database object changes.
This section contains several questions regarding these issues, as follows:
•
What were the last 3 changes of database properties?
•
What are the 5 top-consuming SQL batches?
•
What are the 5 fastest growing database objects?
The answer to each of these questions is provided, in both a chart and a table format, via a popup displayed by clicking Show Me.
Figure 11. SQL Azure FAQt’s Section
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation