| commit | 60fee077c544402f133230c4d3dc85ad0ada9381 | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Thu Jan 13 16:25:04 2022 +0100 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Mon Feb 14 11:32:09 2022 +0100 |
| tree | 34cc6d9b6935968a37b9e7cd1873c73ee3bb7dd1 | |
| parent | e6d4887453f0b23b46c012da7cb26f2beb38ef0e [diff] |
added property SupportedOperationTypes - removed OperationType::single - for backward compatibility incomming OperationType::single alted to produce same output functionality - added property SupportedOperationTypes to ReportManager interface Tested: - In cases where OperationType::single is used same MetricValues are produced - New property is visible on dbus Change-Id: I838581c954abc0d8401e0ed530ce7e9c8013860b 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].