Early Twitter was an adventure. Every day was an open question: would you be able to log in or did the next big story crash the platform? It was taking off and crashing and flying and crashing again. All in real time. It was an exciting time for the internet, and while everything has changed since then it got us thinking: why did we used to tolerate stuff just not working? And why do we still tolerate stuff not working?
What if I told you one of the most common mistakes businesses make is reporting on website performance without understanding user experience? What if I said there was much more to website performance monitoring than simply alerting you when your site is experiencing a downtime outage? No two websites – or baselines – are exactly the same.
One of the most challenging and rewarding things I do as a Principal Software Engineer in our Splunk Mobile division is ensuring our customers’ experience meets the quality and standards we promise to keep. My team and I are part of an on-call rotation that is committed to measuring and optimizing key Service Level Indicators (SLIs) using Splunk Real User Monitoring (RUM) and Splunk On-Call (iOS & Android) mobile apps.
After the global pandemic and lockdowns, most businesses look onward to online solutions for their applications. They want to take their business online by creating mobile or web applications. Companies are looking to monitor every aspect of the application, including deployment, bugs, API failures, etc. But the most important thing is how the application behaves when it goes into the hands of the end-users.