Skip to content

Plugin's log saturation #1996

@matthieumarrast

Description

@matthieumarrast

We temporary set the log level to "DEBUG" in our mfdata module, in production environment, in order to help us solving a critical issue.
But one plugin stopped functionning because the log files reached the limit (100M/5 files)

-rw-r--r-- 1 mfdata metwork 100000000 19 nov.  21:53 step_<plugin>_main.log
-rw-r--r-- 1 mfdata metwork  94079566 19 nov.  20:38 step_<plugin>_main.log.20241119203825
-rw-r--r-- 1 mfdata metwork  94129569 19 nov.  20:58 step_<plugin>_main.log.20241119205820
-rw-r--r-- 1 mfdata metwork  94177526 19 nov.  21:18 step_<plugin>_main.log.20241119211815
-rw-r--r-- 1 mfdata metwork  95796003 19 nov.  21:33 step_<plugin>_main.log.20241119213342

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions