This document contains references to third-party documentation. Cisco AppDynamics does not own any rights and assumes no responsibility for the accuracy or completeness of such third-party documentation.
Onboard Browser Real User Monitoring Applications
- From the Platform Home page click Cisco Digital Experience Monitoring.
- From the Configure left-navigation, click Browser Applications.
- Click Create.
- Define the application by adding:
(Optional) If you are subscribed to the Session replay feature, you can capture user sessions for replay. See Session Replay.
- Use the agent hosted in the Content Delivery Network (CDN), or download the agent and ensure that it is available on your servers.
- Click Save and continue.
Copy the example code command and paste it in the
<head>tag of the HTML page that you want to instrument.
<YOUR-TENANT-NAME>is auto-filled with your value. Your code snippet can vary depending on your version, application name, and tenant name.
- Click Done.
Set Up Health Rules and Alerting
On the Health and Alerting panel, you can create new health rules, or view details on existing health rules that have been created. There are default health rules that are turned on for Base Pages, Virtual Pages on End User Response Time (EURT), Web Vitals, Ajax, and Iframes. See Browser Real User Monitoring Metrics for information on Web Vitals. You have the option to modify and turn-on default health rules. See Create Health Rules to Monitor Entities or Group of Entities.
It's recommended that you review default health rules to ensure that they meet your needs. You can adjust health rule thresholds to suit the needs of your organization.
Critical and Warning Conditions
Conditions are classified as either critical or warning conditions. Critical conditions are evaluated before warning conditions. If you have defined a critical condition and a warning condition in the same health rule, the warning condition is evaluated only if the critical condition is not true. The configuration procedures for critical and warning conditions are identical, but you configure these two types of conditions in separate panels.
You can copy a critical condition configuration to a warning configuration and vice-versa and then adjust the metrics in the copy to differentiate them. For example, in the Critical Condition panel you can create a critical condition based on the rule:
- If the
Request Countis greater than 40
Then from the Warning Condition panel, copy that condition and edit it to be:
- If the
Request Countis greater than 35
As performance changes, a health rule violation can be upgraded from warning to critical if performance deteriorates to the higher threshold or downgrades from critical to warning if performance improves to the warning threshold. See Health Rule Evaluation Conditions.
Health Roll Up
You can aggregate (rollup) the health of the entities to define the health of a group of entities. This means a child entity can define the health of a parent entity by rollup relationship. You can define the health rollup relationship between the entities and the parents. By default, when a page is unhealthy, the application that the page belongs to will not be unhealthy; unless its own health rule is violated.
View Relationships Panel
This section covers navigation through the Browser RUM module. When you click an entity symbol on Observe and the screen refreshes, Relationships displays. The relationships between all objects of the entity type you selected on Observe and all other related entities displays in list views. If you select an object from a list view, Relationships depicts the relationships between that object and all other related entities which displays in the detail view. See Relationships Panel.
You can view the following entities on the Relationships panel:
The Browser Applications page provides these details:
When you click on a specific Browser Application, you can view:
Using Pages allows you to toggle between Base Pages, or Virtual Pages. In this section, you can view:
When you click on a specific Page, you can view:
The Iframes page provides these details:
Using Iframes provides a summary of key performance indicators, which include:
The Ajax page provides these details:
When you click on a specific Ajax, you can view:
Visualize Core Web Vitals and EURT Component Timing
Google Core Web Vitals is a set of metrics that measure the real-world user experience for loading performance, interactivity, and visual stability of the page. In Browser Real User Monitoring, Web Vitals include the following metrics:
- Largest Contentful Paint (LCP).
- First input Delay (FID).
- Cumulative Layout Shift (CLS).
Google refers to Core Web Vitals as one of the signals to rank the webpages so you may require to maintain a healthy metrics for your website that improves the SEO ranking and drives user traffic. For more information, see Core Web Vitals.
The following graphs visualize Web Vitals, and EURT Component Timing in Browser Real User Monitoring.
To see the Web Vitals graph:
- Go to Browser Applications, and click on a specific application.
- Go to Pages, and click on a specific page name.
To see the EURT Component Timings graph:
- Go to Pages, and click on a specific page name.
- Go to Iframes, and click on a specific Iframe name.
You can use filters to refine your view to display only the entities and data you are interested in. You can filter by:
- Attributes (all lists except Observe List)
- Entity Status
- Entity Type (Observe List only)
From the Observe and list views, you can use grouping to display only the data you are interested in, by groups. This provides the ability to group using Group View or shortcuts.
To group your entities by tags:
- From Observe, click on an entity.
- Click on the group view statement bar that is denoted by Add Group.
You can select the populated suggestions or if you begin to type, the autocomplete feature will populate suggestions. To add multiple (up to two) tags, separate by adding a comma. If you attempt to add three or more tags, Apply will turn gray.
- Once you complete your group view statement, click Apply.
To remove grouping, highlight the group view statement and delete or clear the field.