| commit | a8182beb1129b0608d2ddfb82895194ea3485288 | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Mon Jul 04 11:26:20 2022 +0200 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Mon Sep 05 15:45:28 2022 +0200 |
| tree | 4fef52a88a09b5ed1efa31cc3851fb3ecd13b687 | |
| parent | 458a37d19dcba48c6ff18ae4716faa7d39337300 [diff] |
added Enabled to AddReportFutureVersion API - New parameter added to API - Changed API to be more flexible in the future Tested: - Unit tests are passing - Tested together with: https://gerrit.openbmc.org/c/openbmc/bmcweb/+/49796/23 POST, PATCH, PUT for MetricReportDefinitions are working correctly Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com> Change-Id: Ic988446d283a581dc6866418b1b27a989c3bc9a0
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].