| commit | fdb06a141c6d9bbf1088fee974b815d1f35d3bcb | [log] [tgz] |
|---|---|---|
| author | Szymon Dompke <szymon.dompke@intel.com> | Fri Feb 11 11:04:44 2022 +0100 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Tue Feb 15 10:46:08 2022 +0100 |
| tree | 59c85a82c0b3e734a0151852c6af2cc7ca58115e | |
| parent | 60fee077c544402f133230c4d3dc85ad0ada9381 [diff] |
Report: make dbus properties writable ReadingParametersFutureVersion interface for Reports is enhanced from read-only to read write and supports modification of readingParameteres, which is done by updating metrics at the first place and re-registering them for sensors updates. Similar ReportActions interface is enhanced to read write. Additionally reportActions policy was modified that reports always contain 'LogToMetricReportsCollection' action. The whole change enables Redfish support for PATCH method added on webserver side. Tested: - New unit tests were created, ran all new and previous UTs, all passed - Tested under QEMU, interface was checked for RW via dbus cli commands, checked if Reading Parameters of the Report can be read or written, if metrics are properly updated and registration/unregistration for updates works properly, checked if actions of Report can be read or written, if actions are properly updated and related action behavior follows the change accordingly - Tested under QEMU, verified if 'LogToMetricReportsCollection' action is always added when Report is created or when actions of Report are updated by dbus interface - Tested via webserver if it communicates properly with dbus interfaces of Telemetry and read/write operations via Redfish can be successfully executed Signed-off-by: Lukasz Kazmierczak <lukasz.kazmierczak@intel.com> Change-Id: I7f2fe8eae1631c436cf61a516d5fd0b8358a76bd
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].