commit | d528b4f556bfae6d49f3482d2d3376a56d0b9b31 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Wed Jul 09 11:27:27 2025 -0400 |
committer | Patrick Williams <patrick@stwcx.xyz> | Wed Jul 09 11:27:27 2025 -0400 |
tree | 86abbc3a16b58d0ef08d3bd00993e92dff27eff7 | |
parent | a8d8aab855711d69d4fe87561d73b7e242049e5d [diff] |
meson: use non-deprecated systemd packageconfig Systemd's packageconfig file has both `systemdsystemunitdir` and `systemd_system_unit_dir` defined. The non-underscore one appears to be a deprecated alias[1]. Move to the non-deprecated / underscore-separated variant. [1]: https://github.com/systemd/systemd/commit/4908de44b0a0409f84a7cdc5641b114d6ce8ba03 Change-Id: I4cf46ac6aea46dcbbacc439bc2a1dc90cffb32d4 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
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]
.