skills.rest
Melik1986
Melik1986COMMUNITY
Explore all skills by this author →
WebsiteGitHub

sap-btp-cloud-logging

Configure and operate SAP Cloud Logging instances for BTP observability across Cloud Foundry and Kyma.

Updated May 18, 2026
Search Tags:#observability#opentelemetry#opensearch#kyma#cloud logging#sap btp#log ingestion
One-click install
npx skills add https://github.com/Melik1986/axon-erp-api --skill sap-btp-cloud-logging-melik1986
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sap-btp-cloud-logging
Source: https://github.com/Melik1986/axon-erp-api/tree/main/cursor/skills/sap-btp-cloud-logging
Command: npx skills add https://github.com/Melik1986/axon-erp-api --skill sap-btp-cloud-logging-melik1986

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up and operating SAP Cloud Logging on SAP BTP involves many moving parts: choosing service plans, creating instances through four different methods, wiring up log/metric/trace ingestion from Cloud Foundry, Kyma, OpenTelemetry, or JSON API, managing mTLS certificates, and configuring SAML authentication. This Skill consolidates that operational knowledge into actionable guidance with verified commands, configuration templates, and troubleshooting steps. ## Core Features & Use Cases - Instance Provisioning: Create Cloud Logging instances via BTP Cockpit, CF CLI, BTP CLI, or SAP BTP Service Operator with correct plan selection (dev/standard/large) and configuration parameters. - Ingestion Configuration: Set up all four ingestion paths—Cloud Foundry service binding, Kyma Telemetry module pipelines, OpenTelemetry OTLP (gRPC with mTLS), and JSON API with Fluent Bit or Logstash. - Security & Operations: Configure SAML authentication with SAP Identity Authentication, rotate root CA certificates using the 3-step process, and apply BTP security recommendations (BTP-CLS-0001/0002/0003). - Use Case: A platform engineer needs to ship Kyma application logs and Istio access logs to Cloud Logging. The Skill provides the ServiceInstance/ServiceBinding YAML, LogPipeline configuration referencing the secret, and the correct index patterns (logs-json-kyma*, logs-json-istio-envoy-kyma*) to verify data in OpenSearch Dashboards. ## Quick Start Ask the assistant to create a standard-plan SAP Cloud Logging instance with OTLP ingestion enabled and a 14-day retention period using the CF CLI.

Frequently Asked Questions about sap-btp-cloud-logging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an SAP Cloud Logging instance on SAP BTP?▼

Create a Cloud Logging instance using one of four methods: BTP Cockpit UI, CF CLI (`cf create-service cloud-logging standard`), BTP CLI (`btp create services/instance`), or SAP BTP Service Operator with a ServiceInstance YAML. Then create a service key or binding to obtain ingestion credentials.

How to send logs from Kyma to SAP Cloud Logging?▼

Enable the telemetry and btp-operator modules in Kyma, then deploy a ServiceInstance and ServiceBinding in the sap-cloud-logging-integration namespace. Configure a LogPipeline referencing the generated secret's ingest endpoint and mTLS certificates to ship logs.

Does SAP Cloud Logging support OpenTelemetry ingestion?▼

Yes, enable OTLP ingestion by setting `ingest_otlp.enabled: true` in the instance configuration. Only the gRPC protocol is supported; use the OpenTelemetry Collector to convert http/protobuf or http/json. Bindings then include the OTLP endpoint, client certificate, key, and server CA.

What is the difference between Cloud Logging dev, standard, and large plans?▼

The dev plan offers fixed 7.5 GB storage for evaluation only, without auto-scaling or replication. Standard scales from 75 GB to 375 GB for production workloads, while large scales from 750 GB to 3.75 TB for high-volume enterprise use. Plan updates are not supported, so migration requires parallel instances.

Why are my logs not appearing in OpenSearch Dashboards?▼

Missing logs usually stem from expired binding certificates, OTLP not being enabled on the instance, or querying the wrong index pattern. Verify credentials are current, check the correct pattern such as `logs-cfsyslog-*` or `logs-json-*`, and allow one to two minutes for indexing.

How do I rotate Cloud Logging certificates without breaking ingestion?▼

Follow the 3-step root CA rotation: update the instance with `rotate_root_ca: true` to create a new CA, rebind all applications to get new credentials, then set `rotate_root_ca: false` to delete the old CA. Skipping steps causes ingestion interruption.

Related Skills

Explore More Software Engineering Skills→
SAP-samplesSAP-samples
29

btp-cli

Generate SAP BTP CLI commands for accounts, services, and environments.

Official
Advanced
altrupetsaltrupets

Alerting & Incident Management

Automate alerting and incident management setup with Prometheus, Alertmanager, and PagerDuty.

Official
Advanced
dherbe-digitaldherbe-digital

sap-btp-cloud-logging

Deploy and configure SAP Cloud Logging on SAP BTP across Cloud Foundry, Kyma, and Kubernetes.

Community
Advanced
stacklokstacklok
2.1k

deploy-otel

Deploys an OpenTelemetry observability stack with Prometheus, Grafana, and Tempo to a Kind cluster.

Official
Intermediate