[next-gen] Add IConfiguration/Options binding and bootstrap for the mini-SDK #4085
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[Note: This PR is targeting the out-of-process-collection branch]
Changes
Details
See dotnet-monitor OTLP Egress
Everything in the mini-SDK is simple POCOs. It doesn't plug into Options like the main SDK does.
This PR is adding another project to the next-gen solution called
OpenTelemetry.AutoInstrumentation.Sdk.Configuration
. What this project does is allow you to bindOpenTelemetryOptions
to some config section (ex:OpenTelemetry
) and then bootstrap the mini-SDK from the options.The idea is dotnet-monitor (or whatever host) can use this library to bind its configuration and set up the SDK components (span processor, logrecord processor, and metricreader) without having to worry about the gritty details.