Environment variables are a way to store configuration and secrets outside of your code. The following tables display the mandatory variables and runtime specific variables that you can set to monitor your Azure functions with New Relic.
Mandatory environment variables
Regardless of your runtime, you must set the following environment variables to monitor your Azure functions with New Relic:
Variable Name | Description |
---|---|
| Specifies your New Relic account ID |
| Specifies your New Relic ingest key, overriding Secrets Manager |
Additional environment variables
Based on your runtime, you can set the following environment variables to further configure the New Relic Azure Functions monitoring:
Environment variable | Default value | Options | Description |
---|---|---|---|
|
| Required: Inject the agent before your Azure application functions are invoked. | |
| Set the application name, though it is not used in the New Relic UI |
You can find more environment variables in our Node.js configuration documentation.
Environment variable | Default value | Options | Description |
---|---|---|---|
| Set the application name, though it is not used in the New Relic UI | ||
|
| Set the value to | |
|
| Enable the python worker extension. | |
|
| Add the installation path of modules installed using | |
|
|
| Enable serverless mode by setting this to |
|
|
| Generate traces by enabling Distributed Tracing |
You can find more environment variables in our Python configuration documentation.
Environment variable | Default value | Options | Description |
---|---|---|---|
|
|
| Azure Function mode is enabled by default. You can disable Azure Function instrumentation by setting the value to |
You can find more environment variables in our .NET configuration documentation.