13.1 Distributed Tracing¶
Sprint: Sprint 13 - Observability and Resilience
Feature ID: 13.1
Subtasks: 13.1.1, 13.1.2
Objective¶
Deliver "Distributed Tracing" within Sprint 13 - Observability and Resilience.
Dependencies¶
Aggregated from the subtasks below (prerequisite task IDs and enablers):
- Sprints 04-12
- 3.2.6
- 13.1.1
- 4.3.4
Subtasks¶
13.1.1 OTel trace export wiring per service¶
- ID: 13.1.1
- Title: Wire OpenTelemetry trace export to the collector/Tempo in all services
- Description: Confirm every service uses starter-observability with Micrometer Tracing exporting OTLP to the collector (Tempo backend), including Kafka producer/consumer span propagation so traces span the saga across services (NFR-07, roadmap BL-03).
- Business Purpose: A single trace follows a request and its events across all services (NFR-07).
- Inputs: ADR-012, PLATFORM-SPEC Section 9.6, roadmap BL-03.
- Outputs: Verified OTLP export config + Kafka span propagation.
- Acceptance Criteria:
- An onboarding request produces one connected trace in Tempo spanning gateway, order, payment, and subscription, including Kafka spans.
- Dependencies: Sprints 04-12, 3.2.6
- Complexity: M
13.1.2 traceId/correlationId propagation verification¶
- ID: 13.1.2
- Title: Verify traceId/correlationId on every request and log line
- Description: Confirm the gateway injects correlationId, starter-observability propagates trace/ correlation into MDC, and both appear in every service log and trace (NFR-13).
- Business Purpose: 100% request traceability (NFR-13).
- Inputs: NFR-13.
- Outputs: Verification tests/checks.
- Acceptance Criteria:
- Sampled logs across all services contain
traceIdandcorrelationId; the gateway-issued correlationId matches the value seen downstream and in the trace. - Dependencies: 13.1.1, 4.3.4
- Complexity: S
Acceptance Criteria¶
Each subtask above carries its own objective, testable acceptance criteria. This feature is complete when every subtask's acceptance criteria are met.
Deliverables¶
- Verified OTLP export config + Kafka span propagation.
- Verification tests/checks.
Definition of Done¶
- All subtasks (13.1.1, 13.1.2) completed and their acceptance criteria verified.
- All listed dependencies satisfied.
- Build and tests green per the global conventions in ../README.md (Section 3).