ServiceServiceA BTP service you subscribe to and bind, rather than install. It has plans and regions, not versions, and may deliver a product that lives outside the atlas.See every one →What this type is →by SAPby SAPPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →
SAP Application Logging service for SAP BTP
Collects an application's log lines from Cloud Foundry or Kyma into a searchable Kibana, for the retention the plan sets.
What it declares
Every artifact
- Type
- Service
- Origin
- By SAP
As a service
- Plans
- 3
- Regions
- 46
- Support component
- BC-CP-CF-APPLOGBC-CP-LCM-ANS
Connections
Group by
NodeRelationBasis
Functional
LoggingLoggingSeeing what a running service did, in a readable formSAP only
provides
authored
provides Logging
Seeing what a running service did, in a readable form
Technical
slp-supplier-validationslp-supplier-validationCAP reference app validating Ariba supplier registration datasap official, cap
needed by
derived
needed by slp-supplier-validation
the logging service listed among the application's pre-requisite BTP services.
“SAP Application Logging Service for SAP BTP”
CAP reference app validating Ariba supplier registration data
calmcpcalmcpMCP server with read tools over the SAP Cloud ALM APIsindependent, btp
optionally used by
derived
optionally used by calmcp
deployed with the MTA descriptor or `cf push`, which create and bind `calmcp-logs`
the application logs instance the deploy binds to the running server
“This creates and binds `calmcp-xsuaa` (XSUAA), `calmcp-destination` (Destination) and `calmcp-logs` (Application Logs), and runs the HTTP transport with a `/health` check.”
MCP server with read tools over the SAP Cloud ALM APIs
LISALISAMCP server for reading and writing ABAP object translationsindependent, abap
optionally used by
derived
optionally used by LISA
the lisa-logs resource is reactivated in an mtaext override; it is inactive by default
When reactivated, the lisa-logs resource binds the deployed application to the BTP logging service.
“lisa-connectivity and lisa-logs are declared `active: false` below, so these two `requires` are IGNORED by the deploy service by default (an inactive resource silently drops every `requires` that points at it).”
MCP server for reading and writing ABAP object translations
liteinventorymanagementliteinventorymanagementCAP reference app for lightweight local inventory managementsap official, cap
used by
derived
used by liteinventorymanagement
the logging service listed among the application's pre-requisite BTP services.
“SAP Application Logging Service for SAP BTP”
CAP reference app for lightweight local inventory management
tailspendmanagementtailspendmanagementCAP reference application for tail spend managementsap official, cap
used by
derived
used by tailspendmanagement
the logging service listed among the application's pre-requisite BTP services.
“SAP Application Logging Service for SAP BTP”
CAP reference application for tail spend management
Download
Learn more
Readings
- From Application Logging to Cloud Logging: Service Innovation GuideFrom Application Logging to Cloud Logging: Service Innovation GuideSAP Cloud Logging replaces SAP Application Logging service, moving each customer from a shared multitenant stack to a dedicated, fully isolated one, and this guide sets out what changes with the move: a deployment per compliance region instead of per Cloud Foundry landscape, SAML/IDP-based authentication instead of Cloud Foundry-bound auth, retention that is configurable instead of fixed at seven days, and hourly capacity-unit pricing instead of fixed-size monthly plans. It also states the deprecation timeline for logging on BTP: SAP Application Logging closes to new or renewed CPEA contracts after 2025-07-31, while contracts signed before that date keep their entitlement until their next renewal.Hariharan-Gandhi, published 2024-11-22Hariharan-Gandhi, SAP Community
What’s New
from SAP Help Portal, readhelp.sap.com/whats-new, Application Logging ServiceSAP’s wordsOn SAP Help Portal
15 entries from to , counted per month.
REST APIs
Use of Comments for Documentation Feedback
OpenSearch is upgraded to version 2.11.1
New SAP Cloud Logging service
New security recommendations
Log Channels REST API
ALS Custom Metrics as Logs
ALS supports X-Forwarded-Host and X-Custom-Host
Updated Elastic Stack
Gorouter headers are parsed in ALS
Header fields logged by Gorouter are searchable
Vega visualization can now contain links
Custom metrics API endpoint has been removed
Logs REST API
Logs REST API
Others providing
Compare all 4 on the Logging page →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
- SAP Cloud LoggingSAP Cloud LoggingAn instance-based observability service built on OpenSearch that stores and analyses logs, metrics and traces from Cloud Foundry, Kyma, Kubernetes and other runtime environments.sap official, btpOpenSearch-based store for logs, metrics and traces
- @saptools/cf-logs@saptools/cf-logsA command line and typed Node.js library that fetches and streams the logs of one Cloud Foundry app and parses them into structured rows.independent, btpLog fetcher and parser for one Cloud Foundry app
- @saptools/cf-tail@saptools/cf-tailA command line that tails every started app in a Cloud Foundry space at once and merges their logs into one timeline by timestamp, with filters by level, tenant, router status and time window.independent, btpMerged log tail of every started app in a Cloud Foundry space
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
discovered viaSAP-samples/btp-service-metadata · btp-service-metadata
first seen in the atlas
ecosystem and domainbtp, operations-and-runtime
History in the atlas
- First seen.
For your agent
- Ref
artifact:btp-application-logging- JSON
- /artifacts/btp-application-logging.json
- MCP
- Connecting an agent