whizard-telemetry-ruler

Configuring alerting rules for Kubernetes events and logs in KubeSphere is done by defining and managing rules through the WizTelemetry Ruler, which orchestrates consistent alerting across clusters and environments.

The best way to manage WizTelemetry alerting rules across multiple clusters is by using the Ruler component to orchestrate configurations, ensuring deterministic deployment and consistent alerting for events, audits, and logs.

Yes, WizTelemetry Ruler supports AlertManager as a sink, allowing operators to configure and route alerting rules for Kubernetes events, auditing events, and logs directly to AlertManager.

Installation prerequisites for WizTelemetry alerting components are met using template-driven InstallPlan support, which ensures deterministic deployment and configures required dependencies like the WizTelemetry Platform Service.

Yes, you can integrate OpenSearch for optional persistence when configuring log alerting rules, enhancing the WizTelemetry Ruler's capability to manage and retain alerting data across clusters.

Enabling auditing events is required to capture K8s and KubeSphere audit logs, allowing the WizTelemetry Ruler to define, configure, and manage comprehensive alerting rules across your environments.