This skill provides comprehensive guidance for SAP Cloud Logging service on SAP BTP. Use when setting up Cloud Logging instances, configuring log ingestion from Cloud Foundry or Kyma runtimes, implementing OpenTelemetry observability, analyzing logs/metrics/traces in OpenSearch Dashboards, configuring SAML authentication, managing certificates, or troubleshooting ingestion issues. Covers service plans (dev/standard/large), all 4 instance creation methods (BTP Cockpit, CF CLI, BTP CLI, Service Operator), all 4 ingestion methods (Cloud Foundry, Kyma, OpenTelemetry, JSON API), and security best practices.
SAP Cloud Logging is an instance-based observability service built on OpenSearch that stores, visualizes, and analyzes application logs, metrics, and traces from SAP BTP Cloud Foundry, Kyma, Kubernetes, and other runtime environments.
Key Capabilities:
| Plan | Capacity | Use Case | Auto-Scaling |
|---|---|---|---|
| dev | 7.5 GB fixed | Evaluation only | No |
| standard | 75 GB - 375 GB | Production (100 logs/sec) | Yes |
| large | 750 GB - 3.75 TB | Production (1000 logs/sec) | Yes |
Important: Plan updates are not supported. Migration requires running instances in parallel.
Note for SAP Build Code Users: If using SAP Build Code, follow the SAP Build Code Initial Setup instructions instead. Cloud Logging in SAP Build Code is available for evaluation purposes only.
Choose one method based on your workflow:
Option 1: SAP BTP Cockpit (UI)
cloud-logging service and planOption 2: Cloud Foundry CLI
cf create-service cloud-logging standard my-cls-instance -c '{
"retention_period": 14,
"backend": { "max_data_nodes": 10 },
"ingest": { "max_instances": 10 }
}'
# Wait for provisioning
cf services # Check "last operation" status
# Create service key
cf create-service-key my-cls-instance my-cls-key
cf service-key my-cls-instance my-cls-key
Option 3: SAP BTP CLI
btp create services/instance \
--subaccount <SUBACCOUNT_ID> \
--name my-cls-instance \
--offering-name "cloud-logging" \
--plan-name standard \
--parameters '{"retention_period": 14}'
# Create binding
btp create services/binding \
--subaccount <SUBACCOUNT_ID> \
--name my-cls-binding \
--instance-name my-cls-instance
# Get credentials
btp get services/binding --name my-cls-binding --subaccount <SUBACCOUNT_ID>
Option 4: SAP BTP Service Operator (Kubernetes/Kyma)
apiVersion: services.cloud.sap.com/v1