| commit | 74c1e7d8c50175017306e347532c8d7e98dc66d5 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Thu Sep 02 09:50:55 2021 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Thu Sep 02 10:50:04 2021 -0500 |
| tree | 9c85dd1c55f89250ad18df19f5c2b2a9450e168e | |
| parent | fbd7145e2d7da40175ab7939a7e3712ae0215723 [diff] |
exception: switch to public sdbus exception SdBusError was intended to be a private error type inside sdbusplus. Switch all catch locations to use the general sdbusplus::exception type. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ib7b6d079463ab243e3466ca7bba1cf0da9168d70
phosphor-virtual-sensor reads in virtual_sensor_config.json There are two types of data in this file:
See virtual_sensor_config.json in this repository for an example. Sensors added this way can use any expression that is accepted by exprtk.
For example:
{
"Desc":
{
"Config" : "D-Bus",
"Type" : "modifiedMedian"
}
}
Sensors added this way can only use a set of restricted calculations. At this stage the only type supported is modifiedMedian.
The virtual sensor configuration information needs to be added into the relevant hardware configuration file in entity-manager. This method of adding a virtual sensor allows a recipe that builds for different hardware configurations to have different virtual sensors for each configuration.
The virtual sensor configuration in entity manager follows a different format to the JSON in virtual_sensor_config.json (specified in entity-manager/schemas/VirtualSensor.json). In particular, the format for Thresholds is different. The following table shows the severity fields that correspond to a particular threshold.
| Threshold | Severity |
|---|---|
| Warning | 0 |
| Critical | 1 |
| PerformanceLoss | 2 |
| SoftShutdown | 3 |
| HardShutdown | 4 |