dt-obs-problems

Analyze Dynatrace problems to identify root causes and assess business impact.

2|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/pvellido1/traces-flow --skill dt-obs-problems-pvellido1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dt-obs-problems
Source: https://github.com/pvellido1/traces-flow/tree/main/.github/skills/dt-obs-problems
Command: npx skills add https://github.com/pvellido1/traces-flow --skill dt-obs-problems-pvellido1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires dynatrace-api, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the analysis of Dynatrace problems, enabling users to detect root causes and assess business impact with ease.

Core Features & Use Cases

  • Root Cause Analysis: Identify the root cause of problems using causal analysis of Smartscape dependencies.
  • Impact Assessment: Assess the business impact of problems by tracking affected users and services.
  • Problem Correlation: Correlate problems with logs and metrics to gain deeper insights.
  • Use Case: For example, when a service becomes unavailable, use this Skill to automatically detect the root cause and assess the impact on users and business operations.

Quick Start

Analyze problems in Dynatrace by running the dt-obs-problems skill and providing the necessary filters and parameters.

Frequently Asked Questions about dt-obs-problems

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

FAQPage Schema
How do I analyze Dynatrace problems to automatically detect root causes?

To analyze Dynatrace problems and detect root causes, you can automate causal analysis of Smartscape dependencies. This process identifies the underlying issue by evaluating how problems propagate across your monitored environment.

How do I assess the business impact of a service becoming unavailable in Dynatrace?

Assess the business impact of a service becoming unavailable in Dynatrace by tracking affected users and services. This impact assessment helps quantify the operational disruption caused by the problem.

Can I correlate Dynatrace problems with logs and metrics for deeper analysis?

Yes, you can correlate Dynatrace problems with logs and metrics. Correlating this data provides deeper insights into the problem context, linking anomalies directly to the identified root cause.

Do I need access to the Dynatrace API to fetch problem data for impact assessment?

Yes, you need access to the Dynatrace API to fetch problem data and relevant entities. This API access is a prerequisite for automating root cause identification and assessing the impact on users.

What is the best way to identify the root cause of problems using Smartscape dependencies?

The best way to identify the root cause of problems using Smartscape dependencies is through causal analysis. This approach maps the problem across your monitored topology to pinpoint the originating entity.

How does problem correlation work when analyzing Dynatrace problem data?

Problem correlation works by linking the fetched Dynatrace problem data with corresponding logs and metrics. This mechanism reveals deeper insights into how the root cause affects overall system behavior.