From 367144cfa0eb857f4cb9ba786f43933469e19e34 Mon Sep 17 00:00:00 2001 From: Matt Spinler Date: Thu, 19 Sep 2019 15:33:52 -0500 Subject: PEL: Find an entry in the message registry JSON The message registry is a JSON file that holds data required to create a PEL out of an OpenBMC event log. It includes fields like 'subsystem', 'event type', 'action flags', 'SRC reason code', etc. Many fields in the message registry are optional, and a very minimal entry make look like: { "Name": "xyz.openbmc_project.Power.Error.Fault", "Subsystem": "power_supply", "ActionFlags": ["service_action", "report"], "SRC": { "ReasonCode": "0x2030" } } This commit adds support to look up a message registry entry based on an OpenBMC event log's 'Message' property (i.e. xyz.openbmc_project.Power.Error.Fault) and then fill in a structure with the fields found. Future commits will fill in the SRC related fields, as well as actually create the PEL. The message registry file can be found on the BMC at: /usr/share/phosphor-logging/pels/message_registry.json. For testing, users can put their own message_registry.json in /etc/phosphor-logging, and that will take precedence. Signed-off-by: Matt Spinler Change-Id: Ie4195ed7e58ab6a231271f6b295e63b1d0a4cd78 --- test/openpower-pels/pel_manager_test.cpp | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'test/openpower-pels/pel_manager_test.cpp') diff --git a/test/openpower-pels/pel_manager_test.cpp b/test/openpower-pels/pel_manager_test.cpp index 0a82141..61fbedd 100644 --- a/test/openpower-pels/pel_manager_test.cpp +++ b/test/openpower-pels/pel_manager_test.cpp @@ -45,7 +45,8 @@ TEST_F(ManagerTest, TestCreateWithPEL) std::vector additionalData{adItem}; std::vector associations; - manager.create("error message", 42, 0, Entry::Level::Error, additionalData, + manager.create("error message", 42, 0, + phosphor::logging::Entry::Level::Error, additionalData, associations); // We don't know the exact name, but a file should have been added to the -- cgit v1.2.1