dt-obs-services

Analyze service health with RED metrics and DQL queries.

120|26|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/Dynatrace/dynatrace-for-ai --skill dt-obs-services
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dt-obs-services
Source: https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-services
Command: npx skills add https://github.com/Dynatrace/dynatrace-for-ai --skill dt-obs-services

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Service observability can be complex; dt-obs-services provides a unified view of RED metrics, runtime telemetry, and advanced service analysis across multiple runtimes to simplify monitoring and troubleshooting.

Core Features & Use Cases

  • RED metrics for services (Rate, Errors, Duration) to monitor throughput, reliability, and latency.
  • Advanced service analysis with span-based queries for SLA tracking and endpoint-level insights.
  • Service mesh monitoring to compare mesh versus direct performance and detect overhead.
  • Runtime-specific monitoring references for Java, Node.js, .NET, Python, PHP, and Go to diagnose language/runtime behavior (GC, memory, threads, etc).
  • Cross-service and multi-cluster comparisons to identify trends, anomalies, and correlations.

Quick Start

Load the dt-obs-services skill and start querying service health and performance using the included references.

Frequently Asked Questions about dt-obs-services

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

FAQPage Schema
How do I monitor microservices performance using RED metrics?

Monitor microservices performance by tracking RED metrics—Rate, Errors, and Duration—to evaluate throughput, reliability, and latency across your services. This Skill queries runtime telemetry to provide service performance benchmarks using DQL against the Dynatrace telemetry schema.

Can I track service mesh overhead versus direct performance?

Service mesh monitoring compares mesh versus direct performance to detect overhead and analyze throughput. It evaluates telemetry data across microservices to identify latency trends and performance correlations within the mesh architecture.

Does this observability Skill support Java, Node.js, and Python runtime monitoring?

Runtime-specific monitoring references support Java, Node.js, .NET, Python, PHP, and Go to diagnose language-specific behavior. You can analyze runtime telemetry like garbage collection, memory usage, and thread metrics for these environments.

How do I analyze service latency and SLA tracking with span-based queries?

Analyze service latency and SLA tracking using span-based queries for endpoint-level insights. This approach leverages metrics-based timeseries and distributed tracing data to monitor service health and enforce service level agreements.

What is the best way to compare service performance across multiple clusters?

Cross-service and multi-cluster comparisons identify trends, anomalies, and correlations across your architecture. By applying unified RED metrics and runtime telemetry analysis, you can benchmark relative service performance and detect behavioral deviations.