-
|
Do Correlation ID and spans data for OpenTelemetry serve the same purpose? There's mentioning of correlation ID in several pages but I wasn't able to find concrete examples on how to use it or documentation about where does it end up in the various brokers. Maybe we need some more docs for this? If I am using OpenTelemetry on all my application can I just ignore Correlation ID ? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Self-answered. Yes, they serve the same purpose. Correlation ID is a concept from AsyncAPI where ANY field/header can be used to correlate messages in the same operation flow. FastStream uses a header named "correlationID" (hence the confusion), while OpenTelemetry uses spans. It would be great if the correlation ID field were customisable. |
Beta Was this translation helpful? Give feedback.
Self-answered. Yes, they serve the same purpose.
Correlation ID is a concept from AsyncAPI where ANY field/header can be used to correlate messages in the same operation flow.
FastStream uses a header named "correlationID" (hence the confusion), while OpenTelemetry uses spans.
It would be great if the correlation ID field were customisable.