| commit | 36de0563f9f05dd325cf626ac18d0af1437fbab4 | [log] [tgz] |
|---|---|---|
| author | Ed Tanous <edtanous@google.com> | Fri May 27 13:05:49 2022 -0700 |
| committer | Ed Tanous <edtanous@google.com> | Fri May 27 13:07:19 2022 -0700 |
| tree | dcce109f774fcf99e01e47e9366c8521c6d1e5e5 | |
| parent | e0ed508c17b8933762faa7a5e22dd2aa93200278 [diff] |
Include-what-you-use This fixes a build error on the latest rebase by following the coding standard, and including the headers of the resources used. In this case, std::find is in the algorithm library, so add that include. Tested: Code compiles. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: Icd62174faf57c769e114583c841181f2229c9c79
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].