Our infrastructure monitoring provides an integration for Microsoft Azure Functions that reports data from your Azure Functions service to New Relic. This document explains how to activate this integration and describes the data that can be captured.
Our Azure Functions integration reports metric data about your Functions service, like the number of function executions, bytes sent and received and HTTP error counts. It also collects data about the status and configuration of the service.
To enable this integration follow the standard procedures to activate your Azure service for infrastructure monitoring.
You can change the polling frequency and filter data using configuration options.
Default polling information for the Azure Functions integration:
- Polling interval: 5 minutes
- Resolution: 1 data point per minute
To find your integration data, go to one.newrelic.com, in the top nav click Infrastructure, then click Azure and look for the integration.
For more on how to find and use integration data, see Understand and use data.
To view metrics reported by the Azure Functions integration, query the
AzureFunctionsAppSample event type. Use the metadata associated with each metric to filter and facet the data being reported. For detailed metric information, see the Azure supported metrics documentation.
Average count in bytes of memory working set.
Function execution count.
Function execution in units.
Total number of HTTP server errors 500-599.
Total bytes of memory working set.
Total bytes received by the functions.
Total bytes sent by the functions.
After March 2022, we're discontinuing support for several capabilities, including inventory data for cloud integrations. For more details, including how you can easily prepare for this transition, see our Explorers Hub post.
Inventory data is information about your system's state and configuration. For details on how to find and use inventory data, see Understand and use data.
The Azure Functions integration reports this inventory data:
The Azure Functions integration also collects these attributes about the service and its configuration: