dt-obs-services

Solid

Service performance monitoring with RED metrics (Rate, Errors, Duration) and runtime-specific telemetry for Java, .NET, Node.js, Python, PHP, and Go. Use when analyzing service health, SLA compliance, or runtime issues. Trigger: "service response time", "error rate", "throughput", "SLA compliance", "service mesh overhead", "JVM GC", "Java heap", "Node.js event loop", ".NET CLR", "Python threads", "PHP OPcache", "Go goroutines", "service performance", "p95 latency", "request failures", "database response time by name". Do NOT use for explaining existing queries, product documentation questions, infrastructure metrics (use dt-obs-hosts), log analysis (use dt-obs-logs), or distributed tracing workflows (use dt-obs-tracing).

DevOps & Infrastructure 117 stars 24 forks Updated 3 days ago Apache-2.0

Install

View on GitHub

Quality Score: 88/100

Stars 20%
69
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Application Services Skill Monitor application service performance, health, and runtime-specific metrics using DQL. --- ## Core Capabilities ### 1. Service Performance (RED Metrics) Monitor service **Rate, Errors, Duration** using metrics-based timeseries queries. **Key Metrics:** - `dt.service.request.response_time` - Response time (microseconds) - `dt.service.request.count` - Request count - `dt.service.request.failure_count` - Failed request count **Common Use Cases:** - Response time monitoring (avg, p50, p95, p99) - Error rate tracking and spike detection - Traffic analysis (throughput, peaks, growth) - Performance degradation detection - Multi-cluster comparison **Quick Example:** ```dql timeseries { p95 = percentile(dt.service.request.response_time, 95), total_requests = sum(dt.service.request.count), failures = sum(dt.service.request.failure_count) }, by: {dt.service.name} | fieldsAdd p95_ms = p95[] / 1000, error_rate_pct = (failures[] * 100.0) / total_requests[] ``` → **For detailed queries:** See [references/service-metrics.md](references/service-metrics.md) ### 2. Advanced Service Analysis Span-based queries for complex scenarios requiring flexible filtering and custom aggregations. **Use Cases:** - SLA compliance tracking with custom thresholds - Service health scoring (multi-dimensional) - Operation/endpoint-level performance analysis - Custom error classification - Failure pattern detection with error details **Quick Example:** ```dql fetch ...

Details

Author
Dynatrace
Repository
Dynatrace/dynatrace-for-ai
Created
3 months ago
Last Updated
3 days ago
Language
Shell
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

DevOps & Infrastructure Solid

dt-obs-tracing

Distributed traces, spans, service dependencies, and request flow analysis. Use when investigating span-level details, failures, performance bottlenecks, or trace correlation. Trigger: "trace analysis", "slow requests", "failed spans", "service dependencies", "distributed trace", "span details", "HTTP status codes in traces", "database query spans", "messaging spans", "gRPC calls", "Lambda cold starts", "trace ID lookup", "exception analysis", "correlate logs and traces", "request attributes". Do NOT use for explaining existing queries, product documentation or configuration questions, service-level RED metrics (use dt-obs-services), log searching (use dt-obs-logs), or problem analysis (use dt-obs-problems).

117 Updated 3 days ago
Dynatrace
DevOps & Infrastructure Solid

dt-obs-kubernetes

Kubernetes cluster, pod, node, and workload monitoring. Use when analyzing K8s health, resource optimization, pod failures, OOMKills, scheduling, or security posture. Also use for Kubernetes operational events like pod restarts, OOM events, evictions, and cluster event history. Trigger: "Kubernetes pods", "K8s cluster health", "OOMKill", "pod restarts", "container CPU", "namespace resource usage", "over-provisioned pods", "privileged containers", "pod placement", "K8s node capacity", "running containers by cluster", "workload scheduling", "pod evictions", "K8s labels and annotations", "kubernetes events", "pod restart events", "OOM events", "K8s event history". Do NOT use for explaining existing queries, product documentation questions, AWS-specific resource queries, service-level RED metrics, distributed tracing, or log analysis — use the relevant skill instead.

117 Updated 3 days ago
Dynatrace
Data & Documents Solid

dt-obs-logs

Log querying, filtering, pattern analysis, and error rate calculation. Use when searching application or infrastructure logs, analyzing error patterns, or correlating log data. Trigger: "show error logs", "search logs for keyword", "log error rate", "recent errors", "logs from last hour", "find log entries", "top error messages", "log patterns", "parse JSON logs", "logs by process group", "log trends over time", "log entry counts per minute". Do NOT use for explaining existing queries, product documentation questions, distributed tracing or span analysis (use dt-obs-tracing).

117 Updated 3 days ago
Dynatrace