Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-logging / 5eb6a2acc0e8979c004a257f2e53fb4dff5f1566 / . / extensions / openpower-pels
tree: 2a6a27556144dfd96851cf7326917ce3f0385d7e [path history] [tgz]
  1. additional_data.hpp
  2. bcd_time.cpp
  3. bcd_time.hpp
  4. entry_points.cpp
  5. log_id.cpp
  6. log_id.hpp
  7. manager.cpp
  8. manager.hpp
  9. openpower-pels.mk
  10. paths.cpp
  11. paths.hpp
  12. pel.cpp
  13. pel.hpp
  14. private_header.cpp
  15. private_header.hpp
  16. README.md
  17. repository.cpp
  18. repository.hpp
  19. section.hpp
  20. section_header.hpp
  21. stream.hpp
  22. user_header.cpp
  23. user_header.hpp
extensions/openpower-pels/README.md

OpenPower Platform Event Log (PEL) extension

This extension will create PELs for every OpenBMC event log. It is also possible to point to the raw PEL to use in the OpenBMC event, and then that will be used instead of creating one.

Passing PEL related data within an OpenBMC event log

An error log creator can pass in data that is relevant to a PEL by using certain keywords in the AdditionalData property of the event log.

AdditionalData keywords

RAWPEL

This keyword is used to point to an existing PEL in a binary file that should be associated with this event log. The syntax is:

RAWPEL=<path to PEL File>
e.g.
RAWPEL="/tmp/pels/pel.5"

The code will assign its own error log ID to this PEL, and also update the commit timestamp field to the current time.

_PID

This keyword that contains the application's PID is added automatically by the phosphor-logging daemon when the commit or report APIs are used to create an event log, but not when the Create D-Bus method is used. If a caller of the Create API wishes to have their PID captured in the PEL this should be used.

This will be added to the PEL in a section of type User Data (UD), along with the application name it corresponds to.

The syntax is:

_PID=<PID of application>
e.g.
_PID="12345"

The PEL Message Registry

D-Bus Interfaces