| commit | 31db7f71ec023eb6b0e630fa18048b6fd9ae7430 | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Tue Dec 21 12:26:22 2021 +0100 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Tue Dec 21 12:26:22 2021 +0100 |
| tree | fecc78fbfaec836217b2e81c83d85df538277e48 | |
| parent | 3e2cc9d4978cf8f8bab4384dfd2b4996d95040fe [diff] |
Added missing const No functional changes. Tested: - Compiles and unit tests are passing Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com> Change-Id: I3b22bdf1b99fe5893459bb0fa57b261b272700a2
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].