Dynatrace Interview Question: Key User Action vs Key Request – Backend vs Frontend Monitoring Explained

When preparing for Observability or SRE interviews, one of the most frequently asked questions is:

1. What’s the difference between a Key User Action and a Key Request in Dynatrace?
2. How does Key Request help in backend service monitoring?
3. How does Key User Action help in monitoring real user experience?

It may sound simple, but understanding this distinction is crucial because it reflects how well you grasp end-to-end monitoring, from frontend user experience to backend service performance.

Key User Action (Frontend Focus)

A Key User Action represents an important interaction from the user’s perspective. Think of it as the critical touchpoints in the customer journey, the actions that define whether a user’s experience is smooth or frustrating.

1. Definition: A significant user action or webpage load that most users depend on.
2. Purpose: Helps teams proactively track real user experience.
3. Metrics: User action duration, Apdex score, and overall user experience.
4. Examples: Homepage load, Checkout page load, Account Login Page, Catalogue Page

By marking these as Key User Actions, you can easily monitor them in Dynatrace dashboards and quickly spot UX issues. Please refer to the snapshot below for an understanding of Key User Action

Note: A user action must be explicitly marked as a Key User Action; only then does Dynatrace treat it as one. These are the top user actions for the Veerpedia web application, which consistently attract the highest traffic from end users.

Ensure that the necessary user actions are explicitly marked as Key User Actions in Dynatrace, similar to the process shown in the reference image.

After designating a user action as a Key User Action, Dynatrace enables you to track its performance metrics in dashboards through Data Explorer

This serves as the reference for monitoring Key User Actions in the Dynatrace Classic Dashboard.

Key Request (Backend Focus)

A Key Request is all about the backend, the services and APIs that power your application. These are the lifelines of your system, and if they fail, the user experience collapses.

1. Definition: A critical backend service or API request.
2. Purpose: Enables proactive monitoring of business-critical transactions.
3. Metrics: Response time, failure rate, throughput.
4. Examples: Payment API, Order processing service.

Without marking them as Key Requests, you won’t be able to track these transactions directly on dashboards. Navigate through the following steps to mark a request as a Key Request in Dynatrace.

To monitor the api/products request as a Key Request, select the filter icon. This will display only the transactions associated with the api/products request.

Note: After filtering the api/products request, proceed to mark it as a Key Request.

Easy Way to Remember

Here’s a simple tip that interviewers love to hear:

1. Key Request = Backend Service Performance
2. Key User Action = Frontend User Experience

Together, they provide end-to-end observability. This means teams can quickly identify whether an issue is caused by a slow backend service or a poor frontend experience. a vital skill in modern SRE and observability practices.