I would generally agree with that. Happy for the feature but it would probably be cleaner to have an enable/disable toggle. Keeping the current implementation in mind, the log size boxes could still be kept but perhaps with some good default values already filled in for when persistent logging is enabled. Then they can be tweaked as needed.
I’ve always wondered if it would be better if the controller (cloud or local) should essentially act as a syslog server to allow logs to be viewed if the equipment is down but the controller is still operational (in theory anyway). Especially now that the controller can basically ingest and display logs.
Getting a little farther afield and what to do when the controller isn’t available, then there’s the thought of being able to use the Bluetooth that’s built into pretty much everything as a console port or out of bound management like mentioned here: Console (serial) port for OOB management - #2 by jack