| commit | 333e5bf60cdc34450617994f29901b6b131111fa | [log] [tgz] |
|---|---|---|
| author | Manojkiran Eda <manojkiran.eda@gmail.com> | Sun Oct 24 20:12:06 2021 +0530 |
| committer | Manojkiran Eda <manojkiran.eda@gmail.com> | Sun Oct 24 20:12:29 2021 +0530 |
| tree | 2b3128c7dad331f42b0ccb576b4004a02cf0b1c2 | |
| parent | dac2663c7ec47b7cba32e93d0d224ef704ad5436 [diff] |
Add OWNERS file Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: Ia69ea1c4a668ff2beed76dfab3e2a91481e12fe2
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 |