Caution: The documentation you are viewing is
for an older version of Zend Framework.
You can find the documentation of the current version at:
Zend_Service_WindowsAzure_Diagnostics_Manager - Zend_Service
Blob Storage stores sets of binary data. Blob storage offers the following three Windows Azure Diagnostics enables you to collect diagnostic data from a service running in Windows Azure. It can be used for tasks like debugging and troubleshooting, measuring performance, monitoring resource usage, traffic analysis, capacity planning, and auditing. Once collected, diagnostic data can be transferred to a Windows Azure storage account for persistence. Transfers can either be scheduled or on-demand.
You can configure Windows Azure Diagnostics from code running within a role. You can also configure it remotely from an application running outside of the Windows Azure; for example, you can manage Windows Azure Diagnostics from a custom dashboard application running locally. By managing Windows Azure Diagnostics remotely, you can start your service with an initial diagnostic configuration, and then tweak that configuration from code running outside of your service, without having to upgrade your service.
More information on which logs, performance counters, crash dumps, ... can be monitored can be found on the » corresponding MSDN web page.
Note: Diagnostics are configured on a per-role basis. This means that each role should be configured separately. Specifying diagnostics instructions for one role instance does not imply this configuration is loaded on other role instances.
Note: Diagnostics are configured on a per-role basis. This means that each The Diagnostics API in the Windows Azure SDK for PHP can only be used when the DiagnosticsMonitor has been started during role startup. Currently, this is only supported when an application is packaged with the Windows Azure Command-line Tools for PHP Developers.
This topic lists some examples of using the Zend_Service_WindowsAzure_Diagnostics_Manager class. Other features are available in the download package, as well as a detailed API documentation of those features.
Using the following code, you can check if a diagnostics configuration for the current role instance exists.
Example #1 Checking if a diagnostics configuration for the current role instance exists
Using the following code, you can load the current role instance diagnostics configuration.
Example #2 Loading the current role instance diagnostics configuration
Using the following code, you can store the current role instance diagnostics configuration.
Example #3 Storing the current role instance diagnostics configuration
Using the following code, you can subscribe to a performance counter.
Example #4 Subscribing to a performance counter
The current role instance id is defined in the server variable RdRoleId. It will only be available when the application is run in Development Fabric or Windows Azure Fabric.
Example #5 Getting the current role instance id