Monitor Azure Functions

Get visibility into how your Azure Functions perform and use resources. These details help you detect issues early, track execution and performance trends, and control costs.

Before you begin

• Configure your cloud provider.
• Add a cloud account.
• Ensure your cloud account has appropriate privileges.
• Ensure that the feature monitoring is enabled for the account.

Enable monitoring for Azure Functions

If you configured your cloud account to monitor all supported resources or use tags to define the resources, the feature is enabled automatically. If you selected specific resources, enable the feature manually.

1. In SolarWinds Platform Web Console, click Settings > Cloud Discovery. This opens the Manage Cloud Accounts page.

2. Select the Azure account where you want to monitor Azure Functions and click Edit Properties. The Edit Cloud Account wizard opens.

3. Go to the Monitored resources screen, expand Compute, and ensure Azure Functions App is selected.

4. Complete the wizard. Azure Functions for the selected cloud account will now be monitored.

View data on monitored Azure Functions

1. Click Dashboards > Cloud > Azure to get an overview of monitored Azure resources.

2. Activate the Compute tab and click the Explore this data () button. This opens the Azure Function Apps list.

   Azure Functions vs. Azure App Services Licensing

   Monitoring both Azure Functions and Azure App Services consumes two licenses. This is because each service is polled separately and returns different set of metrics.

   Metrics for Azure App Services appear in the App Services view (My Dashboards > Cloud > Azure > click Explore this data on the Azure App Services tile).

   This licensing behavior does not affect your costs within the Azure portal. It applies only to SolarWinds licenses consumption.

3. To view details for a specific Function App, click the item in the table. The app details view displays metrics, such as:

   • Function execution count
   • Azure Functions App Detail (environment name, hosting options, month to date costs,...)
   • Function execution units
   • Always ready units
   • Instance count
   • File system usage
   • I/O read/write bytes per second
   • Memory working set
   • Requests,
   • Data in/out
   • Response time
   • Health check status
   • CPU/memory percent
   • Queue lengths
   • Connections
   • Current assemblies
   • Requests in application queue
   • Daily costs