list-recent-events
Collect recent Kubernetes events to identify issues. Events reveal warnings, errors, and state changes. Keywords: events, warnings, errors, cluster activity, state changes, recent events.
When & Why to Use This Skill
This Claude skill enables automated monitoring of Kubernetes clusters by retrieving and analyzing recent events across all namespaces. It streamlines troubleshooting by surfacing critical warnings, errors, and state changes, allowing DevOps and SRE teams to maintain high availability and quickly diagnose infrastructure health issues.
Use Cases
- Incident Diagnosis: Rapidly identify the root cause of pod crashes or service failures by filtering for recent warning and error events across the cluster.
- Cluster Health Auditing: Perform routine checks on cluster activity to detect silent failures, resource pressure, or unexpected state transitions in real-time.
- Post-Deployment Verification: Monitor event logs immediately following a production rollout to ensure all resources are initialized correctly without underlying configuration errors.
| name | list-recent-events |
|---|---|
| description | > |
| warnings, errors, and state changes. Keywords | events, warnings, errors, |
| domain | k8s |
| category | collection |
| requires-approval | false |
| confidence | 0.95 |
List Recent Cluster Events
Preconditions
Before applying this skill, verify:
- Need to understand recent cluster activity
- Looking for warnings or errors
Actions
1. List Events from All Namespaces
Retrieve recent events from across the cluster.
mcp_tool: kubernetes-mcp-server/events_list
params: {}
timeout: 60s
Success Criteria
The skill succeeds when:
- Events retrieved successfully
- Warnings/errors identified and categorized
Failure Handling
If events unavailable, check API server connectivity.
Examples
Input Context:
{
"reason": "routine health check",
"time_range": "last 1 hour"
}
Expected Outcome: List of recent events with warnings and errors highlighted, categorized by severity and resource type.