How excessive production logging can bury signal, increase cardinality, distort incident timelines, and make debugging slower even when every service appears well instrumented.
Tests can pass while production still breaks when the suite proves the intended path but misses retries, concurrency, dirty data, rollout state, or ambiguous dependency behavior.
Why some bugs appear only under production load, how concurrency, data shape, queues, retries, and partial failures change behavior, and how to diagnose them without guessing.