Dump Internals / Signal

    Fluent Bit v1.4 introduces the Dump Internals feature that can be triggered easily from the command line triggering the Unix signal.

    {% hint style=”info” %} note: this feature is only available on Linux and BSD family operating systems {% endhint %}

    Run the following kill command to signal Fluent Bit:

    Fluent Bit will dump the following information to the standard output interface (stdout):

    1. [engine] caught signal (SIGCONT)
    2. [2020/03/23 17:39:02] Fluent Bit Dump
    4. ===== Input =====
    5. syslog_debug (syslog)
    6. ├─ status
    7. │  └─ overlimit     : no
    8. │     ├─ mem size   : 60.8M (63752145 bytes)
    9. │     └─ mem limit  : 61.0M (64000000 bytes)
    11. ├─ tasks
    12. │  ├─ total tasks   : 92
    13. │  ├─ new           : 0
    14. │  ├─ running       : 92
    15. │  └─ size          : 171.1M (179391504 bytes)
    16. │
    17.    └─ total chunks  : 92
    18.       ├─ up chunks  : 35
    19.       ├─ down chunks: 57
    20.       └─ busy chunks: 92
    21.          ├─ size    : 60.8M (63752145 bytes)
    24. ===== Storage Layer =====
    25. total chunks     : 92
    26. ├─ mem chunks    : 0
    27. └─ fs chunks     : 92
    28.    └─ down       : 57

    The dump provides insights for every input instance configured.

    Overall ingestion status of the plugin.

    The Task dump describes the tasks associated to the input plugin:

    The Chunks dump tells more details about all the chunks that the input plugin has generated and are still being processed.

    Depending of the buffering strategy and limits imposed by configuration, some Chunks might be up (in memory) or down (filesystem).