| commit | e77b83201175011e663db2b91e53853d01179cee | [log] [tgz] |
|---|---|---|
| author | Jayanth Othayoth <ojayanth@gmail.com> | Sun Dec 08 06:45:24 2024 -0600 |
| committer | Jayanth Othayoth <ojayanth@gmail.com> | Sat Jun 07 06:49:18 2025 -0500 |
| tree | 92db6781f37e91ca8ea7225d7433b2af1682af7e | |
| parent | dc5d2f1cd6ab2e3e2b01f415a0b2bc5641af6823 [diff] |
clang-tidy: Improve const-correctness Updated member functions to better reflect const-correctness, enhancing code clarity and maintainability. Change-Id: Ib3fdbd2164cb76ad7f0c454d37dd5c08652f78fc Signed-off-by: Jayanth Othayoth <ojayanth@gmail.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].