Frontend observability with Dynatrace RUM: Core Web Vitals, sessions, errors
Monitor web and mobile frontends with Real User Monitoring in DQL β Core Web Vitals metrics, user events and sessions drill-downs, error tracking, mobile crashes, frontend-backend linking
- What
- Monitor web and mobile frontends with Real User Monitoring in DQL β Core Web Vitals metrics, user events and sessions drill-downs, error tracking, mobile crashes, frontend-backend linking
- Cost
- Free
- Needs
- a Dynatrace account with RUM (Real User Monitoring) enabled β Dynatrace is a paid platform; an agent or person who can query the Dynatrace environment in DQL
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
π³ Paid platform required β Dynatrace is a paid service: you need a Dynatrace account with RUM (Real User Monitoring) enabled for this skill to be usable. Curated by Skill Harbor β @dynatrace's skill for frontend observability on the latest Dynatrace (RUM, not RUM Classic): three data sources for three questions β `dt.frontend.*` timeseries metrics for trends, dashboards and alerting; `user.events` for root cause (page views, requests, clicks, errors); `user.sessions` for journeys, bounce rate and session aggregates. The drill-down pattern: identify the frontend (group by `frontend.name`), find the affected page (`page.name`) or view (`view.name`), then narrow with dimensions (browser, app version, geography, device type, synthetic vs real traffic). Includes the key metric names (LCP, INP, CLS, FID, TTFB, error counts, request/user-action volume), the Core Web Vitals threshold quick reference (LCP good < 2.5 s, INP good < 200 ms, CLS good < 0.1), sensitive-field handling (`client.ip`, `user.identifier` are hidden by default β a fieldset policy grant is needed), and a workflow-to-reference map (web-vitals, user-sessions, error-tracking, mobile-monitoring, frontend-backend-linking, CSP violations, slow-page-load playbook, troubleshooting). Honest caveats: RUM only β synthetic monitoring, backend services, logs and problems are separate skills (dt-obs-synthetic, dt-obs-services, dt-obs-logs, dt-obs-problems) not bundled here; the detailed reference files load on demand. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a Dynatrace account with RUM (Real User Monitoring) enabled β Dynatrace is a paid platform; an agent or person who can query the Dynatrace environment in DQL Install "Frontend observability with Dynatrace RUM: Core Web Vitals, sessions, errors" for me. It teaches my agent @dynatrace's RUM workflow: start with dt.frontend.* metrics for the shape of the problem (Core Web Vitals, error counts, request latency), drill into user.events for root cause and user.sessions for journeys, group by frontend.name then page/view name, narrow by browser/app-version/geo dimensions, handle sensitive fields (client.ip, user.identifier need a fieldset grant), and follow the workflowβreference map for web-vitals, error-tracking, mobile crashes, frontend-backend linking and the slow-page-load playbook. Apache-2.0 licensed. Repository: https://github.com/dynatrace/dynatrace-for-ai/blob/main/skills/dt-obs-frontends/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "dt-obs-frontends". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. make sure RUM is enabled in your Dynatrace environment and the agent can query it; install the companion skills dt-obs-synthetic / dt-obs-services / dt-obs-logs / dt-obs-problems separately if you need them β not bundled here). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you β no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the sellerβs own page, usually Stripe.
What does the β next to a creatorβs name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself β always check a build before installing it.