ZenPack:Microsoft Azure

From Zenoss Wiki
Revision as of 11:17, 3 September 2013 by (Talk)$7

Jump to: navigation, search

Note: This ZenPack is available in commercial versions of Zenoss. Click here to request more information about this commercial ZenPack. Click here to see all commercial ZenPacks.

Zenoss, Inc.
ZenPack name
Git sources (for cloning)

Applications Monitored: 

Microsoft Azure ZenPack

The Microsoft Azure ZenPack allows you to monitor Azure Subscription managing services.


The ZenPack Catalog has moved to its new home at https://www.zenoss.com/product/zenpacks as of January 17, 2017. The following information may be out of date, and this page will eventually be removed.


This ZenPack is included with commercial versions of Zenoss and enterprise support for this ZenPack is provided to Zenoss customers with an active subscription.


Version 1.0.0- Download
Requires PythonCollector ZenPack
Compatible with Zenoss Resource Manager 4.2.x


This ZenPack provides support for monitoring Microsoft Azure Services. Monitoring for the following Azure Subscription entities is provided using Windows Azure SDK for Python.

Bulbgraph.png Note: Please restart zenoss after installing this ZenPack to be able to add a new Azure Subscription. When creating Disk components not related to any Instance or Cloud component, they will be displayed in the Blobs table. Note that the commercial zenoss version requires ZenPacks.zenoss.Impact, otherwise the DynamicServices panel will be missing.



The features added by this ZenPack can be summarized as follows. They are each detailed further below.

  • Discovery of Azure Subscription entities.
  • Monitoring of Storage Service and Site components.
  • Event management and monitoring for certain Azure states.
  • Optional service impact with addition of Zenoss Service Dynamics product.


The following entities will be automatically discovered through an account name, subscription ID and certificate file path you provide. The attributes, tags and collections will be updated on Zenoss' normal remodeling interval which defaults to every 12 hours.

Hosted Services (Cloud Services in Azure Management Portal)

Attributes: ID, URL, Service status, Affinity group, Location, Creation date, Modification date
Collections: Instances, Disks

Instances (Virtual Machines in Azure Management Portal)

Attributes: ID, Hosted service, Instance status, IP address, Power state, Error code
Tags: Name
Collections: Disks
Attributes: ID, Hosted service, Instance, Location, Link, Size
Tags: Name

Storage Services (Storages in Azure Management Portal)

Attributes: ID, URL, Service status, Affinity group, Location
Collections: Containers, Blobs, Tables, Queues
Attributes: ID, Storage service, URL, Modification date
Tags: Name
Collections: Blobs
Attributes: ID, Storage service, Container, URL, Modification date, Content length, Content type, Blob type, Lease status
Tags: Name
Attributes: ID, Storage service, Updating date
Tags: Name
Attributes: ID, Storage service, URL
Tags: Name

Virtual Networks (Networks in Azure Management Portal)

Attributes: ID, Affinity group, State
Collections: Subnets
Attributes: ID, Virtual Network, Address prefix
Tags: Name
Web Spaces
Attributes: ID, Service status, Plan, Geolocation, Workers, Availability state, Compute mode
Collections: Sites

Sites (Web Sites in Azure Management Portal)

Attributes: ID, Web space, State, Availability state, Runtime availability state, Admin enabled, Compute mode, Host names, Enabled host names, Link, Usage state
Tags: Name
Attributes: ID
Affinity Groups
Attributes: ID, Description, Location, Capabilities


The following metrics will be collected every 5 minutes by default. The Average statistic is collected, and the graphed value is per second for anything that resembles a rate.

Storage Services
Metrics: Blobs container count, Blobs object count, Blobs capacity
Metrics: CPU time, Filesystem storage, Memory usage, Bytes received, Bytes sent, Local bytes read, Local bytes written
Metrics: Max core count, Max storage accounts, Max hosted services, Current core count, Current hosted services, Current storage accounts

Event management

According to the following Azure states this ZenPack will trigger info or error events with an appropriate summary message.

Info event:
  • Current core count is equal to Max core count,
  • Current storage accounts number is equal to Max storage accounts number,
  • Current hosted services number is equal to Max hosted services number.

Hosted Service (Cloud Service)

Info event: service status is one of the following: Deleting, Deleted, Changing, ResolvingDns

Instance (Virtual Machine)

Info event: instance status is DeletingVM
Error event:
  • instance status is one of the following: RoleStateUnknown, FailedStartingRole, FailedStartingVM, UnresponsiveRole,
  • instance error code is one of the following: WaitTimeout, VhdTooLarge, AzureInternalError,
  • instance status is Unknown.
Error event: is_corrupted property is True
Storage Service
Info event: service status is one of the following: Deleting, Deleted, Changing, ResolvingDns

Virtual Network Site (Network)

Info event: state is Deleting
Error event: state is Unavailable
Web Space
Error event: availability or service status is Limited
Error event:
  • usage state is Exceeded,
  • availability state is Limited

Service Impact

When combined with the Zenoss Service Dynamics product, this ZenPack adds built-in service impact capability for services running on Microsoft Azure Service. The following service impact relationships are automatically added. These will be included in any services that contain one or more of the explicitly mentioned entities.

Service Impact Relationships
  • Hosted service, storage sevice, virtual network, web space, affinity group or location failure affects subscription.
  • Instance failure affects related hosted service.
  • Disk failure affects related instance.
  • Container, table or queue failure affects related storage service.
  • Blob failure affects related container.
  • Site failure affects related web space.
  • Subnet failure affects related virtual network.


Adding Azure Subscriptions

Use the following steps to start monitoring Azure Subscription using the Zenoss web interface.

  1. Navigate to the Infrastructure page.
  2. Choose Add Azure Subscription from the add device button.
  3. Enter your Azure account name, subscription ID and certificate file name along with absolute path (e.g. /home/zenoss/Downloads/MSAzure.pem).
  4. Optionally choose a collector other than the default localhost.
  5. Click Add.


Certificate file
To add a new Azure Subscription you will need a certificate file used in Management Certificates on Azure Management Page (see [1]), which can be stored anywhere on the disk with read permissions enabled.
If you do not have a certificate, please see Windows Azure Documentation page.
Monitoring configuration
Data monitoring and events triggering will only work if monitoring configuration on Azure Management Page (see [2]) is enabled with at least 1-2 days retention.


If you encounter any issues with Zenpack instalation, please make sure that you have restarted zenoss after installation and your target disk has enough free memory and read permisions enabled. If device adding failed, try to restart your browser and make sure that you have specified a correct id and path to the certificate file (e.g. /home/zenoss/Downloads/MSAzure.pem). In case of any issues when uninstalling this Zenpack, please remove all devices first.

Note that device monitoring requires zenpython deamon to be constantly running. If you have just enabled monitoring, try pressing Zoom in to see the graphs. In case of any issues you can run zenpython daemon in foreground with zenpython run -v10 -c command and check if there are no exceptions. If zenpython runs without errors and prints monitoring data to stdout, then you should check if monitoring templates are bound to subscription and it's components.


Due to limitations of REST API this ZenPack does not monitor some of Azure services:

  • Mobile services
  • SQL Databases
  • SQL Reporting
  • Media services
  • Active Directory

For Virtual Machines there is no performance information available via REST API, so this ZenPack does not provide such information. Hovewer, this information can be retrieved by adding Azure VM as Linux/Windows server device in Zenoss.

Installed Items

Installing this ZenPack will add the following items to your Zenoss system.

Device Classes
  • /Azure
Modeler Plugins
  • AzureCollector
Datasource Types
  • AzureDataSource
Monitoring Templates
  • AzureSite (in /Azure)
  • AzureStorageService (in /Azure)
  • AzureSubscription (in /Azure)
Device Types
  • AzureSubscription (in /Azure)
Component Types
  • AzureHostedService (on AzureSubscription)
  • AzureInstance (on AzureHostedService)
  • AzureDisk (on AzureInstance)
  • AzureStorageService (on AzureSubscription)
  • AzureContainer (on AzureStorageService)
  • AzureQueue (on AzureStorageService)
  • AzureTable (on AzureStorageService)
  • AzureBlob (on AzureContainer)
  • AzureVirtualNetworkSite (on AzureSubscription)
  • AzureSubnet (on AzureVirtualNetworkSite)
  • AzureWebSpace (on AzureSubscription)
  • AzureSite (on AzureWebSpace)
  • AzureLocation (on AzureSubscription)
  • AzureAffinityGroup (on AzureSubscription)


Normal Installation (packaged egg)

  1. Download the appropriate egg file for the version of Zenoss you are running.
  2. Ensure you are logged in as the zenoss user:
    $ sudo su - zenoss
  3. Install the ZenPack:
    $ zenpack --install ZenPacks.zenoss.Microsoft.Azure-*.egg
  4. Restart these services:
    $ zenoss restart


Purplemarker.png New: Don't forget to add yourself to the Zenoss User Map!

blog comments powered by Disqus