Challenge: "Hundreds of machines, hundreds of logs"
Novus's engineering team built a platform responsible for mission-critical performance. As the Novus architecture began to grow, the team responded by scaling its platform into various internal services.
Isolating the responsibilities into decoupled services helped the team reach the scalability demands required by its growth. As Novus' environment grew in scale, the method in which it would diagnose problems did not; using logs to diagnose application and performance issues quickly proved to become tedious, difficult, and unreliable. "Previously, Novus was entirely log driven - hundreds of machines, hundreds of logs," says Brian KimJohnson, Software Engineer at Novus.
Furthermore, associating a particular user to the correct log data to remedy the flawed user experience proved to be difficult. Noah Zucker, Software Engineer at Novus, recalls, "The best example of this that stands out in my mind is we had a case where, for some reason, our entire platform was grinding to a halt." Noah and his team could not diagnose swiftly enough why the user was plagued with the issue and, unfortunately, as a result, "the user was taking down one server after another. We could not keep up with the speed in which we were experiencing problems," says Brian. "That is an example of an issue that we would now solve in minutes, thanks to AppDynamics."