Consumption monitoring
Knowing what a cloud account consumes as it runs, in credits, capacity units and cost per service and organisational unit, and being warned before a budget is spent. LoggingLoggingSeeing what a running service did, in a form something can read afterwards — levels, a formatter that suits a laptop and one that suits a log service.SAP only and telemetryTelemetrySeeing what a running service did — traces across handlers and database calls, metrics, and correlation that survives an async boundary.SAP and community, core adopted it watch what an application does; this watches what it costs.
Overview
Knowing what a BTP global account consumes as it runs, in credits, capacity units and cost per service, directory and subaccount, and being warned before a budget is spent. LoggingLoggingSeeing what a running service did, in a form something can read afterwards — levels, a formatter that suits a laptop and one that suits a log service.SAP only and telemetryTelemetrySeeing what a running service did — traces across handlers and database calls, metrics, and correlation that survives an async boundary.SAP and community, core adopted it watch what an application does; this watches what it costs.
The cockpit's Costs and Usage page shows monthly usage and cost per service, subaccount and directory, and its Budgets tab can e-mail global account administrators when spending crosses a threshold. The Resource Consumption APIs of the SAP Usage Data Management serviceSAP Usage Data Management Service for SAP BTPREST APIs that return BTP usage per metric for an account, directory or region, monthly or daily, and monthly cost per subaccount under the CPEA consumption-based model.sap official, btp return the usage data to a program.
Not covered: At the cadence of the monthly balance statement. Usage data is updated after the statement is generated, with estimates in between, and figures for directories and subaccounts are estimations meant for internal cost allocation.
The SAP-samples repositories on this concern state that their figures are indicative and no replacement for SAP's billing documents; samples are not a presence.
No community artifact is documented here.
Artifacts
Seen working
Never as the figure a billing decision rests on: the repository states this is not a replacement for the official billing documents, that the information it provides is purely indicative, and that it recommends verifying against the official BTP Cockpit usage reports. It is published as a sample or reference implementation and says it is not intended for production use without review, testing and hardening.
Never as the figure a billing decision rests on: the repository states that the tool is provided as-is, is not covered by SAP Support, is not a replacement of the official billing documents you receive from SAP, and that the information it provides is purely indicative. Its daily delta is also an approximation over a 24-hour period rather than a hard data point for the consumption on that day, because some services report usage only the day after it happened.
Details
Coverage
For your agent
- Ref
capability:consumption-monitoring- JSON
- /capabilities/consumption-monitoring.json
- MCP
- Connecting an agent