| commit | 4416fce6fb6539b4e2a6a94a8248934c2eb29820 | [log] [tgz] |
|---|---|---|
| author | Cezary Zwolak <cezary.zwolak@intel.com> | Wed Mar 17 03:21:06 2021 +0100 |
| committer | Lukasz Kazmierczak <lukasz.kazmierczak@intel.com> | Mon Jul 19 10:53:13 2021 +0200 |
| tree | 8ae4f27f0475b2775bc180eeb52c73704d3b2332 | |
| parent | a4e6761643f2ff306d6928ea5537eb151fae79a0 [diff] |
Read persistent triggers from storage
Read json storage file for persistent triggers.
Add trigger to telemetry service.
Cover code with UTs.
Tested:
- Passed unit tests
- Tested on QEMU
* starting app without configuration
* restart app with configuration stored
* restart app with configuration in incorrect version
* restart app with configuration malformed
Change-Id: I2cb9324abdb8323be8a7f0c932ed7f70c5bc2891
Signed-off-by: Cezary Zwolak <cezary.zwolak@intel.com>
Signed-off-by: Lukasz Kazmierczak <lukasz.kazmierczak@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].