![]() ![]() CWV are heavily tied to the user experience, with a focus on the perception of how a page loads. Google introduced the Core Web Vitals (CWV) last year, and they’ve fast become the metrics to prioritize when improving the user experience. The second thing that stood out to me on the Performance tab was the inclusion of Web Vitals (and more specifically, Core Web Vitals). This would have helped with identifying the cause of spikes (for example, if I merged a deployment at 1pm, I would have no way of knowing if the spike on this graph was related to the deployment at 1pm). Personally, I would have liked to see an x-axis on these three graphs, regardless of knowing that it’s one day worth of data based on the time picker in the top right corner. The top of the page is populated by page loads (good for monitoring traffic), load time (a staple for anyone measuring performance), and errors (another staple for any developers wanting to keep an eye on the health of their application). This seems like a good place to start with our investigation! When clicking into my application, you’ll be taken directly to the ‘Performance’ tab. If you like the design of the rest of the suite of AWS tools, you’ll like the look of CW RUM. I won’t comment too critically on the UI/design, as I’m acutely aware that AWS has their own standards and protocols around how everything has to look. Now that my application has been populated with enough traffic from real users, I can finally do what we’ve all been waiting for – click in and see what information they have for us. Time to grab a glass of wine, kick up my feet… First impressions Now that we’re all set up, it’s time to play the waiting game until data gets piped through. Ok, now we’re getting somewhere! Time to add our code snippet to the element of our application. For now, we’re going to leave the optional settings. Next, we set up our authorization settings and configure pages, set up tracing, and add tags. However, for the most part, you’ll want to get complete visibility into how your users are experiencing your application by selecting 100%. ![]() If you’re a price-sensitive team, this option can provide a lot of value, giving more autonomy over your bill. Since we’re working with a site that has a fairly low amount of traffic, we’re going to keep this option at 100%. Next, we’re asked to select what % of sessions we’d like to sample and analyze. For the RUM aspect of their solution, you only really need to select ‘Performance telemetry’, but let’s select all three regardless to see what they’ve got. It’s worth noting that CW RUM only works for web applications, so the data collected is relatively limited with the option to select performance telemetry, JavaScript errors, and HTTP errors. Next, we configure how data gets collected. First you have to select which app to monitor (giving it both a name and domain). Setting up CW RUM was a fairly simple process. I have attempted to be as objective and impartial as possible while writing this review, but naturally, I will have implicit biases and opinions around what makes a ‘good’ RUM solution. * Disclaimer: Before we jump in I would like to point out that I am an employee of Raygun, which has its own Real User Monitoring solution. ![]() Now we’ve got that out of the way, let’s check it out! Before we get started, though, let’s try shortening the name, because none of you want to hear me say ‘AWS CloudWatch Real User Monitoring’ any more than I have to. Today, we’re going to install AWS CloudWatch Real User Monitoring and try it out for ourselves. We’re excited to see what new ideas and functionality Amazon brings to the industry, and what direction they see RUM taking in the future. With Raygun having its own established Real User Monitoring solution since 2015, we like to think we know a thing or two about what makes a good Real User Monitoring tool. As you can imagine, our ears perked up at this announcement and we’re eager to take a look. Real User Monitoring for Amazon CloudWatch was announced at AWS re:Invent 2021, adding to their existing suite of over 200 products and services. It’s not every day that we see a new player enter the market, but last week we did, and a very powerful player at that – Amazon. Real User Monitoring (RUM) has been providing valuable insights into real user experiences for many years. A first look at Amazon CloudWatch Real User Monitoring By Jamie Birss | Posted | 9 min. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |