While we were digging into the topic of observability, we wanted to find a way to monitor whether a user connection is actually active or maybe there is some data missing or none at all coming for some time.
In #1423 there was a proposal to mark connection as REVOKED if there was no data from a connection for longer than a threshold (e.g. 14 days). However, that would count as if the user needed to re-authorize, which is not true for a SDK connection that may still keep tokens in the app.
The proposal is we could add a new STALE ``ConnectionStatus` - that way we could still count these connections as 'active' while also having them marked as possibly stale and not receiving any data
This way, we can also scope it further than just SDK providers - the same mechanism can work for every provider supported.
While we were digging into the topic of observability, we wanted to find a way to monitor whether a user connection is actually active or maybe there is some data missing or none at all coming for some time.
In #1423 there was a proposal to mark connection as
REVOKEDif there was no data from a connection for longer than a threshold (e.g. 14 days). However, that would count as if the user needed to re-authorize, which is not true for a SDK connection that may still keep tokens in the app.The proposal is we could add a new
STALE``ConnectionStatus` - that way we could still count these connections as 'active' while also having them marked as possibly stale and not receiving any dataThis way, we can also scope it further than just SDK providers - the same mechanism can work for every provider supported.