You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently rf_sensor_list is very focused on building sensor tables under the Chassis model, specifically for the Thermal, Power, and Sensor subordinate resources. Some of the constructed sensors pull from State/Health on resources to build a non-numeric reading in the output for devices (like batteries, power supplies, and fans). For example, this output comes from the State and Health properties inside Status for a PowerSupply resource:
Power Supply Bay 1 State | Enabled | Warning | N/A | N/A | N/A | N/A | N/A | N/A | N/A
A user asked me if we can grow and include the same "State" information for other types of resources (like Memory and Drives). I'm inclined to think it's a good addition, but it made me think about what else should this be doing. Should we try to increase the scope of the tool to collect information from other areas of the model based on what it finds in Chassis? I still see "Chassis" as the starting point for all logic.
The text was updated successfully, but these errors were encountered:
Currently rf_sensor_list is very focused on building sensor tables under the Chassis model, specifically for the Thermal, Power, and Sensor subordinate resources. Some of the constructed sensors pull from State/Health on resources to build a non-numeric reading in the output for devices (like batteries, power supplies, and fans). For example, this output comes from the State and Health properties inside Status for a PowerSupply resource:
A user asked me if we can grow and include the same "State" information for other types of resources (like Memory and Drives). I'm inclined to think it's a good addition, but it made me think about what else should this be doing. Should we try to increase the scope of the tool to collect information from other areas of the model based on what it finds in Chassis? I still see "Chassis" as the starting point for all logic.
The text was updated successfully, but these errors were encountered: