| commit | 55824558920fbbfa8c9df64f56fa8efc981b7bb9 | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Fri Feb 18 16:15:31 2022 +0100 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Fri Feb 18 16:15:31 2022 +0100 |
| tree | bbd96facdecaf15d1f3fa7e861225abc7a30020c | |
| parent | 9e8da5468b8ce2f1235bb2c50ce2b163d0704555 [diff] |
Fixed issue with displaying empty triggers It was not possible to display empty triggers due to one of the property handlers returning error. This fixes handlers and proper value is returned instead. Tested: - All unit tests are passing. - Can introspect empty triggers - Empty triggers are correctly listed in redfish Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com> Change-Id: I1ce9a9a43faac5446911f0e44c638b4ca91adb82
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].