The dashboard provides information about the last connection and whether it is just a heartbeat or VPN.
For discovering any patterns or stability problems outside of observing the devices in 3rd party system, having history in the dashboard would help identify the issues.
The resource for device connectivity events is a high frequent, high volume resource that is differently designed than history resources and cannot be easily exposed right now.
Laura (balena): Thank you all for your interest on this. Because it’s been a while, we wanted to provide you all with an update.
Whilst this is still very much on our radar, it’s not something we’re actively working on or something we plan to work on soon. We’re taking the time to really consider our product surface and what functionality is best served from balena. Metrics, as you can appreciate, is a big topic. What we’re exploring is how external tools like Grafana and Prometheus could integrate with balena to offer this functionality, but we would need to make headway with this improvement first Implement webhooks/notifications/a means to be alerted of changes
What we are actively doing however, is improving how we surface information. This is to give our users as accurate reflection of reality as possible when using balena. So whilst not a collective log of history, we hope that this will improve visibility on current states of devices. We hope to be rolling a first phase of this work out imminently.