Context (partial)
For async processing services (distributed workers), the server_live status should be set by the view each time we hear from the processing service. For v1 synchronous processing services with an endpoint_url, those can still be set by the status checker.
Requested Changes (partial)
Rename the following fields on the ProcessingService model:
last_checked_live → last_seen_livelast_checked → last_seen
This naming better reflects the semantic difference between:
- Async/pull model: workers report in, and we record when we last saw them
- Sync/push model: we actively check the service status
References
Context (partial)
For async processing services (distributed workers), the
server_livestatus should be set by the view each time we hear from the processing service. For v1 synchronous processing services with an endpoint_url, those can still be set by the status checker.Requested Changes (partial)
Rename the following fields on the
ProcessingServicemodel:last_checked_live→last_seen_livelast_checked→last_seenThis naming better reflects the semantic difference between:
References