[IAD-94] [CAR-16] Enhance Observability to support end to end latency bottle neck root cause analysis

[mojaloopci]

Migrated from Jira: IAD-94

Original Issue Details:

• Issue Type: Epic
• Priority: Medium
• Status: In Progress
• Reporter: paul.baker
• Assignee: Unassigned
• Created: 24/11/2025

---

Business Value
DRPP is having capacity enough for FUT phase but it is mandatroy to have observability to support deep analyze the overall transaction flow to find the bottle necks preventing to improve the throughput.

Technical Value
Provide observability to support root cause analysis of latency bottlenecks identified in the performance runs. Objective is to get End to end tracing for some of the requests during a performance test run.
Acceptance Criteria / Scope
A. Fill the Gaps in the tracing

1. Enable Traces in the Payment Manager (3)
2. Add traces to fill other gaps identified (3)
3. Kafka Opentelemetry Support (3)
4. Configure for Asynchronous Opentelemetry (risk to exceed more memory than catered for)
   B. Improve Metrics by reviewing what is available, and then creating an appropriate metric & dashboard for each component: (10)
5. Enhance metrics in SDK so that we can better understand where the time in the SDK is being taken
6. Ehnace metrics in the K6 script (removal of timedout transfers from metric)
7. Enhance metrics in the hub
   C. Enhance performance test script to include interscheme discovery (10)
   REF: SERDESK-862