| commit | 995ebe7ef29c9890e87aa4c0e6772f7a586146da | [log] [tgz] |
|---|---|---|
| author | Boleslaw Ogonczyk Makowski <boleslawx.ogonczyk-makowski@intel.com> | Wed Aug 27 14:00:53 2025 +0200 |
| committer | Boleslaw Ogonczyk Makowski <boleslawx.ogonczyk-makowski@intel.com> | Wed Aug 27 14:18:09 2025 +0200 |
| tree | 0e29ef6c3ccbc84557d5ff5647c0d61ab9ecb6ce | |
| parent | 6f56d2688f05b6e4c49cf9b078ea131f196e3018 [diff] |
Remove deprecated "Thresholds" property and fix UTs Thresholds have been split into "DiscreteThresholds" and "NumericThresholds", remove deprecated property, update UTs Tested: UTs passed Change-Id: I1959be879e9016b84fff7f7ae6cfad1f5d00e5aa Signed-off-by: Boleslaw Ogonczyk Makowski <boleslawx.ogonczyk-makowski@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].