The intended behaviour of the status of a collector is described in the documentation's usage section, and posted here:
A collector node's status is determined by its sensors - a collector is only OPERATIONAL if all sensors are operational and it has no errors itself. Any UNKNOWN sensor will cause the collector to be UNKNOWN, and any ERROR sensor will cause the collector to be ERROR, in that order. If the collector has any errors that aren't associated with a sensor, its status is ERROR.
This isn't the current behaviour of the storage node code.
The functions in storage/src/database/repository.py need to updated to do this - currently the collector status will just be the status of one of its sensors.
The intended behaviour of the status of a collector is described in the documentation's usage section, and posted here:
A collector node's status is determined by its sensors - a collector is only
OPERATIONALif all sensors are operational and it has no errors itself. AnyUNKNOWNsensor will cause the collector to beUNKNOWN, and anyERRORsensor will cause the collector to beERROR, in that order. If the collector has any errors that aren't associated with a sensor, its status isERROR.This isn't the current behaviour of the storage node code.
The functions in
storage/src/database/repository.pyneed to updated to do this - currently the collector status will just be the status of one of its sensors.