| commit | 32859b634e366a015331fb8ab62766340df9c7b8 | [log] [tgz] |
|---|---|---|
| author | Karol Niczyj <karol.niczyj@intel.com> | Wed May 19 10:20:46 2021 +0200 |
| committer | karol.niczyj <karol.niczyj@intel.com> | Thu May 20 11:53:36 2021 +0000 |
| tree | 3e0911d297ed71efbd32ad54a2b307b6ae26c9cb | |
| parent | e2c4105f2f416f1c3dbf4107f1204004dc194b56 [diff] |
Add limit for report name length Added limit for report name length, parametrized with max-report-name-length option, because we cannot remove reports with too long report name. Tested: - Confirmed that report with name length equal to 4096 cannot be generated via bmcweb (POST redfish/v1/TelemetryService/MetricReportDefinitions fails with code 500) - Confirmed that report with name length equal to 4095 can be generated and removed via bmcweb - Added unit-test that test that report with name length equal to max-report-name-length + 1 cannot be generated - Added unit-test that test that report with name length equal to max-report-name-length can be generated Change-Id: I6868320f831079af903f3624d1beff648059e351 Signed-off-by: Karol Niczyj <karol.niczyj@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].