| commit | aa4a9dc5ccae9f210d0d63f99b22154c97e53c19 | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Mon Jun 13 06:52:44 2022 +0200 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Mon Jun 13 06:52:47 2022 +0200 |
| tree | 14a9a26974ad057b38d683c2df133ee224e857a4 | |
| parent | 1cdd7e4f89c75de7ec95ea545306e96ddf5a8a2b [diff] |
changed min value to 0 for some meson options Changed min value to 0 for meson options: max-reports, max-reading-parameters and max-trigger. This allows to dissable features and produce resource limit reached error as response. Tested: - Reaching resource limit produces desired error Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com> Change-Id: I1b82438cb5c608c32fcab92bb49823e90f5d2e49
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].