dt-obs-kubernetes

Analyzes Kubernetes infrastructure using Dynactrace DQL for clusters, pods, and security.

2|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/pvellido1/traces-flow --skill dt-obs-kubernetes-pvellido1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dt-obs-kubernetes
Source: https://github.com/pvellido1/traces-flow/tree/main/.github/skills/dt-obs-kubernetes
Command: npx skills add https://github.com/pvellido1/traces-flow --skill dt-obs-kubernetes-pvellido1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides in-depth monitoring and analysis of Kubernetes infrastructure, allowing users to diagnose issues, optimize resources, and ensure compliance.

Core Features & Use Cases

  • Kubernetes Inventory: Query K8s entities like clusters, namespaces, nodes, pods, and workloads.
  • Resource Utilization: Analyze pod and container resource utilization, identify over-provisioned resources, and optimize costs.
  • Pod and Container Analysis: Investigate pod failures, OOMKills, evictions, and restart patterns.
  • Security Assessment: Identify privileged containers, root user access, and security posture.
  • Scheduling Analysis: Verify pod distribution, high availability compliance, and workload scheduling and placement.
  • Multi-Cluster Comparison: Compare resource distribution across clusters and identify patterns.
  • Compliance Tracking: Monitor and enforce labeling standards and compliance policies.
  • Best Practices and Recommendations: Guidance on monitoring, configuration standards, and resource efficiency.

Quick Start

Run the following DQL query to check the number of nodes in each Kubernetes cluster: smartscapeNodes K8S_CLUSTER | fields k8s.cluster.name, count() | sort count() desc.

Frequently Asked Questions about dt-obs-kubernetes

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

FAQPage Schema
How do I monitor Kubernetes cluster health and resource utilization using Dynatrace DQL?

You can monitor Kubernetes infrastructure by running Dynatrace DQL queries to analyze cluster inventory, pod resource utilization, and container health. This allows you to diagnose pod failures, identify over-provisioned resources, and optimize costs across your K8s environments.

What is the best way to analyze Kubernetes pod failures and OOMKills with DQL?

Analyzing Kubernetes pod failures with DQL involves querying container health metrics to investigate OOMKills, evictions, and restart patterns. This provides insights into workload scheduling issues and helps identify underlying resource exhaustion problems affecting your pods.

Do I need a Dynatrace environment to assess Kubernetes security posture and compliance?

Yes, assessing Kubernetes security posture requires a connected Dynatrace environment with necessary scopes. You use DQL knowledge to query and identify privileged containers, root user access, and monitor labeling standards to enforce compliance policies across your clusters.

Can I compare resource distribution and scheduling across multiple Kubernetes clusters?

You can compare resource distribution across multiple Kubernetes clusters by executing DQL queries. This allows you to identify patterns, verify pod distribution, check high availability compliance, and analyze workload placement to ensure optimal scheduling.

How do I check the number of nodes in each Kubernetes cluster using DQL?

To check nodes per Kubernetes cluster, run the DQL query: `smartscapeNodes K8S_CLUSTER | fields k8s.cluster.name, count() | sort count() desc`. This provides a sorted list of your clusters and their corresponding node counts for quick inventory review.

What are the limitations of using DQL for Kubernetes resource optimization?

Using DQL for Kubernetes resource optimization requires specific Dynatrace environment scopes and existing DQL knowledge. Without proper environment access or query expertise, you cannot effectively diagnose issues, analyze utilization, or enforce configuration standards.