| commit | e28aa53dc1492f09a64dc9f1dbfd5b6dba06e31f | [log] [tgz] |
|---|---|---|
| author | Szymon Dompke <szymon.dompke@intel.com> | Wed Oct 27 12:33:12 2021 +0200 |
| committer | Szymon Dompke <szymon.dompke@intel.com> | Fri Oct 29 13:27:50 2021 +0200 |
| tree | 55081e012cf943f4c3ccbc29aa800cccc58f4692 | |
| parent | 7e098e93ef0974739459d296f99ddfab54722c23 [diff] |
Add Id to Trigger Currently, Trigger is using Name as unique identifier. By adding Id, we can be compliant with redfish specification: - Id will be used as unique identifier - Name will be used as human readable, non-unique name AddTrigger dbus method is now requiring both id and name. Each of them can be passed as empty string and the service will fill them with correct values. If only id is an empty string, name will be used to generate its value. Dbus object path and persistent storage filename are now be based on id, instead of name. Added validation for AddTrigger: - correct characters in id - max id length Added Name property for Trigger object, which can be modified from dbus. Testing done: - Unit test added and passing - Trigger was added using dbus, without errors - Id generation is working properly - Name property is accessible and writable from dbus Signed-off-by: Szymon Dompke <szymon.dompke@intel.com> Change-Id: Ibb553586eaf51943044c93a35bc0725e6ef67ce9
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].