If you run flow in debug mode, the debug level will be changed to DEBUG instead of INFO. It shouldn't be a hard thing as you should already have the dotnet sdk installed. All you need is to clone flow and run it with whatever ide you used.

thanks, but it will be more convenient if we can set it just in settings rather than run another debug version, hope it will be added in the future.

thanks, but it will be more convenient if we can set it just in settings rather than run another debug version, hope it will be added in the future.

making sense.

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@taooceros is this still an issue we need to keep fresh?

Well, fell free to close it if not planed.

It's not that easy to change. Logger is initialized at the very beginning. Maybe we can set to debug for default, after loading settings than set it to user defined level?

Is this a hard task??? It doesn't matter if it doesn't reflect in real time. I think we could just put "loglevel" in config and apply it after restart, or even set it directly in json without a config ui. Am I thinking wrong?

+)#2313 jjw's comment confirms that the debug log itself is meaningless. It is more correct to provide logs to make it easier for plugin developers to work with.

It's not that easy to change. Logger is initialized at the very beginning. Maybe we can set to debug for default, after loading settings than set it to user defined level?

Set it to 'Error' level as default, allow the change to 'Debug', request a restart of flow after the change if makes it simpler.