dt-obs-frontends
Real User Monitoring (RUM) on Dynatrace — web and mobile frontends. Core Web Vitals, user sessions, page performance, mobile crashes, frontend errors, and frontend-backend linking. Query via `user.events`, `user.sessions`, and `dt.frontend.*` metrics. Does NOT cover synthetic monitoring (HTTP/browser/network checks) — that's a separate domain.
Install
git clone https://github.com/Dynatrace/dynatrace-for-ai /tmp/dynatrace-for-ai && ln -s /tmp/dynatrace-for-ai/skills/dt-obs-frontends ~/.claude/skills/dt-obs-frontends
From README
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.
More from this repo
dt-obs-analytics
Used to analyze dashboards and notebooks using Davis analyzers — anomaly detection, novelty scoring, and correlation.
dt-obs-compliance-assistant
Used to monitor and investigate EU DORA compliance posture using Dynatrace Compliance Assistant.
dt-obs-ext-monitors
3rd-party test and monitor result ingestion into Dynatrace Grail via the platform events ingest API...
