lab 5

labs/paas/otomi/5_activate_apps/README.md

@@ -1,11 +1,26 @@
 # Lab 5
 
-In this lab we are going to activate some additional apps. Otomi by default ships with a minimal set of apps. These are called the Core apps. With the Core, Otomi offers an advanced ingress architecture, using Nginx, Istio, Keycloak, Certmanager and Oauth2, combined with developer self-service. Next to the Core apps, Otomi offers additional apps like Knative, Harbor, Vault, Kubeapps, Prometheus, Loki, Alertmanager. These apps all fully integrated and can be activated by dragging them to the active apps section in the Console.
+Otomi by default ships with a minimal set of apps. These are called the Core apps. With the Core apps, Otomi offers an advanced ingress architecture, using Nginx, Istio, Keycloak, Certmanager and Oauth2, combined with developer self-service. Next to the Core apps, Otomi offers optional apps like Knative, Harbor, Vault, Kubeapps, Prometheus, Loki, Alertmanager. These apps all fully integrated and can be activated by dragging them to the active apps section in the Console.
+
+In this lab we are going to activate Loki for logging. But first: Otomi by default is not configured for multi-tenancy. When multi-tenancy is enabled, team metrics and logs will be separated per team. When multi-tenancy is disabled this effectively gives all users the admin role and lets them see everything, including metrics and logs of all platform services.
 
 ## Instructions
 
-1. Go to the `Apps` section under `Platform`
+1. Go to the `Settings` section under `Platform` and then choose `Otomi`. In the bottom of the page you will see the flag `Multi-tenancy`. For this lab, we will not enable multi-tenancy.
+
+2. Go to the Apps section under `Platform` and Drag and Drop `Loki` from the `Disabled apps` to the `Enabled apps`. Notice that `Grafana` will also be enabled. This is because Loki uses Grafana and thus is a dependency for Loki (and is also installed).
+
+3. Click on `Deploy changes` (this will now be active)
+
+4. To see the progress of the installation of Loki, go the apps section and click on `Drone`. In the top right you will see a play button. Click on it. The Drone app will now open in a new tab. Click on the `otomi/values` repository and the on the last build execution. When the `apply` step is finished, Loki/Grafana will be installed.
+
+5. In the Apps section, click on `Loki`. In the app bar, click on `Values`. The Loki chart has been installed with sane default values. Click on `Duration` to see the default value. All the defaults (specified in the Otomi values [schema](https://github.com/redkubes/otomi-core/blob/master/values-schema.yaml) can be modified.
+
+6. In the app bar, click on `Raw values`. In the Raw values, all values of the Loki chart that are not provided with defaults from the Otomi values schema can be used here.
+
+7. Click on the play button. A new tab wil open and here you can execute queries to search for logs. Add the following query: `{namespace=team-<team-name>}`. Now you will see all the logs of containers running in the namespace of your team. Copy the path after .nip.io/ in your browser.
+
+7. Go back to the console and in the Loki app, click on `Shortcuts`. Click `Edit` and the `Add item`. Fill in a title (like "team-name logs"), a description (like "The logs of teamname") and the paste the path. Now click Submit. The shortcut you now created can be used to go directly to Loki and see the result of your query.
 
-2. Drag and Drop `Grafana`
 
 Optional: Go to the [next lab](../6_knative/README.md)