azure function integration

[gord02]

What does this PR do?

Creates an integration for the Azure.Functions package to enhance auto-instrumentation.

Checklist

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

Reviewer Checklist

• [ ] 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

---

Python integration examples Python integration docs Running tests for python tracer, including integration tests

Testing Strategy

Try functional testing(run an app with the build of the tracer with integration code) to see when things get executed and if the current wrapping point even makes sense(this hasn't been confirmed).

[pr-commenter[bot]]

Benchmarks

Benchmark execution time: 2024-07-12 20:46:31

Comparing candidate commit 42e81ec2a411586ba78595cf265d0f08b3d8c672 in PR branch gordon.hamilton/azure-function-integration with baseline commit 2ea8da98f8d764e175957f6002e96b35772abdc0 in branch main.

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

[github-actions[bot]]

This pull request has been automatically closed after a period of inactivity. After this much time, it will likely be easier to open a new pull request with the same changes than to update this one from the base branch. Please comment or reopen if you think this pull request was closed in error.