You can add a selection of filters to your Real User Monitoring data, to surface the most useful information. So that you can sort through data faster and be reassured you address performance problems affecting your end users as quickly as possible. (Real User Monitoring filters are automatically added to your account; there’s no need to set anything up.)
Once applied, the filters will pitvot the data on all Real User Monitoring tabs (except the live tab) to show you only the information that conforms to your filters.
Here are the filter types that you can use:
You can use the anonymous user filter to ignore traffic from hackers and bots. This ensures that you can focus on monitoring the user experience of your most important customers by ignoring irrelevant traffic.
Browser and browser version
Browsers have fewer compatibility issues and more features than ever before, therefore performance can vary significantly for your end users. (If you’re unfamiliar with browser monitoring, read this article.) If you’d like to offer a more consistent customer experience across your most popular browsers, use this filter to drill down. This screenshot shows the performance for Chrome version 4.0.2:
The country code filter and Geo tab will help you identify which countries are having a slow average load time. You could also filter all other countries and drill down into the problems on each page. You could also filter all other countries and drill down into the problems on each page:
Use this filter to deliver a more consistent experience across devices for your end users. For example, this filter makes it easy to compare experiences between the Samsung Galaxy Note and the iPhone 7s.
You can use this filter to see specific operating systems and isolate problem pages on each operating system. For example, your development team may find it useful when testing, to filter out Desktop and Mac, to discover if other operating systems are experiencing poor performance. Filtering by an operating system is also a good way to get a performance snapshot of your mobile users.
Tags is a popular feature for Raygun customers, you can add tags to your code when you are sending data into Raygun. For example, tag high priority customers and filter them in Raygun Real User Monitoring to get a better cross-section of how your VIPs are experiencing your application. The screenshot below shows data that has excluded all tags containing “Test”:
Filtering by URL is helpful when you have a lot of external scripts running in your application that you’d like to ignore. Simply set your filter to “contains ‘yoursite.com‘” to eliminate third party scripts. Filtering by URL is also useful when you need an accurate performance cross section of your website. For example, say the URL you would like to check ends in “/store”. Real User Monitoring filters will isolate the performance of your store page (shown below). You may also like to use this filter as an alternative to setting up multiple applications, as you could just filter them out as needed.
Use this filter to understand how the latest deployment has affected end users. Roll back between version numbers to isolate a performance issue and determine which version caused the problem. In the screenshot example below, the child requests are the biggest culprit on this page: