| commit | b9709d9cf6137c2cc788e16c307fb9fdbbcbb894 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Wed Nov 05 00:21:49 2025 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Nov 05 00:21:49 2025 -0500 |
| tree | 396935439c29b302b7b82d48139b65771c39536f | |
| parent | 995ebe7ef29c9890e87aa4c0e6772f7a586146da [diff] |
use sdbusplus unpack syntax Rather than defining a variable and then reading it from a message, sdbusplus also supports directly unpack-ing from the message. Use this syntax instead as it is more efficient and succinct. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I54b14bc229d055428ec3183c488976e659e44d09
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].