
Whizard Telemetry Ruler
Use when working with WizTelemetry Ruler extension for KubeSphere, including...
Install
npx skills add kubesphere/kubesphere --skill whizard-telemetry-ruler -g -a claude-code -y- Repository
- kubesphere/kubesphere17.1k
- Category
- Engineering
- Updated
- 4mo ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Use when working with WizTelemetry Ruler extension for KubeSphere, including installation, configuration, alerting rules management
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): Optional (for alert notification)
- WizTelemetry Data Pipeline (vector): Required if alerting persistence is enabled
- OpenSearch (opensearch): Required if alerting persistence is enabled
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
