dt-obs-frontends

# Frontend Observability (RUM) Monitor web and mobile frontends using Real User Monitoring with DQL. Targets the **New RUM Experience only** — do not use classic RUM 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 **Key `dt.frontend.*` metrics** (all support dimensions: `frontend.name`, `device.type`, `geo.country.iso_code`, `browser.name`, `os.name`, `dt.rum.user_type`, `dt.smartscape.frontend`): - `dt.frontend.web.page.largest_contentful_paint` / `dt.frontend.web.page.interaction_to_next_paint` / `dt.frontend.web.page.cumulative_layout_shift` / `dt.frontend.web.page.first_input_delay` ...