| commit | 9f346790ff22623d73504f62bdcce600f1891e68 | [log] [tgz] |
|---|---|---|
| author | Szymon Dompke <szymon.dompke@intel.com> | Wed Jul 14 21:07:11 2021 +0200 |
| committer | Szymon Dompke <szymon.dompke@intel.com> | Thu Jul 22 14:22:49 2021 +0200 |
| tree | 150de8074baf086996660ad720cfb99f6aacf0fd | |
| parent | 4416fce6fb6539b4e2a6a94a8248934c2eb29820 [diff] |
Change discrete threshold value to string For compliance with redfish schema, trigger with discrete thresholds should use string as a value - instead of double. This will impact dbus method "AddTrigger" for Trigger interface. As there are currently no known sensors with discrete values, telemetry service will still treat the value as a double internally. Tested: - UT passed. - Trigger with discrete threshold value was successfully created using dbus call. - local redfish-tests for trigger persistency are passing after type modification. Signed-off-by: Szymon Dompke <szymon.dompke@intel.com> Change-Id: I8201ce5e2a45647206c5ccd85fc45ea8f32961af
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].