Azure Bot Monitoring | Cloudmon

Azure Bot

Microsoft Azure

Azure Bot

Discover the bots in your connected Azure account, see each one with its SKU, kind, app type, and channels, and track the traffic and latency measures Azure Monitor provides.

Overview

Azure Bot is a resource that registers a bot and connects it to channels, such as Microsoft Teams, so users can talk to it.

Cloudmon automatically discovers the bots in your connected Azure account. Go to Cloud → Azure, open the account, and click the Azure Bot card to view the list.

To connect an Azure account, see How to Set Up Azure Monitoring.

Turning On Monitoring for Azure Bot

The Services tab of the Azure account shows a card for each Azure service. Select All (next to Configured) to see every supported service. A service that is not yet monitored for the account shows an Enable button instead of a resource count.

To turn on monitoring, click Enable on the Azure Bot card. The bots appear in the list once discovery runs for the account. To run discovery straight away, open the account menu (☰) and click Rediscover.

To choose the services discovered for an account, edit the account and select them under Services to be Discovered, as described in Actions in Azure Monitoring.

Azure Bot List

The list displays all discovered bots with the following details:

ColumnDescription
NameThe name of the resource as configured in Azure.
Resource GroupThe resource group the resource belongs to.
LocationThe Azure region where the resource is deployed.
SKUThe bot pricing tier.
KindThe kind of bot resource.
App TypeThe identity type of the bot's app, such as single tenant.
ChannelsThe channels the bot is connected to.
StatusThe current status of the resource.
ActionsOptions for managing monitoring of the resource.

Metrics

Azure Monitor provides the following metrics for bots:

MetricDescription
Requests TrafficThe number of requests made, split by operation, authentication, protocol, status code, and data center.
Request LatencyThe time the server took to process a request, split by operation, authentication, protocol, and data center.

Use Cases

  • Track Requests Traffic to see how much a bot is used and when usage changes.
  • Split Requests Traffic by status code to spot a rise in failed requests.
  • Watch Request Latency to catch a bot that is slowing down.

Troubleshooting

IssueWhat to check
The list shows "There are no Azure Bot Available"The account has no bots, or discovery has not run since they were created. Go to Cloud → Azure, open the account, open the menu (☰), and click Rediscover.
The service card shows EnableThe service is not monitored for this account. Edit the account and select Azure Bot under Services to be Discovered.
Resources are missing after discoveryConfirm that the application registered for Cloudmon has the Reader role on the subscriptions that contain the resources. See How to Set Up Azure Monitoring.

Alarms

To configure alarm rules, see Azure Alarm Rules.

Reports

To create a report, see Reports.