| commit | 51497a0c878d939c9ed2a6ed30d12b465af4d51c | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Tue Nov 09 14:56:22 2021 +0100 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Mon Dec 06 15:45:42 2021 +0100 |
| tree | 66ba8b2f91f2146d8d2b8094f6237ce32e74c4d2 | |
| parent | 3eb56865714cd591b24d2bdef83307508aa072c5 [diff] |
Using enum class instead of string in more places ReportingType and ReportUpdates are now used as enum class in more places than before. Changed how this two fields are stored in persistent configuration. Increased Report::Version to break backward compatibility. Updated unit tests to verify changed functionality. Tested: - All existing tests are passing Change-Id: I55db205aefbe2b5a69fb7a31ccf11885aaecaaf2 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].