commit | bcf045a471227c72b636b526e70d6df36f1a3395 | [log] [tgz] |
---|---|---|
author | Szymon Dompke <szymon.dompke@intel.com> | Fri Sep 16 15:23:30 2022 +0200 |
committer | Szymon Dompke <szymon.dompke@intel.com> | Fri Sep 16 16:08:47 2022 +0200 |
tree | b194e30b355941e2ffb4bbf5bd440f38ec879315 | |
parent | a8182beb1129b0608d2ddfb82895194ea3485288 [diff] |
Fix clang errors - structs used in emplace_back now have defined constructor - removed dead code from ensure Testing done: - CI tests are passing - UTs are passing Signed-off-by: Szymon Dompke <szymon.dompke@intel.com> Change-Id: I3f56a3796e45d608c7a5d3da1f8c2d674d62f567
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]
.