dt-obs-kubernetes

Query Dynatrace Kubernetes data to troubleshoot cluster, namespace, node, pod, and workload health issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Kubernetes environments require real-time visibility to detect degradations, misconfigurations, and outages. This Skill provides Dynatrace DQL-powered queries to inventory resources, monitor health, diagnose degraded deployments, and investigate pod failures across clusters.

Core Features & Use Cases

  • Inventory and health checks for Kubernetes clusters, namespaces, nodes, pods, and workloads
  • Diagnose degraded deployments, OOMKilled pods, failed rollouts, and network/policy issues
  • Correlate pod placement with node capacity and ingress/network policies for security and reliability

Quick Start

Query the current health and inventory of Kubernetes clusters to surface failing pods and degraded deployments.

Frequently Asked Questions about dt-obs-kubernetes

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

FAQPage Schema
How do I troubleshoot Kubernetes pod failures and degraded deployments using Dynatrace?

Troubleshoot Kubernetes pod failures by querying Dynatrace DQL to inventory resources, monitor health, and diagnose degraded deployments, OOMKilled pods, and failed rollouts across multiple clusters.

Can I monitor Kubernetes cluster health and resource utilization with Dynatrace DQL?

Monitor Kubernetes cluster health and resource utilization by running Dynatrace DQL queries against clusters, namespaces, nodes, pods, and workloads to surface failing pods and capacity issues.

What is the best way to diagnose OOMKilled pods and failed rollouts in Kubernetes?

Diagnose OOMKilled pods and failed rollouts by querying Dynatrace Kubernetes data to identify degraded deployments, investigate pod failures, and analyze resource utilization across affected clusters.

Does this Kubernetes observability approach support auditing network policies and pod placement?

This approach supports auditing network policies by correlating pod placement with node capacity and ingress policies, enabling reliability and security diagnostics across Kubernetes clusters.

How do I inventory Kubernetes namespaces, nodes, and workloads across multiple clusters?

Inventory Kubernetes namespaces, nodes, and workloads across multiple clusters by executing Dynatrace DQL queries that aggregate resource states and surface infrastructure degradations.

Why should I use Dynatrace DQL for Kubernetes observability instead of standard kubectl commands?

Dynatrace DQL provides end-to-end operational visibility across multiple clusters by delivering structured query results and reference guidance for health checks, rollout diagnostics, and policy audits beyond standard kubectl output.