whizard-telemetry-ruler
Use when working with WizTelemetry Ruler extension for KubeSphere, including installation, configuration, alerting rules management
Profile →npx skills add kubesphere/kubesphere --skill whizard-telemetry-ruler --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.
What it does
The skill guides you to work with the WizTelemetry Ruler extension for KubeSphere, enabling creation, updating, or deletion of alerting rules (RuleGroup/ClusterRuleGroup), managing alerting configurations, and using the ruler API to manage alerting rules. It details installing the ruler, configuring alert sinks (including AlertManager), and enabling various alerting types (auditing, events, logging). It also provides templates for InstallPlan configurations and example API calls for managing RuleGroups and querying alerts.
How it works
- It defines when to use the ruler: during installation, configuration, and alert rule management.
- It lists components and dependencies, including required WizTelemetry services and optional notification sinks.
- It provides installation templates with placeholders for version, target clusters, and AlertManager host, instructing exact YAML structure and mandatory field usage.
- It specifies configuration parameters for enabling auditing, events, and logging alerting, and for sinks and persistence when applicable.
- It includes concrete API call examples for RuleGroup and ClusterRuleGroup operations and for querying alerts.
When to use it
Use when installing or configuring the WizTelemetry Ruler extension, when creating/updating/deleting alerting rules (RuleGroup/ClusterRuleGroup), when managing alerting configurations, and when using the ruler API to manage alerting rules.
What it can touch
- YAML InstallPlan manifests with fields: apiVersion, kind, metadata.name, metadata.namespace, spec.extension.name, spec.extension.version, spec.enabled, spec.upgradeStrategy, in config block the whizard-telemetry-ruler.config and sinks; clusterScheduling.placement.clusters.
- Values that appear in the templates include VERSION, TARGET_CLUSTERS, and ALERT_MANAGER_HOST, which are placeholders to be replaced with real values.
- It provides commands for kubectl and curl usage within the described workflows and API endpoints within the example blocks.
Caveats
- Requires a specific InstallPlan metadata name: whizard-telemetry-ruler.
- The config field must be YAML with the exact structure shown; placeholders must be replaced; do not modify the structure.
- OpenSearch and vector are required if alerting persistence is enabled; some dependencies are only required when certain alerting types are enabled.
# WizTelemetry Ruler ## Overview WizTelemetry Ruler is an extension component in the KubeSphere Observability Platform that provides event alerting and log alerting capabilities. It can define alerting rules for K8s native events, K8s/KubeSphere auditing events, and K8s logs, evaluate incoming event data and log data, and send alerts to specified receivers such as alertmanager, etc. ## When to Use - Installing or configuring the WizTelemetry Ruler extension - Creating, updating, or deleting alerting rules (RuleGroup/ClusterRuleGroup) - Managing alerting configurations - Using the ruler API to manage alerting rules ## Components | Component | Description | Default Enabled | |-----------|-------------|-----------------| | whizard-telemetry-ruler | Core ruler component for alerting | true | ## Dependencies - **WizTelemetry Platform Service** (whizard-telemetry): Required - **WizTelemetry Events** (whizard-events): Required if event alerting is enabled - **WizTelemetry Auditing** (whizard-auditing): Required if auditing alerting is enabled - **WizTelemetry Logging** (whizard-logging): Required if logging alerting is enabled - **WizTelemetry Notification** (whizard-notification): Option
- Overview
- When to Use
- Components
- Dependencies
- Installation
- Prerequisites
- Install WizTelemetry Ruler
- Configuration Parameters
- Alerting Type Parameters
- Sink Configuration Parameters
- Alert Persistence Parameters (Optional)
- Resource Parameters
- Node Scheduling Parameters
- Alerting Rule API
kubectl get clusters -o jsonpath='{.items[*].metadata.name}'
kubectl get nodes -o jsonpath='{.items[0].status.addresses[?(@.type=="InternalIP")].address}'
curl -X GET "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/logging.whizard.io/v1alpha1/clusterrulegroups?clusterName=host" \
curl -X POST "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/logging.whizard.io/v1alpha1/clusterrulegroups?clusterName=host" \
curl -X POST "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/events.alerting.wiztelemetry.io/v1alpha1/query" \
curl -X POST "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/events.alerting.wiztelemetry.io/v1alpha1/statistics" \
kubectl get installplan whizard-telemetry-ruler
kubectl get extensionversions -l kubesphere.io/extension-ref=whizard-telemetry-ruler
kubectl delete installplan whizard-telemetry-rulerWhat does the whizard-telemetry-ruler skill do?
Use when working with WizTelemetry Ruler extension for KubeSphere, including installation, configuration, alerting rules management
How do I install it?
Run `npx skills add kubesphere/kubesphere --skill whizard-telemetry-ruler --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.