[release/8.0] Seq component is broken with latest UseOtlpExporter - Convert Seq component to use OTEL's AddProcessor
instead of AddOtlpExporter
(#3697)
#3728
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.
Backport of #3697 to release/8.0
cc @liammclennan
Customer Impact
The Seq component no longer works with after the OTLP update to our ServiceDefaults project.
Testing
New automated tests added.
Manual testing that Seq works in the playground app.
Risk
Low. The change only affects the Seq component.
Regression?
Yes
Switch Seq OpenTelemetry configuration from
AddOtlpExporter
toAddProcessor
.Switch Seq OpenTelemetry configuration from
AddOtlpExporter
toAddProcessor
.Move OTLP exporter options onto SeqSettings.cs
Add test
Update README
Renamed Seq settings
Change order of config
Updated code doc
ConfigurationSchema.json
Throw an exception if ServerUrl is unspecified, but HealthChecks is enabled.
Fix tests
PR feedback
Fix #3546
Microsoft Reviewers: Open in CodeFlow