dt-obs-problems

Correlate DAVIS problem events with logs, metrics, and deployments to identify root causes and quantify business impact.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Problem Analysis Skill enables operators and engineers to quickly identify, understand, and triage DAVIS-detected problems by surfacing root causes, assessing business impact, and correlating issues with logs, metrics, and deployments.

Core Features & Use Cases

  • Identify root causes using causal analysis of Smartscape dependencies and cross-reference with dt.davis events.
  • Assess business impact by counting affected users and services, and map to critical services.
  • Correlate problems with logs, metrics, and deployments to speed incident response.
  • Use cases: investigate alert surges, validate root causes, and track problem lifecycles across active and closed incidents.

Quick Start

Start by querying active problems, then pull root-cause and impact data to inform triage.

Frequently Asked Questions about dt-obs-problems

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

FAQPage Schema
What is root-cause analysis for DAVIS problems and how does it work?

Root-cause analysis for DAVIS problems identifies the underlying causes of detected issues by performing causal analysis of Smartscape dependencies and cross-referencing events with logs, metrics, and deployments to speed incident triage.

How do I assess the business impact of active problems on my services?

You assess the business impact of active problems by counting affected users and services, mapping the issues to critical services, and surfacing the blast radius to prioritize targeted remediation and incident response.

Can I correlate logs and metrics with deployments to investigate alert surges?

Yes, you can correlate logs, metrics, and deployments with active and historical problems to investigate alert surges, validate root causes, and track problem lifecycles across closed incidents for targeted remediation.

What's the best way to start querying historical problems for incident triage?

The best way to start querying historical problems for incident triage is to query active problems first, then pull root-cause and impact data to inform triage and track problem lifecycles across closed incidents.