DBA Dash service handling of failed connections - logging

[DavidWiseman]

If DBA Dash fails to connect to a monitored instance, the error is written to the log file but the error doesn't make it's way back to the repository database. If an instance is down, this will be highlighted with the "Snapshot Age" column - but you need to look at the service error log on disk to see the failures.
It would be better to try to write the failures to the repository database. There is a complication that the application needs the ConnectionID for the instance to associate the error with a particular instance in the repository. This might not be available if it wasn't specified in the config. Maybe the config could be updated to persist the ConnectionID?

[DavidWiseman]

Suggestion from Slack: It might also be useful to have an indication in the tree if there are any servers that appear offline.
Issues to consider:
There would need to be a process to keep refreshing the state of the servers
Overhead would need to be considered for repositories with a large number of instances.