| commit | 7d87668cf590570896bfb33974b06fbdc16bc47b | [log] [tgz] |
|---|---|---|
| author | Adrian Ambrożewicz <adrian.ambrozewicz@intel.com> | Fri Jun 27 16:05:37 2025 +0200 |
| committer | Adrian Ambrożewicz <adrian.ambrozewicz@intel.com> | Thu Jul 10 12:32:47 2025 +0000 |
| tree | 6025a434862c246f982bded4fc4915b28e95c6e1 | |
| parent | d528b4f556bfae6d49f3482d2d3376a56d0b9b31 [diff] |
Update OWNERS Change-Id: I3b9fde13549fb87b375f1afbd5bf8c04bc646cae Signed-off-by: Adrian Ambrożewicz <adrian.ambrozewicz@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].