In Diagnostics > Overview > Devices, the section has a red outline indicating items that require attention.
That is indeed inconsistent. I’ll work with the OPC team and Design to determine which way we want to go in order to get this consistent.
In order to get this consistent, we have a lot of work ahead of us. The OPC team does not want connecting resources to display as errored/faulted, even though their healthcheck declares them as unhealthy. The Device Connections page and Connections Overview have special handling to accommodate this and display/count several known states as “neutral”. Those other areas (Platform Overview and Diagnostics Overview) are far more generalized and treat all systems the same way - hence all “unhealthy” resources get counted as errored/faulted and display as such.
To gain consistency, we’ll have to get all systems reporting the same way, most likely giving each a way to denote whether an unhealthy resource should qualify as a warning or an error. This will likely not happen anytime soon due to the scope of the necessary changes across multiple systems.
Sounds like something to make a default part of all Extension Points.
Indeed, which is why we’ll need to take some extra time. It’s one thing to add it to Extension Points (and default it to ERROR), where some new field won’t break existing scripts - this part is trivial. To then make sure the Ignition front-end uses this new field as expected in all of these various areas and that the Ignition systems which would make use of it are using it correctly - this is what will take some time. As adding these new fields to extension points has no immediate gain, there’s no reason for us to rush the back-end changes until the front-end is also ready to go.
