Compatibility and requirements for instrumenting Azure functions

Before you instrument Azure Functions, make sure your system meets the following requirements.

Basic requirements

• Azure Functions hosted on consumption plan or dedicated plan.

• Your Azure function app must use version 4 of the Azure Functions runtime or greater. Look for the following in your function app's .csproj file: <AzureFunctionsVersion>v4</AzureFunctionsVersion>.

• You must have the required permission to access kudu service.

• A New Relic account with either an admin role or an Infrastructure manager role.

• A user key.

• .NET agent version 10.30 or above.

Supported runtimes

Based on your hosting environment, the following Azure Function runtime stacks are supported.

Supported triggers and Distributed Tracing

You can instrument all trigger types, however Distributed Tracing is supported only in the following cases:

• .NET Stack:
  • Isolated model:
    • HttpTrigger
      • Distributed trace headers will be read from the inbound HTTP request.
  • In-process model (.NET agent version 10.38.0 and later):
    • HttpTrigger
      • Distributed tracing is supported when the function method has a parameter of type Microsoft.AspNetCore.Http.DefaultHttpRequest, Microsoft.AspNetCore.Http.HttpRequest or System.Net.Http.HttpRequest.
    • ServiceBusTrigger:
      • Incoming distributed trace headers will be read if the function method has a parameter of type Azure.Messaging.ServiceBus.ServiceBusReceivedMessage. Trace headers are expected to be in the ApplicationProperties collection of that object.
      • Distributed trace headers will be inserted into the ApplicationProperties collection of outbound Service Bus messages if the function method has a return type of Azure.Messaging.ServiceBus.ServiceBusMessage or Task<Azure.Messaging.ServiceBus.ServiceBusMessage>.

What's next