| commit | 753e4b3c843dd5d1068949c4106a6389f0e0ffbc | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Thu Feb 11 12:58:58 2021 +0000 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Thu Mar 04 13:49:30 2021 +0000 |
| tree | 2780320a7f35c359daa28a956c78d0d6934dc31e | |
| parent | 92cfff44d5790b7e59930e8a6acf15751a3cd891 [diff] |
created AddReportFutureVersion dbus method New method will support CollectionTimeScope, CollectionDuration In order to make not breaking interface changes bmcweb will switch to AddReportFutureVersion, then AddReport will be changed to match AddReportFutureVersion, then redfish will switch back to use AddReport, then AddReportFutureVersion will be removed. Change-Id: I9cc906cc1fa7cdf27be7e433390c516f6bae3c50 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].