| commit | 2efa95d8faec80ee1eb2ce500e2cb08849cd478e | [log] [tgz] |
|---|---|---|
| author | Ed Tanous <ed@tanous.net> | Sat Oct 19 11:36:53 2024 -0700 |
| committer | Ed Tanous <ed@tanous.net> | Tue Dec 31 21:53:14 2024 +0000 |
| tree | 6fc86a85bebde95aeab8d06de7354b9f91b9798f | |
| parent | 6050b6559bfa80e3372e6bb4145a14c7ebf6a27c [diff] |
Remove variant from Thresholds interface The Thresholds property on the Trigger interface is currently defined as a relatively complex type: variant< array<discrete struct> array<numeric struct> > This causes some oddities in unpacking given that Dbus properties are already a variant, applications consuming this interface have to double wrap the variant. This was confusing enough that bmcweb has to keep the trigger types separate, and cannot use the common typing. This commit changes by adding two new parameters NumericThresholds: array<numeric struct> DiscreteThresholds: array<discrete struct> Which deduplicates the double wrapped variant. The intent is that this duplicated interface will exist for a transition period of a week or two, while bmcweb (the only user of this) transitions the code to use the new properties, then a followup common will drop the thresholds properly. Tested: WIP Change-Id: I6717d4075de53c91aa179a90c7a844c4a13534cc Signed-off-by: Ed Tanous <ed@tanous.net>
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].