commit | 935a70ab8900dee7e70d8723fc670272d63d6d0c | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Thu Aug 04 11:40:13 2022 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Thu Aug 04 11:40:13 2022 -0500 |
tree | 2c49f923c08da6a1dd9c72666f02bc31ebdc7379 | |
parent | 39cc6ac99a135f1d7284520fbff613d7eb274f34 [diff] |
MAINTAINERS: remove file The MAINTAINERS file is deprecated in favor of OWNERS. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I76ed2bdf188b4055c3758d9aeae57c87e7e68f14
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]
.