controller procedure monitor stuck uses heartbeat

Author: GabrielSalla

configs.yaml

@@ -31,7 +31,7 @@ controller_procedures:
   monitors_stuck:
     schedule: "*/5 * * * *"
     params:
-      time_tolerance: 300
+      time_tolerance: 10
 
 executor_concurrency: 5
 executor_sleep: 5

resources/kubernetes_template/config_map.yaml

@@ -42,7 +42,7 @@ data:
       monitors_stuck:
         schedule: "*/5 * * * *"
         params:
-          time_tolerance: 300
+          time_tolerance: 10
 
     executor_concurrency: 5
     executor_sleep: 5

src/components/controller/sql_files/monitors_stuck.sql

@@ -1,11 +1,11 @@
 with monitors as (
   select
     id,
-    extract(epoch from current_timestamp - greatest(queued_at, running_at)) :: int as seconds_queued
+    extract(epoch from current_timestamp - last_heartbeat) :: int as time_since_last_heartbeat
   from "Monitors"
   where
     enabled and (queued or running)
 )
 select id
 from monitors
-where seconds_queued > $1 :: int;
+where time_since_last_heartbeat > $1 :: int;