| commit | 05b1d41788058cdf255ce1d46b2ff8041abf5656 | [log] [tgz] |
|---|---|---|
| author | Rashmica Gupta <rashmica.g@gmail.com> | Wed Nov 03 12:01:36 2021 +1100 |
| committer | Rashmica Gupta <rashmica.g@gmail.com> | Wed Dec 15 11:44:01 2021 +1100 |
| tree | ee5f00dff28196f5fb512fd9a88bdcab6e08f752 | |
| parent | b57d7370815015ce8f04be16cee39c45b0770355 [diff] |
thresholds: Update Severity to be a string Thresholds are now strings, so update to treat them as such. However still accept unsigned ints for backwards compatibility. Tested: Used both strings and unsigned ints in severity fields in a virtual sensor config, and we see correct threshold properties and behaviour. Signed-off-by: Rashmica Gupta <rashmica.g@gmail.com> Change-Id: I893877a769eb81e6589ce42a01079816e5493b4f
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).