Silencing
Silencing marks a monitor result as muted while you investigate a known issue or perform maintenance. The monitor continues to evaluate health, and its result remains visible. A silencing rule applies to one monitor result on one component.
A component is muted when it has failing monitor results and all those results are silenced. Its health stays unchanged: a critical component can also be muted. If another monitor fails without silencing, the component is unmuted. The muted badge shows a Muted since tooltip.
Permissions
Silencing is available by default.
You need get-silencing-rules to view rules, create-silencing-rules to mute a result, and delete-silencing-rules to unmute it.
Administrator, Power User, and Kubernetes Troubleshooter roles have all three permissions.
The Guest role can view rules.
See Permissions for custom roles.
Mute a monitor result
You need create-silencing-rules and must use live mode.
-
Open the component’s Highlights perspective.
-
Select a monitor message to open its details.
-
Select Silencing rules.
-
Choose a duration under Mute for.
-
Enter a Silencing note to explain the reason.
-
Select Mute monitor.
The rule expires automatically after the selected duration. It does not mute this monitor on other components.
Unmute a monitor result
-
Open the monitor details in live mode.
-
Select Silencing rules.
-
Select Unmute monitor to remove the rule.
You need delete-silencing-rules.
If multiple rules apply, the result stays muted until all applicable silencing ends.
For an external silencing rule, update the external source instead.
Find muted components
In the advanced topology filter, use muted = true to select muted components or muted = false to select unmuted components.
Components whose silencing state is not yet known match neither value.
External health
External monitoring systems can send silencing information with their health results. See Silence an external health result.