Dt Obs Frontends

If you're using Dynatrace's new RUM platform and need to dig into frontend telemetry with DQL, this is your reference. It covers the full data model: timeseries metrics for trends, user.events for granular page views and errors, and user.sessions for aggregated session data. The field naming inconsistency between events (dot notation) and sessions (underscores) will trip you up, so the guide is careful about that. Also useful: it explains zombie sessions and why not every session ID in events will have a matching user.sessions record, which saves you from chasing ghosts. Good for debugging Web Vitals, correlating frontend errors with backend traces, or analyzing mobile app crashes.

skills.sh installs: 2.8K
GitHub stars: 177
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add dynatrace/dynatrace-for-ai --skill dt-obs-frontends --agent claude-code

Installs into .claude/skills of the current project.

Files

Frontend Observability (RUM)

Monitor web and mobile frontends using Real User Monitoring with DQL. Targets RUM on the latest Dynatrace — do not use RUM Classic data.

Concepts and data model: https://docs.dynatrace.com/docs/observe/digital-experience/new-rum-experience/concepts

Data Model

Three data sources, each for a different question:

Source	Use for	Granularity
`timeseries dt.frontend.*`	Trends, dashboards, alerting	Aggregated metric
`fetch user.events`	Root cause, individual page views / requests / clicks / errors	Per-event
`fetch user.sessions`	Bounce rate, session duration, session-level aggregates	Per-session

Rule of thumb: start with metrics for the shape of the problem, drill into events for the why. Use sessions when the question is about user journeys, not individual interactions.

Full event model: https://docs.dynatrace.com/docs/semantic-dictionary/model/rum/user-events

DQL language reference (functions, syntax, operators): https://docs.dynatrace.com/docs/platform/grail/dynatrace-query-language

SKILL.md on GitHub