| commit | 9f9ff90a39219ff3a2f1179f74fc9a6dc857e5ab | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Fri Mar 05 14:57:53 2021 +0000 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Fri Mar 05 15:25:32 2021 +0000 |
| tree | f4249a93528b98f293cb5ef7cb169666c563fd91 | |
| parent | 0e7ae5dbf1c07c19f11166acc812907e4ccd01ec [diff] |
Revert "created AddReportFutureVersion dbus method" This reverts commit 753e4b3c843dd5d1068949c4106a6389f0e0ffbc. Reason for revert: Breaks bmcweb, same approach is needed for changed properties Change-Id: Id868159df916fcf0bdd7fc5062f8c51187fcc7e2
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].