Phase 10 — Observability

[aaqib-hafeez-khan-in]

Parent epic: #3

Objective

Make transaction processing, failures, reconciliation, and settlement observable through structured telemetry.

Scope

• Add structured logging.
• Introduce OpenTelemetry tracing and metrics.
• Track transaction processing latency.
• Track transaction success/failure rate.
• Track retry counts and dead-letter depth.
• Track reconciliation mismatch rate.
• Track settlement success/failure.
• Track processing throughput.
• Correlate logs/events with transaction and correlation identifiers.

Acceptance criteria

• Key processing paths emit structured logs.
• Distributed operations can be traced with correlation identifiers.
• Required operational metrics are exposed.
• Telemetry is useful for reproducing and diagnosing failure scenarios.
• Tests or verification cover the telemetry integration without coupling domain logic to a specific backend.

Out of scope

• Production monitoring vendor setup
• Alerting infrastructure

Delivery

Implement as a focused PR linked back to #3.