| commit | b47b7db48c4f883eb191077848d55d96bd884607 | [log] [tgz] |
|---|---|---|
| author | Michal Orzel <michalx.orzel@intel.com> | Mon Sep 16 10:02:29 2024 +0200 |
| committer | Michal Orzel <michalx.orzel@intel.com> | Mon Sep 16 11:55:33 2024 +0200 |
| tree | e00b8eda41e90dc7bdb53e4bfc9b70602ec65ccf | |
| parent | 95f77e623c1b84663fe62e4506d2291b6919a13d [diff] |
Enable disabled unit tests Enabling tests that were initially disabled, most probably because corresponding features had yet been in development. Tested: Lines coverage increased: - src/report_manager.cpp: 94.2% -> 97.5% - src/trigger_manager.cpp: 94.9% -> 99.0% - src/utils/dbus_path_utils.cpp: 94.6% -> 100.0% Change-Id: Id729c7f2e7e188d878b7348c710a09a4ceb40fd4 Signed-off-by: Michal Orzel <michalx.orzel@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].