k8s-fluent-bit-troubleshooting
Fluent Bit troubleshooting
Find out why Fluent Bit does not ship logs, and propose a fix. Read first, ask before changing. Run the investigation commands freely. Run a command under an "Ask first" line only after the user approves that exact command; if your credentials do not allow it, give it to the user to run. Never run a "Proposed fix"; hand it to the user.
Fluent Bit runs as a DaemonSet: on every node a tail input reads the container log
files under /var/log/containers/, the kubernetes filter adds pod metadata from the
API server, and outputs send the records to a backend (Elasticsearch, Loki, an HTTP
endpoint, a forwarder). Its own log names each part as [input:tail:tail.0],
[filter:kubernetes:kubernetes.0], [output:http:http.0], so the log usually names the
cause. The Helm chart keeps the config in a ConfigMap (fluent-bit.conf); the Fluent
Operator builds it from custom resources into a Secret.