What’s the Best Way to Centralize Logs in a Self-Managed K3s Cluster?

0
16
Asked By CloudySamurai42 On

I'm running a small application on my self-managed Hetzner K3s cluster and want to centralize all the application logs. Typically, all logs are outputted to stdout within the container, but I need a way to persist them when the pods get recreated. Since privacy is a concern, everything needs to stay within the cluster or be self-hostable. Is there a simple and effective solution for this? I've heard Grafana Loki is quite popular, but I'm unsure what to use for shipping the logs—should I go with Fluentbit, Fluentd, Promtail, or something else?

3 Answers

Answered By StreamlineGuru On

Have you thought about using Vector.dev for your log shipping? It pairs nicely with VictoriaLogs as the engine, and it requires a lot less resources than Grafana Loki. Plus, you can visualize everything with Grafana, keeping it simple and low overhead.

Answered By LogMaster99 On

If you’re considering the Grafana stack, check out Grafana Alloy. It’s a solid option that combines many features you'd typically use several tools for.

Answered By DataSmith42 On

Definitely go for Loki + Grafana Alloy! Promtail’s getting replaced by Alloy because it’s an all-in-one agent for logs, metrics, and traces. Plus, the k8s-monitoring-chart uses Alloy operator, which makes it easier to gather everything.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.