Skip to content
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

[release/8.0] Seq component is broken with latest UseOtlpExporter - Convert Seq component to use OTEL's AddProcessor instead of AddOtlpExporter (#3697) #3728

Merged
merged 2 commits into from
Apr 17, 2024

Conversation

eerhardt
Copy link
Member

@eerhardt eerhardt commented Apr 16, 2024

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.

Unhandled exception. System.NotSupportedException: Signal-specific AddOtlpExporter methods and the cross-cutting UseOtlpExporter method being invoked on the same IServiceCollection is not supported.

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 to AddProcessor.

  • Switch Seq OpenTelemetry configuration from AddOtlpExporter to AddProcessor.

  • 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

…pExporter` (dotnet#3697)

* Switch Seq OpenTelemetry configuration from `AddOtlpExporter` to `AddProcessor`.

* Switch Seq OpenTelemetry configuration from `AddOtlpExporter` to `AddProcessor`.

* 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 dotnet#3546
@dotnet-issue-labeler dotnet-issue-labeler bot added the area-integrations Issues pertaining to Aspire Integrations packages label Apr 16, 2024
@dotnet-policy-service dotnet-policy-service bot added the Servicing-consider Issue for next servicing release review label Apr 16, 2024
@eerhardt eerhardt changed the title [release/8.0] Convert Seq component to use OTEL's AddProcessor instead of AddOtlpExporter (#3697) [release/8.0] Seq component is broken with latest UseOtlpExporter - Convert Seq component to use OTEL's AddProcessor instead of AddOtlpExporter (#3697) Apr 16, 2024
@danmoseley danmoseley added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Apr 16, 2024
@danmoseley danmoseley enabled auto-merge (squash) April 16, 2024 18:35
@eerhardt eerhardt added the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Apr 16, 2024
@eerhardt
Copy link
Member Author

This will also need #3734 before it can be merged.

@eerhardt eerhardt removed the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Apr 16, 2024
@eerhardt
Copy link
Member Author

This will also need #3734 before it can be merged.

I've updated this PR with these changes. It can now be merged once approved.

@RussKie
Copy link
Member

RussKie commented Apr 17, 2024

Need more approvals

@danmoseley
Copy link
Member

danmoseley commented Apr 17, 2024

Someone should sign off who has context on the code area.

@danmoseley danmoseley merged commit 4a52c54 into dotnet:release/8.0 Apr 17, 2024
8 checks passed
@eerhardt eerhardt deleted the Port3697 branch April 17, 2024 13:37
@github-actions github-actions bot locked and limited conversation to collaborators May 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-integrations Issues pertaining to Aspire Integrations packages Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants