restsharp / restsharp/RestSharp
Diagnostics with ActivitySource
Open
Nobody has claimed this yet.
diagnostics
keep
- Dominant language
- C#
- Stars
- 9.8k
- Forks
- 2.3k
- PR merge metrics
- No merged PRs in 30d
Description
Use the ActivitySource API to enable distributed tracing.
It's not a strict requirement as HttpClient is already instrumented, but it would be nice to see how much time it takes to make a call, and what time RestSharp takes for pre- and post-processing.
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.
Research direction
No file or test is named. Start by locating RestSharp's request lifecycle and reviewing how HttpClient is already instrumented, then determine where ActivitySource spans would cover the call and RestSharp's pre- and post-processing. Done means distributed tracing exposes those timings without relying only on HttpClient instrumentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100