| commit | 8859c84bdc1f994405cf617accc3d0f47801587a | [log] [tgz] |
|---|---|---|
| author | Matt Spinler <spinler@us.ibm.com> | Mon Feb 06 11:34:18 2023 -0600 |
| committer | Matt Spinler <spinler@us.ibm.com> | Mon Feb 06 13:32:48 2023 -0600 |
| tree | 131ab39faaadff8d4565df549f44772af635f66d | |
| parent | f20aa7c87360a0d2918377a86bbf04c85268d47d [diff] |
Don't crash if mapper times out We've seen cases where there is so much going on at once on a system that the mapper will get too busy and calls to it will time out. When this happens to virtual-sensors it will core dump and restart, but eventually over time it can accumulate so many restarts that it will hit systemd's restart limit and no longer be restarted. To avoid this, just do the same thing as when the sensor isn't on D-Bus, which is to ignore that sensor for now and try again the next time the virtual sensor is calculated. Change-Id: I6a09fe4c56070f1b23c97f66fe38f3b900e02ee9 Signed-off-by: Matt Spinler <spinler@us.ibm.com>
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).