whizard-telemetry
Use when installing or configuring the WizTelemetry Platform Service extension for KubeSphere, which provides the common APIServer backend services for all WizTelemetry observability extensions
npx skills add kubesphere/kubesphere --skill whizard-telemetry --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# WizTelemetry Platform Service ## Overview WizTelemetry Platform Service is a common service for all observability extensions of KubeSphere's WizTelemetry Observability Platform. It provides a common APIServer for all observability extensions, offering backend platform services for Logging, Auditing, Events, Notifications, Tracing, and more. ## When to Use - Installing or configuring the WizTelemetry Platform Service extension - Managing API services for observability extensions - Configuring OpenSearch connections for various data types - Enabling Global Observability monitoring ## Architecture ### Components | Component | Description | Default | |-----------|-------------|---------| | whizard-telemetry-apiserver | Common APIServer for all observability extensions | 1 replica | | wiz-telemetry-console | Web console for WizTelemetry | 1 replica | ### Dependencies The WizTelemetry Platform Service does not have hard dependencies on other components. All APIs can be enabled/disabled based on the deployed extensions: - **Optional**: OpenSearch - Required only when enabling logging, auditing, events, notification history, or traffic APIs - **Optional**: Prometheus - Required only when
- Overview
- When to Use
- Architecture
- Components
- Dependencies
- Installation
- Prerequisites
- Configuration from Other Extensions
- Configuration Parameters
- Image Parameters
- Scheduling Parameters
- Extension Operations
- Check Extension Status
- Check Pod Status
kubectl get extensionversions -l kubesphere.io/extension-ref=whizard-telemetry -o jsonpath='{range .items[*]}{.spec.version}{"\n"}{end}' | sort -V | tail -1
cd whizard-telemetry && ./scripts/generate-config.sh
View extension installation status
kubectl get installplan whizard-telemetry
View extension version
kubectl get extensionversions -l kubesphere.io/extension-ref=whizard-telemetry
View API server pods
kubectl get pods -n extension-whizard-telemetry -l app=whizard-telemetry-apiserver
View console pods
kubectl get pods -n extension-whizard-telemetry -l app=wiz-telemetry-consoleWhat does the whizard-telemetry skill do?
Use when installing or configuring the WizTelemetry Platform Service extension for KubeSphere, which provides the common APIServer backend services for all WizTelemetry observability extensions
How do I install it?
Run `npx skills add kubesphere/kubesphere --skill whizard-telemetry --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From kubesphere/kubesphere, a repository with 17,016 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.