Finalize experimental connection Activities
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- observability
Research direction
Start by reviewing PR #103922, its linked design comment, semantic-conventions PR #1192, and the referenced documentation discussion. Trace the four experimental connection activities and the span-link visualization concerns. Done requires an agreed design, finalized semantic conventions, instrumentation changes, and coordination with monitoring tool authors.
Written by the indexing model from the issue text.
Description
#103922 introduced experimental connection tracing, adding 4 optional activities to enable tracking HTTP connection setup, DNS lookup, socket connect, and TLS handshake. The feature has been marked experimental because of problems with span link visualization in existing monitoring tools (https://github.com/open-telemetry/opentelemetry-specification/discussions/4130). These problems can be addressed by (1) introducing new OTel semantic conventions to mark the links that can result in a high number of backlings so they can be visualized differently, (2) implementing the new semconv in our instrumentation, and (3) working with monitoring tool authors so they can tune their visualization logic.
During the finalization work we have an opportunity to adjust the design and the implementation meaning that we can revisit the design decisions noted in https://github.com/dotnet/runtime/pull/103922#issuecomment-2214295290, and formalized in https://github.com/open-telemetry/semantic-conventions/pull/1192. For example, we should consider linking failed connection setup spans to the (failed) requests that initiated the connection injection as suggested in https://github.com/dotnet/docs/pull/43872#discussion_r1876823555.
- Dominant language
- C#
- Stars
- 18.3k
- Forks
- 5.6k
- PR merge metrics
- PR metrics pending
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/runtime
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
area-System.Reflection blocking-clean-ci-optional Known Build Error os-mac-os-x untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
area-CodeGen-coreclr untriaged
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
agentic-workflows untriaged
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
area-VM-meta-mono untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
Create parent directories only after the containment check in InstallHelper.TryExtractToDirectory Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSResourceGet#2056 ·