| commit | b4ef22e4d365bde35a7fce7950033c9271c68ce7 | [log] [tgz] |
|---|---|---|
| author | Szymon Dompke <szymon.dompke@intel.com> | Mon Feb 07 15:15:12 2022 +0100 |
| committer | Szymon Dompke <szymon.dompke@intel.com> | Mon Feb 07 15:15:12 2022 +0100 |
| tree | 28956a2634c50fcc5d4ef77ce93ebabae54825df | |
| parent | 94f71c5190b64bb47aa34cdce4eb4cca71d36faa [diff] |
Report: Add TriggerIds property This change is adding TriggerIds property for Report interface. It is an array of strings, each representing id of trigger which may update given report Readings property, due to UpdateReport action. This properly is read-only, but it can be changed in the runtime, when: - New Trigger is made using AddTrigger dbus method, when ReportId argument contains id of given report. - Trigger is deleted from dbus, and its ReportNames property included id of given report. - ReportNames property of any trigger is updated to include (or not) id of given report. When this property is modified by service, signal will be emitted on dbus for property change. When there is existing trigger with id of non-existing report in its ReportNames property, its id will be added to TriggerIds property of such report, the moment it is created by user. Testing done: - new UTs were made, all UTs are passing. - manual testing on dbus interface was successful. Signed-off-by: Szymon Dompke <szymon.dompke@intel.com> Change-Id: I1c4c94ce751ddaee001e3cadde3ea60aa8e1c224
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].