| commit | 493e62eb2f2ff6cbf3282b9cb98ebe6e520b88fc | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Mon Feb 14 10:55:50 2022 +0100 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Wed Feb 16 13:05:05 2022 +0100 |
| tree | 5985b8c00d77f97db481fb42d197a09d29904d7b | |
| parent | f7ea2997ae6b4fad0dc35f9afa9b488d774f2ee1 [diff] |
made MetricValues persistent MetricValues are persistent for reportUpdates AppendStopsWhenFull and reportingType different than OnRequest. Tested: - New unit tests are passing - Confirmed MetricValues are preserved after restarting telemetry service Change-Id: I7e1990fb391da9debb0d7df2f1dbda86473350cc Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com>
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].