It's always fun when the app is crashed by a... logger

I was told that if the DB credentials were incorrect that it has to connect to the database and log the error.

What. The. Actual. Duck.

At work we have a central logging server but also always log to stdout.
As our team actively removes noise this works nicely without impact. Did have an instance where sending the logs was sore l so slow (network issue) that there was internal resource usage buildup and it killed the service anyway. At least that was visible.

Never seen that happen. Did someone make logging a part of the main loop somehow?

I mean, I've seen that done for auditory purposes in systems where all actions had to be logged or otherwise they were supposed to fail. But how do you do that not on purpose?