Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-logging / 5b3a11db9c1f9715cc6371ecdcaa6bc54343ecc0 / . / extensions / openpower-pels
tree: 963c85f091e64e9c5bbb496a8e1963f79bcdc850 [path history] [tgz]
  1. additional_data.hpp
  2. ascii_string.cpp
  3. ascii_string.hpp
  4. bcd_time.cpp
  5. bcd_time.hpp
  6. data_interface.cpp
  7. data_interface.hpp
  8. entry_points.cpp
  9. failing_mtms.cpp
  10. failing_mtms.hpp
  11. fru_identity.cpp
  12. fru_identity.hpp
  13. generic.cpp
  14. generic.hpp
  15. log_id.cpp
  16. log_id.hpp
  17. manager.cpp
  18. manager.hpp
  19. mtms.cpp
  20. mtms.hpp
  21. openpower-pels.mk
  22. paths.cpp
  23. paths.hpp
  24. pce_identity.cpp
  25. pce_identity.hpp
  26. pel.cpp
  27. pel.hpp
  28. pel_types.hpp
  29. pel_values.cpp
  30. pel_values.hpp
  31. private_header.cpp
  32. private_header.hpp
  33. README.md
  34. registry.cpp
  35. registry.hpp
  36. repository.cpp
  37. repository.hpp
  38. section.hpp
  39. section_factory.cpp
  40. section_factory.hpp
  41. section_header.hpp
  42. severity.cpp
  43. severity.hpp
  44. stream.hpp
  45. user_data.cpp
  46. user_data.hpp
  47. user_header.cpp
  48. 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