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.
Update OpenTelemetry to v1 (1.0.1)
See original GitHub issueIs your feature request related to a problem? Please describe.
When trying to call AddQuartzInstrumentation and use OpenTelemetry 1.0.1 then II hit this error:
Reference to type 'TracerProviderBuilder' claims it is defined in 'OpenTelemetry', but it could not be found
Describe the solution you’d like
Update the OpenTelemetry dependencies to the non-beta release of 1.0.1. I believe the extensions were renamed from TraceBuilderExtensions to TracerProviderBuilderExtensions.
Describe alternatives you’ve considered
Tried calling extension method directly with OpenTelemetry.Trace.TraceBuilderExtensions, still no 🎲
Additional context Reach v1 release blog: https://devblogs.microsoft.com/dotnet/opentelemetry-net-reaches-v1-0/
Issue Analytics
- State:
- Created 2 years ago
- Reactions:5
- Comments:15 (9 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
Hello,
An update. I have completed the port over to open-telemetry/opentelemetry-dotnet-contrib. Here is the pull request.
@lahma would you like me to create a pull request for quartznet to remove the OpenTelemetry implementation here?
Hi @lahma, I have taken a first glance at taking the existing solution and porting to the open-telemetry-contrib solution. I do not want to overstep but would you be interested in getting some assistance in moving this over?