Jay Cui
08/18/2025, 7:23 PMsystemctl status fluent-bit.service. And I got the following output in the terminal:
root@dev-server:~# systemctl status fluent-bit.service
ā fluent-bit.service - Fluent Bit
Loaded: loaded (/lib/systemd/system/fluent-bit.service; disabled; preset: enabled)
Active: inactive (dead)
Docs: <https://docs.fluentbit.io/manual/>
root@kilogram-dev-1:~#
As soon as I started Fluent Bit by running systemctl start fluent-bit.service, I could start seeing metrics coming into my Grafana dashboard. This was really surprising to me, as I never stopped Fluent Bit in those VMs.
So here's my question: What are some possible reasons why Fluent Bit would stop on their own?Pat
08/18/2025, 7:40 PMJay Cui
08/18/2025, 8:30 PMerror, the most recent log I'm seeing is from 8/6/25, which is way before the death of the Fluent Bit agent. Here's a snippet of my `/etc/fluent-bit/fluent-bit.conf`:
[SERVICE]
Flush 1
Log_Level error
Log_File /var/log/fluent-bit/fluent-bit.log
If you were me, in order to catch future deaths like this, what would you set the log level to instead?
Fluent bit wasn't stopped by anyone, since I've been the only person working on it. My teammate said the VMs didn't get restarted, but I'm going to review the Google Cloud audit logs to see what those VMs went through exactly.
It looks like the Fluent Bit version is v4.0.4 in one of those VMs, but the latest version is v4.0.7. I'll go ahead and update it right now. Pat
08/22/2025, 2:35 PMPat
08/22/2025, 2:35 PMJay Cui
08/26/2025, 5:08 PM