let /admin/edge reveal each edges current state and last online state, such that it can be revealed by backoffice. otherwise troubleshooting and setup is very difficult (have to look at backend container logs which are not even accessible by a typical end user admin).
expose each edge's:
- current connectivity status or time last seen
- recent errors
- detection of common errors and display of the recommended action
- list of modules running
- module initialisation errors
let /admin/edge reveal each edges current state and last online state, such that it can be revealed by backoffice. otherwise troubleshooting and setup is very difficult (have to look at backend container logs which are not even accessible by a typical end user admin).
expose each edge's: