← Search

Frontend observability with Dynatrace RUM: Core Web Vitals, sessions, errors
DevOps 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 4f9aa71
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: a Dynatrace account with RUM (Real User Monitoring)…

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

At a glance
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.

Version:

Quick answer

Frontend observability with Dynatrace RUM is a free Muse skill from @dynatrace for monitoring frontends with Real User Monitoring. It uses timeseries metrics for trends and alerting, user events for root cause and sessions for journeys and bounce rate, drilling down from frontend to page or view, then by browser, app version, geography and device. Note that Dynatrace is paid.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4f9aa71

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/dynatrace/dynatrace-for-ai/4f9aa71f9802aa6db0a4069ae5619eb3392ff411/skills/dt-obs-frontends/SKILL.md Pinned version: install the code at commit 4f9aa71f9802aa6db0a4069ae5619eb3392ff411 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 4f9aa71 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
4f9aa71 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.