Documentation forServer & Application Monitor
Monitoring your applications and environment is a key capability of Hybrid Cloud Observability and is also available in a standalone module, Server & Application Monitor (SAM). Hybrid Cloud Observability and SAM are built on the self-hosted SolarWinds Platform.

Microsoft Azure App Service

This SAM application monitor template contains metrics for monitoring Microsoft Azure App services, an HTTP-based service for hosting web applications, REST APIs, and mobile backends. To use this template, assign it to an external node that points to portal.azure.com.

Microsoft AzureRM was deprecated on February 29, 2024. To use the Az module templates, uninstall the AzureRM module and install the Az module. To install the Azure Az module, refer to: https://docs.microsoft.com/en-us/powershell/azure/install-az-ps?view=azps-7.1.0.

Passwords for legacy Microsoft Azure application monitor templates and related application monitors are stored as plain text in the SolarWinds Platform database. SolarWinds recommends switching to Microsoft Azure API poller templates that leverage OAuth 2.0 authorization.”

Prerequisites

  • PowerShell modules (Az, Az.Accounts, Az.Resources) installed

  • Parameters for connecting to your Azure account

    • Subscription ID

    • Application ID

    • Tenant ID

    • Secret Key

    See Find Microsoft Azure credentials.

  • Any Azure App (with its name and ID) with Reader or Contributor access in Azure access control

  • Azure App Service for which metrics must be calculated and its Resource Group Name

  • PowerShell 5.1 or later

Credentials

  • Windows Administrator privilege on the target system

  • Login credentials to access Azure Portal, passed as script arguments as per prerequisites

    • Example: (<SubscriptionID>, <TenantID>, <ApplicationID>, secretKey=<Enter SecretKey>, <ApplicationName>, <ResourceGroupName>, TimeRange=<Time in hrs>)

  • Optional parameters can be passed to script argument:

    • Time interval for which data is to be fetched (in hours)

Notes

Component monitors

Average number of bytes sent

Provides the average number of bytes sent for the given app.

Unit: MB (megabytes)

Total number of 2xx requests

Provides the count of requests resulting in an HTTP status code >= 200 but < 300 for the given app.

Unit: Count

Total number of 3xx requests

This monitor provides the count of requests resulting in an HTTP status code >= 300 but < 400 for the given app.

Unit: Count

Total number of 401 requests

Provides the count of requests resulting in HTTP 401 status code for the given app.

Unit: Count

Total number of 403 requests

Provides the count of requests resulting in HTTP 403 status code for the given app.

Unit: Count

Total number of 404 requests

Provides the count of requests resulting in HTTP 404 status code for the given.

Unit: Count

Total number of 406 requests

Provides the count of requests resulting in HTTP 406 status code for the given.

Unit: Count

Total number of 4xx requests

Provides the count of requests resulting in an HTTP status code >= 400 but < 500 for the given app.

Unit: Count

Total number of 5xx requests

Provides the count of requests resulting in an HTTP status code >= 500 but < 600 for the given app.

Unit: Count

Total number of requests served by the app

Provides the total number of requests regardless of their resulting HTTP status code for the given app.

Unit: Count

Average number of bytes received

Provides the average number of bytes received for the given app.

Unit: MB (megabytes)

Average memory used

Provides the average amount of memory in MiBs used by the app.

Unit: MB (megabytes)

Average response time

This monitor provides the average time taken for the app to serve requests in ms.

Unit: ms (milliseconds)