-
Notifications
You must be signed in to change notification settings - Fork 812
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
Create spans for HTTP retries and redirects #3072
Create spans for HTTP retries and redirects #3072
Conversation
…tivitySourceTests.netfx.cs Co-authored-by: Michael Maxwell <mike.ian.maxwell@gmail.com>
…xtPropagation.cs Co-authored-by: Michael Maxwell <mike.ian.maxwell@gmail.com>
@@ -14,6 +14,10 @@ | |||
occurs. | |||
([#3407](https://github.com/open-telemetry/opentelemetry-dotnet/issues/3407)) | |||
|
|||
* Create spans for HTTP retries and redirects according to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you describe the change here itself for users benefit?
Having to read spec and PR to understand what changed is too complicated for end users.
@@ -14,6 +14,10 @@ | |||
occurs. | |||
([#3407](https://github.com/open-telemetry/opentelemetry-dotnet/issues/3407)) | |||
|
|||
* Create spans for HTTP retries and redirects according to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you describe the change here itself for users benefit?
Having to read spec and PR to understand what changed is too complicated for end users.
@@ -14,6 +14,10 @@ | |||
occurs. | |||
([#3407](https://github.com/open-telemetry/opentelemetry-dotnet/issues/3407)) | |||
|
|||
* Create spans for HTTP retries and redirects according to | |||
[opentelemetry-specification #2078](https://github.com/open-telemetry/opentelemetry-specification/pull/2078). | |||
([#3072](https://github.com/open-telemetry/opentelemetry-dotnet/pull/3072)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also be specific that this is only done to the HttpClient .NET Core one, and .NET Framework.
This PR was marked stale due to lack of activity and will be closed in 7 days. Commenting or Pushing will instruct the bot to automatically remove the label. This bot runs once per day. |
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
@cijothomas - Please reopen and merge this PR. I can address the comments in a separate PR. Thanks! |
Looks like we have merge conflicts. @denisivan0v - I will create a separate PR using this one and tag you there. |
This PR was marked stale due to lack of activity and will be closed in 7 days. Commenting or Pushing will instruct the bot to automatically remove the label. This bot runs once per day. |
We're very much looking to this being merged to finally resolve microsoft/ApplicationInsights-dotnet#2556 |
This will not fix anything in ApplicationInsights, unless you are using OpenTelemetry based application insights. @vishweshbankwar this PR can be now closed as this functionality is already merged now? |
Yes - This can be closed now. |
Closing as this is covered by alternative PR. Thanks @denisivan0v and @vishweshbankwar |
@cijothomas, can you please provide a link to alternative PR / or clarify if this issue is fixed or not? |
@prateekprshr-nith This was addressed in #3732 |
Thanks @cijothomas, I see that this was released in https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.4.0-beta.2. Is this available in a stable release as well? |
Not yet, the latest release is 1.4.0-rc.1 for core components/1.0.0-rc9.10 for non-core. |
@Kielek Is this SDK released and available to consume ? |
There is some delay: |
Summary
This PR brings an implementation for HTTP retries and redirects instrumentation defined in opentelemetry-specification #2078.
This is the second attempt to add the implementation (#2756 was the first one) with the reduced scope to reflect the current state of HTTP semantic conventions specification.
It addresses a scenario which is in the scope for bringing the existing HTTP semantic conventions for tracing to an initial stable state, see related otep #174.
Changes
traceparent
header is already present.traceparent
header will be overwritten based on current ambient context (Activity.Current
) values.