| commit | 41fa80d8c77fb8822e867e4f436e845d58af3e15 | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Thu Jun 09 13:27:16 2022 +0200 |
| committer | Szymon Dompke <szymon.dompke@intel.com> | Fri Jun 10 07:34:30 2022 +0000 |
| tree | 5807ff54a362f3b329d4d73816376fc50b5487c0 | |
| parent | 973b4bb0d08ef9e29cbe13142a60812edff47565 [diff] |
Minor refactoring in thresholds No functional changes Tested: - All unit tests are passing Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com> Change-Id: I96360276cc7e7797a9e90a577804e94014e0bd91
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].