Our elections are a wee bit more important than a router. AZ auditors don’t even have access to the routers yet so this log is inside a voting machine, scanner or tabulator. Like I said, storage is dirt cheap and tiny. Code to create multiple sequential files is easy. There’s no good reason to not store every bit of logs from start to finish in an election. I don’t think these logs were for troubleshooting but were for logging who accessed the system and when — activity log. Different situation.
Dominion was first designed to steal elections in Venezuela. Every design flaw is no flaw at all. They are by purposeful for cheating. Dominion employees were the only people who had admin access to be able to run a script and fill that log file with nothing useful.
There’s no good reason to not store every bit of logs from start to finish in an election.
As for the device’s log size, it usually competes with all the other uses for memory, so there are tradeoffs between logging and those other uses. You don’t ever want to use all available memory. Some communications devices erase those logs entirely every time they restart, so that they exist at all here on devices which have been turned off, and are 20MB in size, is rather good. Again, this is just the local copy.