| commit | e702a5de6122a8d1afdb4090791c40b8bb128d8d | [log] [tgz] |
|---|---|---|
| author | Lukasz Kazmierczak <lukasz.kazmierczak@intel.com> | Fri Aug 06 16:59:31 2021 +0200 |
| committer | Lukasz Kazmierczak <lukasz.kazmierczak@intel.com> | Thu Aug 12 17:21:29 2021 +0200 |
| tree | e0c4250a816ea01d0300bf6018945cb1dab4be0e | |
| parent | a74e44f6ef7db43d38eb600fbfee152b31b30514 [diff] |
Modify severity text for discrete Triggers Changed text string representation of severity for discrete Triggers, needed to conform to Redfish Schema: https://redfish.dmtf.org/schemas/v1/Triggers.v1_1_4.json AND https://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Health Tested: - Creating various discrete Triggers and retrieving information about them from Telemetry (via bmcweb by POST/GET, via QEMU cli by busctl) - Verifying retrieved Redfish data by using Redfish-Service-Validator Signed-off-by: Lukasz Kazmierczak <lukasz.kazmierczak@intel.com> Change-Id: Ic24cb163a3e7a7ab6228999f6f9d71f6277c7d78
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].