https://github.com/openbmc/phosphor-virtual-sensor
https://github.com/openbmc/phosphor-virtual-sensor
Last synced: over 1 year ago
JSON representation
- Host: GitHub
- URL: https://github.com/openbmc/phosphor-virtual-sensor
- Owner: openbmc
- License: other
- Created: 2020-08-04T13:04:19.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2025-03-04T06:50:12.000Z (over 1 year ago)
- Last Synced: 2025-03-22T04:02:00.624Z (over 1 year ago)
- Language: C++
- Size: 736 KB
- Stars: 3
- Watchers: 6
- Forks: 5
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# phosphor-virtual-sensor
phosphor-virtual-sensor reads the configuration file
`virtual_sensor_config.json` from one of three locations:
1. The current directory.
2. `/var/lib/phosphor-virtual-sensor`
3. `/usr/share/phosphor-virtual-sensor`
By default the repository will install a sample config into (3).
There are two types of data in this file.
## virtual sensor configuration information
See `virtual_sensor_config.json` in this repository for an example. Sensors
added this way can use any expression that is accepted by exprtk.
## information to get a virtual sensor configuration from D-Bus
For example:
```json
{
"Desc": {
"Config": "D-Bus"
}
}
```
Sensors added this way can only use a set of restricted calculations. Currently
supported types are `Average`, `Maximum`, `Minimum`, `Sum` and `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](https://github.com/openbmc/entity-manager/blob/master/schemas/virtual_sensor.json)).