New Relic includes an integration for reporting your Azure App Gateway data to our platform. Here we explain how to activate the integration and what data it collects.
To enable the integration follow standard procedures to activate your Azure service.
You can change the polling frequency and filter data using configuration options.
Default polling information for the Azure App Gateway integration:
- New Relic polling interval: 5 minutes
To find your integration data in Infrastructure, go to one.newrelic.com > Infrastructure > Azure and select an integration.
Data is attached to the following event type:
For more on how to use your data, see Understand and use integration data.
This integration collects Azure App Gateway data for ApplicationGateway.
Number of bytes per second the Application Gateway has served
Number of unhealthy backend hosts
Number of healthy backend hosts
Count of successful requests that Application Gateway has served
Average request count per minute per healthy backend host in a pool
Count of failed requests that Application Gateway has served
Http response status returned by Application Gateway
Count of current connections established with Application Gateway
New connections per second established with Application Gateway
Current CPU utilization of the Application Gateway
Capacity Units consumed
Minimum capacity units that will be charged
Estimated capacity units that will be charged
Compute Units consumed
The number of HTTP response codes generated by the backend members. This does not include any response codes generated by the Application Gateway.
The number of TLS and non-TLS requests initiated by the client that established connection with the Application Gateway. To view TLS protocol distribution, filter by the dimension TLS Protocol.
The total number of bytes sent by the Application Gateway to the clients
The total number of bytes received by the Application Gateway from the clients
Average round trip time between clients and Application Gateway. This metric indicates how long it takes to establish connections and return acknowledgements
Average time that it takes for a request to be processed and its response to be sent. This is calculated as average of the interval from the time when Application Gateway receives the first byte of an HTTP request to the time when the response send operation finishes. It's important to note that this usually includes the Application Gateway processing time, time that the request and response packets are traveling over the network and the time the backend server took to respond.
Time spent establishing a connection with a backend server
Time interval between start of establishing a connection to backend server and receiving the first byte of the response header, approximating processing time of backend server
Time interval between start of establishing a connection to backend server and receiving the last byte of the response body
Web Application Firewall v1 Total Rule Distribution for the incoming traffic
Web Application Firewall v1 blocked requests rule distribution
Web Application Firewall v1 blocked requests count
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.