ref(uptime): Read uptime_status from uptime_subscription

[evanpurkhiser]

Switches reading of uptime_status (and uptime_status_update_date) to
the uptime_subscription model.

We'll need this to migrate to reading from detectors (and implementing
the detector handler)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #90434       +/-   ##
===========================================
+ Coverage   42.26%   87.80%   +45.53%     
===========================================
  Files       10255    10281       +26     
  Lines      582397   583445     +1048     
  Branches    22579    22579               
===========================================
+ Hits       246168   512281   +266113     
+ Misses     335798    70733   -265065     
  Partials      431      431               

[evanpurkhiser]

Verified all the status's match using this query

select
  sub.id as sub_id,
  sub.uptime_status as sub_uptime_status,
  sub.uptime_status_update_date :: text as sub_uptime_status_update_date,
  pus.uptime_status as pus_uptime_status,
  pus.uptime_status_update_date :: text as pus_uptime_status_update_date
from
  uptime_uptimesubscription sub
  join uptime_projectuptimesubscription pus on sub.id = pus.uptime_subscription_id
where

   -- Find mismatched uptime_status
   (
    sub.uptime_status != pus.uptime_status
    -- Trim off the minute, we were dual writing slightly different values due to two calls to `timezone.now()`
    or date_trunc('minute', sub.uptime_status_update_date) != date_trunc('minute', pus.uptime_status_update_date)
  )

[sentry]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ UptimeSubscription.DoesNotExist: UptimeSubscription matching query does not exist. monitors.uptime.result_consumer View Issue
• ‼️ UptimeSubscription.DoesNotExist: UptimeSubscription matching query does not exist. monitors.uptime.result_consumer View Issue
• ‼️ OperationalError: OperationalError('server closed the connection unexpectedly\n\tThis probably means the server terminated abnormally\n\tbefore or while processing the request.\n') monitors.uptime.result_consumer View Issue

_{Did you find this useful? React with a 👍 or 👎}