dt-obs-frontends

Analyze frontend telemetry from web and mobile apps using dt.frontend metrics, user.events, and spans.

120|26|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/Dynatrace/dynatrace-for-ai --skill dt-obs-frontends
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dt-obs-frontends
Source: https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-frontends
Command: npx skills add https://github.com/Dynatrace/dynatrace-for-ai --skill dt-obs-frontends

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides unified visibility into web and mobile frontend performance, real user activity, and reliability by combining RUM metrics, events, and trace data for actionable insights.

Core Features & Use Cases

  • Web & Mobile Telemetry Monitoring: Track Core Web Vitals, request latency, and user sessions across multiple frontends and devices.
  • User Sessions & Engagement: Analyze sessions, active users, and navigation flows to measure engagement and retention.
  • Error Tracking & Trace Correlation: Correlate frontend errors with backend traces to diagnose root causes and improve reliability.

Quick Start

Inspect the primary frontend's performance, sessions, and errors in real time by querying dt.frontend metrics, user events, and trace data.

Frequently Asked Questions about dt-obs-frontends

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor frontend performance and Core Web Vitals across multiple devices?

Frontend performance monitoring tracks Core Web Vitals and request latency across web and mobile apps. It queries dt.frontend metrics, user events, and spans to deliver actionable insights into real user sessions and device health.

How does frontend trace correlation work for diagnosing web application errors?

Frontend trace correlation connects frontend errors with backend traces to diagnose root causes. By analyzing spans and user events alongside telemetry data, it improves reliability through fast root-cause analysis across your application stack.

Can I analyze user sessions and navigation flows to measure engagement using RUM telemetry?

Real user monitoring telemetry analyzes active user sessions and navigation flows to measure engagement and retention. It fetches user events and queries frontend metrics to track user activity across multiple frontends and browsers.

What is the best way to query frontend metrics and user events for real-time observability?

Querying frontend metrics and user events with DQL provides real-time observability for web and mobile apps. You fetch user events, spans, and dt.frontend metrics to inspect primary frontend performance, sessions, and errors.

Does this frontend observability approach work for both web and mobile app health monitoring?

Frontend observability supports both web and mobile app health monitoring. It tracks Core Web Vitals, request latency, and user sessions across multiple frontends, devices, and browsers to ensure comprehensive reliability analysis.

Why do I need frontend telemetry for root-cause analysis when backend traces show no errors?

Frontend telemetry is needed for root-cause analysis because backend traces often miss client-side issues. Correlating frontend errors with backend traces and user events reveals performance bottlenecks invisible to server-side monitoring.