Website monitoring, often called End-User Monitoring (EUM) or Real-User Monitoring (RUM), is an important tool to understand digital user experience.
Loaded asynchronously into the website, the agent will report its findings to Instana in the form of beacons. This beacon data can be found in an aggregated form within the website dashboards in the Instana UI. These dashboards help explore behavior and speed of websites. They are designed to be accessible to a wide audience and to answer the most common questions. More specific questions and hypotheses can be answered via the analyze capabilities.
The following screenshot shows collected data for a page load. Which combines an end-user’s browser activity and links to backend tracing.
If you want to use website monitoring with Wordpress, you can use our WP Instana EUM Plugin.
The speed tab focuses on the throughput, latency, and metrics that describe page load times.
Third-party resources (like scripts and images) are often responsible for slow page loads. With our new resource overview, you will find it much easier to identify slow resource providers.
Broken down by origin, this table shows you all the resource providers that are actively used by your website. Clicking on the origin will reveal more detailed information including load time breakdowns and caching performance. Users can see changes in caching statistics over time and how this relates to loading times.
Uncaught errors can have a large impact on a business. This is especially true for critical processes such as checkout of purchased items in an online storefront. Errors here can often cause dual purchases, resulting in dissatisfied customers who now have to deal with credit card refunds.
While seeing uncaught errors in traces is helpful, sometimes you don’t care about a single issue. When many teams are involved, or many errors occur, it is much more useful to get an overview of the situation. This is where the error breakdown is helpful. This breakdown is located in the website dashboard and helps you understand the following:
- What types or errors are occurring, and how many are there?
- In which browsers do they occur?
- On what pages do they occur?
Learn which of your HTTP requests, i.e. requests issues via the
fetch APIs, are slow or
problematic. Selecting a specific origin provides insight into throughput and latency, as well as error rates and
Often it’s important to isolate specific pages and analyze their performance. This view is also a great one to find your page with the most traffic, or the slowest response times.
After selecting a specific page, you see all of the metrics just for this single page.
Beacon data can be used to filter and group. Filters are connected with AND logic operator so a beacon needs to match all the filters. The default grouping depends on the selected beacon type. Grouping can be removed to inspect the individual beacon that match filters.
Within the grouped analyze view, beacon data is grouped by a certain tag. By default, we group…
- page loads by the name of the page (
- resources by resource origin (
- HTTP requests by call target origin (
The following screenshot shows page loads grouped by browser name (
beacon.browser.name) with a chart visualizing
page load time (mean) distribution across these browsers for a website called Shop Shop.
The analyze table shows a default set of metrics for every beacon type that are helpful in most cases. To answer more specific questions, we support the selection of metrics for these tables. This enables analysis using different aggregations, e.g. percentiles, as well as completely separate metrics, e.g. TCP/SSL times.
The combination of filtering, grouping, metric selection and charting is so powerful that almost all of the tables and charts found within the website dashboards can be rebuild in analyze!
The ungrouped view is accessible once the grouping criteria is removed. It lists every single beacon that matches the given filters. The ungrouped view is also the gateway to the page load view.
Page Load View
Similar to the trace view for traces and calls, the page load view is the highest detail level within Instana. A page load is defined as the retrieval of the initial HTML document and everything that follows after that until the next full-page navigation.
The page load view is modeled after common web developer tools’ network tabs. Filtering and searching is possible to handle even a lot of data. Even navigation to backend traces is possible to gain a full understanding why something is behaving the way it is!
Trace View Integration
Enabling website monitoring for your websites also enhances the trace views. The trace views are enriched with website monitoring data as the following screenshot shows.