You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 27, 2025. It is now read-only.
When an event is received (either from Discord or Lavalink), a log message with the DEBUG level is generated to indicate that the event is about to be processed. Once processing is complete, another log message is emitted to indicate that the event has been processed. The log level of this final message depends on the time taken to process the event: it is INFO if the duration is below a certain threshold, and WARN if it exceeds that threshold.
I suggest changing the log levels: use DEBUG instead of INFO, and INFO instead of WARN, to reduce the volume of logs in production environments.
Additionally, I recommend enabling DEBUG-level logs in release builds, stripping only TRACE-level logs.
When an event is received (either from Discord or Lavalink), a log message with the DEBUG level is generated to indicate that the event is about to be processed. Once processing is complete, another log message is emitted to indicate that the event has been processed. The log level of this final message depends on the time taken to process the event: it is INFO if the duration is below a certain threshold, and WARN if it exceeds that threshold.
I suggest changing the log levels: use DEBUG instead of INFO, and INFO instead of WARN, to reduce the volume of logs in production environments.
Additionally, I recommend enabling DEBUG-level logs in release builds, stripping only TRACE-level logs.