Promote poc-sdk-otel branch to main

[pellared]

Why

This issue is created to have a "signup" if the design proposed in poc-sdk-otel branch is how we plan to evolve the project. This would mean that we can use it as the main branch (and abandon the current main branch).

Initial design docs

There would be a separate issue to track what we would consider as ALPHA or even BETA release. We are probably missing good user documentation.

What is included

• SDK-based instrumentations; more
  • HTTP client
  • ASP.NET
  • ASP.NET Core
  • SQL Server client
• profiler-based (IL-rewrite) instrumentations; more
  • MongoDB client
  • GraphQL server
• Plugin support using OTEL_DOTNET_TRACER_INSTRUMENTATION_PLUGINS; more

What scenarios were checked

• Using ActivitySource API. See: here
• Assembly versioning conflicts. See: here and here

What is missing (but probably not blocking)

• building "artifacts" (even zip files that can be extracted and used)
• usage and readme docs update and cleanup
• developing docs update
• more integration tests for existing code

Lots of other stuff but probably the ☝️ is the most important if we would like anyone to use the output.

[pellared]

@RassK Can you confirm that the instrumentation works also for SNK-signed applications and on IIS?

[pjanotti]

Yes, as we discussed in previous meetings it is time. Let's merge the latest upstream pull and then make the switch. We should target this to be done by 10/13.

[zacharycmontoya]

Agreed, let's prioritize this

[nrcventura]

Yes. We should also call out aspnetcore as a separate thing that we also support.

[pjanotti]

This was done. Update your local branch names by using

git branch -m main legacy-main
git fetch origin
git branch -u origin/legacy-main legacy-main
git remote set-head origin -a

git branch -m poc-otel-sdk main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a

If you want to remove old tracking references use:

git remote prune origin

See https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes