Is Azure cloud part of your infrastructure? You can use IDERA Uptime Cloud Monitor to monitor your Azure cloud resources. As of today, we support monitoring for Azure Virtual Machines, Azure MSSQL, Azure database for MySQL and Azure database for PostgreSQL.

Prerequisites

Uptime Cloud Monitor from IDERA offers a SAAS based out-of-the-box solution for monitoring Azure resources for performance and availability. You need the following to monitor an Azure account on UCM.

  1. An Uptime Cloud Monitor account - If you don’t already have an account, you can sign up for a 14 day FREE TRIAL of Uptime Cloud Monitor here (no Credit Card required).
  2. An Active Azure account with running resources.
  3. Azure Application - Access to create application in Azure account for monitoring.

Monitor Azure Resources from Uptime Cloud Monitor

There are three steps that you need to do to start monitoring an Azure Account using IDERA Uptime Cloud Monitor:

  1. Add an Azure Account for Monitoring
  2. Verify that the Dashboard for all Azure monitored entities is up and running
  3. Configure Alerts to be notified about performance and availability issues with Azure monitored entities (by default, no alerts will be created automatically)

1. Add an Azure Account for Monitoring

Figure 1: In your Uptime Cloud Monitor Account, navigate to Azure

Login to your Uptime Cloud Monitor account and navigate to Azure Tab. Click on ‘Click Here’ to add an Azure account.

Figure 2: Wizard to enter Azure Tenant ID, Azure client ID and Client Secret key.

1. Enter Azure Tenant ID.

2. Enter Azure client ID.

3. Enter Azure client secret key.

4. If you are not sure how to get the above values for your Azure account, click on “Show me how” link to check the steps to get required data from your Azure account.

5. Go to the next wizard after filling required fields.

Figure 3: Wizard to enter label for Azure account and tags.

6. Enter Unique label for Azure account.

7. Enter comma separated tags (optional).

8. Click on ‘Done’ button to verify creds and add account for monitoring.

2. Verify that the Dashboard for all Azure monitored entities is up and running

In Azure tab, there is an Overview secondary tab in the left navigation menu where stats for resources of all accounts can be viewed. Also by clicking on account name in the left navigation menu, resources of the chosen account will be visible.

A. Overview/Summary

Figure 4: Overview for Azure account showing metrics count and objects count.

B. Virtual Machines

Figure 5: Virtual Machines Dashboard.

As Figure 5 illustrates, from the Azure Virtual Machines Dashboard, a user can:

  1. See CPU usage for a monitored Azure Virtual Machine.
  2. See Network usage for a monitored Azure Virtual Machine.
  3. Click on ‘Details’ button to see more details about this monitored Azure Virtual Machine.
  4. Click on ‘Next’ button to see more widgets if available for other monitored Azure Virtual Machines.

C. SQL Databases

Figure 6: SQL Database Dashboard

As Figure 6 illustrates, from the Azure SQL Database Dashboard, a user can:

  1. See CPU usage for a monitored Azure SQL database
  2. See Storage percentage for a monitored Azure SQL database
  3. See Data Input/Output for a monitored Azure SQL database
  4. See Throughput details for a monitored Azure SQL database
  5. See Workers count for a monitored Azure SQL database
  6. See Number of successful and failed connections for a monitored Azure SQL database
  7. Click on ‘Details’ button to see more details about this monitored Azure SQL database.
  8. Click on ‘Next’ button to see more widgets if available for other monitored Azure SQL databases.

D. MySQL Servers

Figure 7: MySQL servers dashboard.

As Figure 7 illustrates, from the Azure MySQL Servers Dashboard, a user can:

  1. See CPU usage for a monitored Azure MySQL Server
  2. See Memory usage for a monitored Azure MySQL Server
  3. See IO details for a monitored Azure MySQL Server
  4. See Storage consumption for a monitored Azure MySQL Server
  5. See used and total available storage for a monitored Azure MySQL Server
  6. See active and failed connections for a monitored Azure MySQL Server
  7. Click on ‘Details’ button to see more details about this monitored Azure MySQL Server.
  8. Click on ‘Next’ button to see more widgets if available for other monitored Azure MySQL Servers.

E. PostgreSQL Servers

Figure 8: PostgreSQL servers dashboard.

