feat(azure_functions): add azure functions integration

[duncanpharvey]

This PR adds an integration for tracing the azure-functions package.

Additional Notes:

• This change only supports the v2 programming model. If there are enough requests for the v1 programming model we can add tracing in a future PR
• This change only supports tracing Http triggers. Tracing for other triggers will be added in future PRs
• Azure Functions package currently supports Python versions 3.7 to 3.11 (no 3.12 support at the moment)
• Builds off the integration work started by @gord02 in azure function integration #9726
• Dockerfile changes to testrunner made in ci: update image and standardize to using both hash and sha256 #11617 and ci: add azure and chrome to testrunner image #11609
  • mariadb install was broken in the testrunner image
  • azure-functions-core-tools package must be installed on the test runner for tests to work
    • Version pinned to 4.0.6280 due to some issues with the most recent versions
    • Package only supported on linux/amd64 architecture

Checklist

• PR author has checked that all the criteria below are met
• The PR description includes an overview of the change
• The PR description articulates the motivation for the change
• The change includes tests OR the PR description describes a testing strategy
• The PR description notes risks associated with the change, if any
• Newly-added code is easy to change
• The change follows the library release note guidelines
• The change includes or references documentation updates if necessary
• Backport labels are set (if applicable)

Reviewer Checklist

• Reviewer has checked that all the criteria below are met
• Title is accurate
• All changes are related to the pull request's stated goal
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Newly-added code is easy to change
• Release note makes sense to a user of the library
• If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
• Backport labels are set in a manner that is consistent with the release branch maintenance policy

[github-actions]

CODEOWNERS have been resolved as:

.riot/requirements/1337ee3.txt                                          @DataDog/apm-python
.riot/requirements/14b54db.txt                                          @DataDog/apm-python
.riot/requirements/1e62aea.txt                                          @DataDog/apm-python
.riot/requirements/73109d5.txt                                          @DataDog/apm-python
.riot/requirements/c2420c2.txt                                          @DataDog/apm-python
ddtrace/contrib/azure_functions/__init__.py                             @DataDog/apm-core-python @DataDog/apm-idm-python
ddtrace/contrib/azure_functions/patch.py                                @DataDog/apm-core-python @DataDog/apm-idm-python
ddtrace/contrib/internal/azure_functions/patch.py                       @DataDog/apm-core-python @DataDog/apm-idm-python
releasenotes/notes/feat-add-azure-functions-integration-108911bfe1e5f081.yaml  @DataDog/apm-python
tests/contrib/azure_functions/__init__.py                               @DataDog/apm-core-python @DataDog/apm-idm-python
tests/contrib/azure_functions/azure_function_app/function_app.py        @DataDog/apm-core-python @DataDog/apm-idm-python
tests/contrib/azure_functions/azure_function_app/host.json              @DataDog/apm-core-python @DataDog/apm-idm-python
tests/contrib/azure_functions/azure_function_app/local.settings.json    @DataDog/apm-core-python @DataDog/apm-idm-python
tests/contrib/azure_functions/test_azure_functions_patch.py             @DataDog/apm-core-python @DataDog/apm-idm-python
tests/contrib/azure_functions/test_azure_functions_snapshot.py          @DataDog/apm-core-python @DataDog/apm-idm-python
tests/snapshots/tests.contrib.azure_functions.test_azure_functions_snapshot.test_http_get_error.json  @DataDog/apm-python
tests/snapshots/tests.contrib.azure_functions.test_azure_functions_snapshot.test_http_get_ok.json  @DataDog/apm-python
tests/snapshots/tests.contrib.azure_functions.test_azure_functions_snapshot.test_http_post_ok.json  @DataDog/apm-python
ddtrace/_monkey.py                                                      @DataDog/apm-core-python
ddtrace/_trace/trace_handlers.py                                        @DataDog/apm-sdk-api-python
ddtrace/ext/__init__.py                                                 @DataDog/apm-core-python @DataDog/apm-idm-python
riotfile.py                                                             @DataDog/apm-python
tests/contrib/suitespec.yml                                             @DataDog/apm-core-python @DataDog/apm-idm-python

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-12-18 02:05:36

Comparing candidate commit bf3baa9 in PR branch duncan-harvey/azure-functions-integration with baseline commit de9bc48 in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 378 metrics, 2 unstable metrics.

[emmettbutler]

Looking good! There are a few areas where this change could be more aligned with our common practice in this repo.

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: duncan-harvey/azure-functions-integration
Commit report: 04c98f4
Test service: dd-trace-py

✅ 0 Failed, 697 Passed, 771 Skipped, 5m 11.71s Total duration (28m 17.54s time saved)

[wconti27]

@duncanpharvey Can you please provide instructions for running these tests locally? When I try running with riot -v run -p 3.11 --pass-env ^azure_functions$ -s -- -vv -k test_http_get_ok, I get failures saying 404 page not found?

[duncanpharvey]

@duncanpharvey Can you please provide instructions for running these tests locally? When I try running with riot -v run -p 3.11 --pass-env ^azure_functions$ -s -- -vv -k test_http_get_ok, I get failures saying 404 page not found?

Sure!

• Start test agent: docker compose up -d testagent
• Start testrunner shell (azure-functions-core-tools is only installed on amd64 architecture): DOCKER_DEFAULT_PLATFORM=linux/amd64 scripts/ddtest
• Run test with traces sent to test agent (in testrunner shell): DD_AGENT_PORT=9126 riot -v run -p 3.11 --pass-env ^azure_functions$ -s -- -vv -k test_http_get_ok

Sometimes on the initial run it times out when starting up the Azure Function. If you add a delay to client.wait(), like delay=0.5 it should work. I don't see this issue when the tests run in CI.

dd-trace-py/tests/contrib/azure_functions/test_azure_functions_snapshot.py

Line 35 in 04c98f4

client.wait()

12/13 update: I committed this retry delay so it doesn't trip up someone running these tests locally in the future. It shouldn't affect how long the tests take to run in CI.

[wconti27]

If possible, we should try to detect/infer a user's expected service name for the function