AWS X-Ray
X-Ray
You need to trace request paths across instrumented services to understand latency and failures.
Reach for it when
- Connecting trace segments to investigate a slow downstream dependency.
- Examining sampled request traces alongside logs and metrics.
Do not reach for it when
- Assuming traces are complete without instrumentation or sampling review.
- Using traces as a replacement for audit logs of administrative API activity.
Alternatives, and how to choose
| Service | Pick it instead when |
|---|---|
| CloudWatch | Combine traces with operational logs and metrics. |
| OpenTelemetry tooling | Use compatible instrumentation and evaluate the current collection and export path. |
How you pay
- The model
- Trace recording, retrieval and related observability features can contribute to cost.
- The line item that surprises people
- Sampling and retention choices change both visibility and expense.
What trips people up
- Instrumentation and trace context propagation determine which relationships appear.
- Check current AWS guidance before choosing a new SDK; compatible OpenTelemetry instrumentation is relevant to modern tracing workflows.
Verify the live service
This page is a concept reference. Cost models are qualitative; confirm the current offering, Region and pricing before deploying.