This document contains links to Microsoft documentation, which are provided for reference and informational purposes only.  is not affiliated, associated, authorized, or endorsed by Microsoft, or any of its subsidiaries or its affiliates, and as such makes no representation as to the accuracy or content of Microsoft documentation. |
serverless monitoring for Azure Functions gives you visibility into the performance of your applications that run as functions on Microsoft Azure. The .NET Agent supports Azure Functions hosted on App Service plans. Once installed, the .NET Agent automatically discovers business transactions in your Azure Functions.
You can monitor your applications running in Azure Functions exactly as you would any other application instrumented with the .NET Agent. Correlate business transactions between and through Azure Functions receive snapshots, create callgraphs, and integrate functions with End User Monitoring.
Instrument Windows Hosted Azure Functions
Before You Begin
Before you start instrumenting the .NET Agent with Azure Functions, make sure you meet the following requirements:
Microsoft Azure Requirements
- Applications hosted on the AppService plan
- Azure Functions versions 1.x and 4.x
- An instrumented Azure Function that is
- implemented in .NET and
- hosted on Windows OS
For EUM correlation to work, you need to disable the the Azure Function instrumentors, AzureFunctionsEntryInstrumentor and AzureFunctionsGenericTriggerInstrumentor. After disabling these instrumentors, the agent will start to monitor ASP.NET traffic. Then, you need to add the node property: aspdotnet-core-instrumentation with the value HTTP.
Requirements
Instrument Linux Hosted Azure Functions
Before You Begin
Before you start instrumenting the .NET Agent with Azure Functions, make sure you meet the following requirements:
Microsoft Azure Requirements
- Applications hosted on any existing plan that supports deploying using a customized Linux Docker container. For information on building custom containers for Azure Functions, see Working with containers and Azure Functions.
- Azure Functions version 4.x
- In-process Azure Functions only, the isolated worker process is not supported.
Requirements
For information on how to install the .NET Agent in a Linux container, see Install the .NET Agent for Linux in Containers.
Install Azure Site Extension
To add the Azure Site extension:
- Log in to the Windows Azure Portal.
Browse to Function App and select the desired function.
- Select Platform Features > Site Extensions > +Add.
- Click Choose Extensions and select Azure Site Extension 4.5.
- Click Legal Terms. Review AppDynamic's legal terms and conditions and select OK.
- Click OK in the Add Extension menu to complete the installation.
- Restart the function app.
After you install the Azure Site Extension, it appears in the list of the installed extensions.
Connect the .NET Agent to the Controller
You can connect your Azure Function apps to your Controller using the Kudu Console.
- Navigate to the Controller Configuration page in the Kudu Console:
http://{web app}.scm.azurewebsites.net/appdynamics/
For example: https://myazureexample.scm.azurewebsites.net/appdynamics/ - On the Controller Configuration page, enter your Controller connection information.
For example:- Controller Host:
mycompany.saas.appdynamics.com - Port:
443 - Enable SSL: selected
- Account Name:
MyAccount - Acccess Key:
<string> - Application Name:
MyAzureApp
- Click Validate to test the connection to the Controller and save your settings.
- Restart your function app.
Verify Instrumentation
To verify Azure Function instrumentation, view the function on flow maps in the Controller UI.
Azure Function Names in the Controller UI
In the Controller, the business transaction names match the Azure Function name.
HTTP Trigger functions are named using two segments of the function URL. You can change the name of HTTP Trigger functions in custom transaction naming.
Microsoft Azure, the Azure logo, Azure, and any other Microsoft Marks used in these materials are trademarks of Microsoft.com, Inc. or its affiliates in the United States and/or other countries.