Follow one request through several services — X-Ray and Distributed tracing

Your goal

Store a sample request trace and find its annotated segment.

Why this matters

A trace connects a request’s identity with records of its work. You will store a synthetic segment with your own annotation and retrieve it by trace ID. Its timing is training data, not measured website performance.

Words you will use

A trace follows a request across components. A span or segment describes one part of that work. Instrumentation records timing and context. Sampling selects which requests are traced.

How to proceed

Start a fresh emulator, read each numbered step, and enter the practice settings shown. Run the action, inspect its API receipt, then continue. Finish lab checks the emulator state again before saving your progress.

1. Create a trace group

Create a group that selects the cloudarcade-practice service. A trace follows one request; a segment describes one part of its work. This lab uses synthetic timing data.

2. Send a sample segment

Choose a practice label and save a completed segment with that annotation. The request includes a trace ID, segment ID, and start and end times. These are training values, not measured website latency.

Practice label: This label is saved in the emulator. Use 1–80 characters. Suggested practice value: moonbase.

3. Retrieve this exact trace

Use the returned trace ID to request its stored segments. Check your annotation in the segment document. A real trace may have many segments from several services.

Practice, then check your understanding

Perform the actions yourself and inspect the returned state. Errors keep your settings so you can retry. Starting another lab clears the previous live environment. Earned XP is kept, and signed-in achievements sync to your account. Replay does not award duplicate XP.

Read the official AWS documentation for service behavior and production details.