| commit | ae9bd58a009c69a43f1b1b35b4f16e4673ea0a73 | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Mon Feb 14 11:03:21 2022 +0100 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Mon Feb 14 11:03:44 2022 +0100 |
| tree | aaf02c634ea09d89a716bdb723379d929c7046a2 | |
| parent | b4ef22e4d365bde35a7fce7950033c9271c68ce7 [diff] |
updated google test version Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com> Change-Id: I0d48bfa6a19e604fb3a4d07fc4cdb4220924329f
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].