docs/doc/source/fault-mgmt/openstack/openstack-alarm-messages-300s.rst
egoncalv fa9957b251 Update Alarms for Release 21.07
Fixed tables format and typo.

Removed note and applied changes requested by Mary.

Signed-off-by: egoncalv <elisamaraaoki.goncalves@windriver.com>
Change-Id: I9614f576628b3eb4cc76552147dae37f0c680e42
2021-07-26 13:17:12 -03:00

13 KiB

Alarm Messages - 300s

The system inventory and maintenance service reports system changes with different degrees of severity. Use the reported alarms to monitor the overall health of the system.

For more information, see Overview <openstack-fault-management-overview>.

In the following tables, the severity of the alarms is represented by one or more letters, as follows:

  • C: Critical
  • M: Major
  • m: Minor
  • W: Warning

A slash-separated list of letters is used when the alarm can be triggered with one of several severity levels.

An asterisk (*) indicates the management-affecting severity, if any. A management-affecting alarm is one that cannot be ignored at the indicated severity level or higher by using relaxed alarm rules during an orchestrated patch or upgrade operation.

Differences exist between the terminology emitted by some alarms and that used in the , GUI, and elsewhere in the documentation:

  • References to provider networks in alarms refer to data networks.
  • References to data networks in alarms refer to physical networks.
  • References to tenant networks in alarms refer to project networks.