Browse Source

Update docs/en/framework/infrastructure/correlation-id.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
pull/24868/head
Engincan VESKE 2 months ago
committed by GitHub
parent
commit
8ea537cc88
No known key found for this signature in database GPG Key ID: B5690EEEBB952194
  1. 2
      docs/en/framework/infrastructure/correlation-id.md

2
docs/en/framework/infrastructure/correlation-id.md

@ -138,7 +138,7 @@ No manual configuration is required. ABP's `ClientProxyBase` automatically reads
When you publish a [distributed event](../infrastructure/event-bus/distributed/index.md), ABP automatically attaches the current correlation ID to the outgoing event message. When the event is consumed (potentially by a different service), the correlation ID is extracted from the message and set in the consumer's context.
> This works with all supported event bus providers. Including,[RabbitMQ](../infrastructure/event-bus/distributed/rabbitmq.md), [Kafka](../infrastructure/event-bus/distributed/kafka.md), [Azure Service Bus](../infrastructure/event-bus/distributed/azure.md) and [Rebus](../infrastructure/event-bus/distributed/rebus.md).
> This works with all supported event bus providers. Including, [RabbitMQ](../infrastructure/event-bus/distributed/rabbitmq.md), [Kafka](../infrastructure/event-bus/distributed/kafka.md), [Azure Service Bus](../infrastructure/event-bus/distributed/azure.md) and [Rebus](../infrastructure/event-bus/distributed/rebus.md).
```
Service A publishes event (CorrelationId: abc123)

Loading…
Cancel
Save