whizard-notification

Name: whizard-notification
Availability: InStock
Author: KubeSphere

Automate centralized alert routing across multi-tenant Kubernetes clusters using WizTelemetry CRDs.

17.0k|2.8k|Updated Apr 21, 2018

Search Tags:#routing #kubernetes #extension #alerting #notification #ops #tenancy

Ready to run

npx skills add https://github.com/kubesphere/kubesphere --skill whizard-notification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: whizard-notification
Source: https://github.com/kubesphere/kubesphere/tree/main/skills/whizard-notification
Command: npx skills add https://github.com/kubesphere/kubesphere --skill whizard-notification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

WizTelemetry Notification centralizes alert delivery in a multi-tenant Kubernetes environment, enabling consistent routing, silencing, and channel delivery to reduce noise and ensure critical alerts reach the right teams.

Core Features & Use Cases

Supports CRDs such as Receiver, Router, and Silence for flexible, API-driven alert management across tenants.
Routes notifications to multiple channels (Email, Slack, DingTalk, WeChat, Feishu, Webhook, and more) and supports channel-specific configuration and templates.
Use cases include enterprise incident response, on-call rotation, and per-tenant notification policies with isolated namespaces.

Quick Start

Install the whizard-notification extension and configure a sample Receiver and Router to start routing alerts to your chosen channels.

Frequently Asked Questions about whizard-notification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I route Kubernetes alert notifications to multiple channels in a multi-tenant environment?▼

You can route Kubernetes alert notifications by configuring Receiver and Router CRDs to direct alerts to channels like Email, Slack, DingTalk, and Webhook while maintaining per-tenant namespace isolation.

How does centralized alert routing work for tenant-specific notification policies?▼

Centralized alert routing uses custom CRDs to apply API-driven notification policies, ensuring alerts are delivered to the correct tenant teams with isolated namespace configurations and channel-specific templates.

Can I silence noisy alerts per tenant in a Kubernetes cluster?▼

Yes, you can silence noisy alerts per tenant by applying the Silence CRD, which stops specific alert notifications within isolated namespaces to reduce noise during maintenance or known issues.

What notification channels are supported for Kubernetes alert delivery?▼

Supported notification channels for Kubernetes alert delivery include Email, Slack, DingTalk, WeChat, Feishu, and Webhook, allowing flexible configuration and templates for enterprise incident response.

How do I install and configure alert notification routing for KubeSphere?▼

To set up alert notification routing, install the whizard-notification extension and configure a sample Receiver and Router to immediately start delivering alerts to your chosen notification channels.