What is a default setting that ended up causing unexpected troble for you?

by

We almost ran into a major incident recently because a new service silent inherited a production config without anyone explicitly setting it. Because everything seemed to be working normally, nobody realized logging was completely turned off until weeks later.


It made me realize how dangerous "smart defaults" can be when they hide implicit decisions.


Have you ever been burned by a default config that seemed convenient until it silently broke something?

2 views

Add a comment

Replies

Be the first to comment