Files
k8s-apps/logging
2025-08-24 13:38:37 +02:00
..
2025-08-24 13:38:37 +02:00
2025-08-24 13:38:37 +02:00
2025-08-24 13:38:37 +02:00
2025-08-24 13:38:37 +02:00
2025-08-24 13:38:37 +02:00
2025-08-24 13:38:37 +02:00
2025-08-24 13:38:37 +02:00
2025-08-24 13:38:37 +02:00
2025-08-24 13:38:37 +02:00
2025-08-24 13:38:37 +02:00
2025-08-24 13:38:37 +02:00
2025-08-24 13:38:37 +02:00
2025-08-24 13:38:37 +02:00
2025-08-24 13:38:37 +02:00

logging

beats, elasticsearch, kibana

jeez...

beats collects logs and sends them to logstash (fluentd or fluentbit would be an elternative)

logstash is the database that stores the data

elasticsearch is the search engine for the data

kibana is the web interface for elasticsearch

there are multiple ways to deploy all of that the most k8 way is ECK (elastic cloud on kubernetes) ECK is a operator and CRDs (like rook) it includes crds for beats, elasticsearch and kibana

BUT NOT LOGSTASH! logstash might not be needed if one uses filebeat (part of beats) ???

improvements: get working! metrics liveness probes resource limits