Member-only story
Journey Of A Microservice Application In The Kubernetes World
Observability using the Loki stack
TL;DR
In the previous article we explained how to use GitOps with Argo CD to set up the Continuous Deployment part of the CI/CD pipeline. We will now deploy the Loki stack to get application logs and metrics.
Articles in this series
- Presentation of the webhooks.app
- Running the application on a local one-node Kubernetes using Helm
- Running the application on a Civo Kubernetes cluster
- Continuous Deployment using GitOps with Argo CD
- Observability using the Loki stack (this article)
- Defining the application using Acorn
- Security considerations : security related tools
- Security considerations : fixing misconfigurations
- Security considerations : policies enforcement
- Security considerations : vulnerability scanning (coming soon)
In a nutshell the Loki stack from Grafana Labs is a multi components application that can be installed into a Kubernetes cluster and which allows users to view logs and metrics using Grafana. In this short article we won’t go into the details of this stack but we will show how it can be installed and used in a simple way to monitor the webhooks application.
As many application in the Kubernetes world the Loki stack is available as a Helm chart:
Using the helm binary, the stack can be installed using the following command:
# Adding grafana repo
$ helm repo add grafana https://grafana.github.io/helm-charts# Installing the stack
$ helm install my-loki grafana/loki --version 3.0.7 --set grafana.enabled=true --set prometheus.enabled=true
In this example we enabled both grafana and prometheus as they are not enabled in the stack by default (only the components related to the logs management are installed by…
