| commit | 620c65ad386ea542bcc18122577a3aab6dbac96d | [log] [tgz] |
|---|---|---|
| author | Szymon Dompke <szymon.dompke@intel.com> | Wed Mar 23 21:09:27 2022 +0100 |
| committer | Szymon Dompke <szymon.dompke@intel.com> | Mon Apr 04 10:35:38 2022 +0000 |
| tree | 9d42dfdc45cf6c671015f2c5ab7832e4085f83b2 | |
| parent | aa572361124d4797b25674297bbc4cc2682030fa [diff] |
OnChange trigger should not handle first reading When OnChange trigger register for updates, it gets current sensor value as an update. This reading fires trigger actions and is undesirable. This change skips handling of first reading update for OnChange trigger. Testing done: - UTs updated and are passing, - OnChange trigger is not doing an action on first reading update. Signed-off-by: Szymon Dompke <szymon.dompke@intel.com> Change-Id: Ief2d1edd5923fd332f3ea3234a9988e1967d972f
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].