| commit | cc8abc0be58c19acd088da455454fdf466a1745f | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Wed Jun 07 12:12:21 2023 +0000 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Wed Jun 07 12:12:31 2023 +0000 |
| tree | 1e6445ac2ff2be1db6860d49e445901735d2da45 | |
| parent | cff70c14ef8cadb7fffd0cd41e06b972fa240e56 [diff] |
passing owner responsibilities Change-Id: I0561af6d0fac610c4ec77eb009ca040ac4f2002d Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@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].