commit | a950e42ba579a3498face1654e58c94d9ff1cf9a | [log] [tgz] |
---|---|---|
author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Fri Dec 31 13:49:00 2021 +0100 |
committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Fri Jan 14 09:18:48 2022 +0100 |
tree | deb5f529e1ae9e97d396a64cef125e8451d01b26 | |
parent | fbeb5bf41438f84a1336e018d3cc44251a84aa9f [diff] |
Added constrains to id generator This commit prevents id with more than one '/'. Slash can be used to create namespaces to avoid id conflicts between multiple users. Changed generator logic to take provided id as a name if no name was provided. Tested: - Tested that id and name generates correctly - It is no longer possible to add id with more than one '/' Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com> Change-Id: Ieef32ddb71b5a4870117aab0d624cbd46b5893e6
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]
.