| commit | 3a62ee15d4edd8498adbfaf3abd23796a7655ee7 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Fri Dec 03 10:13:25 2021 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Dec 03 10:14:13 2021 -0600 |
| tree | 0d2c1b416192acb413562feb9d25294a037b24a6 | |
| parent | e28aa53dc1492f09a64dc9f1dbfd5b6dba06e31f [diff] |
sensor: add missing header for sdbusplus::bus::match Telemetry doesn't seem to compile with the latest version of sdbusplus because of a missing header file. Add this in. Also, recently sdbusplus added short-named aliases for many types, so switch match::match to just match_t. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I4946edfa39db741bab8e30ffd77f03bf59c4d6f3
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].