Not every error needs a stacktrace about authelia

[glime-ai]

Please note this response was created using generative AI leveraging previously available information from the repository. This information may be helpful however it is our strong recommendation that you carefully consider the information before blindly applying it.

---

To address the issue of overly noisy log formats due to stack traces for configuration errors in Authelia, it's important to understand that Authelia's logging behavior, including error reporting and stack traces, is part of its design to aid in troubleshooting. However, based on the context provided, there isn't a direct mention of a feature to disable stack traces for configuration errors specifically.

The logging configuration in Authelia allows for adjusting the verbosity of the logs through the log_level setting, which can be set to trace, debug, info, warn, or error. Setting this to a higher level like error would reduce the amount of logged information, but it would not selectively remove stack traces while keeping the error messages intact as you've described. The documentation does not explicitly mention the ability to disable stack traces for configuration errors without affecting other types of errors.

Given this, the best course of action would be to adjust the log_level to control the verbosity of the logs to some extent. For more granular control over logging output, such as removing stack traces for configuration errors while keeping them for actual program errors, you would likely need to request this feature directly from the Authelia team. This could be done by creating an issue on the Authelia GitHub repository, explaining your use case and how this feature would benefit users.

For immediate relief from the noisy logs, reviewing and fixing the configuration errors as indicated by the error messages would be advisable. The error messages you've shared are quite descriptive and should guide you in correcting the configuration issues.

Remember, the logging and error reporting mechanisms are designed to assist in diagnosing and troubleshooting issues effectively. While stack traces can be verbose, they often provide valuable context for understanding the root cause of errors, especially in complex applications like Authelia.

This comment was generated by Glime.

[james-d-elliott]

While in this instance the errors are fairly noisy and unnecessary they are critical during normal operation to isolate causes of unexpected errors. Adding a specific rule for these may be possible but may however add unnecessary complexity for a fairly small gain. We can however look at it depending on user feedback so I'll convert this to an idea.