yes. I had the same though and have been running test code that disables everything. It’s a workaround though since, even in production, we want to know when critical errors occur. We just can’t risk seeing log floods like this so I’ll likely have to disable by default and loose any field error reporting… which is the purpose of the logging system!!
Note that setting log levels before all the log backends are active won’t work because they will activate at their default level after you tried to disable them. I saw this and reported it in Log filtering not working for one module.
I’m calling it from the Golioth on_connect function now.