| commit | 8069771c0db62887b72aa2b8c51cd64eb5f99b2d | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Thu Mar 04 09:49:27 2021 +0000 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Wed Sep 08 08:35:43 2021 +0000 |
| tree | 9823b017959eace0af5b3b690b5894bdba94d4b4 | |
| parent | e702a5de6122a8d1afdb4090791c40b8bb128d8d [diff] |
added support for Collection Functions new supported operations: min,max,sum,avg new supported time scopes: interval,startup added unit test to verify that each collection function returns correct timestamp and value Tested: - POST/GET on telemetry features in bmcweb, no regression detected - Using dbus API metric with collection function works as expected Change-Id: Ib364c433915e07fd7a102f00109525362c40ab8a 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].