commit | 85db8bdfac85e26742926f5aa6a938fe71d10cff | [log] [tgz] |
---|---|---|
author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Fri May 28 12:13:23 2021 +0000 |
committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Wed Jun 09 09:24:57 2021 +0000 |
tree | e8bb74273456d2080dcc2b0c44aeeca247611ccc | |
parent | 32859b634e366a015331fb8ab62766340df9c7b8 [diff] |
Add skipping PropertiesChanged signal on init Prevents sending initial PropertiesChanged for report when new report is created. Information about initial values is already present in signal InterfacesAdded. Signals about actual updates are correctly send. Tested: - Verified that signal is not send during AddReport - Verified that signal is still being send when properties are updated Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com> Change-Id: I19d6aee431a947ca52ca79af738e2a571a16b694
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]
.