1description: >
2    Implement to provide PEL event/error entry attributes.
3properties:
4    - name: Hidden
5      type: boolean
6      default: false
7      description: >
8          Hidden Error - This flag allows events to be placed in a system, but
9          remain hidden from the customer. This event log is visible to
10          development personnel only, e.g. hardware recovered error, etc. No
11          service action is required for this type of errors. In general, when
12          this value is used, the Error Action Flags has the value of "Hidden
13          Error". An event log with this value is used primarily for error
14          thresholding design/code debug or as a record to indicate an error
15          frequency or trend.
16    - name: Subsystem
17      type: string
18      description: >
19          A free form, implementation defined string which uniquely and
20          permanently identifies a specific subsystem string. This field should
21          not be used for programmatic interrogation of an object.
22    - name: ManagementSystemAck
23      type: boolean
24      default: false
25      description: >
26          Notifies the PEL handler that the management system acknowledged a
27          PEL. The management system can be any system monitoring the hardware.
28    - name: PlatformLogID
29      type: uint32
30      description: >
31          This is the Platform Log ID field in the Private Header section of a
32          PEL.  It is the unique ID for a single event.  Multiple PELs can be
33          linked to the same event by using the same PLID value.
34    - name: Deconfig
35      type: boolean
36      default: false
37      description: >
38          Indicates that one or more resources were deconfigured due to this
39          error.
40    - name: Guard
41      type: boolean
42      default: false
43      description: >
44          Indicates that one or more resources were guarded due to this error.
45    - name: Timestamp
46      type: uint64
47      description: >
48          The creation timestamp of the PEL in milliseconds since the epoch. For
49          PELs created by subsystems other than the BMC, this can be different
50          than the timestamp property on the xyz.openbmc_project.Logging.Entry
51          interface.
52