whizard-events
Use when working with WizTelemetry Events extension for KubeSphere, including installation, configuration, and event query API
Install / Use
npx skills add kubesphere/kubesphere --skill whizard-eventsInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OperationsSupported Platforms
Our assessment of whizard-events
whizard-events scores 97/100 on our quality scale, 31st of 259 Operations skills we index (top 12%).
Its SKILL.md is 6.9 KB long, well organised into 20 sections with 9 code examples: a thorough specification that gives an agent plenty to work with.
With 17,059 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so whizard-events is actively maintained.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-26. Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
whizard-events compared with similar skills
All 4 of these similar skills score higher than whizard-events; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| whizard-events (this skill)by kubesphere | 97 | 17.1k | 2mo ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 85.5k | 10d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 73.8k | today | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 83.7k | today | MCP Server |
| LocalAIby mudler | 100 | 49.3k | today | MCP Server |
Frequently asked questions
- How do I install whizard-events?
- Run
npx skills add kubesphere/kubesphere --skill whizard-events. The install tabs above show the steps for each supported agent. - Which AI agents does whizard-events work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is whizard-events safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is whizard-events still maintained?
- The repository was last updated about 2 months ago, so whizard-events is actively maintained.
Skill content
View source on GitHubname: whizard-events description: Use when working with WizTelemetry Events extension for KubeSphere, including installation, configuration, and event query API
WizTelemetry Events
Overview
WizTelemetry Events is an extension component in the KubeSphere Observability Platform for Kubernetes event collection, processing, and storage.
When to Use
- Installing or configuring the WizTelemetry Events extension
- Understanding event collection architecture
- Using the event query API to query events
Components
| Component | Description | Default Enabled | |-----------|-------------|-----------------| | kube-events-exporter | Kubernetes event collection and export | true |
Dependencies
- WizTelemetry Platform Service (whizard-telemetry): Required
- WizTelemetry Data Pipeline (vector): Required
- OpenSearch (opensearch): Required
Installation
Prerequisites
REQUIRED: Complete all steps in order before generating InstallPlan.
Step 1: Get Available Clusters and Confirm Target
⚠️ CRITICAL: DO NOT proceed until target clusters are determined.
Step 1.1: Get available clusters
kubectl get clusters -o jsonpath='{.items[*].metadata.name}'
Step 1.2: Determine target clusters
- If user explicitly specified target clusters in the request → Use those clusters directly, proceed to Step 2
- If user did NOT specify target clusters → Ask user to confirm which clusters to deploy to, then proceed to Step 2
Ask user (if not specified):
Available clusters: host, dev
Which clusters do you want to deploy WizTelemetry Events to?
Step 2: Get Latest Version (if not provided by user)
MUST do this to get the latest version:
kubectl get extensionversions -l kubesphere.io/extension-ref=whizard-events -o jsonpath='{range .items[*]}{.spec.version}{"\n"}{end}' | sort -V | tail -1
This outputs the latest version (e.g., 1.4.0). Note this down - you'll use it in the InstallPlan.
Install WizTelemetry Events
⚠️ IMPORTANT: Complete prerequisite steps BEFORE this step.
Based on your selections:
- Target clusters: User-confirmed cluster names
⚠️ CRITICAL: InstallPlan metadata.name MUST be whizard-events. DO NOT use any other name.
⚠️ CRITICAL: config field is YAML format. You MUST:
- Use the config structure exactly as shown in the template
- DO NOT add configuration fields that are not shown in the template
- DO NOT modify the structure or hierarchy
⚠️ CRITICAL: All placeholders MUST be replaced with actual values. DO NOT leave them as placeholders.
Template
apiVersion: kubesphere.io/v1alpha1
kind: InstallPlan
metadata:
name: whizard-events
spec:
extension:
name: whizard-events
version: <VERSION> # From Step 2
enabled: true
upgradeStrategy: Manual
clusterScheduling:
placement:
clusters:
- <TARGET_CLUSTERS>
Replace placeholders:
<VERSION>: From Step 2 (e.g.,1.4.0)<TARGET_CLUSTERS>: User-confirmed cluster names
Note: OpenSearch sink configuration (endpoints, auth) is provided by the vector extension. Make sure vector is installed and configured with OpenSearch before installing events.
Enable ISM Policy
apiVersion: kubesphere.io/v1alpha1
kind: InstallPlan
metadata:
name: whizard-events
namespace: kubesphere-system
spec:
extension:
name: whizard-events
version: <VERSION> # From Step 2
enabled: true
upgradeStrategy: Manual
config: |
kube-events-exporter:
sinks:
opensearch:
enabled: true
index:
prefix: "{{ .cluster }}-events"
timestring: "%Y.%m.%d"
ism_policy:
enable: true
min_index_age: "7d"
clusterScheduling:
placement:
clusters:
- <TARGET_CLUSTERS>
Configuration Parameters
OpenSearch Sink Parameters
| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| kube-events-exporter.sinks.opensearch.enabled | bool | true | Enable OpenSearch sink |
| kube-events-exporter.sinks.opensearch.index.prefix | string | "{{ .cluster }}-events" | Index prefix |
| kube-events-exporter.sinks.opensearch.index.timestring | string | "%Y.%m.%d" | Index time format |
ISM Policy Parameters
| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| kube-events-exporter.ism_policy.enable | bool | false | Enable Index State Management policy |
| kube-events-exporter.ism_policy.min_index_age | string | "7d" | Minimum index retention period |
Event Query API
Query Events
curl -X GET "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/logging.kubesphere.io/v1alpha2/events?operation=query&sort=desc&size=10&cluster=host" \
-H "X-Remote-User: admin"
Query Parameters:
| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| operation | string | query | Operation type: query/statistics/histogram/export |
| workspace_filter | string | | Comma-separated list of workspaces |
| workspace_search | string | | Fuzzy match workspace names |
| involved_object_namespace_filter | string | | Comma-separated list of namespaces (involvedObject.namespace) |
| involved_object_namespace_search | string | | Fuzzy match namespace names |
| involved_object_name_filter | string | | Comma-separated list of object names |
| involved_object_name_search | string | | Fuzzy match object names |
| involved_object_kind_filter | string | | Comma-separated list of kinds |
| reason_filter | string | | Comma-separated list of reasons |
| reason_search | string | | Fuzzy match reason |
| message_search | string | | Fuzzy match message |
| type_filter | string | | Event type: Warning/Normal |
| start_time | string | | Start time (seconds since epoch) |
| end_time | string | | End time (seconds since epoch) |
| interval | string | 15m | Time interval for histogram |
| sort | string | desc | Sort order: asc/desc |
| from | int | 0 | Offset |
| size | int | 10 | Number of results |
| cluster | string | host | Cluster name |
Extension Operations
Check Extension Status
kubectl get installplan whizard-events
kubectl get extensionversions -l kubesphere.io/extension-ref=whizard-events
Uninstall Extension
Uninstall from all clusters:
kubectl delete installplan whizard-events
Uninstall from specific cluster:
To remove WizTelemetry Events from a specific cluster, update the InstallPlan by removing that cluster from clusterScheduling.placement.clusters:
apiVersion: kubesphere.io/v1alpha1
kind: InstallPlan
metadata:
name: whizard-events
spec:
extension:
name: whizard-events
version: <VERSION>
enabled: true
upgradeStrategy: Manual
clusterScheduling:
placement:
clusters:
- <REMAINING_CLUSTERS> # Remove the cluster you want to uninstall from
Related Skills
Agent-Reach
85.5kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
73.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Scrapling
83.7k🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
LocalAI
49.3kLocalAI is the open-source AI engine. Run any model - LLMs, vision, voice, image, video - on any hardware. No GPU required.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
