In the early days of an application, deploying new features and functionality are at the top of the list. As the number of users grows and the traffic increases, other issues make their way to the forefront. Whether because of complaints from users, monitoring alerts about overloaded machines, or even a whopping AWS bill, it becomes important to be able to answer the question, "What is my application truly spending our servers' CPU time and resources doing?"
