Free C_KYMD_01 SAP Updates

Observability tools are used to monitor system behaviour and performance, as well as to troubleshoot issues and identify root causes. Observability tools in SAP BTP, Kyma runtime include Grafana, Prometheus, Loki, and Jaeger, which provide dashboards, metrics, logs, and traces for the workloads running in the cluster1. Distributed tracing is a technique to track the flow of requests across microservices and visualize the latency, errors, and dependencies of each service2. Observability tools help developers and operators to ensure the reliability, availability, and security of their applications and services. 

Kyma Eventing simplifies the process of publishing and subscribing to events in the cluster. Publishing events means sending information about a change in the state of the application or the system to the Eventing backend. Subscribing to events means registering interest for a specific event type from a specific source. Kyma Eventing allows users to publish events by sending HTTP requests to the Event Publisher Proxy component, which validates and forwards the events to the NATS backend. Kyma Eventing also allows users to subscribe to events by creating Subscription custom resources that specify the event source, type, and the HTTP endpoint of the service that will receive the events. Kyma Eventing handles the delivery of the events from the NATS backend to the subscribers with the help of the Eventing Controller and the Eventing Dispatcher components. References: 

 A service mesh in Kyma typically consists of two components: the data plane and the control plane12. The data plane is responsible for handling the communication between the microservices in the cluster. It consists of a set of sidecar proxies (Envoy) that are injected into each pod and intercept the traffic. The control plane is responsible for managing the configuration and policies of the data plane. It consists of a set of components (Istio) that provide features like service discovery, security, traffic management, observability, and more12. References: Discovering the Service Mesh, SAP BTP – KYMA – SERVICE MESH | SAP Blogs

 The service mesh solution in SAP BTP, Kyma runtime is based on Istio, which is one of the most popular service mesh solutions. Istio uses the Sidecar proxy pattern, which means that a proxy is deployed as a sidecar container next to each service. This way, the proxy can intercept and manage the traffic between the services, without requiring any changes in the application code. The proxy also communicates with the Istio control plane, whichprovides configuration and policies for the service mesh. The other options are not valid proxy patterns for the service mesh solution in SAP BTP, Kyma runtime. References: Discovering the Service Mesh - SAP Learning, Istio Documentation - What is Istio?