| commit | e6c417cfe7f092352b4d6058cf852b2d72023e74 | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Wed Feb 02 17:25:53 2022 +0100 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Wed Feb 02 17:25:53 2022 +0100 |
| tree | 1d3bcfe6e2cb30201e94b1473992ac42ceb3f30e | |
| parent | cd5b0b7e8e1a473262e4753e46e62d416a65649d [diff] |
Fixed handling maxAppendLimit
maxLimit prevented using numeric_limits<uint64_t>::max as a way to let
telemetry service deduce appendLimit. This commit fixes constrain to
allow passing this special value.
Tested:
- Added new unit tests that confirm numeric_limits<uint64_t>::max is
correctly handled in telemetry service
Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com>
Change-Id: I5d67e83475cdfcbb58a71b783ac9eef1e5ad7010
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].