UI - fix operations new empty logger

[thfries]

Hi, please find this PR to fix #1809

@thjaeckle: btw: don't we need an option to delete a logger, too?

[thjaeckle]

@thfries when I remember correctly, deleting a logger or setting its log level to OFF was problematic.
At least not all off loggers could be queried and displayed, because the logger api Ditto uses would return for log level "off" basically all loggers which don't have a defined log level.
And those are thousands.. 😕

Or did you mean something else?

[thfries]

I was testing to create new loggers like "foobar" (which is invalid, too) and was not able to "undo" that operation. In general you can create additional loggers but there is no way to undo.
Log level "OFF" is currently not available in the UI.
May be this is exactly what I mean: if you would set the log level to "OFF" it would disappear from the list? We could show a confirmation modal in this case.

[thjaeckle]

I was testing to create new loggers like "foobar" (which is invalid, too) and was not able to "undo" that operation. In general you can create additional loggers but there is no way to undo. Log level "OFF" is currently not available in the UI. May be this is exactly what I mean: if you would set the log level to "OFF" it would disappear from the list? We could show a confirmation modal in this case.

Yes, that is a good idea:

• make "off" configurable as log level
• show a confirmation that - in order to show/activate the logger again - it must be explicitly added as a new logger again

[thjaeckle]

LGTM 👍

@thfries do you also want to address the "off" logger in this PR, or not for now?

[thfries]

@thjaeckle, let s make it separately.