I think this makes sense as its own service, separate from rpc_flight_monitor (which monitors afe https on a whole bunch of shards).

Why separate? Because there's only 1 tko db, and this service would only need to make, say, and rpc to our master afe (which in the backend forwrds some simple SELECT) to tko db.

+jkop because I think this will make a nice side project. The code for autotest/site_utils/rpc_flight_monitor can be adapted or generalized for a second daemon that only talks to 1 server instead of many in parallel.