| commit | a4e6761643f2ff306d6928ea5537eb151fae79a0 | [log] [tgz] |
|---|---|---|
| author | Cezary Zwolak <cezary.zwolak@intel.com> | Thu Feb 18 13:16:16 2021 +0100 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Mon Jul 19 07:31:39 2021 +0000 |
| tree | d053ace1e9c069ec07888aab0d701b27a17264c9 | |
| parent | d2620704f721c60f730404c47c15b5f061b29d4c [diff] |
Save persistent triggers to storage
Create json storage file for persistent triggers.
Handle persistent dbus property.
Save/remove persistent triggers on add/delete.
Cover code with UTs.
Tested:
- Passed unit tests
- Tested on QEMU
* adding new valid and invalid trigger from cli
* verifying if valid trigger is properly stored
* deleting existed trigger from storage
Change-Id: I243326e84833a8cb22075fbf565573b62b205b4a
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].