| commit | 0452976942f7c9e9a3ace74bf71b946d53ead203 | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Thu Nov 24 15:16:42 2022 +0000 |
| committer | Szymon Dompke <szymon.dompke@intel.com> | Tue Dec 20 17:46:56 2022 +0100 |
| tree | edc20e25b9dd85e59019d9498a0be66cdd0d6879 | |
| parent | 9189e35fb25188b438fd536e4f7173bbf2911473 [diff] |
removed unused include Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com> Change-Id: I1cd4601a327c17f1bb5ada5b82600e1c886364f9
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].