Skip to main content
Alert on requests/s for Azure App Service
  1. Posts/

Alert on requests/s for Azure App Service

·184 words·1 min
Christoph Petersen
Author
Christoph Petersen

A customer of mine had the following rule configured:

Alert configuration

It was his expectation that this rule would be triggered when in the last five minutes at some point more that 200 requests/s were being made to the App Service. Unfortunately this is not the case. The rule will sum the number of requests for the last five minutes and if that number is > 200 the rule will trigger.

There is an easy solution for this though. With a simple log alert running in Application Insights we can build a bucket with the requests for the last five minutes by second. In the following example I’ve added the cloud_RoleName as an option. This is only required if more than one microservice or application writes to the same Application Insights instance.

requests
| where timestamp >= ago(5m)
| where cloud_RoleName != "" 
| summarize AggregatedValue=count() by bin(timestamp, 1s), cloud_RoleName

Metric alerts for App Services are not yet onboarded to the new Alert experience in Azure Monitor. By following the guide you can work around that and create a metric alert in the new alert experience:

Metric alert against Application Insights data

Related

Application Insights Connector deprecation

·101 words·1 min
In a time before cross-resource queries were possible the Application Insights Connector would copy data from Application Insights to a Log Analytics workspace. With the emergence of cross-resource queries the duplication of data is not required anymore as queries can be sent to both (or even more) entities at the same time in real time.

Merge Azure Backup reporting data into one storage account using Logic Apps

·709 words·4 mins
When using Azure Backup to manage (geo-)distributed backups across a company you may find that the Azure Backup Reports with Power BI is limited to a single storage account. Unfortunately the reporting telemetry coming from Azure Backup needs to be written to a storage account that is in the same region as the Recovery Services Vault.