commit | d2ad09fb0c47a050ae864e1efd65054c6981c78d | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Thu Dec 08 06:13:10 2022 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Fri Dec 09 07:43:54 2022 -0600 |
tree | a57836ea941fdb62685b4eaa5eec1bfa7f241549 | |
parent | 89cf7d7dafe2c073d781a40d59fa9c46cb344be6 [diff] |
prettier: re-format Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML files to have consistent formatting for these file types. Re-run the formatter on the whole repository. Change-Id: I20c1cb77e30d3072e9a8709690306011319e9007 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
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]
.