| commit | b8cc78ddf9cc87c83176c7bda575ceef2678d00f | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Mon Nov 29 15:54:53 2021 +0100 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Mon Dec 06 15:45:50 2021 +0100 |
| tree | ab5364882979c0b56de21b6a9327786c9714c079 | |
| parent | 51497a0c878d939c9ed2a6ed30d12b465af4d51c [diff] |
Api changes in AddReportFuture version Added support for CollectionFunction, CollectionDuration, CollectionTimeScope, ReportUpdates, AppendLimit. New API separates Id and Name, user can decide to pass only Name to auto generate Id or pass Id which needs to be unique. Tested: - No functional changes to old API, everything works as before - All use cases can be replaced with new API to achieve same results - New features which require new API work as expected Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com> Change-Id: I647efab36d90a548754f89968223e162a087481e
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].