Set-PveClusterCephHealthMute

Mute or unmute a Ceph health check. A muted check no longer counts towards the cluster status, but stays visible and keeps being evaluated.

API: PUT /cluster/ceph/health-mute/{code}, Proxmox VE API viewer

Syntax

Set-PveClusterCephHealthMute
    [-PveTicket <PveTicket>]
    -Code <string>
    [-Sticky <bool>]
    [-Ttl <string>]
    -Value <bool>
    [<CommonParameters>]

Parameters

Parameter	Type	Required	Description
-PveTicket	PveTicket	No	Ticket data connection.
-Code	string	Yes	The health check to mute, as reported by ‘ceph health’, for example ‘AUTH_INSECURE_CLIENT_KEY_TYPE’.
-Sticky	bool	No	Keep the mute even when the check gets worse. Without this a mute clears itself as soon as the number of affected items grows, which brings the check back to attention. Only used when muting.
-Ttl	string	No	How long the mute lasts, for example ‘2h’, ‘3d’ or ‘1w’. Without it the mute has no expiry. Only used when muting.
-Value	bool	Yes	Whether to mute (true) or unmute (false) the check.

Every parameter also binds by property name from the pipeline, so an object with node and vmid properties (the output of Get-PveGuest, for one) fills -Node and -Vmid. Without -PveTicket the cmdlet uses the last connection, see Connection.

Output

A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.