| commit | 39cc6ac99a135f1d7284520fbff613d7eb274f34 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Fri Jul 22 19:26:56 2022 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Jul 25 12:03:53 2022 +0000 |
| tree | 4ca4a3e10ed989e3005860a4a6fe6b9302710126 | |
| parent | 32305f14d8a7560980735c04fbb2067d633e08d8 [diff] |
sdbusplus: use shorter type aliases The sdbusplus headers provide shortened aliases for many types. Switch to using them to provide better code clarity and shorter lines. Possible replacements are for: * bus_t * exception_t * manager_t * match_t * message_t * object_t * slot_t Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I20ad4fc3a2c6d8cb342156bd3e8d05f3a22d3eb8
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].