New Relic's integrations include an integration for reporting your Microsoft Azure CDN profile metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported.
Features
New Relic gathers metrics data from Azure Monitor for the Azure CDN profile service. Azure Content Delivery Network is a globally distributed network of servers that can efficiently deliver web content to consumers.
Using New Relic, you can:
- View Azure CDN profile 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 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 Azure CDN profile services through the 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 CDN profile
Metric | Description |
|---|---|
| This is the ratio of the total bytes served from the cache compared to the total response bytes. |
| The percentage of successful health probes from AFDX to backends. |
| The time calculated from when the request was sent by AFDX edge to the backend until AFDX received the last response byte from the backend. |
| The number of requests sent from AFDX to origin. |
| The percentage of all the client requests for which the response status code is 4XX. |
| The percentage of all the client requests for which the response status code is 5XX. |
| The number of client requests served by the HTTP/S proxy. |
| The number of bytes sent as requests from clients to AFDX. |
| The number of bytes sent as responses from HTTP/S proxy to clients. |
| The time calculated from when the client request was received by the HTTP/S proxy until the client acknowledged the last response byte from the HTTP/S proxy. |
| The number of client requests processed by the Web Application Firewall. |