| commit | e8fc57514575f07565035db07cb522fe21988224 | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Fri Feb 05 14:30:45 2021 +0000 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Mon Feb 08 14:35:32 2021 +0000 |
| tree | e8c01f5809b060bdee4fdfaef3b37b23535f804f | |
| parent | 1ac4d547845d70f987a7bf43bb65405be92727d8 [diff] |
Changed dbus add report interface - metric parameters now take single sensor instead of list - added interface support for new operation types Tested: - All telemetry tests are passing. Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com> Change-Id: Id3a41c48e81a287e7d205ae1c747daa36d4cdb29
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].