| commit | 0253f6d3cbcad7714bea2e8c67845bb9ed18a2ee | [log] [tgz] |
|---|---|---|
| author | Szymon Dompke <szymon.dompke@intel.com> | Thu Sep 15 23:18:19 2022 +0200 |
| committer | Szymon Dompke <szymon.dompke@intel.com> | Fri Sep 16 16:31:54 2022 +0200 |
| tree | 9d7268fec67161e0c828d7f22aec2a834261128e | |
| parent | bcf045a471227c72b636b526e70d6df36f1a3395 [diff] |
Persistency: store special double values Json library handles infinity and NaN as null. During deserialization, we expect a double and those files were marked as invalid and removed. To prevent this behavior and preserve all double values, LabeledTuple 'to_json' and 'from_json' functions were improved to accommodate those special values by using string literals. Testing done: - UTs added for double<=>json conversion. - UTs passing. Signed-off-by: Szymon Dompke <szymon.dompke@intel.com> Change-Id: I9193df29cce1db28cda3c895d117d9f3bfca2c24
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].