How to Check for Fluent Bit Internal Errors

Better Stack Team

Updated on August 5, 2024

To check for internal errors in Fluent Bit, you should set the Log_Level option in the [SERVICE] section to debug:

fluent-bit.conf

Copied!

# Service Section
[SERVICE]
    Flush        1
    Daemon       off
    Log_Level    debug
...

When you restart Fluent Bit, you will see logs with internal errors and debug information:

Output

...
[2024/08/05 10:55:05] [debug] [out flush] cb_destroy coro_id=230
[2024/08/05 10:55:05] [debug] [task] destroy task=0x7f5439e76020 (task_id=0)
[2024/08/05 10:55:07] [debug] [input:tail:tail.0] inode=266432, /var/log/logify/app.log, events: IN_MODIFY

To continue learning about Fluent Bit, see the Beginner's Guide to Fluent Bit.

Got an article suggestion? Let us know

Explore more

How to Truncate Long Logs in Fluent Bit

Questions

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

How to Truncate Long Logs in Fluent Bit

To truncate logs in Fluent Bit, the easiest option is to use a Lua script. Assuming you have the following log entry from an application: {"status": "200", "ip": "127.0.0.1", "level": 30, "emailAdd...

Questions

Make your mark

Join the writer's program

Are you a developer and love writing and sharing your knowledge with the world? Join our guest writing program and get paid for writing amazing technical guides. We'll get them to the right readers that will appreciate them.

Write for us

Writer of the month

Marin Bezhanov

Marin is a software engineer and architect with a broad range of experience working...

Build on top of Better Stack

Write a script, app or project on top of Better Stack and share it with the world. Make a public repository and share it with us at our email.

community@betterstack.com

or submit a pull request and help us build better products for everyone.

See the full list of amazing projects on github