メニュー
Retrieve logs from a Kubernetes node. Supports journalctl (systemd units) and file-based logs. Use when you need to inspect node-level logs (containerd, kubelet, etc.). Run via host_script (preferred) or node_script.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Show and ping the gateway of a network interface, on a Kubernetes node or inside a pod's network namespace. Auto-detects the gateway from the routing table (ip -j route), reports interface type (RoCE / Ethernet / IB), and tests reachability with ping. Use for default-route / gateway questions, network reachability checks, RoCE/RDMA data-path validation, and "can this node/pod reach its gateway" investigations.
Guide for writing and improving Siclaw skills. Read this when creating or modifying a skill. Covers skill directory layout, SKILL.md format, script execution modes, and best practices.
Check node health and diagnose node-level issues (NotReady, DiskPressure, MemoryPressure, PIDPressure). Inspects node conditions, resource allocation, and real-time usage.
Diagnose DNS resolution failures in the cluster (NXDOMAIN, timeouts, SERVFAIL). Checks CoreDNS health, service endpoints, and DNS configuration.
Diagnose NetworkPolicy-related connectivity issues (traffic unexpectedly blocked, default-deny effects, egress blocking DNS). Identifies which NetworkPolicies affect a pod, checks ingress/egress rules, and verifies CNI support.
Diagnose Service connectivity issues (empty Endpoints, selector mismatch, port mismatch, no backend pods). Checks Service, Endpoints, and target pods to identify why traffic is not reaching backends.
| name | node-logs |
| description | Retrieve logs from a Kubernetes node. Supports journalctl (systemd units) and file-based logs. Use when you need to inspect node-level logs (containerd, kubelet, etc.). Run via host_script (preferred) or node_script. |
Prefer host_script when the node is a bound SSH host (check host_list) — it runs over
SSH with no debug pod. Fall back to node_script otherwise. Both take the same skill/script/args.
host_script: host="<host>", skill="node-logs", script="get-node-logs.sh", args="<args>"
node_script: node="<node>", skill="node-logs", script="get-node-logs.sh", args="<args>"
Required (one of):
| Parameter | Description |
|---|---|
--unit UNIT | Systemd unit name (e.g. containerd, kubelet). Use this or --file. |
--file PATH | Log file path on the node (e.g. /var/log/messages). Use this or --unit. |
Optional:
| Parameter | Default | Description |
|---|---|---|
--since DURATION | 1h ago | Time range for journalctl (only with --unit), e.g. 30m ago, 2h ago, today |
--grep PATTERN | — | Case-insensitive grep filter pattern |
--tail N | 200 | Maximum number of output lines |
Check containerd logs on a node:
node_script: node="node-1", skill="node-logs", script="get-node-logs.sh", args="--unit containerd --tail 50"
Search containerd logs for a specific image:
node_script: node="node-1", skill="node-logs", script="get-node-logs.sh", args='--unit containerd --grep "myregistry.com/myapp" --since "2h ago"'
Check kubelet logs for errors:
node_script: node="node-1", skill="node-logs", script="get-node-logs.sh", args='--unit kubelet --grep "error" --since "30m ago"'
Read a log file on the node:
node_script: node="node-1", skill="node-logs", script="get-node-logs.sh", args='--file /var/log/messages --grep "containerd" --tail 100'
Check containerd or cri-o logs when pods fail to start, images fail to pull, or containers crash unexpectedly.
Check kubelet logs for node-level issues like pod evictions, volume mount failures, or resource pressure.
Read /var/log/messages, /var/log/syslog, or other log files for kernel or system-level issues affecting the node.