RUM

Question 1

What are the three ways Dynatrace RUM can be injected into a web application? Why might you choose one method over another?

Answer 1

1. Automatically by OneAgent (easiest, requires OneAgent installation)
2. Manually if using agentless monitoring (for environments where OneAgent can’t be installed)
3. Using Dynatrace browser extensions (to monitor third-party applications)

Question 2

How does Dynatrace monitor mobile applications, and what is the injection process like?

Answer 2

1.OneAgent for iOS or Android (provides comprehensive monitoring)
2. No injection required (OneAgent handles the instrumentation automatically)

Question 3

In the context of Dynatrace RUM, what constitutes a “user action,” and how does it relate to web server requests

Answer 3

A user action is any interaction with the web browser that triggers a request to the web server. This could be loading a page, clicking a button, submitting a form, etc.

Question 4

What are the types of user actions

Answer 4

1. Load action (page load)
2. XHR action (AJAX requests)
3. Custom action (defined using the JavaScript API)

Question 5

What are two key factors that differentiate the various types of user actions in Dynatrace RUM?

Answer 5

1. How the action duration is calculated (varies depending on the type of action)
2. What metrics are available (different metrics are relevant for different action types)

Question 6

How does Dynatrace define and measure the duration of a “load action”? What are the start and end points for this measurement?

Answer 6

1. Definition: The actual loading of a page in the browser.
2. Duration: Measured from the start of the page load to the completion of the onLoad event handler (or a subsequent XHR triggered by it).
3. Start: navigationStart attribute or the moment the JavaScript RUM code initializes.
4. End: When the onLoad handler finishes or after the completion of an XHR triggered by the handler.

Question 7

How does Dynatrace define and measure the duration of an “XHR action”? How does this differ from a load action?

Answer 7

1. Definition: Triggered when user actions lead to an XHR or fetch() call.
2. Duration: Measured from the initiation of the XHR/fetch call to the completion of loading all related resources.
3. Start: When the XHR or fetch() call is initiated.
4. End: When all resources associated with the XHR/fetch call have finished loading.

Question 8

Where in the Dynatrace UI can you configure which types of user interactions are automatically detected and monitored by RUM?

Answer 8

Application -> Edit -> Advanced Settings -> Advanced Setup

Question 9

How can you extend Dynatrace RUM to track user interactions that aren’t automatically captured?

Answer 9

By using the JavaScript RUM API.

Question 10

What are the three main components that make up the total duration of a user action in Dynatrace?

Answer 10

1. Components: Frontend time, Network time, Server time.

Question 11

How does Dynatrace calculate the “frontend time,” “network time,” and “server time” for a user action?

Answer 11

1. Frontend time: User action duration - Network time - Server time.
2. Network time: (requestStart - actionStart) + (responseEnd - responseStart)
3. Server time: responseStart - requestStart
4. User action duration: (loadEventEnd or lastXHREnd) - actionStart

Question 12

How can you improve the readability and understandability of user action names in Dynatrace RUM?

Answer 12

Insert the data-dtname attribute into HTML elements to provide descriptive names.

Question 13

How does Dynatrace track user sessions, even for anonymous users?

Answer 13

Tracking: By storing a persistent cookie on the user’s browser.

Question 14

What events mark the beginning and end of a user session in Dynatrace?

Answer 14

1. Session Start: When the first user action is initiated.
2. Session End:
   After 35 minutes of
   browser inactivity.
   When the user closes
   their browser.(A user
   session remains live in the Dynatrace web UI for up to 35 minutes after the user closes their browser.)
   After a limit of 200 user
   actions.
   When the session
   duration reaches 8
   hours.
   By calling the
   dtrum.endSession()
   method of the JavaScript
   API.

Question 15

How are user actions grouped and correlated into user sessions by Dynatrace?

Answer 15

Visibility in Search: Usually 4 minutes, but can take up to 10.5 minutes.
Grouping: Dynatrace uses cookies and local storage to correlate user actions into sessions.

Question 16

Difference between Live and active users

Answer 16

1. A live user is a user who was active once before, but whose session has not yet been ended.
2. An active user is a user who has been confirmed still active at a given time.

Question 17

Where in the Dynatrace UI can you adjust the Apdex settings for an entire application?

Answer 17

Application Apdex: Apps -> select app -> edit app -> general

Question 18

How can you fine-tune Apdex thresholds for specific key user actions within an application?

Answer 18

Key User Action Apdex: Apps -> select app -> top 3 user actions -> view full details -> scroll down to key user actions -> select key user action -> edit

Question 19

List some of the key performance metrics that Dynatrace captures and analyzes to evaluate web application performance.

Answer 19

User action duration
Visual complete
DOM interactive
Speed index
Time to first byte
Load event start
Load event end
HTML downloaded
Time to first byte
Largest contentful paint(how quickly a web page’s main content is visible to a user)
Cumulative layout shift( the score measuring the unexpected shifting of visible webpage element)
First input delay (RUM web only)

Question 20

How are user actions with JavaScript errors categorized in terms of Apdex performance levels?

Answer 20

JavaScript Errors: Rated as “Frustrating.”

Question 21

What does the “user experience score” represent in Dynatrace RUM, and how is it calculated?

Answer 21

User Experience Score: Represents the Apdex for user sessions, reflecting overall user satisfaction.

Question 22

How does Dynatrace protect sensitive user data in session replays? What types of masking are available, and which are applied by default?

Answer 22

Masking Types:
All form fields (enabled)
Password fields (enabled)
Content
Attribute
Interaction (enabled for
select forms e.g., gender)

Question 23

If you’re monitoring internal applications, how can you ensure that Dynatrace accurately associates user activity with the correct geographical locations?

Answer 23

Settings > Web and mobile monitoring > Map IP addresses to locations.

Question 24

When is it appropriate to use the Dynatrace browser extension for RUM?

Answer 24

Browser Extension: When you want to monitor 3rd party applications.

Question 25

In what situations would you opt for agentless RUM monitoring?

Answer 25

Agentless Monitoring: When you can’t install OneAgent on your server.

Question 26

What kind of information does the Waterfall analysis view provide in Dynatrace RUM?

Answer 26

Data Displayed: Document requests, XHR requests, Resources.

Question 27

What are some of the “top findings” highlighted in the Waterfall analysis view?

Answer 27

Uncompressed text resources
Resources larger than 100kb
Resources with a browser cache rate lower than 50%
Slow first-party, third-party, or CDN resources (> 200 ms)
Contacted third-party and CDN domains
First-party, third-party, and CDN resources

Question 28

Which metrics can be selected and analyzed within the Waterfall analysis view?

Answer 28

Selectable Metrics: Key performance metrics.

Question 29

Dynatrace allows you to define “conversion goals” to track specific user behaviors. What are the four types of conversion goals you can create?

Answer 29

User action
Session duration
Number of user actions
Destination