| commit | e6d4887453f0b23b46c012da7cb26f2beb38ef0e | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Tue Feb 08 13:41:30 2022 +0100 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Mon Feb 14 11:03:44 2022 +0100 |
| tree | 147c83c8fd5e4b693653f2255abf3cedee9934d1 | |
| parent | ae9bd58a009c69a43f1b1b35b4f16e4673ea0a73 [diff] |
Removed dependency to TriggerManager introduces Messanger class which allows to send messages directly to subscribed targets, which allows to break dependencies between classes. Testes: - All unit tests are passing - Links are correctly updated - Report is correctly updated by Trigger Action Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com> Change-Id: I32d3aaba22f9ec07e611f53fe553bd27e1c04c6d
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].