dt-obs-kubernetes

Solid

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.

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

# Infrastructure Kubernetes Monitor and analyze Kubernetes infrastructure using Dynatrace DQL. Query cluster resources, monitor workload health, analyze pod placement, optimize costs, and assess security posture. ## When to Use This Skill - Monitoring Kubernetes cluster health and capacity - Analyzing pod and container resource utilization - Investigating pod failures, OOMKills, evictions, or crash loops - Debugging degraded deployments, stuck rollouts, or node pressure - Optimizing Kubernetes resource costs - Assessing security posture and compliance - Troubleshooting workload scheduling and placement - Auditing ingress routing and network policies ## Knowledge Base Structure ### Core Monitoring (Start Here) 1. **Cluster Inventory** → `references/cluster-inventory.md` - Clusters, namespaces, resource distribution 2. **Node Monitoring** - Node capacity, CPU/memory usage, pod density 3. **Pod Monitoring** - Pod CPU, memory, lifecycle events 4. **Workload Monitoring** - Deployment, StatefulSet, DaemonSet resources ### Advanced Topics 1. **Configuration Analysis** → `references/labels-annotations.md` - Parse k8s.object, labels, annotations 2. **Scheduling & Placement** → `references/pod-node-placement.md` - Node selectors, affinity, taints, HA 3. **Cost Optimization** - Right-sizing, waste detection, efficiency scoring 4. **Security & Compliance** - Privileged containers, security contexts ## Key Concepts ### Entity Types **Workloads:** `K8S_DEPLOYMENT`, `K8S_...

Details

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

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

DevOps & Infrastructure Listed

kubernetes-skills

Kubernetes orchestration patterns, deployments, and best practices

0 Updated today
murtazatouqeer
DevOps & Infrastructure Solid

dt-obs-aws

AWS cloud resource monitoring including EC2, RDS, Lambda, ECS/EKS, VPC networking, load balancers, S3, DynamoDB, SQS/SNS, and cost optimization. Use when analyzing AWS infrastructure, resource inventory, security compliance, capacity planning, or cost savings. Trigger: "show EC2 instances", "find RDS databases", "VPC resources", "AWS cost optimization", "Lambda functions", "ECS services", "security groups", "unattached EBS volumes", "AWS load balancer topology", "publicly accessible databases", "AWS dashboards". Do NOT use for explaining existing queries, product documentation questions, generic host CPU/memory metrics (use dt-obs-hosts), application-level tracing (use dt-obs-tracing), or log analysis (use dt-obs-logs).

117 Updated 3 days ago
Dynatrace
DevOps & Infrastructure Solid

dt-obs-hosts

Host and process metrics including CPU, memory, disk, network, containers, and process-level telemetry. Use when analyzing infrastructure health, resource utilization, process consumption, or host discovery. Also use when building timeseries queries for host metrics that feed into analytical workflows like anomaly detection, forecasting, or seasonality analysis. Trigger: "show hosts", "CPU usage", "memory utilization", "disk space", "high CPU", "host with most free disk", "top hosts by CPU", "top processes by memory", "Linux hosts in AWS", "what databases are running", "infrastructure costs by cost center", "hosts running EOL Java", "container monitoring", "listening ports", "process resource consumption", "CPU forecast", "memory anomaly", "host seasonality". Do NOT use for explaining existing queries, product documentation questions, Kubernetes pod/workload queries (use dt-obs-kubernetes), AWS cloud resource inventory (use dt-obs-aws), or service-level metrics (use dt-obs-services).

117 Updated 3 days ago
Dynatrace