feat(outbox): carry the drop's trace identity and re-join Outbox.Proc… - #98
Conversation
Reviewer's GuideCarries the originating publish span’s W3C trace identity and outbox row ID through persistence, then re-joins Outbox.Process spans to that trace with a worker-loop link while preserving legacy behavior for existing or untraced rows; comprehensive activity-based tests cover both paths. Sequence diagram for outbox trace continuitysequenceDiagram
participant EventBus
participant EfCoreOutboxStore
participant OutboxRow
participant OutboxProcessor
participant ActivitySource
EventBus->>EfCoreOutboxStore: StoreAsync(envelope, cancellationToken)
EfCoreOutboxStore->>OutboxRow: Persist TraceParent and TraceState
EfCoreOutboxStore->>EventBus: SetTag(outbox.message_id)
OutboxProcessor->>OutboxRow: Read TraceParent and TraceState
OutboxProcessor->>ActivitySource: StartActivity(Outbox.Process, parentContext, links)
ActivitySource-->>OutboxProcessor: Outbox.Process activity
OutboxProcessor->>EventBus: Publish stored event
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Duplication | 4 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
|



…ess to it
Summary by Sourcery
Carry event trace identity through the outbox so processed messages remain connected to their originating traces.
New Features:
Enhancements:
Tests: