From 7537d673e2f15d5d28c2753f3c7f2fddc6a1dac6 Mon Sep 17 00:00:00 2001
From: Nina Hingerl <n.hingerl@sap.com>
Date: Tue, 5 Dec 2023 14:40:28 +0100
Subject: [PATCH 1/4] docs: Remove 3 telemetry examples

---
 jaeger/README.md              | 181 ------------------------
 jaeger/values.yaml            |  19 ---
 loki/README.md                | 232 ------------------------------
 loki/apirule.yaml             |  17 ---
 loki/dashboard-configmap.yaml |  18 ---
 loki/grafana-values.yaml      |   9 --
 loki/loki-values.yaml         |  38 -----
 loki/promtail-values.yaml     |   8 --
 trace-demo/README.md          | 176 -----------------------
 trace-demo/values.yaml        | 259 ----------------------------------
 10 files changed, 957 deletions(-)
 delete mode 100644 jaeger/README.md
 delete mode 100644 jaeger/values.yaml
 delete mode 100644 loki/README.md
 delete mode 100644 loki/apirule.yaml
 delete mode 100644 loki/dashboard-configmap.yaml
 delete mode 100644 loki/grafana-values.yaml
 delete mode 100644 loki/loki-values.yaml
 delete mode 100644 loki/promtail-values.yaml
 delete mode 100644 trace-demo/README.md
 delete mode 100644 trace-demo/values.yaml

diff --git a/jaeger/README.md b/jaeger/README.md
deleted file mode 100644
index 237db94e..00000000
--- a/jaeger/README.md
+++ /dev/null
@@ -1,181 +0,0 @@
-# Install custom Jaeger in Kyma
-
-## Overview
-
-The following instructions outline how to use [`Jaeger`](https://github.com/jaegertracing/helm-charts/tree/main/charts/jaeger) as a tracing backend with Kyma's [TracePipeline](https://kyma-project.io/#/telemetry-manager/user/03-traces).
-
-## Prerequisites
-
-- Kyma version 2.10 or higher as the target deployment environment
-- The [Telemetry module](https://kyma-project.io/#/telemetry-manager/user/README) is [installed](https://kyma-project.io/#/02-get-started/08-install-uninstall-upgrade-kyma-module?id=install-uninstall-and-upgrade-kyma-with-a-module)
-- kubectl version 1.22.x or higher
-- Helm 3.x
-
-## Installation
-
-### Preparation
-
-1. Export your Namespace as a variable. Replace the `{namespace}` placeholder in the following command and run it:
-
-    ```bash
-    export K8S_NAMESPACE="{namespace}"
-    ```
-
-1. Export the Helm release name that you want to use. The release name must be unique for the chosen Namespace. Be aware that all resources in the cluster will be prefixed with that name. Run the following command:
-    ```bash
-    export HELM_JAEGER_RELEASE="jaeger"
-    ```
-
-1. Update your Helm installation with the required Helm repository:
-
-    ```bash
-    helm repo add jaegertracing https://jaegertracing.github.io/helm-charts
-    helm repo update
-    ```
-
-### Install Jaeger
-
-> **NOTE:** It is officially recommended to install Jaeger with the [Jaeger operator](https://github.com/jaegertracing/helm-charts/tree/main/charts/jaeger-operator). Because the operator requires a cert-manager to be installed, the following instructions use a plain Jaeger installation. However, the described installation is not meant to be used for production setups.
-
-Run the Helm upgrade command, which installs the chart if not present yet.
-```bash
-helm upgrade --install --create-namespace -n $K8S_NAMESPACE $HELM_JAEGER_RELEASE jaegertracing/jaeger -f https://raw.githubusercontent.com/kyma-project/examples/main/jaeger/values.yaml
-```
-
-You can either use the [`values.yaml`](./values.yaml) provided in this `jaeger` folder, which contains customized settings deviating from the default settings, or create your own `values.yaml` file.
-
-### Verify the installation
-
-Check if the `jaeger` Pod was successfully created in the Namespace and is in the `Running` state:
-```bash
-kubectl -n $K8S_NAMESPACE rollout status deploy $HELM_JAEGER_RELEASE
-```
-
-### Activate a TracePipeline
-
-To configure the Kyma trace collector with the deployed Jaeger instance as the backend. To create a new [TracePipeline](https://kyma-project.io/#/telemetry-manager/user/03-traces), 
-execute the following command:
-   ```bash
-   cat <<EOF | kubectl -n $K8S_NAMESPACE apply -f -
-   apiVersion: telemetry.kyma-project.io/v1alpha1
-   kind: TracePipeline
-   metadata:
-     name: jaeger
-   spec:
-     output:
-       otlp:
-         protocol: http
-         endpoint:
-           value: http://$HELM_JAEGER_RELEASE-collector.$K8S_NAMESPACE.svc.cluster.local:4318
-   EOF
-   ```
-  
-### Activate Istio Tracing
-
-To [enable Istio](https://kyma-project.io/#/telemetry-manager/user/03-traces?id=step-2-enable-istio-tracing) to report span data, apply an Istio telemetry resource and set the sampling rate to 100%. This approach is not recommended for production.
-
-```bash
-cat <<EOF | kubectl apply -f -
-apiVersion: telemetry.istio.io/v1alpha1
-kind: Telemetry
-metadata:
-  name: tracing-default
-  namespace: istio-system
-spec:
-  tracing:
-  - providers:
-    - name: "kyma-traces"
-    randomSamplingPercentage: 100.00
-EOF
-```
-
-### Access Jaeger
-
-To access Jaeger using port forwarding, run:
-```bash
-kubectl -n $K8S_NAMESPACE port-forward svc/$HELM_JAEGER_RELEASE-query 16686
-```
-
-Open the Jaeger UI in your browser under `http://localhost:16686`.
-
-### Deploy a workload and activate Kyma's TracePipeline feature
-
-To see distributed traces visualized in Jaeger, follow the instructions in [`trace-demo`](./../trace-demo/).
-
-## Advanced Topics
-
-### Integrate with Grafana
-
-Jaeger can be provided as a data source integrated into Grafana. For example, it can be part of a Grafana installation as described in the [Prometheus tutorial](./../prometheus/README.md). To have a Jaeger data source as part of the Grafana installation, deploy a Grafana data source in the following way:
-
-```bash
-cat <<EOF | kubectl -n $K8S_NAMESPACE apply -f -
-apiVersion: v1
-kind: ConfigMap
-metadata:
-  name: jaeger-grafana-datasource
-  labels:
-    grafana_datasource: "1"
-data:
-    jaeger-grafana-datasource.yaml: |-
-      apiVersion: 1
-      datasources:
-      - name: Jaeger-Tracing
-        type: jaeger
-        access: proxy
-        url: http://$HELM_JAEGER_RELEASE-query.$K8S_NAMESPACE:16686
-        editable: true
-EOF
-```
-Restart the Grafana instance. Afterwards, the Jaeger data source will be available in the `Explore` view.
-
-### Authentication
-
-Jaeger does not provide authentication mechanisms by itself. To secure Jaeger, follow the instructions provided in the [Jaeger documentation
-](https://www.jaegertracing.io/docs/latest/security/#browser-to-ui).
-
-### Exposure
->**CAUTION**: The following approach exposes the Jaeger instance as it is without providing any ways of authentication.
-
-To expose Jaeger using Kyma API Gateway, create the following APIRule:
-```bash
-cat <<EOF | kubectl -n $K8S_NAMESPACE apply -f -
-apiVersion: gateway.kyma-project.io/v1beta1
-kind: APIRule
-metadata:
-  name: jaeger
-spec:
-  host: jaeger-ui
-  service:
-    name: $HELM_JAEGER_RELEASE-query
-    port: 16686
-  gateway: kyma-system/kyma-gateway
-  rules:
-    - path: /.*
-      methods: ["GET", "POST"]
-      accessStrategies:
-        - handler: noop
-      mutators:
-        - handler: noop
-EOF
-```
-
-Get the public URL of your Jaeger instance:
-```bash
-kubectl -n $K8S_NAMESPACE get vs -l apirule.gateway.kyma-project.io/v1beta1=jaeger.$K8S_NAMESPACE -ojsonpath='{.items[*].spec.hosts[*]}'
-```
-
-## Cleanup
-
-When you're done, remove the example and all its resources from the cluster.
-
-1. Remove the stack by calling Helm:
-
-    ```bash
-    helm delete -n $K8S_NAMESPACE $HELM_JAEGER_RELEASE
-    ```
-
-2. If you created the `$K8S_NAMESPACE` Namespace specifically for this tutorial, remove the Namespace:
-    ```bash
-    kubectl delete namespace $K8S_NAMESPACE
-    ``` 
diff --git a/jaeger/values.yaml b/jaeger/values.yaml
deleted file mode 100644
index e51ca586..00000000
--- a/jaeger/values.yaml
+++ /dev/null
@@ -1,19 +0,0 @@
-provisionDataStore:
-  cassandra: false
-allInOne:
-  enabled: true
-  args: ["--memory.max-traces", "10000", "--query.base-path", "/jaeger/ui"]
-  resources:
-    limits:
-      memory: 275Mi
-  podLabels:
-    sidecar.istio.io/inject: "false"
-storage:
-  type: none
-agent:
-  enabled: false
-collector:
-  enabled: false
-query:
-  enabled: false
-
diff --git a/loki/README.md b/loki/README.md
deleted file mode 100644
index cd01d96b..00000000
--- a/loki/README.md
+++ /dev/null
@@ -1,232 +0,0 @@
-# Installing a custom Loki stack in Kyma
-
-## Overview
-The following instructions outline how to use [`Loki`](https://github.com/grafana/loki/tree/main/production/helm/loki) as a logging backend with Kyma's [LogPipeline](https://kyma-project.io/#/telemetry-manager/user/02-logs) or with [Promtail](https://grafana.com/docs/loki/latest/clients/promtail/).
-
->**CAUTION:** This example uses the Grafana Loki version, which is distributed under AGPL-3.0 only and might not be free of charge for commercial usage.
-
-## Table of Content
-
-- [Prerequisites](#prerequisites)
-- [Preparation](#preparation)
-- [Loki installation](#loki-installation)
-- [Log agent installation](#log-agent-installation)
-- [Grafana installation](#grafana-installation)
-- [Grafana Exposure](#grafana-exposure)
-
-## Prerequisites
-
-- Kyma as the target deployment environment
-- The [Telemetry module](https://kyma-project.io/#/telemetry-manager/user/README) is [installed](https://kyma-project.io/#/02-get-started/08-install-uninstall-upgrade-kyma-module?id=install-uninstall-and-upgrade-kyma-with-a-module)
-- Kubectl version 1.22.x or higher
-- Helm 3.x
-
-## Preparation
-
-1. Export your Namespace as a variable. Replace the `{NAMESPACE}` placeholder in the following command and run it:
-
-    ```bash
-    export K8S_NAMESPACE="{NAMESPACE}"
-    ```
-
-2. Export the Helm release names that you want to use. It can be any name, but be aware that all resources in the cluster will be prefixed with that name. Run the following command:
-
-    ```bash
-    export HELM_LOKI_RELEASE="loki"
-    ```
-
-3. Update your Helm installation with the required Helm repository:
-
-    ```bash
-    helm repo add grafana https://grafana.github.io/helm-charts
-    helm repo update
-    ```
-
-## Loki installation
-
-Depending on your scalability needs and storage requirements, you can install Loki in different [Deployment modes](https://grafana.com/docs/loki/latest/fundamentals/architecture/deployment-modes/). The following instructions install Loki in a lightweight in-cluster solution that does not fulfil production-grade qualities. Consider using a scalable setup based on an object storage backend instead (see [Simple scalable deployment of Grafana Loki with Helm](https://grafana.com/docs/loki/latest/installation/helm/install-scalable/)).
-
-### Install Loki
-
-You install the Loki stack with a Helm upgrade command, which installs the chart if not present yet.
-
-```bash
-helm upgrade --install --create-namespace -n ${K8S_NAMESPACE} ${HELM_LOKI_RELEASE} grafana/loki -f https://raw.githubusercontent.com/kyma-project/examples/main/loki/loki-values.yaml
-```
-
-In any case, you can either create your own `values.yaml` file, or use the [loki-values.yaml](./loki-values.yaml) provided in this `loki` folder, which contains customized settings deviating from the default settings: The provided `values.yaml` file activates the `singleBinary` mode and disables additional components that are usually used when running Loki as a central backend. 
-
-### Verify Loki installation
-
-Check that the `loki` Pod has been created in the Namespace and is in the `Running` state:
-
-```bash
-kubectl -n ${K8S_NAMESPACE} get pod -l app.kubernetes.io/name=loki
-```
-## Log agent installation
-
-### Install the log agent
-
-To ingest the application logs from within your cluster to Loki, you can either choose an installation based on [Promtail](https://grafana.com/docs/loki/latest/clients/promtail/), which is the log collector recommended by Loki and provides a ready-to-use setup. Alternatively, you can use Kyma's LogPipeline feature based on Fluent Bit.
-
-<div tabs name="default-settings" group="configuration">
-  <details>
-  <summary label="promtail-installation">
-  Install Promtail
-  </summary>
-
-To install Promtail pointing it to the previously installed Loki instance, run:
-
-```bash
-helm upgrade --install --create-namespace -n ${K8S_NAMESPACE} promtail grafana/promtail -f https://raw.githubusercontent.com/kyma-project/examples/main/loki/promtail-values.yaml --set "config.clients[0].url=https://${HELM_LOKI_RELEASE}.${K8S_NAMESPACE}.svc.cluster.local:3100/loki/api/v1/push" 
-```
-  </details>
-  <details>
-  <summary label="fluent-bit-installation">
-  Install Fluent Bit with Kyma's LogPipeline
-  </summary>
-
->**CAUTION:** This setup uses an unsupported output plugin for the LogPipline.
-
-Apply the LogPipeline:
-
-   ```bash
-   cat <<EOF | kubectl apply -f -
-   apiVersion: telemetry.kyma-project.io/v1alpha1
-   kind: LogPipeline
-   metadata:
-     name: custom-loki
-   spec:
-      input:
-         application:
-            namespaces:
-              system: true
-      output:
-         custom: |
-            name   loki
-            host   ${HELM_LOKI_RELEASE}-headless.${K8S_NAMESPACE}.svc.cluster.local
-            port   3100
-            auto_kubernetes_labels off
-            labels job=fluentbit, container=\$kubernetes['container_name'], namespace=\$kubernetes['namespace_name'], pod=\$kubernetes['pod_name'], node=\$kubernetes['host'], app=\$kubernetes['labels']['app'],app=\$kubernetes['labels']['app.kubernetes.io/name']
-   EOF
-   ```
-
-When the status of the applied LogPipeline resource turns into `Running`, the underlying Fluent Bit is reconfigured and log shipment to your Loki instance is active.
-
->**NOTE:** The used output plugin configuration uses a static label map to assign labels of a Pod to Loki log streams. It's not recommended to activate the `auto_kubernetes_labels` feature for using all labels of a Pod because this lowers the performance. Follow [Loki's labelling best practices](https://grafana.com/docs/loki/latest/best-practices/) for a tailor-made setup that fits your workload configuration.
-
-  </details>
-</div>
-
-### Verify the setup by accessing logs using the Loki API
-
-1. To access the Loki API, use kubectl port forwarding. Run:
-
-   ```bash
-   kubectl -n ${K8S_NAMESPACE} port-forward svc/$(kubectl  get svc -n ${K8S_NAMESPACE} -l app.kubernetes.io/name=loki -ojsonpath='{.items[0].metadata.name}') 3100
-   ```
-
-1. Loki queries need a query parameter **time**, provided in nanoseconds. To get the current nanoseconds in Linux or macOS, run:
-
-   ```bash
-   date +%s
-   ```
-
-1. To get the latest logs from Loki, replace the `{NANOSECONDS}` placeholder with the result of the previous command, and run:
-
-   ```bash
-   curl -G -s  "http://localhost:3100/loki/api/v1/query" \
-     --data-urlencode \
-     'query={job="fluentbit"}' \
-     --data-urlencode \
-     'time={NANOSECONDS}'
-   ```
-
-## Grafana installation
-
-Because Grafana provides a very good Loki integration, you might want to install it as well.
-
-### Install Grafana
-
-1. To deploy Grafana, run:
-
-   ```bash
-   helm upgrade --install --create-namespace -n ${K8S_NAMESPACE} grafana grafana/grafana -f https://raw.githubusercontent.com/kyma-project/examples/main/loki/grafana-values.yaml
-   ```
-
-1. To enable Loki as Grafana data source, run:
-   ```bash
-   cat <<EOF | kubectl apply -n ${K8S_NAMESPACE} -f -
-   apiVersion: v1
-   kind: ConfigMap
-   metadata:
-     name: grafana-loki-datasource
-     labels:
-       grafana_datasource: "1"
-   data:
-      loki-datasource.yaml: |-
-         apiVersion: 1
-         datasources:
-         - name: Loki
-           type: loki
-           access: proxy
-           url: "http://${HELM_LOKI_RELEASE}:3100"
-           version: 1
-           isDefault: false
-           jsonData: {}
-   EOF
-   ```
-
-1. Get the password to access the Grafana UI:
-
-   ```bash
-   kubectl get secret --namespace ${K8S_NAMESPACE} grafana -o jsonpath="{.data.admin-password}" | base64 --decode ; echo
-   ```
-
-1.  To access the Grafana UI with kubectl port forwarding, run:
-   ```bash
-   kubectl -n ${K8S_NAMESPACE} port-forward svc/grafana 3000:80
-   ```
-   
-1. In your browser, open Grafana under `http://localhost:3000` and log in with user admin and the password you retrieved before.
-  
-## Grafana Exposure
-
-### Expose Grafana
-1. To expose Grafana using the Kyma API Gateway, create an APIRule:
-   ```bash
-   kubectl -n ${K8S_NAMESPACE} apply -f https://raw.githubusercontent.com/kyma-project/examples/main/loki/apirule.yaml
-   ```
-1. Get the public URL of your Loki instance:
-   ```bash
-   kubectl -n ${K8S_NAMESPACE} get virtualservice -l apirule.gateway.kyma-project.io/v1beta1=grafana.${K8S_NAMESPACE} -ojsonpath='{.items[*].spec.hosts[*]}'
-   ```
-
-### Add a link for Grafana to the Kyma Dashboard
-1. Download the `dashboard-configmap.yaml` file and change `{GRAFANA_LINK}` to the public URL of your Grafana instance.
-   ```bash
-      curl https://raw.githubusercontent.com/kyma-project/examples/main/loki/dashboard-configmap.yaml -o dashboard-configmap.yaml
-   ```
-
-1. Optionally, adjust the ConfigMap: You can change the label field to change the name of the tab. If you want to move it to another category, change the category tab.
-
-1. Apply the ConfigMap, and go to Kyma Dashboard. Under the Observability section, you should see a link to the newly exposed Grafana. If you already have a busola-config, merge it with the existing one:
-   ```bash
-   kubectl apply -f dashboard-configmap.yaml 
-   ```
-   
-## Cleanup
-
-1. To remove the installation from the cluster, run:
-
-   ```bash
-   helm delete -n ${K8S_NAMESPACE} ${HELM_LOKI_RELEASE}
-   helm delete -n ${K8S_NAMESPACE} promtail
-   helm delete -n ${K8S_NAMESPACE} grafana
-   ```
-
-2. To remove the deployed LogPipeline instance from cluster, run:
-
-   ```bash
-   kubectl delete LogPipeline custom-loki
-   ```
diff --git a/loki/apirule.yaml b/loki/apirule.yaml
deleted file mode 100644
index e3a9c57c..00000000
--- a/loki/apirule.yaml
+++ /dev/null
@@ -1,17 +0,0 @@
-apiVersion: gateway.kyma-project.io/v1beta1
-kind: APIRule
-metadata:
-  name: grafana
-spec:
-  host: my-grafana
-  service:
-    name: grafana
-    port: 80
-  gateway: kyma-gateway.kyma-system.svc.cluster.local
-  rules:
-    - path: /.*
-      methods: ["GET", "POST"]
-      accessStrategies:
-        - handler: noop
-      mutators:
-        - handler: noop
diff --git a/loki/dashboard-configmap.yaml b/loki/dashboard-configmap.yaml
deleted file mode 100644
index b85ceb63..00000000
--- a/loki/dashboard-configmap.yaml
+++ /dev/null
@@ -1,18 +0,0 @@
-kind: ConfigMap
-apiVersion: v1
-metadata:
-  name: busola-config
-  namespace: kube-public
-data:
-  config: |
-    config:
-      features:
-        EXTERNAL_NODES:
-          isEnabled: true
-          stage: SECONDARY
-          nodes:
-          - category: Observability
-            icon: course-book
-            children:
-            - label: My Grafana
-              link: https://{grafana-link}
diff --git a/loki/grafana-values.yaml b/loki/grafana-values.yaml
deleted file mode 100644
index d7b77889..00000000
--- a/loki/grafana-values.yaml
+++ /dev/null
@@ -1,9 +0,0 @@
-
-sidecar:
-  datasources:
-    enabled: true
-  dashboards:
-    enabled: true
-
-podLabels:
-  sidecar.istio.io/inject: "true"
diff --git a/loki/loki-values.yaml b/loki/loki-values.yaml
deleted file mode 100644
index bc6783cb..00000000
--- a/loki/loki-values.yaml
+++ /dev/null
@@ -1,38 +0,0 @@
-loki:
-  podLabels:
-    # enable istio sidecar injection
-    sidecar.istio.io/inject: "true"
-  # configure the filesystem storage
-  commonConfig:
-    replication_factor: 1
-  storage:
-    type: 'filesystem'
-  # disable multi-tenancy
-  auth_enabled: false
-  limits_config:
-    # reduce the ingestion rate to avoid crashing the lightweight setup
-    ingestion_rate_mb: 3
-  # increase retention time to 5 days
-  chunk_store_config:
-    max_look_back_period: 120h
-  table_manager:
-    retention_deletes_enabled: true
-    retention_period: 120h
-# use single binary mode instead of scalable
-singleBinary:
-  replicas: 1
-
-# Disable any additional components of the chart
-test:
-  enabled: false
-monitoring:
-  serviceMonitor:
-    enabled: false
-  selfMonitoring:
-    enabled: false
-    grafanaAgent:
-      installOperator: false
-  lokiCanary:
-    enabled: false
-gateway:
-  enabled: false
diff --git a/loki/promtail-values.yaml b/loki/promtail-values.yaml
deleted file mode 100644
index b2073595..00000000
--- a/loki/promtail-values.yaml
+++ /dev/null
@@ -1,8 +0,0 @@
-
-# enable istio sidecar injection
-podLabels:
-  sidecar.istio.io/inject: "true"
-
-config:
-  clients: 
-    - url: http://loki:3100/loki/api/v1/push
diff --git a/trace-demo/README.md b/trace-demo/README.md
deleted file mode 100644
index 16c48a2e..00000000
--- a/trace-demo/README.md
+++ /dev/null
@@ -1,176 +0,0 @@
-# Install OpenTelemetry Demo Application in Kyma
-
-## Overview
-
-The following instructions install the OpenTelemetry [demo application](https://github.com/open-telemetry/opentelemetry-demo) on a Kyma cluster using a provided [Helm chart](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-demo). The demo application will be configured to push trace data via OTLP to the collector provided by Kyma, so that they will be collected together with the related Istio trace data.
-
-## Prerequisites
-
-- Kyma as the target deployment environment
-- The [Telemetry module](https://kyma-project.io/#/telemetry-manager/user/README) is [installed](https://kyma-project.io/#/02-get-started/08-install-uninstall-upgrade-kyma-module?id=install-uninstall-and-upgrade-kyma-with-a-module)
-- kubectl version 1.22.x or higher
-- Helm 3.x
-
-### Preparation
-
-1. Export your Namespace as a variable. Replace the `{namespace}` placeholder in the following command and run it:
-
-    ```bash
-    export K8S_NAMESPACE="{namespace}"
-    ```
-1. If you don't have created a Namespace yet, do it now:
-    ```bash
-    kubectl create namespace $K8S_NAMESPACE
-    ```
-
-1. To enable Istio injection in your Namespace, set the following label:
-    ```bash
-    kubectl label namespace $K8S_NAMESPACE istio-injection=enabled
-    ```
-
-1. Export the Helm release name that you want to use. The release name must be unique for the chosen Namespace. Be aware that all resources in the cluster will be prefixed with that name. Run the following command:
-    ```bash
-    export HELM_OTEL_RELEASE="otel"
-    ```
-
-1. Update your Helm installation with the required Helm repository:
-
-    ```bash
-    helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts
-    helm repo update
-    ```
-
-### Activate a Kyma TracePipeline
-
-1. Provide a tracing backend and activate it.
-   Install [Jaeger in-cluster](./../jaeger/) or provide a custom backend supporting the OTLP protocol.
-2. Activate the Istio tracing feature.
-To [enable Istio](https://kyma-project.io/#/telemetry-manager/user/03-traces?id=step-2-enable-istio-tracing) to report span data, apply an Istio telemetry resource and set the sampling rate to 100%. This approach is not recommended for production.
-   ```bash
-   cat <<EOF | kubectl apply -f -
-   apiVersion: telemetry.istio.io/v1alpha1
-   kind: Telemetry
-   metadata:
-     name: tracing-default
-     namespace: istio-system
-   spec:
-     tracing:
-     - providers:
-       - name: "kyma-traces"
-       randomSamplingPercentage: 100.00
-   EOF
-   ```
-
-### Install the application
-
-Run the Helm upgrade command, which installs the chart if not present yet.
-```bash
-helm upgrade --version 0.24.0 --install --create-namespace -n $K8S_NAMESPACE $HELM_OTEL_RELEASE open-telemetry/opentelemetry-demo -f https://raw.githubusercontent.com/kyma-project/examples/main/trace-demo/values.yaml
-```
-
-You can either use the [`values.yaml`](./values.yaml) provided in this `trace-demo` folder, which contains customized settings deviating from the default settings, or create your own `values.yaml` file. The customizations cover the following areas:
-- Disable the observability tooling provided with the chart
-- Configure Kyma Telemetry instead
-- Extend memory limits of the demo apps to avoid crashes caused by memory exhaustion
-- Adjust initContainers and services of demo apps to work proper with Istio
-
-### Verify the application
-
-To verify that the application is running properly, set up port forwarding and call the respective local hosts.
-
-1. Verify the frontend:
-   ```bash
-   kubectl -n $K8S_NAMESPACE port-forward svc/$HELM_OTEL_RELEASE-frontend 8080
-   ```
-   ```bash
-   open http://localhost:8080
-   ````
-
-2. Verify that traces arrive in the Jaeger backend. If you deployed [Jaeger in your cluster](./../jaeger/) using the same Namespace as used for the demo app, run:
-   ```bash
-   kubectl -n $K8S_NAMESPACE port-forward svc/tracing-jaeger-query 16686
-   ```
-   ```bash
-   open http://localhost:16686
-   ````
-
-3. Enable failures with the feature flag service:
-   ```bash
-   kubectl -n $K8S_NAMESPACE port-forward svc/$HELM_OTEL_RELEASE-featureflagservice 8081
-   ```
-   ```bash
-   open http://localhost:8081
-   ````
-
-4. Generate load with the load generator:
-   ```bash
-   kubectl -n $K8S_NAMESPACE port-forward svc/$HELM_OTEL_RELEASE-loadgenerator 8089
-   ```
-   ```bash
-   open http://localhost:8089
-   ```
-
-## Advanced
-
-### Browser Instrumentation and missing root spans
-
-The frontend application of the demo uses [browser instrumentation](https://opentelemetry.io/docs/demo/services/frontend/#browser-instrumentation). Because of that, the root span of a trace is created externally to the cluster and will not be captured with the described setup. In Jaeger, you can see a warning at the first span indicating that there is a parent span that is not being captured.
-
-In order to capture the spans reported by the browser, you need to expose the trace endpoint of the collector and configure the frontend to report the spans to that exposed endpoint.
-
-To expose the frontend web app and the relevant trace endpoint, define an Istio Virtualservice as in the following example.
->**CAUTION** The example shows an insecure way of exposing the trace endpoint. Do not use it in production.
-```bash
-export CLUSTER_DOMAIN={my-domain}
-
-cat <<EOF | kubectl -n $K8S_NAMESPACE apply -f -
-apiVersion: networking.istio.io/v1beta1
-kind: VirtualService
-metadata:
-  name: frontend
-spec:
-  gateways:
-  - kyma-system/kyma-gateway
-  hosts:
-  - frontend.$CLUSTER_DOMAIN
-  http:
-  - route:
-    - destination:
-        host: telemetry-otlp-traces.kyma-system.svc.cluster.local
-        port:
-          number: 4318
-    match:
-    - uri:
-        prefix: "/v1/traces"
-    corsPolicy:
-      allowOrigins:
-      - prefix: https://frontend.$CLUSTER_DOMAIN
-      allowHeaders:
-      - Content-Type
-      allowMethods:
-      - POST
-      allowCredentials: true
-  - route:
-    - destination:
-        host: $HELM_OTEL_RELEASE-frontend.$K8S_NAMESPACE.svc.cluster.local
-        port:
-          number: 8080
-EOF
-```
-
-Then, update the frontend configuration. To do that, run the following helm command and set the additional configuration:
-```bash
-helm upgrade --version 0.22.2 --install --create-namespace -n $K8S_NAMESPACE $HELM_OTEL_RELEASE open-telemetry/opentelemetry-demo \
--f https://raw.githubusercontent.com/kyma-project/examples/main/trace-demo/values.yaml \
---set 'components.frontend.envOverrides[1].name=PUBLIC_OTEL_EXPORTER_OTLP_TRACES_ENDPOINT' \
---set "components.frontend.envOverrides[1].value=https://frontend.$CLUSTER_DOMAIN/v1/traces"
-```
-
-Afterwards, the web application will be accessible in your browser at `https://frontend.$CLUSTER_DOMAIN`. Using the developer tools of the browser you should see that requests to the traces endpoint are successful. Now, every trace should have a proper root span recorded.
-## Cleanup
-
-When you're done, you can remove the example and all its resources from the cluster by calling Helm:
-
-```bash
-helm delete -n $K8S_NAMESPACE $HELM_OTEL_RELEASE
-```
diff --git a/trace-demo/values.yaml b/trace-demo/values.yaml
deleted file mode 100644
index 9b3e70e4..00000000
--- a/trace-demo/values.yaml
+++ /dev/null
@@ -1,259 +0,0 @@
-opentelemetry-collector:
-  enabled: false
-jaeger:
-  enabled: false
-prometheus:
-  enabled: false
-grafana:
-  enabled: false
-
-default:
-  envOverrides:
-  - name: OTEL_SERVICE_NAME
-    valueFrom:
-      fieldRef:
-        apiVersion: v1
-        fieldPath: "metadata.labels['app.kubernetes.io/name']"
-
-components:
-  accountingService:
-    enabled: true
-    envOverrides:
-      - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
-        value: 'http://telemetry-otlp-traces.kyma-system:4317'
-      - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
-        value: 'http://telemetry-otlp-metrics.kyma-system:4317'
-    initContainers:
-      - name: wait-for-kafka
-        image: busybox:latest
-        command: ['sh', '-c', 'until nc -z -v -w30 {{ include "otel-demo.name" . }}-kafka 9092; do echo waiting for kafka; sleep 2; done;']
-        securityContext:
-          runAsUser: 1337
-
-  adService:
-    enabled: true
-    envOverrides:
-      - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
-        value: 'http://telemetry-otlp-traces.kyma-system:4317'
-      - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
-        value: 'http://telemetry-otlp-metrics.kyma-system:4317'
-    service:
-      port: null
-    ports:
-      - name: grpc
-        value: 8080
-
-  cartService:
-    enabled: true
-    envOverrides:
-      - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
-        value: 'http://telemetry-otlp-traces.kyma-system:4317'
-      - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
-        value: 'http://telemetry-otlp-metrics.kyma-system:4317'
-    service:
-      port: null
-    ports:
-      - name: grpc
-        value: 8080
-    initContainers:
-      - name: wait-for-redis
-        image: busybox:latest
-        command: ['sh', '-c', 'until nc -z -v -w30 {{ include "otel-demo.name" . }}-redis 6379; do echo waiting for redis; sleep 2; done;']
-        securityContext:
-          runAsUser: 1337
-
-  checkoutService:
-    enabled: true
-    envOverrides:
-      - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
-        value: 'http://telemetry-otlp-traces.kyma-system:4317'
-      - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
-        value: 'http://telemetry-otlp-metrics.kyma-system:4317'
-    service:
-      port: null
-    ports:
-      - name: grpc
-        value: 8080
-    initContainers:
-      - name: wait-for-kafka
-        image: busybox:latest
-        command: ['sh', '-c', 'until nc -z -v -w30 {{ include "otel-demo.name" . }}-kafka 9092; do echo waiting for kafka; sleep 2; done;']
-        securityContext:
-          runAsUser: 1337
-
-  currencyService:
-    enabled: true
-    envOverrides:
-      - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
-        value: 'http://telemetry-otlp-traces.kyma-system:4317'
-      - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
-        value: 'http://telemetry-otlp-metrics.kyma-system:4317'
-    service:
-      port: null
-    ports:
-      - name: grpc
-        value: 8080
-
-  emailService:
-    enabled: true
-    envOverrides:
-      - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
-        value: 'http://telemetry-otlp-traces.kyma-system:4318'
-      - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
-        value: 'http://telemetry-otlp-metrics.kyma-system:4318'
-    service:
-      port: null
-    ports:
-      - name: http
-        value: 8080
-    resources:
-      limits:
-        memory: 150Mi
-
-  featureflagService:
-    enabled: true
-    envOverrides:
-      - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
-        value: 'http://telemetry-otlp-traces.kyma-system:4317'
-      - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
-        value: 'http://telemetry-otlp-metrics.kyma-system:4317'
-    initContainers:
-      - name: wait-for-ffspostgres
-        image: busybox:latest
-        command: ['sh', '-c', 'until nc -z -v -w30 {{ include "otel-demo.name" . }}-ffspostgres 5432; do echo waiting for ffspostgres; sleep 2; done']
-        securityContext:
-          runAsUser: 1337
-
-  frauddetectionService:
-    enabled: true
-    envOverrides:
-      - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
-        value: 'http://telemetry-otlp-traces.kyma-system:4317'
-      - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
-        value: 'http://telemetry-otlp-metrics.kyma-system:4317'
-    initContainers:
-      - name: wait-for-kafka
-        image: busybox:latest
-        command: ['sh', '-c', 'until nc -z -v -w30 {{ include "otel-demo.name" . }}-kafka 9092; do echo waiting for kafka; sleep 2; done;']
-        securityContext:
-          runAsUser: 1337
-
-  frontend:
-    enabled: true
-    resources:
-      limits:
-        memory: 500Mi
-    envOverrides:
-      - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
-        value: 'http://telemetry-otlp-traces.kyma-system:4317'
-      - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
-        value: 'http://telemetry-otlp-metrics.kyma-system:4317'
-    service:
-      port: null
-    ports:
-      - name: http
-        value: 8080
-
-  frontendProxy:
-    enabled: true
-
-  loadgenerator:
-    enabled: true
-    envOverrides:
-      - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
-        value: 'http://telemetry-otlp-traces.kyma-system:4317'
-      - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
-        value: 'http://telemetry-otlp-metrics.kyma-system:4317'
-    resources:
-      limits:
-        memory: 170Mi
-
-  paymentService:
-    enabled: true
-    envOverrides:
-      - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
-        value: 'http://telemetry-otlp-traces.kyma-system:4317'
-      - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
-        value: 'http://telemetry-otlp-metrics.kyma-system:4317'
-    service:
-      port: null
-    ports:
-      - name: grpc
-        value: 8080
-
-  productCatalogService:
-    enabled: true
-    envOverrides:
-      - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
-        value: 'http://telemetry-otlp-traces.kyma-system:4317'
-      - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
-        value: 'http://telemetry-otlp-metrics.kyma-system:4317'
-    service:
-      port: null
-    ports:
-      - name: grpc
-        value: 8080
-
-  quoteService:
-    enabled: true
-    envOverrides:
-      - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
-        value: 'http://telemetry-otlp-traces.kyma-system:4317'
-      - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
-        value: 'http://telemetry-otlp-metrics.kyma-system:4317'
-    service:
-      port: null
-    ports:
-      - name: http
-        value: 8080
-    resources:
-      limits:
-        memory: 80Mi
-
-  recommendationService:
-    enabled: true
-    envOverrides:
-      - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
-        value: 'http://telemetry-otlp-traces.kyma-system:4317'
-      - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
-        value: 'http://telemetry-otlp-metrics.kyma-system:4317'
-    service:
-      port: null
-    ports:
-      - name: grpc
-        value: 8080
-
-  shippingService:
-    enabled: true
-    envOverrides:
-      - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
-        value: 'http://telemetry-otlp-traces.kyma-system:4317'
-      - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
-        value: 'http://telemetry-otlp-metrics.kyma-system:4317'
-    service:
-      port: null
-    ports:
-      - name: grpc
-        value: 8080
-
-  ffsPostgres:
-    enabled: true
-    envOverrides:
-      - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
-        value: 'http://telemetry-otlp-traces.kyma-system:4317'
-      - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
-        value: 'http://telemetry-otlp-metrics.kyma-system:4317'
-
-  kafka:
-    enabled: true
-    envOverrides:
-      - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
-        value: 'http://telemetry-otlp-traces.kyma-system:4317'
-      - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
-        value: 'http://telemetry-otlp-metrics.kyma-system:4317'
-    resources:
-      limits:
-        memory: 700Mi
-
-  redis:
-    enabled: true
\ No newline at end of file

From 522b5ec043bc4bd6a5f69f7b2c5330f576086997 Mon Sep 17 00:00:00 2001
From: Nina Hingerl <n.hingerl@sap.com>
Date: Tue, 5 Dec 2023 14:56:23 +0100
Subject: [PATCH 2/4] remove broken links

---
 README.md         | 1 -
 tracing/README.md | 2 +-
 2 files changed, 1 insertion(+), 2 deletions(-)

diff --git a/README.md b/README.md
index b7b8ca21..71a1e83f 100644
--- a/README.md
+++ b/README.md
@@ -34,7 +34,6 @@ The summary of the documentation in the `examples` repository lists all availabl
 | [Custom serverless runtime image](custom-serverless-runtime-image/README.md) | Build custom runtime image. | Python |
 | [Kiali](kiali/README.md) | Deploy Kiali to Kyma. | Kiali, Istio, Prometheus |
 | [Prometheus](prometheus/README.md) | Deploy a Prometheus stack to monitor custom metrics. | Prometheus, Grafana |
-| [Loki](loki/README.md) | Deploy Loki to store Pod logs. | Loki, Grafana |
 
 ## Installation
 
diff --git a/tracing/README.md b/tracing/README.md
index bc9c2058..1f11befa 100644
--- a/tracing/README.md
+++ b/tracing/README.md
@@ -1,6 +1,6 @@
 # Example Tracing
 
->**CAUTION** This example is outdated and will be updated soon. Please have a look at the [trace-demo](./../trace-demo/) and [jaeger](./../jaeger/) instead.
+>**CAUTION** This example is outdated and will be updated soon.
 
 ## Overview
 

From 52511b5e0a5a64f679289dc6b63d69a4a834ff3f Mon Sep 17 00:00:00 2001
From: Nina Hingerl <n.hingerl@sap.com>
Date: Mon, 11 Dec 2023 14:27:53 +0100
Subject: [PATCH 3/4] temporarily keep README files for redirect

---
 jaeger/README.md     | 3 +++
 loki/README.md       | 3 +++
 trace-demo/README.md | 3 +++
 3 files changed, 9 insertions(+)
 create mode 100644 jaeger/README.md
 create mode 100644 loki/README.md
 create mode 100644 trace-demo/README.md

diff --git a/jaeger/README.md b/jaeger/README.md
new file mode 100644
index 00000000..a09775a5
--- /dev/null
+++ b/jaeger/README.md
@@ -0,0 +1,3 @@
+# Install custom Jaeger in Kyma
+
+The document has been moved to [Telemetry Integration Guides](https://github.com/kyma-project/telemetry-manager/tree/main/docs/user/integration).
diff --git a/loki/README.md b/loki/README.md
new file mode 100644
index 00000000..135a67af
--- /dev/null
+++ b/loki/README.md
@@ -0,0 +1,3 @@
+# Installing a custom Loki stack in Kyma
+
+The document has been moved to [Telemetry Integration Guides](https://github.com/kyma-project/telemetry-manager/tree/main/docs/user/integration).
diff --git a/trace-demo/README.md b/trace-demo/README.md
new file mode 100644
index 00000000..adaca637
--- /dev/null
+++ b/trace-demo/README.md
@@ -0,0 +1,3 @@
+# Install OpenTelemetry Demo Application in Kyma
+
+The document has been moved to [Telemetry Integration Guides](https://github.com/kyma-project/telemetry-manager/tree/main/docs/user/integration).

From 8521c133cce83e4df77a0d2e0740b62a3b4a2fab Mon Sep 17 00:00:00 2001
From: Nina Hingerl <n.hingerl@sap.com>
Date: Wed, 13 Dec 2023 09:00:29 +0100
Subject: [PATCH 4/4] update link to website

---
 jaeger/README.md     | 2 +-
 loki/README.md       | 2 +-
 trace-demo/README.md | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/jaeger/README.md b/jaeger/README.md
index a09775a5..d26abad9 100644
--- a/jaeger/README.md
+++ b/jaeger/README.md
@@ -1,3 +1,3 @@
 # Install custom Jaeger in Kyma
 
-The document has been moved to [Telemetry Integration Guides](https://github.com/kyma-project/telemetry-manager/tree/main/docs/user/integration).
+The document has been moved. Find the updated instructions in [Integrate With Jaeger](https://kyma-project.io/#/telemetry-manager/user/integration/jaeger/README).
diff --git a/loki/README.md b/loki/README.md
index 135a67af..7e32e112 100644
--- a/loki/README.md
+++ b/loki/README.md
@@ -1,3 +1,3 @@
 # Installing a custom Loki stack in Kyma
 
-The document has been moved to [Telemetry Integration Guides](https://github.com/kyma-project/telemetry-manager/tree/main/docs/user/integration).
+The document has been moved. Find the updated instructions in [Integrate With Loki](https://kyma-project.io/#/telemetry-manager/user/integration/loki/README).
diff --git a/trace-demo/README.md b/trace-demo/README.md
index adaca637..d67df9c6 100644
--- a/trace-demo/README.md
+++ b/trace-demo/README.md
@@ -1,3 +1,3 @@
 # Install OpenTelemetry Demo Application in Kyma
 
-The document has been moved to [Telemetry Integration Guides](https://github.com/kyma-project/telemetry-manager/tree/main/docs/user/integration).
+The document has been moved. Find the updated instructions in [Integrate OpenTelemetry Demo App](https://kyma-project.io/#/telemetry-manager/user/integration/opentelemetry-demo/README).