| commit | 6c956488f7a1d796353cfd008787f9b6f7f64d29 | [log] [tgz] |
|---|---|---|
| author | Boleslaw Ogonczyk Makowski <boleslawx.ogonczyk-makowski@intel.com> | Tue Jan 14 12:34:54 2025 +0100 |
| committer | Boleslaw Ogonczyk Makowski <boleslawx.ogonczyk-makowski@intel.com> | Tue Jan 14 12:34:54 2025 +0100 |
| tree | ce7a868d47aad62935908d1d58171faa191fe89b | |
| parent | 2efa95d8faec80ee1eb2ce500e2cb08849cd478e [diff] |
Fix boost url According to [1] boost url has been changed [1]: https://github.com/boostorg/boost/issues/996#issuecomment-2567031602 Change-Id: I3f7b1de93caad6fe392b3f672102938087170aea Signed-off-by: Boleslaw Ogonczyk Makowski <boleslawx.ogonczyk-makowski@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].