Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Dynatrace/dynatrace-for-ai --skill dt-obs-problemsgit clone --depth 1 https://github.com/Dynatrace/dynatrace-for-aiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/dynatrace/dynatrace-for-ai/dt-obs-problems)<a href="https://agentmods.dev/skills/dynatrace/dynatrace-for-ai/dt-obs-problems"><img src="https://agentmods.dev/badge/skills/dynatrace/dynatrace-for-ai/dt-obs-problems/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dynatrace/dynatrace-for-ai/dt-obs-problems"><img src="https://agentmods.dev/badge/skills/dynatrace/dynatrace-for-ai/dt-obs-problems.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00123 | $0.04267 |
| Opus 5 | $0.00062 | $0.02133 |
| Sonnet 5 | $0.00025 | $0.00853 |
| Haiku 4.5 | $0.00012 | $0.00427 |
Grade A, and why
dt-obs-problems scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 482 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Problem Analysis Skill
Analyze Dynatrace AI-detected problems including root cause identification, impact assessment, and correlation with logs and metrics.
Use Cases
1. Active Problem Triage
- Goal: List and prioritize currently active problems
- Trigger: "active problems", "what problems are open", "current issues", "availability issues"
- Done: Prioritized list of active problems with category, user impact, and display IDs
2. Root Cause Investigation
- Goal: Identify the root cause entity for a specific problem
- Trigger: "root cause of P-12345", "what caused this problem", "which entity is the root cause"
- Done: Root cause entity identified with affected entity list and blast radius
3. Problem Trending
- Goal: Analyze problem patterns over time to identify recurring issues
- Trigger: "recurring problems", "problem history", "problem trends last 30 days"
- Done: Trend data showing problem frequency, recurring root causes, and resolution times
Overview
Dynatrace automatically detects anomalies, performance degradations, and failures across your environment, creating problems that aggregate related alert, warning and info-level events and provide root cause and impact insights.
What are Problems?
Problems are automatically detected, software and infrastructure health and resilience issues that:
- Automatically correlate related alert, warning, and info-level events across services, infrastructure, frontend applications, and user sessions
- Identify root causes using causal analysis of Smartscape dependencies
- Assess business impact by tracking affected users and services
- Reduce alert noise by grouping related symptoms into single problems that share the same root cause and impact
- Track problem lifecycle from early detection through resolution
Event Kinds
The event.kind field (stable, permission) identifies the high-level event type:
event.kind value |
Description |
|---|---|
DAVIS_EVENT |
Davis-detected infrastructure/application events |
BIZ_EVENT |
Business events (ingested via API or captured from spans) |
RUM_EVENT |
Real User Monitoring events |
AUDIT_EVENT |
Administrative/security audit events |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 482 lines · 123 tokens per session scan A 6501e5d771a3
dt-obs-problems is a skill published in the GitHub repository Dynatrace/dynatrace-for-ai (137 stars, last pushed 10d ago), licensed Apache-2.0. It adds 123 tokens to every session and 4,267 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
dtctl
Investigate incidents, debug performance issues, analyze logs, and manage observability resources in Dynatrace using the dtctl CLI. Use this skill whenever the user asks about error rates, latency spikes, service health, crash-looping pods, web vitals, SLO status, open problems, root cause analysis, log patterns…
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…