| commit | 9e8da5468b8ce2f1235bb2c50ce2b163d0704555 | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Thu Feb 17 10:40:16 2022 +0100 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Thu Feb 17 10:50:06 2022 +0100 |
| tree | 3c6a685b5d09b912743aefde55780baedf4f0315 | |
| parent | 493e62eb2f2ff6cbf3282b9cb98ebe6e520b88fc [diff] |
fixed issue with invalid readings being visible Before this change readings for sensors that are not yet available were displayed as value 0.0 with timestamp 1970-01-01 which was meant to represent invalid readings. This behaviour is undesired in case of periodic report with appendLimit set. After this change invalid readings are no longer visible. Tested: - Readings for sensors that is currently not available are not present on redfish. - Confirmed in new unit tests that sensor readings can appear in any order. And produce correct results. Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com> Change-Id: I340b85017530d120f2da2cc8ac4ae1840177e78c
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].