| commit | a8d8aab855711d69d4fe87561d73b7e242049e5d | [log] [tgz] |
|---|---|---|
| author | Jayanth Othayoth <ojayanth@gmail.com> | Sun Dec 08 06:03:09 2024 -0600 |
| committer | Jayanth Othayoth <ojayanth@gmail.com> | Sun Jun 15 00:45:21 2025 -0500 |
| tree | dc5c5bd02baf3067882efdb5a5c79afa30527d86 | |
| parent | 5e47b162d100b66507d8b065e8a31c7b3221c2f2 [diff] |
clang-tidy: Initial commit Added initial .clang-tidy configuration file with recommended C++ checks aligned with the OpenBMC-approved checklist. This setup enforces modern C++ best practices and helps catch common issues early in development. Tested: verified build. Change-Id: I7914c72f734f164793f04df1ca452e44fe3c9617 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].