whizard-logging
Use when working with WizTelemetry Logging extension for KubeSphere, including installation, configuration, and log query API
Install / Use
npx skills add kubesphere/kubesphere --skill whizard-loggingInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of whizard-logging
whizard-logging scores 97/100 on our quality scale, 125th of 1,947 Development & Engineering skills we index (top 7%).
Its SKILL.md is 8.9 KB long, well organised into 25 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-logging 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-logging compared with similar skills
All 4 of these similar skills score higher than whizard-logging; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| whizard-logging (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 |
| ai-job-searchby MadsLorentzen | 100 | 44.0k | 4d ago | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 41.7k | today | CLAUDE.md |
Frequently asked questions
- How do I install whizard-logging?
- Run
npx skills add kubesphere/kubesphere --skill whizard-logging. The install tabs above show the steps for each supported agent. - Which AI agents does whizard-logging 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-logging 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-logging still maintained?
- The repository was last updated about 2 months ago, so whizard-logging is actively maintained.
Skill content
View source on GitHubname: whizard-logging description: Use when working with WizTelemetry Logging extension for KubeSphere, including installation, configuration, and log query API
WizTelemetry Logging
Overview
WizTelemetry Logging is an extension component in the KubeSphere Observability Platform for log collection, processing, and storage.
When to Use
- Installing or configuring the WizTelemetry Logging extension
- Understanding log collection architecture (container logs + disk log collection)
- Using the log query API to query logs
Components
| Component | Description | Default Enabled | |-----------|-------------|-----------------| | vector-logging | Container log collection (collects stdout/stderr from Docker/Containerd) | true | | logsidecar-injector | Disk log collection (collects logs from files inside containers) | false |
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 Logging 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-logging -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 Logging
⚠️ IMPORTANT: Complete prerequisite steps BEFORE this step.
Based on your selections:
- Target clusters: User-confirmed cluster names
⚠️ CRITICAL: InstallPlan metadata.name MUST be whizard-logging. 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-logging
spec:
extension:
name: whizard-logging
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 logging.
Enable Disk Log Collection
To enable disk log collection, add logsidecar-injector to the config:
apiVersion: kubesphere.io/v1alpha1
kind: InstallPlan
metadata:
name: whizard-logging
spec:
extension:
name: whizard-logging
version: <VERSION> # From Step 2
enabled: true
upgradeStrategy: Manual
config: |
logsidecar-injector:
enabled: true
vector-logging:
filter:
extraLabelSelector: "app.kubernetes.io/name!=kube-events-exporter"
calico:
enabled: true
systemd:
docker:
enabled: true
kubelet:
enabled: true
sinks:
opensearch:
enabled: true
index:
prefix: "{{ .cluster }}-logs"
timestring: "%Y.%m.%d"
clusterScheduling:
placement:
clusters:
- <TARGET_CLUSTERS>
Configuration Parameters
Logsidecar Injector Parameters
| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| logsidecar-injector.enabled | bool | false | Enable disk log collection |
| logsidecar-injector.sidecar.sidecarType | string | vector | Sidecar type |
| logsidecar-injector.resources.limits.cpu | string | 100m | CPU limit |
| logsidecar-injector.resources.limits.memory | string | 100Mi | Memory limit |
| logsidecar-injector.resources.requests.cpu | string | 10m | CPU request |
| logsidecar-injector.resources.requests.memory | string | 10Mi | Memory request |
Vector Logging Parameters
Filter Parameters
| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| vector-logging.filter.extraLabelSelector | string | "app.kubernetes.io/name!=kube-events-exporter" | Extra label selector |
| vector-logging.filter.extraNamespaceLabelSelector | string | "" | Extra namespace label selector |
| vector-logging.filter.includeNamespaces | list | [] | List of namespaces to collect |
| vector-logging.filter.excludeNamespaces | list | [] | List of namespaces to exclude |
Calico Log Parameters
| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| vector-logging.calico.enabled | bool | true | Enable Calico log collection |
| vector-logging.calico.logPath | list | ["/var/log/calico/cni/cni*.log"] | Calico log paths |
Systemd Log Parameters
| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| vector-logging.systemd.docker.enabled | bool | true | Enable Docker systemd log collection |
| vector-logging.systemd.kubelet.enabled | bool | true | Enable Kubelet systemd log collection |
| vector-logging.systemd.directory | string | /var/log/journal | Systemd journal directory |
OpenSearch Sink Parameters
| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| vector-logging.sinks.opensearch.enabled | bool | true | Enable OpenSearch sink |
| vector-logging.sinks.opensearch.index.prefix | string | "{{ .cluster }}-logs" | Index prefix |
| vector-logging.sinks.opensearch.index.timestring | string | "%Y.%m.%d" | Index time format |
ISM Policy Parameters
| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| vector-logging.ism_policy.enable | bool | false | Enable Index State Management policy |
| vector-logging.ism_policy.min_index_age | string | "7d" | Minimum index retention period |
Log Query API
Query Logs
curl -X GET "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/logging.kubesphere.io/v1alpha2/logs?operation=query&log_query=error&size=10&cluster=host&sort=desc" \
-H "X-Remote-User: admin"
Query Parameters:
| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| operation | string | query | Operation type: query/statistics/histogram/export |
| namespaces | string | | Comma-separated list of namespaces |
| namespace_query | string | | Fuzzy match namespace names |
| workloads | string | | Comma-separated list of workloads |
| workload_query | string | | Fuzzy match workload names |
| pods | string | | Comma-separated list of pods |
| pod_query | string | | Fuzzy match pod names |
| containers | string | | Comma-separated list of containers |
| container_query | string | | Fuzzy match container names |
| log_query | string | | Log content keywords (case-insensitive) |
| interval | string | 15m | Time interval for histogram (e.g., 15m, 1h, 1d) |
| start_time | string | | Start time (seconds since epoch) |
| end_time | string | | End time (seconds since epoch) |
| sort | string | desc | Sort order: asc/desc |
| from | int | 0 | Offset |
| size | int | 10 | Number of results |
| cluster | string | host | Cluster name |
| exportLineLimit | int | | Max lines for export |
Extension Operations
Check Extension Status
kubectl get installplan whizard-logging
kubectl get extensionversions -l kubesphere.io/extension-ref=whizard-logging
Uninstall Extension
Uninstall from all clusters:
kubectl delete installplan whizard-logging
Uninstall from specific cluster:
To remove WizTelemetry Logging from a specific cluster, update the InstallPlan by removing that cluster from clusterScheduling.placement.clusters:
apiVersion: kubesphere.io/v1alpha1
kind: InstallPlan
metadata:
name: whizard-logging
spec:
extension:
name: whizard-logging
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.
ai-job-search
44.0kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
41.7kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
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.
