| commit | 5e7cbf42eabe916a82a13d41199ecc0921c4cac4 | [log] [tgz] |
|---|---|---|
| author | Michal Orzel <michalx.orzel@intel.com> | Thu Aug 01 15:44:42 2024 +0200 |
| committer | Adrian Ambrożewicz <adrian.ambrozewicz@linux.intel.com> | Tue Aug 20 08:31:07 2024 +0000 |
| tree | bdc4904d3c60d6c97863742b964842b53ad07f25 | |
| parent | 53fb785568946ef22dd79dde100bb6d77a58f080 [diff] |
Verify reading parameters on update Adds verification of ReadingParameter's metric count when property is being updated. This brings consistency with behavior upon adding a new report, where that same check is being made. Also adds a unit test for that check. Tested: On platform, by updating report's ReadingParameter with object containing metric count exceeding one specified by `max-reading-parameters` project option. With this change applied, that operation failed, as expected. Change-Id: I06c8e21178d6bd554b62886e0e4f8cd0589f0d09 Signed-off-by: Michal Orzel <michalx.orzel@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].