| commit | 162b97614fc2d4780c434af4a3b4335b072a3b23 | [log] [tgz] |
|---|---|---|
| author | Szymon Dompke <szymon.dompke@intel.com> | Tue Jun 07 12:45:48 2022 +0200 |
| committer | Szymon Dompke <szymon.dompke@intel.com> | Fri Jun 10 10:06:09 2022 +0200 |
| tree | 5ed0db9569fe4ef45339f64fca0aafbc51aa0726 | |
| parent | 41fa80d8c77fb8822e867e4f436e845d58af3e15 [diff] |
Fix numeric threshold There was an issue when sensor value reach threshold set by the user. Example: given numeric threshold, set as increasing with value of 20.0, and following sensor updates: 20 -> 30 -> 40, trigger action would not start, which is clearly a defect, as 30 is crossed. Testing done: - numeric threshold now works with example given above. - UTs were updated and are passing. Signed-off-by: Szymon Dompke <szymon.dompke@intel.com> Change-Id: I955876e076f2286efd98d187cae775a7ab2f4e28
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].