| commit | 3a617023eacf8a7fcc49e15d5767b35f47c7c089 | [log] [tgz] |
|---|---|---|
| author | Szymon Dompke <szymon.dompke@intel.com> | Mon Jul 19 18:23:02 2021 +0200 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Tue Jul 27 13:13:37 2021 +0000 |
| tree | 75c55eec3214da31f7aafff3125f63198090405f | |
| parent | dcc4e1936173a93251a02066432bc2bcbc386240 [diff] |
Refactor metadata returned by Readings property Reading metadata is now JSON containg SensorDbusPath and SensorRedfishUri. It is returned only if JSON metadata was provided during Report creation, otherwise old behavior is maintained. Additionally, json.hpp was removed as LabeledTupple is now used for serialization and deserialization of metric and reading metadata. Testing done: - Unit test is passing as metric is returning proper metadata. - Redfish get on redfish/v1/TelemetryService/MetricReports is containing MetricDefinition property, which utilizes SensorDbusPath metadata.. Done on custom version of bmcweb. Change-Id: I1b2cc4440d03e0fe45151b630f4e439839ed8589 Signed-off-by: Szymon Dompke <szymon.dompke@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].