Use when working with WizTelemetry Notification extension for KubeSphere, including installation, configuration, troubleshooting, notification channel setup, alert routing, and silence management.
Install
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add kubesphere/kubesphere --skill whizard-notification -a cursor -y
Download skills/whizard-notification/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does whizard-notification live?
The publisher keeps it at https://github.com/kubesphere/kubesphere.
Which agents can use whizard-notification?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.
Use when working with WizTelemetry Notification extension for KubeSphere, including installation, configuration, troubleshooting, notification channel setup, alert routing, and silence management.
name: whizard-notification
description: Use when working with WizTelemetry Notification extension for KubeSphere, including installation, configuration, troubleshooting, notification channel setup, alert routing, and silence management.
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).
All APIs are at /kapis/notification.kubesphere.io/v2beta2/, routed through whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80. No authentication token is required.
# Basic search
curl -X GET "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/notification.kubesphere.io/v2beta2/notifications/search?size=10"
# Search with filters
curl -X GET "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/notification.kubesphere.io/v2beta2/notifications/search?alertname=KubeNodeReady&severity=critical&namespace=default&size=20&sort=startTime&order=desc"
# Search with time range
curl -X GET "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/notification.kubesphere.io/v2beta2/notifications/search?start_time=1704067200&end_time=1704153600&size=50"
Notification Search Query Parameters:
Parameter
Description
status
Alert status: firing, resolved (comma-separated)
alertname
Alert name (comma-separated, exact match)
alertname_fuzzy
Alert name fuzzy match
alerttype
Alert type (comma-separated)
alerttype_fuzzy
Alert type fuzzy match
severity
Severity level (comma-separated)
severity_fuzzy
Severity level fuzzy match
namespace
Namespace (comma-separated)
namespace_fuzzy
Namespace fuzzy match
message_fuzzy
Alert message fuzzy match
start_time
Start time (Unix timestamp, seconds)
end_time
End time (Unix timestamp, seconds)
sort
Sort field (e.g., startTime)
order
Sort order: asc or desc (default: desc)
from
Offset from result set (default: 0)
size
Number of results (default: 10, max: 100)
cluster
Cluster name
Extension Operations
Check Extension Status
kubectl get installplan whizard-notification
kubectl get extension whizard-notification
kubectl get extensionversion -l kubesphere.io/extension-ref=whizard-notification
Check Pod Status
# notification-manager operator + deployment
kubectl get pods -n kubesphere-monitoring-system -l notification-manager=notification-manager
# alertmanager
kubectl get pods -n kubesphere-monitoring-system -l app.kubernetes.io/name=alertmanager
# alertmanager-proxy
kubectl get pods -n kubesphere-monitoring-system -l name=alertmanager-proxy
# 1. Check if notification-manager is running
kubectl get pods -n kubesphere-monitoring-system -l notification-manager=notification-manager
# 2. Check if alertmanager receives alerts
kubectl logs -n kubesphere-monitoring-system -l app.kubernetes.io/name=alertmanager --tail=50
# 3. Check notification-manager logs
kubectl logs -n kubesphere-monitoring-system -l notification-manager=notification-manager -c notification-manager --tail=100 | grep -i error
# 4. Check if Receiver and Config exist
kubectl get receivers,configs -n kubesphere-monitoring-system
# 5. Check if silenced by Silence CR
kubectl get silences
Issue 2: Notification History Empty
# 1. Check if vector aggregator is running
kubectl get pods -n kubesphere-logging-system -l app.kubernetes.io/name=vector-aggregator
# 2. Check if vector-sinks secret exists
kubectl get secret vector-sinks -n kubesphere-logging-system
# 3. Check OpenSearch indices exist
# (requires OpenSearch API or Kibana)
# Check image tag config; manually set old tags block upgrades
kubectl get installplan whizard-notification -n kubesphere-system -o yaml | grep -i image
# Remove or update manually set image.tag in InstallPlan config
Important Notes
Dependency order: Install vector, and opensearch first if notification history is enabled
OpenSearch: Notification history sink credentials are auto-loaded from vector-sinks Secret
Image tags: Before upgrading, check and remove manually set image.tag to avoid pulling stale images
How do I install whizard-notification?
Download skills/whizard-notification/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does whizard-notification live?
The publisher keeps it at https://github.com/kubesphere/kubesphere.
Which agents can use whizard-notification?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.