Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when working with WizTelemetry Logging extension for KubeSphere, including installation, configuration, and log query API
.claude/skills/kubesphere-whizard-logging/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 72% | 0% |
| case-07 | ✗→✓ | ▲ Improved | 14% | 0% |
| case-06 | ✗→✓ | ▲ Improved | 41% | 0% |
| case-02 | ✗→✓ | ▲ Improved | 199% | 0% |
| case-03 | ✗→✓ | ▲ Improved | 215% | 0% |
WizTelemetry Logging is an extension component in the KubeSphere Observability Platform for log collection, processing, and storage.
| 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 |
REQUIRED: Complete all steps in order before generating InstallPlan.
⚠️ CRITICAL: DO NOT proceed until target clusters are determined.
Step 1.1: Get available clusters
bashkubectl get clusters -o jsonpath='{.items[*].metadata.name}'
Step 1.2: Determine target clusters
Ask user (if not specified):
Available clusters: host, dev
Which clusters do you want to deploy WizTelemetry Logging to?MUST do this to get the latest version:
bashkubectl 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.
⚠️ IMPORTANT: Complete prerequisite steps BEFORE this step.
Based on your selections:
⚠️ CRITICAL: InstallPlan metadata.name MUST be whizard-logging. DO NOT use any other name.
⚠️ CRITICAL: config field is YAML format. You MUST:
⚠️ CRITICAL: All placeholders MUST be replaced with actual values. DO NOT leave them as placeholders.
yamlapiVersion: 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 namesNote: OpenSearch sink configuration (endpoints, auth) is provided by the vector extension. Make sure vector is installed and configured with OpenSearch before installing logging.
To enable disk log collection, add logsidecar-injector to the config:
yamlapiVersion: 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>
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
bashcurl -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 |
bashkubectl get installplan whizard-logging kubectl get extensionversions -l kubesphere.io/extension-ref=whizard-logging
Uninstall from all clusters:
bashkubectl 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:
yamlapiVersion: 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
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→pass | 21,276 | 21,567 | +1% | 1 | 1 | 0% | 2,580 | 4,446 | +72% | 0 | 0 | — |
case-07 | fail→pass | 12,817 | 1,513 | -88% | 1 | 1 | 0% | 2,298 | 2,610 | +14% | 0 | 0 | — |
case-06 | fail→pass | 10,240 | 4,713 | -54% | 1 | 1 | 0% | 1,976 | 2,796 | +41% | 0 | 0 | — |
case-02 | fail→pass | 33,886 | 6,018 | -82% | 1 | 1 | 0% | 1,060 | 3,166 | +199% | 0 | 0 | — |
case-03 | fail→pass | 6,732 | 7,107 | +6% | 1 | 1 | 0% | 1,191 | 3,757 | +215% | 0 | 0 | — |
case-04 | fail→pass | 11,053 | 1,982 | -82% | 1 | 1 | 0% | 979 | 2,753 | +181% | 0 | 0 | — |
case-05 | fail→pass | 25,234 | 3,162 | -87% | 1 | 1 | 0% | 1,630 | 2,891 | +77% | 0 | 0 | — |
case-08 | pass→pass | 9,468 | 1,520 | -84% | 1 | 1 | 0% | 1,670 | 2,601 | +56% | 0 | 0 | — |
case-09 | pass→pass | 5,856 | 1,270 | -78% | 1 | 1 | 0% | 977 | 2,595 | +166% | 0 | 0 | — |
case-10 | fail→pass | 9,806 | 1,830 | -81% | 1 | 1 | 0% | 988 | 2,634 | +167% | 0 | 0 | — |
case-11 | fail→pass | 10,707 | 3,105 | -71% | 1 | 1 | 0% | 1,531 | 2,707 | +77% | 0 | 0 | — |
case-12 | fail→pass | 9,083 | 1,563 | -83% | 1 | 1 | 0% | 1,536 | 2,567 | +67% | 0 | 0 | — |
case-13 | fail→pass | 13,697 | 3,473 | -75% | 1 | 1 | 0% | 2,221 | 3,024 | +36% | 0 | 0 | — |
case-14 | fail→pass | 8,721 | 2,637 | -70% | 1 | 1 | 0% | 1,486 | 2,850 | +92% | 0 | 0 | — |
case-15 | fail→pass | 11,976 | 3,303 | -72% | 1 | 1 | 0% | 2,179 | 3,067 | +41% | 0 | 0 | — |
case-16 | fail→pass | 10,111 | 1,883 | -81% | 1 | 1 | 0% | 1,480 | 2,685 | +81% | 0 | 0 | — |
case-17 | fail→pass | 9,175 | 2,996 | -67% | 1 | 1 | 0% | 1,463 | 2,664 | +82% | 0 | 0 | — |
case-18 | pass→pass | 5,843 | 4,098 | -30% | 1 | 1 | 0% | 957 | 3,183 | +233% | 0 | 0 | — |
case-19 | fail→pass | 13,694 | 2,042 | -85% | 1 | 1 | 0% | 2,164 | 2,775 | +28% | 0 | 0 | — |
case-20 | fail→fail | 19,184 | 6,607 | -66% | 1 | 1 | 0% | 1,547 | 3,317 | +114% | 0 | 0 | — |
case-21 | fail→fail | 16,958 | 9,846 | -42% | 1 | 1 | 0% | 2,235 | 4,242 | +90% | 0 | 0 | — |
case-22 | fail→fail | 16,883 | 13,316 | -21% | 1 | 1 | 0% | 3,277 | 4,692 | +43% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 20 counted toward the lift figure. The other 2 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +73 percentage points is the difference between those two pass rates over the 20 comparable cases.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.