Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for custom log levels #35

Open
tibersept opened this issue Nov 16, 2022 · 1 comment
Open

Support for custom log levels #35

tibersept opened this issue Nov 16, 2022 · 1 comment

Comments

@tibersept
Copy link

Mapping custom log levels to a default level (whether DEBUG, INFO or other) breaks tool chains in complex projects. With DEBUG as default, production environments are forced to that level of logging for some packages, when the custom log levels cannot be avoided.

Some SPI handling or even manual introduction of custom log levels could improve the behavior of the LevelTranslator for such cases.

@jamezp
Copy link
Member

jamezp commented Nov 1, 2023

My apologies for just now seeing this. I've got no idea how I haven't noticed this in nearly a full year.

If it's not way too late, can you give an example of how you create custom levels? This project is typically used in WildFly and JBoss EAP where custom levels are not supported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants