| commit | 51f0fd501f4b772533271d15cb27d396186a7192 | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Tue Dec 28 16:32:08 2021 +0100 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Wed Dec 29 10:59:04 2021 +0000 |
| tree | 182f819d1bddc684ef8eaf71da7d42141d33db74 | |
| parent | 31db7f71ec023eb6b0e630fa18048b6fd9ae7430 [diff] |
Fixed issue with wrong timestamp Telemetry service used steady_clock for generating timestamps, but it produced incorrect time. This change makes telemetry service use steady_clock for intervals and system_clock for timestamps. Changed readings timestamp to display current timestamp instead of a time when reading was received. Tested: - correct timestamp is visible on dbus - other telemetry service features are still working Change-Id: Ic49f45640532cfffaeff5e0bd5591e6d99e5def5 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].