Ability to restore log levels

[oscarfh]

As a user, I want to be able to restore log levels, so everything is back to how it was configured when the service started

Notes:

• If someone else made some change before I open the UI and I reset, everything is back to what it was configured
• The original value is the value in the "configured" field for each logger

[survivant]

I'll add this. Be able to store the logs levels in json file on disk. When the application start, this extension load the file if the file is present. If the file is not present or deleted.. we have the default value.

We have that feature in our "Springboot" application and we need to have that in Quarkus too. We are using Kubernetes with Persistent volumes, so when the pod restart we don't loose our logging levels.

[phillip-kruger]

The idea here is to allow changing of log levels in runtime (like we currently do) then with one button restore to what the levels was.
To permanently change log levels, you can use application.properties.

[survivant]

The goal is not to have to modify the code. Suppose you want to trace something live. You could set the logs to trace level live, kill the pod and check the results. You dont want to package you application again. Le lun. 8 mars 2021 04 h 15, Phillip Krüger <[email protected]> a écrit :

…

The idea here is to allow changing of log levels in runtime (like we currently do) then with one button restore to what the levels was. To permanently change log levels, you can use application.properties. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#40 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABO3B2G6GA3LN75BYZPMCLTCSIRLANCNFSM4WJJD7NA> .

[phillip-kruger]

Well, that seems to be more a config issue than a logger-manager.
The way to configure logging in Quarkus is via config, you might want to then look at an external ConfigSource that you can change without having to repackage the application.