| commit | 18e7101cf3283c32fa52ed8b00697e1e1f59015a | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Wed Nov 02 13:17:01 2022 +0000 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Wed Nov 02 15:14:08 2022 +0000 |
| tree | 489941942d2edf8728611cd9b9795efe2d9001bd | |
| parent | 62c08e9b5e835df0e6ca463331908235086acb4d [diff] |
simplified appendLimit implementation AppendLimit is now set to max value by default. This simplifies the code while keeping most of the feature functionality. This change increases report version and will cause older report to be deleted. Tested: - AppendLimit is set by default to max value - Telemetry features are working as expected Change-Id: I94c85393a9601c90c00776bf0bc814d85cbf006a Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com>
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].