dt-obs-problems

Analyze Dynatrace DAVIS problems for root cause, impact, and trends using DQL queries.

Updated Dec 12, 2025
One-click install
npx skills add https://github.com/ricardojjulia/ESACompanion --skill dt-obs-problems-ricardojjulia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dt-obs-problems
Source: https://github.com/ricardojjulia/ESACompanion/tree/main/.github/skills/dt-obs-problems
Command: npx skills add https://github.com/ricardojjulia/ESACompanion --skill dt-obs-problems-ricardojjulia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Investigating Dynatrace-detected problems manually is slow and error-prone, especially when writing DQL queries with correct field names, status values, and deduplication filters. This Skill provides ready-to-use query patterns for triaging active problems, identifying root causes, and assessing business impact. ## Core Features & Use Cases - Active Problem Triage: List and prioritize currently active problems by category, affected users, and blast radius using dt.davis.problems queries. - Root Cause Investigation: Identify root cause entities, recurring offenders, and infrastructure-level causes with correct field names like root_cause_entity_id and event.category. - Impact & Trend Analysis: Calculate blast radius, user impact scores, problem duration trends, and correlate problems with logs, deployments, and Kubernetes entities. - Use Case: When asked "what caused problem P-12345 and who is affected", the Skill generates a DQL query filtering by display_id, returning the root cause entity name, affected services, and impacted user count. ## Quick Start Ask the AI to list all active Dynatrace problems from the last 24 hours with their root causes and affected user counts.

Frequently Asked Questions about dt-obs-problems

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

FAQPage Schema
How do I list active problems in Dynatrace with DQL?▼

Query dt.davis.problems with a time range, filter by event.status == "ACTIVE", and exclude duplicates using not(dt.davis.is_duplicate). Include display_id, event.name, and event.category fields, then sort by event.start descending.

How to find the root cause of a Dynatrace problem?▼

Filter dt.davis.problems by the problem's display_id and retrieve root_cause_entity_id and root_cause_entity_name fields. For recurring root causes, group problems by root_cause_entity_name and count occurrences over a time window.

Why does my Dynatrace problem query return no results?▼

The most common cause is using event.status == "OPEN", which does not exist; valid values are ACTIVE and CLOSED. Also verify you are using event.name instead of title and event.category instead of severity.

Can I correlate Dynatrace problems with logs?▼

Yes, use the problem's smartscape.affected_entity.ids or affected_entity_ids in a subquery to filter the logs data source. Align time ranges between the problem and log queries, and filter loglevel to ERROR or WARN for relevant entries.

What is the difference between event.category and root cause entity in Dynatrace?▼

event.category describes the problem type such as AVAILABILITY, ERROR, SLOWDOWN, RESOURCE, or CUSTOM. The root cause entity identifies the specific service, host, or application that triggered the problem, so use category for cause patterns and root_cause_entity_name for specific offenders.