[Starlingx-discuss] CONTEXT in events.yaml
Waines, Greg
Greg.Waines at windriver.com
Wed Feb 22 19:38:53 UTC 2023
Just a reminder ... from your StarlingX DOCS Team,
If you are updating stx/fault/fm-doc/fm_doc/events.yaml ,
In order to add a new Alarm or Log for StarlingX,
DO NOT FORGET to include the new 'Context' field. ( # Context: < none | starlingx | openstack > )
... which indicates what section of docs.starlingx.io (i.e. the platform or openstack) that the alarm/log should be published.
e.g.
100.103:
Type: Alarm
Description: |-
Memory threshold exceeded; threshold x%, actual y% .
CRITICAL @ 90%
MAJOR @ 80%
Entity_Instance_ID: |-
host=<hostname>
OR
host=<hostname>.memory=total
OR
host=<hostname>.memory=platform
OR
host=<hostname>.numa=node<number>
Severity: [critical, major]
Proposed_Repair_Action: "Monitor and if condition persists, contact next level of support; may require additional memory on Host."
Maintenance_Action:
critical: degrade
major: degrade
Inhibit_Alarms:
Alarm_Type: operational-violation
Probable_Cause: threshold-crossed
Service_Affecting: False
Suppression: True
Management_Affecting_Severity: none
Degrade_Affecting_Severity: critical
Context: starlingx
Greg / Juanita
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20230222/d0ce883a/attachment-0001.htm>
More information about the Starlingx-discuss
mailing list