| commit | c1dbac16fe3c705b773155f607a4541cf2ad79fa | [log] [tgz] |
|---|---|---|
| author | Piotr Sulewski <piotrx.sulewski@intel.com> | Wed Nov 12 14:14:09 2025 +0100 |
| committer | Piotr Sulewski <piotrx.sulewski@intel.com> | Wed Nov 12 15:06:58 2025 +0100 |
| tree | 2034b3e2726c49ea8e66575de59d397d2e321a8c | |
| parent | b9709d9cf6137c2cc788e16c307fb9fdbbcbb894 [diff] |
Resolve coverity issues * Added Rule of Five compliance to the reported classes * Added explicit default destructors and assignment operators * Corrected comparison statement Tested: UTs passed Change-Id: Ifcfc1055e2e65d9f3ce10e3878ff3f1dd5d84929 Signed-off-by: Piotr Sulewski <piotrx.sulewski@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].