dt-obs-problems

Analyze Dynatrace problems for root cause, impact, and trends.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/mf-dynatrace/dt-mcp-workspace --skill dt-obs-problems-mf-dynatrace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dt-obs-problems
Source: https://github.com/mf-dynatrace/dt-mcp-workspace/tree/main/skills/dt-obs-problems
Command: npx skills add https://github.com/mf-dynatrace/dt-mcp-workspace --skill dt-obs-problems-mf-dynatrace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires dtapi, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies root cause identification and problem impact assessment, allowing you to quickly understand and prioritize issues in your environment.

Core Features & Use Cases

  • Root Cause Analysis: Identifies the root cause of a problem with detailed analysis.
  • Impact Assessment: Assess the business and technical impact of a problem.
  • Problem Trending: Analyze problem patterns over time to detect recurring issues.
  • Use Case: When you encounter a service outage, use this Skill to identify the root cause, assess its impact, and determine the necessary actions.

Quick Start

Trigger: "active problems"

Frequently Asked Questions about dt-obs-problems

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform root cause analysis on active Dynatrace problems?

Root cause analysis for Dynatrace problems is performed by querying your environment data to identify the originating failure point. This Skill analyzes active problems to pinpoint the exact root cause and assess its technical impact.

Can I assess the business impact of a service outage using Dynatrace DQL?

Yes, you can assess the business impact of a service outage using Dynatrace DQL. This Skill evaluates problem data to determine the scope and severity of an incident, allowing you to prioritize necessary response actions.

What is the best way to detect recurring problem patterns in a Dynatrace environment?

The best way to detect recurring problem patterns is through problem trending analysis. This Skill analyzes Dynatrace problem data over time to identify recurring issues, helping you resolve underlying systemic vulnerabilities.

Do I need DQL query capabilities to use this Skill for incident response?

Yes, you need DQL query capabilities and access to Dynatrace data sources for incident response. The Skill relies on the dtapi dependency to query your environment and execute root cause identification and impact assessment.

How does problem trending work for troubleshooting Dynatrace incidents?

Problem trending works by analyzing historical Dynatrace problem data to detect recurring patterns over time. This mechanism helps during troubleshooting by highlighting repeated systemic failures rather than isolated incidents.

What are the limitations of using automated root cause identification during a service outage?

Automated root cause identification requires continuous access to Dynatrace data sources and DQL query execution. It is limited by the availability of your environment's data streams and cannot analyze issues outside the monitored infrastructure.