Microsoft Azure Event Hub Namespace

This SAM application monitor template contains metrics, including requests, messages, errors, connections and traffic for monitoring Microsoft Azure Event Hubs. Some counters may require manual configuration, such as setting up installation-specific instances or correcting thresholds for your environment.

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

  • ApplicationID

  • TenantID

  • Secret Key

• Any Azure App (with its name and ID) having minimum role as Read Only

• Application name for which metrics must be calculated and its Resource Group Name

• PowerShell 5.1 or later

Credentials

• Windows Administrator privileges on the target system
• Login credential to access the Azure Portal, passed as script arguments per prerequisites (<SubscriptionID>, <TenantID>, <ApplicationID>, value=<Secret Key>, <Namespace Name>, Resource Group Name, value=<Time Interval>)
• Optional parameters can be passed to script argument:
• Time interval for which data has to be fetched (in hours)
• Number of retries as the second last argument; the default is 3 retries.
• WaitTime as the last argument; the default is 0.5 seconds.

Notes

• Run scripts as the Administrator.
• The ApplicationID with which you are connecting to the Azure portal must be registered in Azure Active Directory as read-only/contributor role for the monitored application. See Add an Azure Active Directory app for cloud monitoring in the SolarWinds Platform.
• Portions of this document were originally created by and are excerpted from the following sources:
  • Create an event hub using Azure PowerShell

  • Azure Event Hubs metrics in Azure Monitor

  • Supported metrics with Azure Monitor.

Component monitors

Archive backlog messages

This monitor provides the total Archive messages in backlog for the given namespace via PowerShell cmd-let.

Unit: Count

Archive message throughput

This monitor provides total Event Hub archived message throughput for the given namespace via PowerShell cmd-let.

Unit: Bytes

Archive messages

This monitor provides total Event Hub archived messages for the given namespace via PowerShell cmd-let.

Unit: Count

Incoming Bytes

This monitor provides the total Event Hub incoming message throughput for the given namespace via PowerShell cmd-let.

Unit: Bytes

Outgoing bytes

This monitor provides the total Event Hub outgoing message throughput for the given namespace via PowerShell cmd-let.

Unit: Bytes

Incoming Messages

This monitor provides the total incoming messages for the given namespace via PowerShell cmd-let.

Unit: Count

Incoming Requests

This monitor provides the Total incoming send requests for the given namespace via PowerShell cmd-let.

Unit: Count

Internal Server Errors

This monitor provides the Total internal server errors for the given namespace via PowerShell cmd-let.

Unit: Count

Other Errors

This monitor provides the total failed requests for the given namespace via PowerShell cmd-let.

Unit: Count

Outgoing Messages

This monitor provides the total outgoing messages for the given namespace via PowerShell cmd-let.

Unit: Count

Successful Requests

This monitor provides the total successful requests for the given namespace via PowerShell cmd-let.

Unit: Count

Server Busy Errors

This monitor provides the Total server busy errors for the given namespace via PowerShell cmd-let.

Unit: Count