Skip to content

STAC-25181: Rename suppression -> silencing-rule - #391

Open
aacevedoosorio wants to merge 1 commit into
rancher:mainfrom
aacevedoosorio:stac-25181
Open

STAC-25181: Rename suppression -> silencing-rule#391
aacevedoosorio wants to merge 1 commit into
rancher:mainfrom
aacevedoosorio:stac-25181

Conversation

@aacevedoosorio

Copy link
Copy Markdown
Contributor

No description provided.

@aacevedoosorio
aacevedoosorio requested a review from a team as a code owner August 24, 2026 12:21
@netlify

netlify Bot commented Aug 24, 2026

Copy link
Copy Markdown

Deploy Preview for suse-obs ready!

Name Link
🔨 Latest commit e761006
🔍 Latest deploy log https://app.netlify.com/projects/suse-obs/deploys/6a8c39c8cb84fd000807f67f
😎 Deploy Preview https://deploy-preview-391--suse-obs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.




Silencing rules let you acknowledge health violations that are already known or being actively worked on, so that ongoing incidents don't generate noise for your team. A Silencing rules can be applied to a single health violation directly from the UI, with an optional note and an expiry window. Suppressed states remain visible but are visually distinguished from non silenced violations; they are also reflected in notifications, which can be configured to include or exclude silencing events. External monitoring sources can carry silencing information directly on the health stream..

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Silencing rules let you acknowledge health violations that are already known or being actively worked on, so that ongoing incidents don't generate noise for your team. A Silencing rules can be applied to a single health violation directly from the UI, with an optional note and an expiry window. Suppressed states remain visible but are visually distinguished from non silenced violations; they are also reflected in notifications, which can be configured to include or exclude silencing events. External monitoring sources can carry silencing information directly on the health stream..
Silencing rules let you acknowledge health violations that are already known or being actively worked on, so that ongoing incidents don't generate noise for your team. A Silencing rules can be applied to a single health violation directly from the UI, with an optional note and an expiry window. Silenced states remain visible but are visually distinguished from non silenced violations; they are also reflected in notifications, which can be configured to include or exclude silencing events. External monitoring sources can carry silencing information directly on the health stream..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants