This website uses cookies to ensure you get the best experience.
Learn more.
A service needs end-to-end tracing across an API, asynchronous queue processing, and downstream calls. Which design is appropriate?
Published
- Use one request timestamp as proof that every downstream call belongs to it.
- Propagate supported trace context and instrument the participating components using appropriate tracing integrations.
- Disable queue correlation because asynchronous work cannot be observed.
- Enable only CPU metrics and assume they contain complete causal request traces.
Comments — 0
Sign in to comment