@cap-js/telemetry enhances CAP observability and automatically publishesruntimeanddatabasemetrics.
B – Memory Usage Metrics
Telemetry captures Node.js process metrics such as:
Heap usage
Resident Set Size (RSS)
Garbage collection metrics
Memory allocations and consumption patterns
These help diagnose memory leaks or heavy load conditions.
C – Database Pool Statistics
Telemetry gathers database-layer metrics such as:
Active/idle database connections
Pool usage and saturation
Connection acquisition time
Query execution statistics
These metrics are critical for diagnosing bottlenecks in SAP HANA Cloud or SQLite adapters.
Why the Others Are Incorrect:
A – Network latency and jitter:
Telemetry does not measure network latency at the protocol layer.
This requires external APM or monitoring tools.
D – CPU allocation / thread management:
CAP telemetry exposes basic CPU metrics only through Node.js process stats but does not provide deep OS-level CPU or thread-management metrics.
[References:, CAP Telemetry Module – Metrics Documentation, CAP Observability & Monitoring Best Practices]
