| commit | f670b0261ba539256a30d45177eec84f82749faa | [log] [tgz] |
|---|---|---|
| author | Szymon Dompke <szymon.dompke@intel.com> | Wed Mar 16 19:21:11 2022 +0100 |
| committer | Szymon Dompke <szymon.dompke@intel.com> | Wed Mar 16 19:24:18 2022 +0100 |
| tree | eb88ca3f88541a393689255f7642a966c61ccc63 | |
| parent | 55824558920fbbfa8c9df64f56fa8efc981b7bb9 [diff] |
Remove code duplication from trigger actions Logging actions were using duplicated functions for discrete::Severity and numeric::Type conversion. They were replaced with common utility functions. Testing done: - UTs are passing. - Logging actions are unchanged and working properly. Signed-off-by: Szymon Dompke <szymon.dompke@intel.com> Change-Id: I353d5f58fc82809c59bc2c1fb3b926d1a6579098
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].