菜单
Diagnose Kubernetes node incidents, including NotReady, MemoryPressure, DiskPressure, PIDPressure, NetworkUnavailable, high CPU/memory/disk, kubelet/container runtime errors, node instability, and node OOM using Prometheus metrics and VictoriaLogs node logs.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/clcc2019/dsflow --skill k8s-node-analyzer命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Calculate incident impact, detection and recovery durations, classify incidents as L0-L3 from service criticality and impact inputs, compute weighted SLA impact and derived availability, and generate post-incident Markdown reports. Use for SLA calculations, incident severity assessment, outage-duration review, availability summaries, postmortems, incident reports, and remediation tracking.
云原生 SRE 值班助理和巡检编排技能。用于基础设施早检、Kubernetes 集群健康检查、Ceph 存储巡检、计算集群巡检、网关故障初筛、异常证据汇总和值班日报生成。触发场景：用户要求早检、巡检、检查集群是否正常、检查 Ceph、检查计算集群、排查网关错误或生成基础设施健康报告。
Create, review, tune, and validate production-grade Prometheus alerting rules and Kubernetes PrometheusRule resources. Use when writing or repairing alert rule YAML, designing PromQL alert expressions, recommending defensible thresholds and for durations, building SLO/error-budget burn-rate alerts, reducing alert noise, standardizing severity/labels/annotations, adding promtool tests, or reviewing an existing Prometheus rule catalog. 用户要求创建、评审或优化 Prometheus 告警规则、PromQL、告警阈值、告警降噪时使用。
基于 SOC 职业分类
正在显示 SKILL.md
| name | k8s-node-analyzer |
| description | Diagnose Kubernetes node incidents, including NotReady, MemoryPressure, DiskPressure, PIDPressure, NetworkUnavailable, high CPU/memory/disk, kubelet/container runtime errors, node instability, and node OOM using Prometheus metrics and VictoriaLogs node logs. |
Use scripts to collect JSON data. The agent analyzes conditions, metrics, Pods, and logs to identify root cause and actions.
# Node status: conditions, capacity, allocatable, kubelet/runtime info
scripts/get_node_status.sh -c prod-cluster -n <node>
# Node metrics: CPU, memory, disk, inode, network, load
scripts/get_node_metrics.sh -c prod-cluster -n <node>
# Pods on node, sorted by memory or CPU
scripts/get_node_pods.sh -n <node> --sort memory -l 50
scripts/get_node_pods.sh -n <node> --sort cpu -l 20
# Memory-focused diagnosis
scripts/diagnose_node_memory.sh -n <node> --top 20
# Node logs: kubelet, OOM, or all patterns
scripts/query_node_logs.sh -n <node>
scripts/query_node_logs.sh -n <node> --type oom
scripts/query_node_logs.sh -n <node> --type all -t 2026-01-23T10:00:00Z -r 1h
scripts/query_node_logs.sh -n <node> --raw
Common parameters:
-c/--cluster: default prod-cluster.-n/--node: required node name.--prometheus: override Prometheus URL for metric scripts.--sort: memory or cpu for get_node_pods.sh.--top: number of Pods returned by diagnose_node_memory.sh.-t/--time, -r/--range, -l/--limit, --type, --raw: log query controls.Defaults:
https://prometheus.example.comhttps://victorialogs.example.comget_node_status.sh to check Ready, pressure conditions, taints, unschedulable, capacity, and pod count.get_node_metrics.sh to quantify CPU, memory, disk, inode, network, and load.get_node_pods.sh or diagnose_node_memory.sh to identify noisy Pods, missing limits, requests mismatch, or memory oversell.query_node_logs.sh around the incident time to confirm kubelet/runtime/OOM/network/storage errors.<70% normal, 70-85% warning, >85% critical.load1/cores <0.7 normal, 0.7-1.0 warning, >1.0 critical.<100% normal, 100-150% warning, >150% critical.Ready=True, MemoryPressure=False, DiskPressure=False, PIDPressure=False, NetworkUnavailable=False.MemoryPressure or high memory: run diagnose_node_memory.sh, then query_node_logs.sh --type oom; inspect top Pods, pods without limits, and limits/request oversell.DiskPressure: inspect disk and inode usage, kubelet logs, /var/log, /var/lib/containerd, image garbage collection, and noisy Pod logs.PIDPressure: check process leaks or fork storms in workloads.NetworkUnavailable: query all node logs and inspect CNI/NetworkPlugin errors.Ready=False/Unknown: inspect kubelet, container runtime, certificates, API server connectivity, resource pressure, and recent node reboot.query_node_logs.sh recognizes patterns for OOM, disk pressure, PLEG unhealthy, kubelet errors, container runtime errors, image pull failures, network errors, certificates, NotReady, evictions, volume errors, and API server connectivity.
prod-cluster: productioncompute-cluster: computetencent-cluster: Tencent Cloudaliyun-cluster: AliyunRead references/node_conditions.md only when detailed Condition semantics are needed.