whizard-notification
Use when working with WizTelemetry Notification extension for KubeSphere, including installation, configuration, troubleshooting, notification channel setup, alert routing, and silence management.
Profile →npx skills add kubesphere/kubesphere --skill whizard-notification --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 describes a WizTelemetry Notification component for KubeSphere. It covers receiving alerts, cloud events, and audit logs in a multi-tenant Kubernetes environment and distributing notifications to channels based on tenant labels. It outlines the overall architecture, key components, and CRDs used to configure notification management, routing, silencing, and history storage. It also provides installation prerequisites, installation templates, and configuration parameters for notification history, alertmanager, and resource limits. Finally, it includes API patterns and concrete examples for creating receivers across global and tenant scopes.
How it works
The skill presents an operational flow where alerts flow from Prometheus/Alertmanager through a notification-manager service, then through stages (silence, route, filter, aggregation, notify) to various channels (Email, Slack, DingTalk, WeChat, Feishu, Webhook). It defines CRDs under notification.kubesphere.io/v2beta2 (NotificationManager, Receiver, Config, Router, Silence) and explains how credentials and labels link Config to Receiver and Receiver to Router for multi-tenant isolation. It lists 11 supported channels and maps configuration fields to receiver config fields. It also provides concrete installation steps: obtain the latest extension version, create an InstallPlan with required metadata, and optional config blocks to disable history or customize index formats. The API section shows how to list and create receivers via REST endpoints, including tenant-scoped operations, and provides sample payloads for creating various receivers.
When to use it
Use when working with WizTelemetry Notification for KubeSphere to install, configure, troubleshoot, and manage notification channels, alert routing, and silence management. Use the provided installation templates when installing and the REST API examples when managing receivers and related resources.
What it can touch
- CRDs under notification.kubesphere.io/v2beta2 (NotificationManager, Receiver, Config, Router, Silence)
- External services: Alertmanager, Vector, OpenSearch, and notification-history storage as part of the architecture
- APIs at /kapis/notification.kubesphere.io/v2beta2/, including tenant-scoped paths under /users/{user}/
- Commands and YAML snippets for kubectl/install plans, and curl payloads for receivers
Caveats
- The skill requires access to the WizTelemetry extension ecosystem and dependent services (Vector, OpenSearch).
- It specifies defaults and templates; deviations may affect installation plans and channel configurations as described.
- It uses explicit versioning and NodePort values for services (e.g., 31093) as defaults in the examples.
# WizTelemetry Notification ## Overview WizTelemetry Notification is the notification component of the KubeSphere observability platform. It receives alerts, cloud events, and audit logs in a multi-tenant Kubernetes environment and distributes notifications to different channels based on tenant labels (e.g., namespace). ## Architecture ``` ┌──────────────────────────────────────────────────────────────────────────────┐ │ Alertmanager │ │ Prometheus ──▶ metrics alert ──▶ notification-manager-svc:19093 │ │ K8s Events ──▶ events alert ──▶ notification-manager-svc:19093 │ │ Auditing ──▶ auditing alert ──▶ notification-manager-svc:19093 │ │ Logging ──▶ logging alert ──▶ notification-manager-svc:19093 │ └──────────────────────────────────────────────────────────────────────────────┘ │ notification-manager (:19093) │ ┌──────────────────────────┼──────────────────────────┐ │ │ │ [Silence Stage] [Route Stage] [Filter Stage] │ │ │ ▼ ▼ ▼ [Match Silence CRs] [Match Router CRs] [alertSelector filtering] │ [Aggregation Stage] │ [Notify Stage] │ ┌────────────────────────┼────────────────────────────┐ │ │ │ Email/Slack DingTalk/Feishu WeChat/Webhook │ ▼ [History Webhook] │ ▼ ┌─────────────────────
- Overview
- Architecture
- Components
- Dependencies
- CRDs
- Supported Notification Channels (11 channels)
- Config → Receiver Association Mechanism
- Installation
- Prerequisites
- Configuration Parameters
- Notification History
- Alertmanager
- Notification Manager
- Alertmanager-Proxy
kubectl get extensionversions -l kubesphere.io/extension-ref=whizard-notification -o jsonpath='{range .items[*]}{.spec.version}{"\n"}{end}' | sort -V | tail -1
curl -X GET "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/notification.kubesphere.io/v2beta2/receivers" \
curl -X GET "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/notification.kubesphere.io/v2beta2/receivers?type=email" \
curl -X GET "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/notification.kubesphere.io/v2beta2/users/admin/receivers" \
curl -X POST "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/notification.kubesphere.io/v2beta2/receivers" \
curl -X POST "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/notification.kubesphere.io/v2beta2/users/admin/receivers" \
curl -X PUT "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/notification.kubesphere.io/v2beta2/receivers/email-receiver" \
curl -X PATCH "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/notification.kubesphere.io/v2beta2/receivers/email-receiver" \
curl -X DELETE "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/notification.kubesphere.io/v2beta2/receivers/email-receiver"
curl -X GET "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/notification.kubesphere.io/v2beta2/silences"What does the whizard-notification skill do?
Use when working with WizTelemetry Notification extension for KubeSphere, including installation, configuration, troubleshooting, notification channel setup, alert routing, and silence management.
How do I install it?
Run `npx skills add kubesphere/kubesphere --skill whizard-notification --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.