[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BW92B5VHAWH0RQVCPSMKG3":3,"skill-same:01M7BW92B5VHAWH0RQVCPSMKG3":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BW92B5VHAWH0RQVCPSMKG3","dt-obs-services",null,"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).","CognitionAI\u002Fdevin-marketplace","CognitionAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F163493330?v=4","01M7BVSRD98NC4FG8T3EZS6V5M","Cognition","01M7BVSRDX111C2XPWJ0E6MY26",29,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-services\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dt-obs-services\ndescription: >-\n  Service performance monitoring with RED metrics (Rate, Errors, Duration) and runtime-specific\n  telemetry for Java, .NET, Node.js, Python, PHP, and Go. Use when analyzing service health,\n  SLA compliance, or runtime issues.\n  Trigger: \"service response time\", \"error rate\", \"throughput\", \"SLA compliance\",\n  \"service mesh overhead\", \"JVM GC\", \"Java heap\", \"Node.js event loop\", \".NET CLR\",\n  \"Python threads\", \"PHP OPcache\", \"Go goroutines\", \"service performance\",\n  \"p95 latency\", \"request failures\", \"database response time by name\".\n  Do NOT use for explaining existing queries, product documentation questions,\n  infrastructure metrics (use dt-obs-hosts), log analysis (use dt-obs-logs),\n  or distributed tracing workflows (use dt-obs-tracing).\nlicense: Apache-2.0\n---\n\n# Application Services Skill\n\nMonitor application service performance, health, and runtime-specific metrics using DQL.\n\n---\n\n## Core Capabilities\n\n### 1. Service Performance (RED Metrics)\n\nMonitor service **Rate, Errors, Duration** using metrics-based timeseries queries.\n\n**Key Metrics:**\n- `dt.service.request.response_time` - Response time (microseconds)\n- `dt.service.request.count` - Request count\n- `dt.service.request.failure_count` - Failed request count\n\n**Common Use Cases:**\n- Response time monitoring (avg, p50, p95, p99)\n- Error rate tracking and spike detection\n- Traffic analysis (throughput, peaks, growth)\n- Performance degradation detection\n- Multi-cluster comparison\n\n**Quick Example:**\n```dql\ntimeseries {\n  p95 = percentile(dt.service.request.response_time, 95),\n  total_requests = sum(dt.service.request.count),\n  failures = sum(dt.service.request.failure_count)\n}, by: {dt.service.name}\n| fieldsAdd p95_ms = p95[] \u002F 1000, error_rate_pct = (failures[] * 100.0) \u002F total_requests[]\n```\n\n→ **For detailed queries:** See [references\u002Fservice-metrics.md](references\u002Fservice-metrics.md)\n\n### 2. Advanced Service Analysis\n\nSpan-based queries for complex scenarios requiring flexible filtering and custom aggregations.\n\n**Use Cases:**\n- SLA compliance tracking with custom thresholds\n- Service health scoring (multi-dimensional)\n- Operation\u002Fendpoint-level performance analysis\n- Custom error classification\n- Failure pattern detection with error details\n\n**Quick Example:**\n```dql\nfetch spans, from: now() - 1h | filter request.is_root_span == true\n| fieldsAdd meets_sla = if(request.is_failed == false AND duration \u003C 3s, 1, else: 0)\n| summarize total = count(), sla_compliant = sum(meets_sla), by: {dt.service.name}\n| fieldsAdd sla_compliance_pct = (sla_compliant * 100.0) \u002F total\n```\n\n→ **For detailed queries:** See [references\u002Fservice-metrics.md](references\u002Fservice-metrics.md)\n\n### 3. Service Messaging Metrics\n\nMonitor message-based service communication (queues, topics).\n\n**Key Metrics:**\n- `dt.service.messaging.publish.count` - Messages sent to queues or topics\n- `dt.service.messaging.receive.count` - Messages received from queues or topics\n- `dt.service.messaging.process.count` - Messages successfully processed\n- `dt.service.messaging.process.failure_count` - Messages that failed processing\n\n**Use Cases:**\n- Message throughput monitoring (publish\u002Freceive rates)\n- Message processing failure tracking\n- Queue\u002Ftopic health analysis\n- Consumer lag detection (publish vs receive rate comparison)\n\n**Quick Example:**\n```dql\ntimeseries {\n  published = sum(dt.service.messaging.publish.count),\n  received = sum(dt.service.messaging.receive.count),\n  processed = sum(dt.service.messaging.process.count),\n  failed = sum(dt.service.messaging.process.failure_count)\n}, by: {dt.service.name}\n```\n\n→ **For detailed queries:** See [references\u002Fservice-metrics.md](references\u002Fservice-metrics.md)\n\n### 4. Service Mesh Monitoring\n\nMonitor service mesh ingress performance and overhead.\n\n**Key Metrics:**\n- `dt.service.request.service_mesh.response_time` - Mesh response time (microseconds)\n- `dt.service.request.service_mesh.count` - Mesh request count\n- `dt.service.request.service_mesh.failure_count` - Mesh failure count\n\n**Use Cases:**\n- Mesh vs direct performance comparison\n- Mesh overhead calculation\n- Mesh failure analysis\n- gRPC traffic monitoring\n- Multi-cluster mesh performance\n\n**Quick Example:**\n```dql\ntimeseries {\n  direct_p95 = percentile(dt.service.request.response_time, 95),\n  mesh_p95 = percentile(dt.service.request.service_mesh.response_time, 95)\n}, by: {dt.service.name}\n| fieldsAdd mesh_overhead_ms = (mesh_p95[] - direct_p95[]) \u002F 1000\n```\n\n→ **For detailed queries:** See [references\u002Fservice-metrics.md](references\u002Fservice-metrics.md)\n\n### 5. Runtime-Specific Monitoring\n\nTechnology-specific runtime performance and resource usage metrics.\n\n**Java\u002FJVM** - [references\u002Fjava.md](references\u002Fjava.md)\n- Memory: heap, pools, metaspace\n- GC: impact, suspension, frequency, pause time\n- Threads: count monitoring, leak detection\n- Classes: loading, unloading, growth\n\n**Node.js** - [references\u002Fnodejs.md](references\u002Fnodejs.md)\n- Event loop: utilization, active handles\n- V8 heap: memory used, total\n- GC: collection time, suspension\n- Process: RSS memory\n\n**.NET CLR** - [references\u002Fdotnet.md](references\u002Fdotnet.md)\n- Memory: consumption by generation\n- GC: collection count, suspension time\n- Thread pool: threads, queued work\n- JIT: compilation time\n\n**Python** - [references\u002Fpython.md](references\u002Fpython.md)\n- Threads: active thread count\n- Heap: allocated blocks\n- GC: collection by generation, pause time\n- Objects: collected, uncollectable\n\n**PHP** - [references\u002Fphp.md](references\u002Fphp.md)\n- OPcache: hit ratio, memory, restarts\n- GC: effectiveness, duration\n- JIT: buffer usage\n- Interned strings: usage, buffer\n\n**Go** - [references\u002Fgo.md](references\u002Fgo.md)\n- Goroutines: count, leak detection\n- GC: suspension, collection time\n- Memory: heap by state, committed\n- Scheduler: worker threads, queue size\n- CGo: call frequency\n\n---\n\n## When to Use This Skill\n\n✅ **Use for:**\n- Monitoring service performance (response time, errors, traffic)\n- Calculating SLA compliance\n- Analyzing service mesh performance\n- Monitoring messaging throughput and processing failures\n- Troubleshooting runtime-specific issues (GC, memory, threads)\n- Multi-cluster service comparison\n- Operation\u002Fendpoint-level analysis\n\n❌ **Don't use for:**\n- Infrastructure metrics (use infrastructure skills)\n- Log analysis (use logs skills)\n- Distributed tracing workflows (use traces\u002Fspans skills)\n- Database performance (use database skills)\n- Product documentation or how-to configuration questions → use `ask-dynatrace-docs`\n\n---\n\n## Agent Instructions\n\n### Act First, Refine Later\n\nWhen a user asks for analysis — threshold checks, anomaly detection, performance\ncomparisons — **proceed immediately** with sensible defaults. Do not ask the user\nfor parameter values you can reasonably assume.\n\nWhy this matters: analysis tools (e.g., `static-threshold-analyzer`) require specific\ninputs like threshold values and service scope. The user expects results, not a\nparameter interview. Pick reasonable defaults, state them clearly in the response,\nand let the user refine.\n\n**Default values when not specified:**\n\n| Parameter | Default | Rationale |\n|-----------|---------|-----------|\n| Response time threshold | 1000 ms (= 1,000,000 µs in the metric's base unit) | Common SLA boundary |\n| Service scope | All services | Show the most relevant violations |\n| Timeframe | From the request, or last 30 min for threshold checks, 2h for general analysis | Matches typical operational windows |\n\n**Example: threshold violation request**\n1. Use `create-dql` to build a timeseries query for `avg(dt.service.request.response_time)` grouped by `dt.smartscape.service`\n2. Pass the query to `static-threshold-analyzer` with threshold = 1000000 (µs), alertCondition = ABOVE\n3. Resolve entity IDs to names using `get-entity-name`\n4. Present violations with service names, timestamps, values, and duration\n\n**Reading user phrasing:** Phrases like \"the fixed threshold\", \"a threshold\", or \"the limit\"\nname the *type of analysis* — static threshold check — not a specific number the user expects\nyou to already know. \"Fixed\" distinguishes a static cutoff from a dynamic or seasonal baseline.\nWhen you see these phrases, apply the 1000 ms default from the table above and present\nresults — the user can then refine if the default doesn't match their intent.\n\n### Scope Boundary\n\nThis skill covers **service performance metrics and runtime monitoring only**. If the\nuser asks a product documentation or configuration question (e.g., \"How do I add custom\nsensors?\", \"How do I configure service detection?\"), use `ask-dynatrace-docs` instead —\nthis skill does not contain configuration how-tos.\n\n### Understanding User Intent\n\n**Map user questions to capabilities:**\n\n| User Request | Use Capability | Key Files |\n|--------------|----------------|-----------|\n| \"service performance\", \"response time\", \"error rate\" | Service Performance (RED) | service-metrics.md |\n| \"SLA tracking\", \"health scoring\" | Advanced Service Analysis | service-metrics.md |\n| \"service mesh\", \"Istio\", \"Linkerd\", \"mesh overhead\" | Service Mesh Monitoring | service-metrics.md |\n| \"messaging\", \"queue\", \"topic\", \"publish\", \"consumer\" | Service Messaging Metrics | service-metrics.md |\n| \"JVM GC\", \"Java memory\", \"heap\" | Runtime-Specific (Java) | java.md |\n| \"Node.js event loop\", \"V8 heap\" | Runtime-Specific (Node.js) | nodejs.md |\n| \".NET CLR\", \"GC generation\" | Runtime-Specific (.NET) | dotnet.md |\n| \"Python GC\", \"thread count\" | Runtime-Specific (Python) | python.md |\n| \"OPcache\", \"PHP GC\" | Runtime-Specific (PHP) | php.md |\n| \"goroutines\", \"Go GC\", \"scheduler\" | Runtime-Specific (Go) | go.md |\n\n### Query Construction Patterns\n\n**1. Metrics-based (timeseries)**\n- **Use for:** Standard monitoring, dashboards, alerting\n- **Pattern:** `timeseries \u003Cmetric> = \u003Caggregation>(\u003Cmetric_name>), by: {dimensions}`\n- **Files:** service-metrics.md, all runtime-specific files\n\n**2. Span-based (fetch spans)**\n- **Use for:** Complex filtering, custom logic, detailed analysis\n- **Pattern:** `fetch spans | filter request.is_root_span == true | fieldsAdd ... | summarize ...`\n- **Files:** service-metrics.md (Advanced Service Analysis section)\n\n**3. Comparison queries**\n- Use `append` for baseline comparison\n- Use `shift: -15m` for time-shifted baselines\n- **Example:** Performance degradation detection\n\n### Response Construction Guidelines\n\n**Always include:**\n1. **Metric name(s)** - Clear metric identifiers\n2. **Aggregation** - How data is aggregated (avg, sum, percentile)\n3. **Grouping** - Dimensions used (`dt.service.name`, `k8s.workload.name`, etc.)\n4. **Unit conversion** - Convert microseconds to milliseconds where appropriate\n5. **Filtering** - Relevant thresholds or conditions\n\n**When referencing runtime-specific content:**\n- **Check** user's technology stack first\n- **Provide** only relevant runtime queries (don't overwhelm with all 6 runtimes)\n- **Explain** runtime-specific metrics (e.g., \"OPcache hit ratio\" measures PHP opcode cache efficiency)\n\n---\n\n## Common Workflows\n\n### Workflow: Service Health Check\n```\n1. Check response time (RED metrics)\n2. Check error rate (RED metrics)\n3. Check traffic patterns (RED metrics)\n4. If runtime-specific issues suspected → Load runtime-specific reference\n```\n\n### Workflow: SLA Monitoring\n```\n1. Define SLA criteria (e.g., \u003C 3s response time AND \u003C 1% error rate)\n2. Use span-based query for custom SLA logic\n3. Calculate compliance percentage\n4. Filter non-compliant services\n```\n\n### Workflow: Service Mesh Analysis\n```\n1. Check mesh response time\n2. Compare mesh vs direct performance\n3. Calculate mesh overhead\n4. Analyze mesh failure rates\n```\n\n### Workflow: Runtime Troubleshooting\n1. Identify technology stack → Load runtime-specific reference\n2. Check memory\u002FGC metrics → threads\u002Fgoroutines → runtime features\n\n---\n\n## Troubleshooting\n\n| Problem | Cause | Solution |\n|---------|-------|----------|\n| Response time values look too large | Metric is in microseconds | Divide by 1000 to convert to milliseconds |\n| No data for service mesh metrics | Service mesh not configured | Verify mesh sidecar injection is enabled |\n| Runtime metrics missing | Wrong technology or no OneAgent | Confirm the runtime is supported and OneAgent is active |\n| `dt.smartscape.service` returns SmartscapeId, not name | Need entity name resolution | Use `getNodeName(dt.smartscape.service)` |\n| Error rate always zero | Using wrong failure metric | Use `dt.service.request.failure_count`, not custom fields |\n\n---\n\n## References\n\n**Core Service Monitoring:**\n- [references\u002Fservice-metrics.md](references\u002Fservice-metrics.md) - Complete RED metrics, SLA tracking, service mesh queries\n\n**Runtime-Specific Monitoring:**\n- [references\u002Fjava.md](references\u002Fjava.md) - Java\u002FJVM monitoring\n- [references\u002Fnodejs.md](references\u002Fnodejs.md) - Node.js monitoring  \n- [references\u002Fdotnet.md](references\u002Fdotnet.md) - .NET CLR monitoring\n- [references\u002Fpython.md](references\u002Fpython.md) - Python monitoring\n- [references\u002Fphp.md](references\u002Fphp.md) - PHP monitoring\n- [references\u002Fgo.md](references\u002Fgo.md) - Go runtime monitoring\n","# Application Services Skill\n\nMonitor application service performance, health, and runtime-specific metrics using DQL.\n\n---\n\n## Core Capabilities\n\n### 1. Service Performance (RED Metrics)\n\nMonitor service **Rate, Errors, Duration** using metrics-based timeseries queries.\n\n**Key Metrics:**\n- `dt.service.request.response_time` - Response time (microseconds)\n- `dt.service.request.count` - Request count\n- `dt.service.request.failure_count` - Failed request count\n\n**Common Use Cases:**\n- Response time monitoring (avg, p50, p95, p99)\n- Error rate tracking and spike detection\n- Traffic analysis (throughput, peaks, growth)\n- Performance degradation detection\n- Multi-cluster comparison\n\n**Quick Example:**\n```dql\ntimeseries {\n  p95 = percentile(dt.service.request.response_time, 95),\n  total_requests = sum(dt.service.request.count),\n  failures = sum(dt.service.request.failure_count)\n}, by: {dt.service.name}\n| fieldsAdd p95_ms = p95[] \u002F 1000, error_rate_pct = (failures[] * 100.0) \u002F total_requests[]\n```\n\n→ **For detailed queries:** See [references\u002Fservice-metrics.md](references\u002Fservice-metrics.md)\n\n### 2. Advanced Service Analysis\n\nSpan-based queries for complex scenarios requiring flexible filtering and custom aggregations.\n\n**Use Cases:**\n- SLA compliance tracking with custom thresholds\n- Service health scoring (multi-dimensional)\n- Operation\u002Fendpoint-level performance analysis\n- Custom error classification\n- Failure pattern detection with error details\n\n**Quick Example:**\n```dql\nfetch spans, from: now() - 1h | filter request.is_root_span == true\n| fieldsAdd meets_sla = if(request.is_failed == false AND duration \u003C 3s, 1, else: 0)\n| summarize total = count(), sla_compliant = sum(meets_sla), by: {dt.service.name}\n| fieldsAdd sla_compliance_pct = (sla_compliant * 100.0) \u002F total\n```\n\n→ **For detailed queries:** See [references\u002Fservice-metrics.md](references\u002Fservice-metrics.md)\n\n### 3. Service Messaging Metrics\n\nMonitor message-based service communication (queues, topics).\n\n**Key Metrics:**\n- `dt.service.messaging.publish.count` - Messages sent to queues or topics\n- `dt.service.messaging.receive.count` - Messages received from queues or topics\n- `dt.service.messaging.process.count` - Messages successfully processed\n- `dt.service.messaging.process.failure_count` - Messages that failed processing\n\n**Use Cases:**\n- Message throughput monitoring (publish\u002Freceive rates)\n- Message processing failure tracking\n- Queue\u002Ftopic health analysis\n- Consumer lag detection (publish vs receive rate comparison)\n\n**Quick Example:**\n```dql\ntimeseries {\n  published = sum(dt.service.messaging.publish.count),\n  received = sum(dt.service.messaging.receive.count),\n  processed = sum(dt.service.messaging.process.count),\n  failed = sum(dt.service.messaging.process.failure_count)\n}, by: {dt.service.name}\n```\n\n→ **For detailed queries:** See [references\u002Fservice-metrics.md](references\u002Fservice-metrics.md)\n\n### 4. Service Mesh Monitoring\n\nMonitor service mesh ingress performance and overhead.\n\n**Key Metrics:**\n- `dt.service.request.service_mesh.response_time` - Mesh response time (microseconds)\n- `dt.service.request.service_mesh.count` - Mesh request count\n- `dt.service.request.service_mesh.failure_count` - Mesh failure count\n\n**Use Cases:**\n- Mesh vs direct performance comparison\n- Mesh overhead calculation\n- Mesh failure analysis\n- gRPC traffic monitoring\n- Multi-cluster mesh performance\n\n**Quick Example:**\n```dql\ntimeseries {\n  direct_p95 = percentile(dt.service.request.response_time, 95),\n  mesh_p95 = percentile(dt.service.request.service_mesh.response_time, 95)\n}, by: {dt.service.name}\n| fieldsAdd mesh_overhead_ms = (mesh_p95[] - direct_p95[]) \u002F 1000\n```\n\n→ **For detailed queries:** See [references\u002Fservice-metrics.md](references\u002Fservice-metrics.md)\n\n### 5. Runtime-Specific Monitoring\n\nTechnology-specific runtime performance and resource usage metrics.\n\n**Java\u002FJVM** - [references\u002Fjava.md](references\u002Fjava.md)\n- Memory: heap, pools, metaspace\n- GC: impact, suspension, frequency, pause time\n- Threads: count monitoring, leak detection\n- Classes: loading, unloading, growth\n\n**Node.js** - [references\u002Fnodejs.md](references\u002Fnodejs.md)\n- Event loop: utilization, active handles\n- V8 heap: memory used, total\n- GC: collection time, suspension\n- Process: RSS memory\n\n**.NET CLR** - [references\u002Fdotnet.md](references\u002Fdotnet.md)\n- Memory: consumption by generation\n- GC: collection count, suspension time\n- Thread pool: threads, queued work\n- JIT: compilation time\n\n**Python** - [references\u002Fpython.md](references\u002Fpython.md)\n- Threads: active thread count\n- Heap: allocated blocks\n- GC: collection by generation, pause time\n- Objects: collected, uncollectable\n\n**PHP** - [references\u002Fphp.md](references\u002Fphp.md)\n- OPcache: hit ratio, memory, restarts\n- GC: effectiveness, duration\n- JIT: buffer usage\n- Interned strings: usage, buffer\n\n**Go** - [references\u002Fgo.md](references\u002Fgo.md)\n- Goroutines: count, leak detection\n- GC: suspension, collection time\n- Memory: heap by state, committed\n- Scheduler: worker threads, queue size\n- CGo: call frequency\n\n---\n\n## When to Use This Skill\n\n✅ **Use for:**\n- Monitoring service performance (response time, errors, traffic)\n- Calculating SLA compliance\n- Analyzing service mesh performance\n- Monitoring messaging throughput and processing failures\n- Troubleshooting runtime-specific issues (GC, memory, threads)\n- Multi-cluster service comparison\n- Operation\u002Fendpoint-level analysis\n\n❌ **Don't use for:**\n- Infrastructure metrics (use infrastructure skills)\n- Log analysis (use logs skills)\n- Distributed tracing workflows (use traces\u002Fspans skills)\n- Database performance (use database skills)\n- Product documentation or how-to configuration questions → use `ask-dynatrace-docs`\n\n---\n\n## Agent Instructions\n\n### Act First, Refine Later\n\nWhen a user asks for analysis — threshold checks, anomaly detection, performance\ncomparisons — **proceed immediately** with sensible defaults. Do not ask the user\nfor parameter values you can reasonably assume.\n\nWhy this matters: analysis tools (e.g., `static-threshold-analyzer`) require specific\ninputs like threshold values and service scope. The user expects results, not a\nparameter interview. Pick reasonable defaults, state them clearly in the response,\nand let the user refine.\n\n**Default values when not specified:**\n\n| Parameter | Default | Rationale |\n|-----------|---------|-----------|\n| Response time threshold | 1000 ms (= 1,000,000 µs in the metric's base unit) | Common SLA boundary |\n| Service scope | All services | Show the most relevant violations |\n| Timeframe | From the request, or last 30 min for threshold checks, 2h for general analysis | Matches typical operational windows |\n\n**Example: threshold violation request**\n1. Use `create-dql` to build a timeseries query for `avg(dt.service.request.response_time)` grouped by `dt.smartscape.service`\n2. Pass the query to `static-threshold-analyzer` with threshold = 1000000 (µs), alertCondition = ABOVE\n3. Resolve entity IDs to names using `get-entity-name`\n4. Present violations with service names, timestamps, values, and duration\n\n**Reading user phrasing:** Phrases like \"the fixed threshold\", \"a threshold\", or \"the limit\"\nname the *type of analysis* — static threshold check — not a specific number the user expects\nyou to already know. \"Fixed\" distinguishes a static cutoff from a dynamic or seasonal baseline.\nWhen you see these phrases, apply the 1000 ms default from the table above and present\nresults — the user can then refine if the default doesn't match their intent.\n\n### Scope Boundary\n\nThis skill covers **service performance metrics and runtime monitoring only**. If the\nuser asks a product documentation or configuration question (e.g., \"How do I add custom\nsensors?\", \"How do I configure service detection?\"), use `ask-dynatrace-docs` instead —\nthis skill does not contain configuration how-tos.\n\n### Understanding User Intent\n\n**Map user questions to capabilities:**\n\n| User Request | Use Capability | Key Files |\n|--------------|----------------|-----------|\n| \"service performance\", \"response time\", \"error rate\" | Service Performance (RED) | service-metrics.md |\n| \"SLA tracking\", \"health scoring\" | Advanced Service Analysis | service-metrics.md |\n| \"service mesh\", \"Istio\", \"Linkerd\", \"mesh overhead\" | Service Mesh Monitoring | service-metrics.md |\n| \"messaging\", \"queue\", \"topic\", \"publish\", \"consumer\" | Service Messaging Metrics | service-metrics.md |\n| \"JVM GC\", \"Java memory\", \"heap\" | Runtime-Specific (Java) | java.md |\n| \"Node.js event loop\", \"V8 heap\" | Runtime-Specific (Node.js) | nodejs.md |\n| \".NET CLR\", \"GC generation\" | Runtime-Specific (.NET) | dotnet.md |\n| \"Python GC\", \"thread count\" | Runtime-Specific (Python) | python.md |\n| \"OPcache\", \"PHP GC\" | Runtime-Specific (PHP) | php.md |\n| \"goroutines\", \"Go GC\", \"scheduler\" | Runtime-Specific (Go) | go.md |\n\n### Query Construction Patterns\n\n**1. Metrics-based (timeseries)**\n- **Use for:** Standard monitoring, dashboards, alerting\n- **Pattern:** `timeseries \u003Cmetric> = \u003Caggregation>(\u003Cmetric_name>), by: {dimensions}`\n- **Files:** service-metrics.md, all runtime-specific files\n\n**2. Span-based (fetch spans)**\n- **Use for:** Complex filtering, custom logic, detailed analysis\n- **Pattern:** `fetch spans | filter request.is_root_span == true | fieldsAdd ... | summarize ...`\n- **Files:** service-metrics.md (Advanced Service Analysis section)\n\n**3. Comparison queries**\n- Use `append` for baseline comparison\n- Use `shift: -15m` for time-shifted baselines\n- **Example:** Performance degradation detection\n\n### Response Construction Guidelines\n\n**Always include:**\n1. **Metric name(s)** - Clear metric identifiers\n2. **Aggregation** - How data is aggregated (avg, sum, percentile)\n3. **Grouping** - Dimensions used (`dt.service.name`, `k8s.workload.name`, etc.)\n4. **Unit conversion** - Convert microseconds to milliseconds where appropriate\n5. **Filtering** - Relevant thresholds or conditions\n\n**When referencing runtime-specific content:**\n- **Check** user's technology stack first\n- **Provide** only relevant runtime queries (don't overwhelm with all 6 runtimes)\n- **Explain** runtime-specific metrics (e.g., \"OPcache hit ratio\" measures PHP opcode cache efficiency)\n\n---\n\n## Common Workflows\n\n### Workflow: Service Health Check\n```\n1. Check response time (RED metrics)\n2. Check error rate (RED metrics)\n3. Check traffic patterns (RED metrics)\n4. If runtime-specific issues suspected → Load runtime-specific reference\n```\n\n### Workflow: SLA Monitoring\n```\n1. Define SLA criteria (e.g., \u003C 3s response time AND \u003C 1% error rate)\n2. Use span-based query for custom SLA logic\n3. Calculate compliance percentage\n4. Filter non-compliant services\n```\n\n### Workflow: Service Mesh Analysis\n```\n1. Check mesh response time\n2. Compare mesh vs direct performance\n3. Calculate mesh overhead\n4. Analyze mesh failure rates\n```\n\n### Workflow: Runtime Troubleshooting\n1. Identify technology stack → Load runtime-specific reference\n2. Check memory\u002FGC metrics → threads\u002Fgoroutines → runtime features\n\n---\n\n## Troubleshooting\n\n| Problem | Cause | Solution |\n|---------|-------|----------|\n| Response time values look too large | Metric is in microseconds | Divide by 1000 to convert to milliseconds |\n| No data for service mesh metrics | Service mesh not configured | Verify mesh sidecar injection is enabled |\n| Runtime metrics missing | Wrong technology or no OneAgent | Confirm the runtime is supported and OneAgent is active |\n| `dt.smartscape.service` returns SmartscapeId, not name | Need entity name resolution | Use `getNodeName(dt.smartscape.service)` |\n| Error rate always zero | Using wrong failure metric | Use `dt.service.request.failure_count`, not custom fields |\n\n---\n\n## References\n\n**Core Service Monitoring:**\n- [references\u002Fservice-metrics.md](references\u002Fservice-metrics.md) - Complete RED metrics, SLA tracking, service mesh queries\n\n**Runtime-Specific Monitoring:**\n- [references\u002Fjava.md](references\u002Fjava.md) - Java\u002FJVM monitoring\n- [references\u002Fnodejs.md](references\u002Fnodejs.md) - Node.js monitoring  \n- [references\u002Fdotnet.md](references\u002Fdotnet.md) - .NET CLR monitoring\n- [references\u002Fpython.md](references\u002Fpython.md) - Python monitoring\n- [references\u002Fphp.md](references\u002Fphp.md) - PHP monitoring\n- [references\u002Fgo.md](references\u002Fgo.md) - Go runtime monitoring\n",{"name":5,"license":15,"description":7},"main","9836d94e88404aabb682086405c2aa9cba7657ac","plugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-services",156,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace","https:\u002F\u002Fgithub.com\u002FCognitionAI","https:\u002F\u002Fcognition.ai\u002F","Makers of Devin, the AI software engineer.","2026-11-13 07:08:23",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add CognitionAI\u002Fdevin-marketplace --skill dt-obs-services",{"tool":39,"command":40},"bunx","bunx skills add CognitionAI\u002Fdevin-marketplace --skill dt-obs-services",{"tool":42,"command":43},"pnpm","pnpm dlx skills add CognitionAI\u002Fdevin-marketplace --skill dt-obs-services","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-services\u002FSKILL.md",true,[47,53,57,61,65,69,73],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fdotnet.md","REFERENCE","参考文档",3552,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-services\u002Freferences\u002Fdotnet.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fgo.md",6882,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-services\u002Freferences\u002Fgo.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fjava.md",9258,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-services\u002Freferences\u002Fjava.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fnodejs.md",4148,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-services\u002Freferences\u002Fnodejs.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fphp.md",6581,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-services\u002Freferences\u002Fphp.md",{"path":70,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fpython.md",3779,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-services\u002Freferences\u002Fpython.md",{"path":74,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fservice-metrics.md",16108,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-services\u002Freferences\u002Fservice-metrics.md",[78,85,92,98,105,112],{"skillNo":79,"name":80,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7BYC4AJGM98P2G9JH7QS24Z","business-data","MIT","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fwindsor-ai\u002Fskills\u002Fbusiness-data\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7BYBZ0CD4CBCPZHRZ551BNK","workflow","Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of \"workflow\", \"durable functions\", \"resumable\", \"workflow sdk\", \"queue\", \"event\", \"push\", \"subscribe\", or step-based orchestration.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002Fupstream\u002FSKILL.md",[],[],{"skillNo":93,"name":87,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7BYB1XSZHKHD8JZTQJ62JN0","Vercel Workflow SDK expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause\u002Fresume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7BYASGMK935J33E21N5WTW0","verification","Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fverification\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7BY9WJERKSKEH9HK6E71GW2","vercel-storage","Vercel storage expert guidance — Blob, Global Config (formerly Edge Config), and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-storage\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M7BY9N034894YV2J9DCRZHYS","vercel-services","Configure and troubleshoot Vercel Services for multiple frontends and backends in one project. Use when composing a polyglot or multi-service application on one Vercel deployment; defining the `services` key, service-targeted rewrites, or service bindings in `vercel.json`; or running all services with `vercel dev`.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002FSKILL.md",[],[]]