starlingx/docs
Code Issues Proposed changes
47040fa69b
docs/doc/source/fault-mgmt/kubernetes/unsuppressing-an-alarm-using-the-cli.rst
Ron Stone f125a8b892 Remove spurious escapes (r8,dsR8) 
This change addresses a long-standing issue in rST documentation imported from XML.
That import process added backslash escapes in front of various characters. The three
most common being '(', ')', and '_'.
These instances are removed.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Id43a9337ffcd505ccbdf072d7b29afdb5d2c997e
2023-03-01 11:19:04 +00:00

1.0 KiB
Raw Blame History

Unsuppress an Alarm Using the CLI

If you need to reactivate a suppressed alarm, you can do so using the CLI.

  • Use the fm event-unsuppress CLI command to unsuppress a currently suppressed alarm.

    ~(keystone_admin)$ fm event-unsuppress [--nowrap] --alarm_id <alarm-id>[,<alarm-id>] \
[--nopaging] [--uuid]

    where

    <alarm-id>

    is a comma separated Alarm ID list of alarms to unsuppress.

    --nowrap

    disables output wrapping.

    --nopaging

    disables paged output

    --uuid

    includes the alarm type UUIDs in the output.

    Alarm type(s) with the specified <alarm-id(s)> will be unsuppressed.

    You can unsuppress all currently suppressed alarms using the following command:

    ~(keystone_admin)$ fm event-unsuppress -all [--nopaging] [--uuid]