- Page Load View
- Trace View Integration
- Geographic Data
Website monitoring, often called End-User Monitoring (EUM), or Real-User Monitoring (RUM), is an important tool to understand digital user experience.
Instana supports website monitoring by analyzing actual browser request times and route loading times. It allows detailed insights into the web browsing experience of users, and deep visibility into application call paths.
Loaded asynchronously into the website, the agent reports 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. The dashboards help explore behavior and speed of websites. They are accessible to a wide audience and to answer the most common questions. More specific questions and hypotheses can be answered by using analyze capabilities.
The following screen capture shows collected data for a page load, which combines a user's browser activity and links to backend tracing.
If you want to use website monitoring with Wordpress, use the WP Instana EUM plug-in.
For more information about Wordpress, see What is Wordpress.
In the speed tab you can view the throughput, latency, and metrics that describe page load times.
Third-party resources, like scripts and images, are often responsible for slow page loading. On the resource tab, you can find a table that shows you all the resource providers that are actively used by your website.
After you click a specific origin, you can see more detailed information, including load time breakdowns and caching performance. You can see changes in caching statistics over time and how it relates to loading times.
Errors can occur in critical processes. For example, in a process to checkout purchased items in an online storefront, duplicate charge payment errors might occur. As a result, the customer can be dissatisfied and the business needs make provisions such as to process a credit card refund.
Although 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. In the Instana UI, you have the complete error breakdown, with the following information:
- What errors are occurring and how many errors exist
- Number of affected users
- In which browsers the errors occur
- In which operating systems the errors occur
- In which pages the errors occur
On the HTTP Requests tab, you can analyze which of your HTTP requests are slow or problematic. If you select a specific origin, you see an insight into HTTP Method Breakdown, throughput and latency, and error rates and latency breakdown.
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 you select a specific page, you can see all the metrics just for this single page.
View a list of all your configured Smart Alerts. Click an alert to view its configuration, modify it, or view its revision history. If required, you can also disable or remove the alert.
For more information about how to add an alert, see Smart Alerts.
Beacon data can be used to filter and group. The default grouping depends on the selected beacon type. Grouping can be removed to inspect the individual beacon that match filters.
Within the grouped analytics view, beacon data is grouped by a certain tag. By default, beacon data is grouped as follows:
- Page loads by page name (
- Resources by resource origin (
- HTTP requests by call target origin (
The following screen capture shows page loads grouped by browser name (
beacon.browser.name), with a chart that is displaying the distribution of page load times (mean) across browsers for a website called Robotshop.
The analyze table shows a default set of metrics for every beacon type that are helpful in most cases. To answer more specific questions, Instana supports the selection of metrics for these tables. The selection of metrics enables analysis by using different aggregations, for example percentiles, and separate metrics, like the TCP/SSL times.
The combination of filtering, grouping, metric selection and charting is enough that all the tables and charts that are found within the website dashboards can be rebuilt in the analytics view.
The ungrouped view is accessible after the grouping criteria is removed. It lists every beacon that matches the provided 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 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 much data. Even navigation to backend traces is possible to gain a full understanding why something is behaving the way that 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 screen capture shows.
Instana maps end-user IP addresses to geographic details based on GeoLite2 database, which is provided by MaxMind. The IP addresses are collected by using the reverse proxy server. For the self-hosted installation, make sure that you configure the URL of the end-user Monitoring endpoint as the agent reporting URL. Otherwise, the IP addresses are not collected, and the related geographic details information is not available.