As Figure 8 illustrates, from the Azure PostgreSQL Servers Dashboard, a user can:

  1. See CPU usage for a monitored Azure PostgreSQL Server
  2. See Memory usage for a monitored Azure PostgreSQL Server
  3. See IO details for a monitored Azure PostgreSQL Server
  4. See Storage consumption for a monitored Azure PostgreSQL Server
  5. See used and total available storage for a monitored Azure PostgreSQL Server
  6. See active and failed connections for a monitored Azure PostgreSQL Server
  7. Click on ‘Details’ button to see more details about this monitored Azure PostgreSQL Server.
  8. Click on ‘Next’ button to see more widgets if available for other monitored Azure PostgreSQL Servers.

F. All Entities

Figure 9: All entities list.

This is a paginated list of all Azure resources.

Note: UCM currently supports monitoring for four resources (VM, Azure SQL databases, Azure MySQL Servers and Azure PostgreSQL Servers) but all entities page will list all your Azure resources. If there is a different Azure resource you are running (Eg. Azure Redis Cache) for which there is no UCM support for detailed monitoring, then the “Details” button will be hidden for that resource/resources. As an illustration, in Figure 9, Azure entities of type “Other” do not have an associated Details button.

G. Accounts

Accounts is a paginated list of all Azure accounts added for monitoring. User can either enable, disable or edit an account.

User can also add a new account by clicking on New Azure Account button.

Figure 10: Tree List of entities within an Azure Account.

As shown in Figure 10, the user would be presented with a tree list of all entities within an Azure account, segregated by Azure Resource Groups. The user can disable monitoring for specific entities or disable monitoring for all entities within a specific Resource Group.

H. Details

Details for a resource can be opened from All Entities page. Details can also be viewed by clicking ‘Details->’ on the resource widget on Dashboards page.

In the details page, data graphs are available for all the monitored metrics for that resource.

Screenshot shows Details graph for VM CPU usage.

Figure 11: CPU Utilization data for a Virtual Machine.

3. Configure Alerts to be notified about performance and availability issues with Azure monitored entities

Figure 12: A new alert being added that will be triggered when Azure VM CPU metric exceeds a threshold of 90% within a time period of 5 min

Alerts can be configured against any of these all monitored metrics for Azure resources.

You can configure new alerts that will be triggered when performance issues with Azure resources. You can also configure the notification mechanisms for a triggered alert.

1. Go to Alerts Tab > Configure alerts and click on “New Alerts” button

2. Provide values for these fields in the New Alert page:

  • Description: A description of the alert that will be easily recognized by you and your team if the alert is triggered
  • Alert me when: Select the metric of interest and the condition upon which the alert is triggered. In the Alert me when dropdown, you can prefill “Azure:” to get only the list of monitored metrics of selected type of Azure resource. From this list, you can then select the specific metric for which you want to configure an alert. As an illustration, in Figure 12, the chosen metric of interest in ‘Alert me when’ is ‘Azure: VM: CPU Utilization’ and the condition for triggering the alert is if the average value is more than or equal to the specified value of 90%
  • For at least: The duration for which the alert condition must be valid for the alert to be triggered
  • Matching tags: By default, (match everything) is chosen. If needed, you can attach tags to a particular metric object and select those tags here, which would cause only alerts on that metric object to be triggered.
  • Excluding tags: By default, (exclude nothing) is chosen. If needed, you can attach tags to a particular metric object and select those tags here, which would cause alerts on that metric object to be skipped.
  • Annotate: When enabled, an annotation is automatically created when the alert is triggered. Annotations will be visible in the custom metrics dashboard where the data stream is displayed.
  • Automatic Clear: When enabled, the alert issue is automatically cleared if the triggering condition is no longer true
  • Notify on clear: When enabled, notifications are also sent when the alert issue is cleared. Please do note that notifications are always sent when the alert issue is triggered.
  • Send Notifications To: Here you can configure the notification mechanisms by which the alert is communicated to you and others in your team.

    Uptime Cloud Monitor supports notifying different sets of users with differing notification mechanisms for each alert type. Notification mechanisms include:

    • Email
    • SMS
    • PagerDuty
    • Twitter
    • HipChat
    • Campfire
    • Slack
    • OpsGenie

    Webhooks are also exposed for clients to configure custom notification mechanisms.

    More about setting up website probe alerts can be found here.

    Uptime Cloud Monitor Free Trial! Sign up today!

    Sign up for a 14 day FREE TRIAL of Uptime Cloud Monitor (no Credit Card required).

    You can find more information about Uptime Cloud Monitor pricing options here.

    We charge only $0.08 per month per metric!

    Sign up today!

    Anonymous