Linux instrumentation

You can configure New Relic monitoring for Azure Function Apps hosted on Linux. This is achieved by instrumenting your Function App with the appropriate New Relic agent for its runtime such as Node.js, .NET, or Python. This instrumentation allows you to monitor the performance and health of your Azure Functions in real-time within New Relic.

Prerequisites

Ensure your Azure Function meets our compatibility and requirements.
Link your Azure account to New Relic. For more information, refer to Azure integration.

Configure Azure Functions monitoring

You can configure Azure Functions monitoring for different environments and various combinations of runtimes and deployment methods:

In the root directory of your Node.js Azure Function App project, install the New Relic agent as a project dependency by running:
```
npm i newrelic
```
To ensure that the New Relic agent is installed with your project dependencies during the Azure deployment process, set the SCM_DO_BUILD_DURING_DEPLOYMENT to true in your application settings by running:
```
az functionapp config appsettings set --name {NAME_OF_YOUR_AZURE_FUNCTION_APP} --settings SCM_DO_BUILD_DURING_DEPLOYMENT=true
```
Publish your Azure Function App using the Azure CLI or your preferred publishing method. You can use one of the following commands to publish your Azure Function App:
```
func azure functionapp publish {NAME_OF_YOUR_AZURE_FUNCTION_APP}
```
OR
```
az functionapp app up
```
OR
```
az functionapp deploy
```
Importante
The commands shown here are examples and may require additional parameters based on your specific Azure configuration and deployment strategy such as OS, Node.js version, Azure resource group, Azure subscription, Azure storage account, Azure region, and so on. Refer to Azure documentation to know more about these parameters for func azure functionapp publish, az functionapp up, and az functionapp deploy methods.

In the root directory of your Python Azure Function App project, open the requirements.txt file.
Add the following line to your requirements.txt file to install the New Relic agent for Azure Function instrumentation:
bash
```
$newrelic
```
Initialize and register the New Relic agent in your Azure Function code using one of the following methods:
Open the your function_app.py file in your project.
To import the New Relic agent, add the following statement to the top of the file:
import newrelic.agent
Initialize the New Relic agent. For more information, refer to Initialize Python agent.
Register the New Relic agent with your Azure Function. For more information, refer to Register Python agent.
Importante
The New Relic agent uses environment variables to name your application in the New Relic UI. Ensure that either NEW_RELIC_APP_NAME (recommended) or WEBSITE_SITE_NAME (Azure's default site name variable) is available as an environment variable for your Function App.
Your function_app.py file should resemble the following structure:
import newrelic.agent import os import azure.functions as func ... newrelic.agent.initialize() app_name = os.environ.get("NEW_RELIC_APP_NAME", \ os.environ.get("WEBSITE_SITE_NAME", None)) newrelic.agent.register_application(app_name) ... # Code here
In the root directory of your Python Azure Function App project, create a new file named initialization.sh.
Add the following script content to the initialization.sh file:
bash
$#!/bin/bash $ # initialization.sh $ $ ##################################################################### $ # $ # This one-time use script performs the following tasks: $ # 1. Creates a new function_app.py file with New Relic $ # initialization and registration $ # 2. Moves the original function_app.py file into a directory $ # named "original". $ # 3. Adds the "original" directory to the .funcignore file $ # to prevent duplication in published files. $ # $ ##################################################################### $ $ mkdir original $ mv function_app.py ./original/ $ $ echo -e 'import newrelic.agent\nimport os\n\nnewrelic.agent.initialize()\napp_name = os.environ.get("NEW_RELIC_APP_NAME", os.environ.get("WEBSITE_SITE_NAME", None))\nnewrelic.agent.register_application(app_name)\n' | cat - ./original/function_app.py > function_app.py $ $ echo 'original' >> .funcignore
Save the initialization.sh file.
Provide the permissions to script file by running:
bash
$chmod 755 initialization.sh
Run the script from the root directory of your project:
bash
$./initialization.sh
Publish your Azure Function App using the Azure CLI or your preferred publishing method. You can use the following command to publish your Azure Function App:
bash
```
$func azure functionapp publish ${NAME_OF_YOUR_AZURE_FUNCTION_APP}
```

Add the latest version of the NewRelic.Agent NuGet package to your application project.
Use your preferred publishing mechanism to deploy your updated application to Azure.
When you deploy your application, the .NET agent is installed in the /home/site/wwwroot/newrelic folder.

Configure environment variables

After you've published the Azure Function app, configure environment variables:

Navigate to your Azure Function in the Azure portal.
Under Settings, click Environment variables, and then click Advanced edit.
Based on your deployment runtime, paste the following values:

Importante

Ensure that you add a comma at the end of the last existing line and update your license key in the following configurations.

{
  "NODE_OPTIONS": "-r newrelic",
  "NEW_RELIC_LICENSE_KEY": "YOUR-NEW-RELIC-INGEST-LICENSE-KEY",
  "NEW_RELIC_APP_NAME": "NAME-OF-THE-FUNCTION-APP"
}

{
  "NEW_RELIC_LICENSE_KEY": "YOUR-NEW-RELIC-LICENSE-KEY",
  "NEW_RELIC_APP_NAME": "NAME-OF-THE-FUNCTION-APP",
  "PYTHONPATH": "${PYTHONPATH}:/home/site/wwwroot:/home/site/wwwroot/.python_packages/lib/site-packages",
  "FUNCTIONS_WORKER_RUNTIME": "python",
  "PYTHON_ENABLE_WORKER_EXTENSIONS": 1
}

({
  "name": "CORECLR_ENABLE_PROFILING",
  "value": "1",
  "slotSetting": false
},
{
  "name": "CORECLR_NEW_RELIC_HOME",
  "value": "/home/site/wwwroot/newrelic",
  "slotSetting": false
},
{
  "name": "CORECLR_PROFILER",
  "value": "{36032161-FFC0-4B61-B559-F6C5D41BAE5A}",
  "slotSetting": false
},
{
  "name": "CORECLR_PROFILER_PATH",
  "value": "/home/site/wwwroot/newrelic/libNewRelicProfiler.so",
  "slotSetting": false
},
{
  "name": "NEW_RELIC_LOG_DIRECTORY",
  "value": "/home/LogFiles/NewRelic",
  "slotSetting": false
},
{
  "name": "NEW_RELIC_LICENSE_KEY",
  "value": "<your New Relic ingest license key here>",
  "slotSetting": false
})

Restart your Azure Function

After you've added the environment variables, restart your Azure Function to apply the changes.

Find and use data

After you have configured your Azure Function, you can find and use the data in the New Relic UI.

Go to https://one.newrelic.com > APM & Services.
In the search banner, set the search criteria as isAzureFunction = true:
From the displayed list, select your Azure Function to view the data.

Compatibility and requirements

Requirements for your Azure Functions

Windows instrumentation

Learn how to set up your Azure Functions for Windows to monitor them in New Relic.

Container instrumentation

Learn how to set up your Azure Functions for Containers to monitor them in New Relic.

Prerequisites

Configure Azure Functions monitoring

Importante

Option 1: Manually update the function_app.py file

Importante

Option 2: Using New Relic provided one-time script

Configure environment variables

Importante

Restart your Azure Function

Find and use data

Compatibility and requirements

Windows instrumentation

Container instrumentation

Linux instrumentation

Prerequisites .css-21sua1{background:none;border:none;width:0;padding:0;}

Configure Azure Functions monitoring

Importante

Option 2: Using New Relic provided one-time script

Configure environment variables

Importante

Restart your Azure Function

Find and use data

Related articles

Compatibility and requirements

Windows instrumentation

Container instrumentation

Prerequisites