Which metrics are provided out-of-the-box by the @cap-js/telemetry tool? Note: There are 2 correct answers to this question.

Question

Options

• ANetwork latency and jitter
• BMemory usage metrics
• CDatabase pool statistics
• DCPU allocation and thread management

• A
  4% (1)
• B
  93% (26)
• D
  4% (1)

Explanation

@cap-js/telemetry is SAP CAP's OpenTelemetry integration plugin, designed to instrument CAP-native concerns rather than low-level infrastructure. Memory usage metrics (B) are collected automatically as part of Node.js runtime telemetry, giving you heap and process memory visibility without any configuration. Database pool statistics (C) are a natural fit because CAP actively manages database connection pools, making pool size, active connections, and wait times directly observable through the plugin's built-in instrumentation.

Network latency and jitter (A) are transport-layer metrics that belong to network monitoring tools (e.g., a service mesh or APM agent), not an application-level CAP plugin. CPU allocation and thread management (D) are OS/infrastructure concerns typically handled by host-level monitoring (e.g., Prometheus node exporter), outside the scope of what CAP telemetry instruments.

Memory tip: Think "CAP owns what CAP controls" - the plugin measures things the CAP runtime itself manages (memory it runs in, database pools it governs). Anything below the application layer (network, CPU/threads) is handled elsewhere.

No community discussion yet for this question.