Let’s review the steps that Gerald took to identify and analyze the issue, and learn which metrics he looked at on both the end-user and server sides. And, because not everyone is fortunate enough to have an expert like Gerald in their team, we show you how Dynatrace automates these steps through our Problem Pattern Detection and with Artificial Intelligence.
The impact was seen across every browser and every geo location. So it was not something that they simply missed in testing, nor was it a problem related with connection or timeout issues in a certain geo location.
The Problem: Object not found errors
Root Cause: Slow CDNs caused by bad CRON job
Gerald’s next step was to drill down to some of these real end-user browser sessions. He wanted to see whether there was anything else abnormal about them. Turns out that most of these users had one thing in common: a very slow responding CDN Server:
CRON Jobs to be blamed
Better rely on Dynatrace in case Gerald is not there for you!
First: Hats off to Gerald for doing a great job digging through the Dynatrace AppMon data. Also, thanks for sharing the dashboards which are useful when dealing with CDNs or 3rd parties.
While Dynatrace AppMon collects all this data to make troubleshooting of these problems easier, it requires you to know how to navigate the data. Because of scenarios shared by Gerald and others over the years, we have made significant investment in automating error, problem and root-cause detection.
In the latest versions of Dynatrace AppMon (sign up for your lifetime AppMon Personal License) we automate problem pattern detection, and highlight the “Top Findings” for both End-User and Server-Side Performance Hotspots in the Dynatrace AppMon Web Interface:
In the Dynatrace SaaS/Managed platform (sign up for our Dynatrace SaaS trial) we went a step further by running all this data through our Artificial Intelligence Engine. A problem like the one Gerald detected would pop up in a Problem Ticket, and include the information on the Impact and Root Cause. This allows you to analyze and fix these problems, even if you don’t have an expert like Gerald on your team. It just means that you can spend more time on innovating, rather than bug hunting.
If you have stories like this one that you want to share with your peers, please let us know. Send me an email to Share your PurePath or your Best Artificially Detected Problem Pattern.