Debugging
Seeing what the framework did between a request arriving and a query being issued — which handlers ran, how the query was rewritten, why a value ended up as it did.
Overview
@cap-js/console Connects a running CAP application to the CAP console.
@cap-js/data-inspector Inspects database entities and their contents at the CAP service level.
@sap/cds-dk The command line client and development toolkit for CAP projects, with the commands cds build, cds deploy, cds watch and cds add among them.
com.sap.cds:cds-feature-console A CAP Java plugin that connects a running application to CAP console, which consumes its remote monitoring data; CAP console itself is installed separately and still being developed.
com.sap.cds:cds-feature-dev-dashboard A browser dashboard for a running CAP Java service that shows and manages its messaging, resilience and multitenancy state while developing, open to users with the cds.Developer role.
Not covered: It stops at inspecting data. Seeing which handlers ran, how a query was rewritten and why a value came out as it did still means reading framework source.
Community tools reach the questions the core leaves open: sap-cap-debuggersap-cap-debuggerAttaches a debugger to a CAP application already running on Cloud Foundry — enables the Node inspector inside the container, assigns a port and hands you a Chrome DevTools or VS Code attach.independent, cap attaches a Node debugger to a CAP application already running on Cloud Foundry, and @saptools/service-flow@saptools/service-flowTraces one CAP operation end to end across several repositories without running anything — handlers, helper packages, local database access, remote OData calls, external HTTP and async channels.independent, cap traces one CAP operation through handlers, database access and remote calls without running anything.
Artifacts
Content
Details
Coverage
For your agent
- Ref
capability:debugging- JSON
- /capabilities/debugging.json
- MCP
- Connecting an agent