[SVLS-8031] Clarify .NET Azure Function Hosting Plan Support #33098
Conversation
duncanpharvey
changed the title
Preview links (active after the
|
duncanpharvey
changed the title
|
|
||
| In addition, the extension supports Azure Functions for .NET on Basic, Standard, and Premium plans. The extension does not support Flex Consumption or Consumption plans for any runtime. Azure Function support for .NET on Flex Consumption and Consumption plans, Java on all hosting plans, and Node on all hosting plans is available using the <a href="/serverless/azure_functions">Serverless Compatibility Layer</a>. | ||
| For all other Azure Functions configurations, you must use the <a href="/serverless/azure_functions">Serverless Compatibility Layer</a>: | ||
| - Azure Functions on Flex Consumption or Consumption plans (for any runtime). |
There was a problem hiding this comment.
Azure Functions on Flex Consumption or Consumption plans (for any runtime).
Azure Functions for Java (on any hosting plan).
Azure Functions for Node (on any hosting plan).
It might make it confusing to list out what runtimes/hosting plans Azure Functions support in such detail on this page? I think this could be taken out and you could just have
For all other Azure Functions configurations, you must use the Serverless Compatibility Layer.
since it should make sense already that any configuration other than .NET runtime on the plans you specified is recommended for Azure Functions (and it's reiterated on the Azure Functions page). This would also shorten the alert section per @nhulston's comment. But just a thought - I can also see how this can be helpful with clarifying things
There was a problem hiding this comment.
Agreed! The reduced amount of text addresses both your and @nhulston's comments
| This page explains how to collect traces, trace metrics, runtime metrics, and custom metrics from your Azure Functions. To collect additional metrics, install the [Datadog Azure integration][5]. | ||
|
|
||
| The recommended installation method depends on your Azure Function’s configuration: | ||
| - For .NET Windows Azure Functions running on Dedicated/App Service or Premium plans: use the [Datadog .NET APM Extension][9]. |
What does this PR do? What is the motivation?
Directs customers to use the appropriate Datadog instrumentation depending on the hosting plan of their Azure Function.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes