| commit | d7cebdd37fade28b0efd34bb9d641135bff758a0 | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Thu Mar 04 13:45:29 2021 +0000 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Thu Apr 01 07:03:22 2021 +0000 |
| tree | 2d75bff9db72a96b72fead7374bdc7001249cc65 | |
| parent | 9f9ff90a39219ff3a2f1179f74fc9a6dc857e5ab [diff] |
updated MAINTAINERS - changed IRC to Discord - added Szymon Dompke as maintainer - added Cezary Zwolak as maintainer - moved Jozef to reviewers - added OWNERS file Change-Id: I8e0b5f6b53fdc58694c5e5da3ec82865ff91c391 Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com> Signed-off-by: Adrian Ambrożewicz <adrian.ambrozewicz@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].