> used Spring's AOP to inject performance and usage logs across entire chunks of the program. It worked great and took way less time than scheduled. There was

> used Spring's AOP to inject performance and usage logs across entire chunks of the program. It worked great and took way less time than scheduled. There was the guy who used AOP to inject logging and perf, and set it to "instrument every method". _Every method_. It was Ok in test, but when the production load rose to the daily peak, the volume of logging data was in itself sufficient to saturate a network and requests got dropped. Including health checks, which caused machines to be taken out of the load balancer, increasing load on the survivors. Autoscaling didn't help, new machines came up with the same issue. The failure cascade brought down the entire service. True story.