dt-obs-logs

Extract and analyze Dynatrace logs using DQL with time and entity filters.

2|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/israel-salgado/dt-mcp-server --skill dt-obs-logs-israel-salgado
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dt-obs-logs
Source: https://github.com/israel-salgado/dt-mcp-server/tree/main/.agents/skills/dt-obs-logs
Command: npx skills add https://github.com/israel-salgado/dt-mcp-server --skill dt-obs-logs-israel-salgado

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dynatrace logs are a critical source for troubleshooting and observability, but finding relevant entries across large volumes can be painful. This skill provides targeted querying, filtering, and pattern analysis to quickly surface actionable log insights and correlate events with specific entities and processes.

Core Features & Use Cases

  • Fetch and filter logs by time window, severity, and entity (e.g., process_group or service)
  • Search log messages with keyword, full-text, or pattern matching, and compute basic statistics
  • Analyze patterns and trends, group results by dimensions like process name or service, and export concise summaries for dashboards

Quick Start

Show me the last hour of error logs for the payment-service grouped by process name.

Frequently Asked Questions about dt-obs-logs

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

FAQPage Schema
How do I query Dynatrace logs using DQL for troubleshooting?

You query Dynatrace logs using DQL by applying targeted filtering to specific time windows and entities. This extracts relevant log data, applying scope to process groups or services to facilitate troubleshooting and surface actionable insights.

Can I filter Dynatrace log analysis by specific services and time windows?

Yes, you can filter Dynatrace log analysis by specific time windows, severity, and entities like process groups or services. This ensures robust filtering and time bucketing to narrow down large volumes of log entries.

What is the best way to detect patterns in Dynatrace time-series logs?

The best way to detect patterns in Dynatrace time-series logs is to use DQL queries that support pattern detection and aggregation. You can group results by dimensions like process name or service to compute basic statistics and analyze trends.

How do I group Dynatrace log entries by process name for observability?

You group Dynatrace log entries by process name for observability by applying DQL aggregation functions. This groups results by dimensions like process name or service, allowing you to compute statistics and export concise summaries for dashboards.

Does Dynatrace log querying support full-text search and keyword matching?

Yes, Dynatrace log querying supports full-text search, keyword matching, and pattern matching. You can search log messages with these methods to compute basic statistics and ensure safe defaults with clear error handling.

Why are my Dynatrace log queries returning too much data during troubleshooting?

Your Dynatrace log queries may return too much data if you do not apply scope to specific time windows and entities. Ensure robust filtering, time bucketing, and safe defaults to extract only relevant log data for troubleshooting.