| commit | 892f7c81da31149699c01a086f93f28bd3039df8 | [log] [tgz] |
|---|---|---|
| author | Szymon Dompke <szymon.dompke@intel.com> | Wed Oct 12 09:54:22 2022 +0200 |
| committer | Szymon Dompke <szymon.dompke@intel.com> | Thu Oct 13 18:49:16 2022 +0200 |
| tree | 2c2ff6e50cdf53c51dc5e0978746e59dbc363957 | |
| parent | 5f7ca1a466099638ce906eff5c461fefe1d177f7 [diff] |
Fix sensor count not updating When ReadingsParamaters are updated, sensor count may change. This action should resize buffer and update value of "AppendLimit" property in case it was not set by user. Testing done: -UTs passing Signed-off-by: Szymon Dompke <szymon.dompke@intel.com> Change-Id: I96486a808a3cce83c09936262304d0a1f55b3fd7
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].