This website uses cookies to ensure you get the best experience.
Learn more.
A request crosses an API, queue consumer, and database. Which TWO telemetry practices support end-to-end latency attribution? Select TWO.
Published
- Collect only an hourly count of releases
- Propagate trace context across supported service and messaging boundaries
- Generate unrelated identifiers without any correlation
- Instrument operations as spans using supported OpenTelemetry integration
Comments — 0
Sign in to comment