| commit | b07851c5c5dc97e7ee19b66e3e4a630952ac222c | [log] [tgz] |
|---|---|---|
| author | Lei YU <yulei.sh@bytedance.com> | Thu Mar 13 02:36:19 2025 +0000 |
| committer | Lei YU <yulei.sh@bytedance.com> | Thu Mar 13 02:36:19 2025 +0000 |
| tree | ae3e6fe457efa6140c844575824fdd547f0e3593 | |
| parent | 9916d41882ff7660578edeebad2b6559d7941229 [diff] |
Fix compile error for !send-to-logger
If `send-to-logger` is disabled, the code fails to compile due to the
previous refactor for clang-tidy.
Tested: Verify the CI passes for both send-to-logger is defined or not
defined.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: Ifed296c9ac4890171b09325404d1c797923d61f4
The SEL Logger daemon handles all requests to add new IPMI SEL records to the journal. SEL records stored in the journal are identified by the standard MESSAGE_ID metadata. Other metadata fields are used to store event-specific information for each record.
SEL records are identified in the journal using the MESSAGE_ID field.
The MESSAGE_ID for SEL records is "b370836ccf2f4850ac5bee185b77893a".
The additional metadata fields for a SEL record are
IPMI_SEL_RECORD_ID = Two byte unique SEL Record ID
IPMI_SEL_RECORD_TYPE = The type of SEL entry (system or OEM)
which determines the definition of the
remaining bytes
IPMI_SEL_GENERATOR_ID = The IPMI Generator ID (usually the
IPMB Slave Address) of the requester
IPMI_SEL_SENSOR_PATH = D-Bus path of the sensor in the event
IPMI_SEL_EVENT_DIR = Direction of the event (assert or deassert)
IPMI_SEL_DATA = Raw binary data included in the SEL record
The SEL Logger daemon exposes an interface for manually adding System and OEM type SEL events, and provides the capability to monitor for types of events and log them automatically.
The interface for System type events requires
The interface for OEM type events requires
The MESSAGE_ID and IPMI_SEL_RECORD_ID metadata fields are added by the daemon.
The SEL Logger daemon can be configured to watch for specific types of events and automatically log SEL records for them.
As an example, the SEL Logger has a "threshold event monitor" which implements a D-Bus match for any "PropertiesChanged" event on the xyz.openbmc_project.Sensor.Threshold interface. The handler then checks for any new threshold events and logs SEL records accordingly.