| commit | 1cdd7e4f89c75de7ec95ea545306e96ddf5a8a2b | [log] [tgz] |
|---|---|---|
| author | Szymon Dompke <szymon.dompke@intel.com> | Wed Jun 08 14:43:13 2022 +0200 |
| committer | Szymon Dompke <szymon.dompke@intel.com> | Fri Jun 10 08:35:00 2022 +0000 |
| tree | f1d49c1c988e5b0b3215cd9b5f8e3565339b8b38 | |
| parent | 162b97614fc2d4780c434af4a3b4335b072a3b23 [diff] |
Use proper dbus path when possible. Following methods and properties were updated to use full dbus path, instead of internal telemetry id: - TriggerManager.AddTrigger() - 'reportIds' arg - Trigger.ReportIds - renamed to 'Reports' - Report.TriggerIds - renamed to 'Triggers' Testing done: - UTs were updated and are passing. Signed-off-by: Szymon Dompke <szymon.dompke@intel.com> Change-Id: I78d812d38289fac575d25b48503cc8b9c6f736fe
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].