Kyma's Telemetry component supports shipping observability signals to SAP Cloud Logging instances. You can configure different observability signal types independently of each other.
Ensure that you consider the SAP BTP Security Recommendation BTP-CLS-0003.
-
An SAP BTP Kyma runtime instance
-
Kubernetes CLI (kubectl) v1.23 or higher (see the kubectl tutorial).
-
SAP Cloud Logging instance with Ingest via OpenTelemetry API Endpoint enabled to ingest distributed traces. We recommend you create it with the SAP BTP Service Operator (see Create an SAP Cloud Logging Instance through SAP BTP Service Operator), because it takes care of creation and rotation of the required Secret.
To integrate Cloud Logging on SAP BTP Kyma Runtime, please follow Kyma documentation on how to ship from Kyma to SAP Cloud Logging.
You can analyze the ingested data in OpenSearch Dashboards (see Access and Analyze Observability Data) based on the following index patterns:
logs-json-istio-envoy-kyma* for istio access logslogs-json-kyma*for application logs- OpenTelemetry related indices