Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

ALERT: Possible app crash for OpenTelemetry .NET versions 1.3.0 and prior #3629

Closed
CodeBlanch opened this issue Sep 6, 2022 · 0 comments
Closed

Comments

@CodeBlanch
Copy link
Member

CodeBlanch commented Sep 6, 2022

What is the impact?

An application crash can be caused by adding ActivityEvents or ActivityLinks with tags and using one of the exporters provided by the opentelemetry-dotnet project. Adding an ActivityEvent or ActivityLink may be performed by your code or any instrumentation package you reference (e.g., OpenTelemetry.Instrumentation.HttpClient).

First reported by #3593.

Who this will impact?

Applications referencing System.Diagnositcs.DiagnosticSource version 7.0 - either directly or via an indirect dependency - plus version 1.3.0 or prior of the following OpenTelemetry exporters can experience the application crash:

  • OpenTelemetry.Exporter.Jaeger versions 1.3.0 or lower
  • OpenTelemetry.Exporter.OpenTelemetryProtocol versions 1.3.0 or lower
  • OpenTelemetry.Exporter.Zipkin versions 1.3.0 or lower

What action should I take?

Upgrade the affected packages to version 1.3.1 or later.

utpilla added a commit to utpilla/opentelemetry-dotnet that referenced this issue Sep 6, 2022
utpilla added a commit to utpilla/opentelemetry-dotnet that referenced this issue Sep 6, 2022
@alanwest alanwest changed the title ALERT: Upgrade to 1.3.1 or 1.4.* to avoid potential runtime exceptions ALERT: Possible app crash for OpenTelemetry .NET versions 1.3.0 and prior Sep 7, 2022
@CodeBlanch CodeBlanch pinned this issue Sep 8, 2022
@open-telemetry open-telemetry locked and limited conversation to collaborators Sep 20, 2022
@utpilla utpilla converted this issue into discussion #3682 Sep 20, 2022
@cijothomas cijothomas unpinned this issue Mar 14, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

2 participants