| commit | 031ebcafb7af06af9705eab1cb8f9ec9fea16969 | [log] [tgz] |
|---|---|---|
| author | Michal Orzel <michalx.orzel@intel.com> | Fri Aug 02 12:50:14 2024 +0200 |
| committer | Michal Orzel <michalx.orzel@intel.com> | Thu Aug 08 07:44:03 2024 +0000 |
| tree | 6796c6bbf262b02c1d6b48d72b04e108630c4112 | |
| parent | 4d1c2ce2bf939405b31c5a62c665c04dcc4b0a34 [diff] |
Add gcovr config Adds configuration file for gcovr coverage scan. Change-Id: I27bdea88b5901cc18ccd8cfa333dc35b80bf1625 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].