| commit | 8018a3ba9782e85ac49686a454183dc4580547e9 | [log] [tgz] |
|---|---|---|
| author | Michal Orzel <michalx.orzel@intel.com> | Wed Jun 26 14:14:16 2024 +0200 |
| committer | Michal Orzel <michalx.orzel@intel.com> | Mon Jul 15 15:04:35 2024 +0200 |
| tree | 8645febe14d1be28bf39a0e247bd7ec60b9d402e | |
| parent | b3e03d2d6b42298411d29329b5456d62da289461 [diff] |
Adjust LogToRedfish trigger action to DMTF standard This patch modifies messages sent to Redfish event log to be compliant with message registry schema [1]. Tested: On platform, with corresponding bmcweb patch [2]. Verified that messages appearing in Redfish event log are compliant with schema. UTs passed. [1] https://redfish.dmtf.org/registries/Telemetry.1.0.0.json [2] https://gerrit.openbmc.org/c/openbmc/bmcweb/+/72315 Change-Id: Ide3d5a13e5be077806df6398c5f51da41f7a7922 Signed-off-by: Michal Orzel <michalx.orzel@intel.com>
This component implements middleware for sensors and metrics aggregation.
This application is implementation of Telemetry proposed in OpenBMC design docs [1].
It's responsible for:
[2],[3] updates.[4]There are two way to build telemetry service:
To build it using bitbake follow the guide from OpenBMC docs[5]. To build it using meson follow the quick guide to install meson[6] and then run below commands
meson build
cd build
ninja
After successful build you should be able to run telemetry binary or start unit tests
./tests/telemetry-ut ./telemetry
In case if system is missing boost dependency, it is possible to build it locally and set BOOST_ROOT environment variable to location of built files for meson. After this change meson should be able to detect boost dependency. See [7] for more details.
More information can be found in OpenBMC docs repository [8].