All the Components of Loki Explained | Grafana Labs

preview_player
Показать описание
Here are all the components of Loki explained so that you can figure out how many instances of each you need for a resilient Loki deployment. Senior Developer Advocates Jay Clifford and Nicole van der Hoeven talk you through what each component does and which ones are optional.

TIMESTAMPS
00:00 Intro
01:04 Distributors and hash rings
05:07 Ingesters
09:21 Query frontend
10:25 Query scheduler
10:56 Queriers
12:53 Index gateway
13:49 Compactor
14:39 Ruler

Helpful links:

-----
👍 If you found this video useful, be sure to give it a thumbs up and subscribe to our channel for more helpful Grafana videos.

📱 Follow us for the latest and greatest on all things Grafana and our other OSS projects.

#Grafana #Observability #loki #architecture #distributed #logs
Рекомендации по теме
Комментарии
Автор

We broke down these components assuming a microservices mode deployment of Loki, but you can also choose a simple scalable or monolithic deployment if you'd like simpler configurations. If you have any other questions on Loki components and architecture, we'd love to hear them!

Grafana
Автор

This is gold and really cool! I really enjoyed this type of analogy-type content. Looking forward to watch more videos like this for other Grafana projects!

zulhilmizainudin
Автор

It would be great to have access to the Excalidraw diagrams shown in the video, thanks!

bukran
Автор

Personally, I'm not a huge fan of metaphors for descriptions like this - I find it ends up being a layer of abstraction I need to translate to get to the actual answer of what each component is doing. That said, this is an excellent resource, and I absolutely +1 the need for this kind of content but covering things like Mimir and Tempo.

Destenoth
Автор

I like to see a workflow lab session using these latest Grafana re-organized charts (Alloy, Loki distributed, Prometheus Operator to get AlertManager and its needed AlertManagerConfig CRDs) and show how to configure these using Minio storage and then deploying a Go or Node.js log-generator app to Kubernetes (to a KinD or K3D) Cluster and have a Loki Rule that keys on a pattern match in the logs to trigger an AlertManager dispatch to Gmail and Slack... A real production case workflow

countbrappcula