Searched hist:"10 f3d932" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/phosphor-logging/extensions/openpower-pels/registry/schema/ |
| H A D | registry_example.json | 10f3d932 Thu Sep 26 16:24:14 CDT 2019 Matt Spinler <spinler@us.ibm.com> PEL: Add message registry JSON schema
The message registry is JSON data that will aid in converting OpenBMC
event logs into IBM's Platform Event Log (PEL) format. PELs have more
fields than event logs, many with specific IBM defined values, that need
to be able to be looked up for an OpenBMC event log so the PEL can be
filled in. In addition to aiding in creating PELs, it also contains
information to aid in parsing PELs.
This schema defines how that JSON will look, and this commit also
contains an example registry file.
A script will be added in the future to validate the registry JSON
against the schema during a bitbake build.
Until there is a need, the message registry will be contained in a
single JSON file. If there is a need, it can be split up along some
predetermined rules in the future.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I98620b263bd1faff27e36da7a0c101a982b58057
|
| H A D | schema.json | 10f3d932 Thu Sep 26 16:24:14 CDT 2019 Matt Spinler <spinler@us.ibm.com> PEL: Add message registry JSON schema
The message registry is JSON data that will aid in converting OpenBMC
event logs into IBM's Platform Event Log (PEL) format. PELs have more
fields than event logs, many with specific IBM defined values, that need
to be able to be looked up for an OpenBMC event log so the PEL can be
filled in. In addition to aiding in creating PELs, it also contains
information to aid in parsing PELs.
This schema defines how that JSON will look, and this commit also
contains an example registry file.
A script will be added in the future to validate the registry JSON
against the schema during a bitbake build.
Until there is a need, the message registry will be contained in a
single JSON file. If there is a need, it can be split up along some
predetermined rules in the future.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I98620b263bd1faff27e36da7a0c101a982b58057
|