Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Diagnostics with ActivitySource #1669

Open
alexeyzimarev opened this issue Dec 18, 2021 · 2 comments
Open

Diagnostics with ActivitySource #1669

alexeyzimarev opened this issue Dec 18, 2021 · 2 comments

Comments

@alexeyzimarev
Copy link
Member

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.

@alexeyzimarev alexeyzimarev added this to the v107.1 milestone Dec 18, 2021
@stale stale bot added the wontfix label Mar 2, 2022
@stale stale bot added the wontfix label Apr 16, 2022
@restsharp restsharp deleted a comment from stale bot Jun 13, 2022
@restsharp restsharp deleted a comment from stale bot Jun 13, 2022
@restsharp restsharp deleted a comment from stale bot Jun 13, 2022
@restsharp restsharp deleted a comment from repo-ranger bot Jun 13, 2022
@restsharp restsharp deleted a comment from repo-ranger bot Jun 13, 2022
@hanhanyao
Copy link

Any update of adding OpenTelemetry integration

@alexeyzimarev
Copy link
Member Author

Not yet; the default HTTP client instrumentation works just fine, except it doesn't measure the overhead (serialisation, etc.).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants