What it does
AWS X-Ray collects application request traces and presents the relationships between front-end services, AWS resources, databases, microservices, and external APIs in a trace map. Teams instrument incoming requests and outbound calls, then filter and inspect traces to locate latency spikes or failing dependencies. It is a dedicated distributed-tracing service within AWS's wider observability family, not a general-purpose metrics or log console.
Instrument before investigating
The official guide describes automatic, library-based, and manual instrumentation. An application can use AWS's OpenTelemetry distribution to send traces to X-Ray and other backends, or use the language-specific X-Ray SDKs for a more tightly integrated single-vendor workflow. The choice matters for new work: AWS recommends OpenTelemetry for many instrumentation needs, including portability across tracing backends.
Once trace data reaches the service, the trace map shows the client, front-end service, and downstream services involved in a request. An engineer can follow a delayed request through its dependencies and inspect where time or errors accumulated. For example, an illustrative checkout trace might reveal that the application waited on a downstream service rather than spending most of its time in its own handler; this is a scenario, not a test performed for this listing.
AWS documents X-Ray SDK and daemon maintenance mode beginning February 25, 2026, with future releases limited to security fixes and a recommendation to migrate to OpenTelemetry. This is an important setup consideration for new instrumentation. AWS pricing is usage-based and provides a monthly free allowance for recorded and retrieved or scanned traces; usage beyond the allowance is billed according to the relevant AWS region and service rates.
Strengths
- A trace map can show the front-end service and the downstream resources or services involved in requests.
- AWS documents both its X-Ray SDKs and an OpenTelemetry-based instrumentation path.
- The service is designed to help investigate latency spikes and bottlenecks in distributed application requests.
Watch out for
- Applications must be instrumented or integrated with a trace collector before X-Ray has request data to analyze.
- AWS X-Ray SDKs and the daemon entered maintenance mode in 2026; AWS recommends OpenTelemetry for new instrumentation.
Best for
- Following request paths across AWS services, microservices, databases, and external APIs
- Investigating latency or errors in distributed applications that already emit trace data
- Teams standardizing on OpenTelemetry while retaining AWS X-Ray as a trace destination
Sources
- What is AWS X-Ray? - AWS X-Ray (Oct 25, 2026)
- Instrumenting your application for AWS X-Ray - AWS X-Ray (Oct 25, 2026)
- Amazon CloudWatch Pricing | Free Tier Available (Oct 25, 2026)