New Relic's integrations include an integration for reporting your Microsoft Azure Web Apps metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported.
Features
Azure Web Apps provide a platform to build an app in Azure without having to deploy, configure and maintain your own Azure VM's. You can build Web Apps using the ASP.NET, PHP, Node.js and Python. They also integrate common development environments like Visual Studio and GitHub.
Using New Relic, you can:
- View Azure Web Apps data in pre-built dashboards.
- Run custom queries and visualize the data.
- Create alert conditions to notify you of changes in data.
Activate integration
Follow standard Azure Monitor integration procedure to activate your Azure Web Apps service in New Relic infrastructure monitoring.
Configuration and polling
You can change the polling frequency and filter data using configuration options.
New Relic queries your Web Apps service through Azure Monitor integration according to a default polling interval.
Find and use data
To explore your integration data, go to one.newrelic.com/infra > Azure > (select an integration).
Metric data
This integration collects the following metric data.
Azure Web Apps metrics
Metric | Description |
|---|---|
| The number of bound sockets existing in the sandbox (w3wp.exe and its child processes). A bound socket is created by calling bind()/connect() APIs and remains until said socket is closed with CloseHandle()/closesocket(). For WebApps and FunctionApps. |
| The average amount of memory used by the app, in megabytes (MiB). For WebApps and FunctionApps. |
| The average time taken for the app to serve requests, in seconds. For WebApps and FunctionApps. |
| The amount of incoming bandwidth consumed by the app, in MiB. For WebApps and FunctionApps. |
| The amount of outgoing bandwidth consumed by the app, in MiB. For WebApps and FunctionApps. |
| The amount of CPU consumed by the app, in seconds. For more information about this metric. Please see https://aka.ms/website-monitor-cpu-time-vs-cpu-percentage (CPU time vs CPU percentage). For WebApps only. |
| The current number of Assemblies loaded across all AppDomains in this application. For WebApps and FunctionApps. |
| Function Execution Count. For FunctionApps only. |
| Function Execution Units. For FunctionApps only. |
| The number of times the generation 0 objects are garbage collected since the start of the app process. |
| The number of times the generation 1 objects are garbage collected since the start of the app process. Higher generation GCs include all lower generation GCs. For WebApps and FunctionApps. |
| The number of times the generation 2 objects are garbage collected since the start of the app process. For WebApps and FunctionApps. |
| The total number of handles currently open by the app process. For WebApps and FunctionApps. |
| Health check status. For WebApps and FunctionApps. |
| The count of requests resulting in an HTTP status code 101. For WebApps and FunctionApps. |
| The count of requests resulting in an HTTP status code equal or bigger than 200 but smaller than 300. For WebApps and FunctionApps. |
| The count of requests resulting in an HTTP status code equal or bigger than 300 but smaller than 400. For WebApps and FunctionApps. |
| The count of requests resulting in HTTP 401 status code. For WebApps and FunctionApps. |
| The count of requests resulting in HTTP 403 status code. For WebApps and FunctionApps. |
| The count of requests resulting in HTTP 404 status code. For WebApps and FunctionApps. |
| The count of requests resulting in HTTP 406 status code. For WebApps and FunctionApps. |
| The count of requests resulting in an HTTP status code equal or bigger than 400 but smaller than 500. For WebApps and FunctionApps. |
| The count of requests resulting in an HTTP status code equal or bigger than 500 but smaller than 600. For WebApps and FunctionApps. |
| The time taken for the app to serve requests, in seconds. For WebApps and FunctionApps. |
| The rate at which the app process is issuing bytes to I/O operations that don't involve data, such as control operations. For WebApps and FunctionApps. |
| The rate at which the app process is issuing I/O operations that aren't read or write operations. For WebApps and FunctionApps. |
| The rate at which the app process is reading bytes from I/O operations. For WebApps and FunctionApps. |
| The rate at which the app process is issuing read I/O operations. For WebApps and FunctionApps. |
| The rate at which the app process is writing bytes to I/O operations. For WebApps and FunctionApps. |
| The rate at which the app process is issuing write I/O operations. For WebApps and FunctionApps. |
| The current amount of memory used by the app, in MiB. For WebApps and FunctionApps. |
| Private Bytes is the current size, in bytes, of memory that the app process has allocated that can't be shared with other processes. For WebApps and FunctionApps. |
| The total number of requests regardless of their resulting HTTP status code. For WebApps and FunctionApps. |
| The number of requests in the application request queue. For WebApps and FunctionApps. |
| The number of threads currently active in the app process. For WebApps and FunctionApps. |
| The current number of AppDomains loaded in this application. For WebApps and FunctionApps. |
| The total number of AppDomains unloaded since the start of the application. For WebApps and FunctionApps. |
| Workflow Action Completed Count. For LogicApps only. |
| Workflow Job Execution Delay. For LogicApps only. |
| Workflow Job Execution Duration. For LogicApps only. |
| Workflow Runs Completed Count. For LogicApps only. |
| Workflow Runs Dispatched Count. For LogicApps only. |
| Workflow Runs Started Count. For LogicApps only. |
| Workflow Triggers Completed Count. For LogicApps only. |