Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Breaking changes in 1.1.0-beta3 with AddLegacySource method
See original GitHub issueWith the 1.1.0-beta3 there are breaking changes with the use of AddLegacySource in the Instrumentation packages.
AddLegacySource method was moved from TracerProviderBuilderExtensions.cs in SDK to API in 1.1.0-beta3.
1.0.0-rc4 version of the instrumentation packages expect AddLegacySource method to be present in the SDK and they fail when used with an SDK version 1.1.0-beta3. Up until 1.1.0-beta2, AddLegacySource method was in the SDK.
We need to release new packages for API + SDK (1.1.0-beta4) and for instrumentation packages (1.0.0-rc5).
Issue Analytics
- State:
- Created 2 years ago
- Reactions:11
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We have released the newer versions of core components (1.1.0-beta4) and instrumentations (1.0.0-rc5). Please update the package versions to fix this issue.
@Mario-Hofstaetter This issue is not about
OpenTelemetry.Exporter.Jaeger. The issue is with Instrumentation libraries such asOpenTelemetry.Instrumentation.HttpandOpenTelemetry.Instrumentation.AspNetCorethat are calling theAddLegacySourcemethod.