v2.12.0 - 14/Oct/2026
Release Notes: SUSE® Observability Helm Chart v2.12.0
|
Before you upgrade, review the version-specific upgrade instructions. Apply all steps from your current version up to this version. |
Component Versions
| Component | Version |
|---|---|
SUSE Observability |
|
SUSE Observability Values ( |
|
SUSE Observability Agent |
|
SUSE Observability CLI |
|
Resource naming changes
Selected Kubernetes resources now use fixed suse-observability-* names instead
of names derived from the Helm release or fullname settings. Bundled component
connections and collector environment overrides have also changed.
Before upgrading, follow the upgrade instructions for v2.12.0.
Monitor Silencing
Silencing lets you mute a monitor result on a component during a known issue or maintenance window. The monitor keeps evaluating health, and the result stays visible.
-
Silencing Rules: Mute a result from the monitor details. Add a note and a duration. The rule expires automatically.
-
Notification Control: By default, muted results do not trigger notifications. Optionally, get notified when silencing changes.
-
Muted Filter: Find muted components with
muted = truein the advanced topology filter.
For more information, see Silencing.
New Features & Enhancements
-
Agent Secret Management: The SUSE Observability Agent Helm chart now supports sourcing the cluster name and receiver URL directly from existing Kubernetes Secrets, simplifying GitOps workflows and enhancing credential security.
Bug Fixes
-
SUSE AI StackPack Topology: Fixed a regression where the SUSE AI StackPack failed to render OpenTelemetry-based topology relationships.
-
Show Topology Action: Fixed a rendering issue with the Show Topology button inside the Related Resources drawer.
-
Notification Email Logging: Fixed an issue where the email notification client failed to log error messages during delivery failures.
-
CPU Throttling Monitor: Adjusted the CPU Throttling monitor evaluation window to inspect the last 5 minutes of data, preventing false positives caused by brief, momentary spikes in activity.
-
Self-Monitoring Metrics: Fixed an issue where opening the same topology view across multiple browser tabs or sessions caused self-monitoring metrics (such as topology stream and WebSocket viewer counts) to intermittently drop from endpoint scrapes.