jpuris
02/16/2023, 9:06 AMName: {{ work_queue.name }}
Last polled: {{ work_queue.last_polled }}
Late run count: {{ work_queue.late_runs_count }}
URL: {{ work_queue|ui_url }}
But.. why are all but 2 notifications with no values? (see screenshot below).
The two valid notifications are
1. The first one at 21:53 CEST
2. At 22:54 CEST (visible in screenshot)
edit: For the record.. We do not intend to run such trigger condition (it was a mis-configuration). We do not really care being notified every 10 seconds about a queue being healthy 😅 Hence the subject of the notifications in screenshot is mis-leadingWill Raphaelson
02/16/2023, 3:03 PMjpuris
02/16/2023, 3:05 PMWill Raphaelson
02/16/2023, 3:12 PMjpuris
02/16/2023, 3:15 PM• Trigger Type: Work queue health
• _*Work Queues*_: <single production work queue>
• _*Work Queue*_: Stays in > Healthy
• _*For*_: 10 SecondsShould not have generated gazillion events? If so, then it makes sense! The two "valid" events we received were exactly 1 hour apart, so I suppose this condition would generate hourly alerts of queue "being healthy" for more than 10 seconds 🤷
Will Raphaelson
02/16/2023, 5:04 PMStéphan Taljaard
02/16/2023, 7:06 PMfor 9 minutes
) was ignored, and as soon my batch of flows were due even if a flow is only seconds late, the alert fires.
Should I message in this thread if it happens again?Will Raphaelson
02/16/2023, 7:06 PMStéphan Taljaard
02/24/2023, 8:13 AMUnhealthy work queue
Name: default
Last polled: 2023-02-24T08🔟25.029779+00:00
Late run count:
URL: https://app.prefect.cloud/account/2a0672be-6e64-4081-bdfd-a4dfded5a802/workspace/b70a86f1-659f-408f-add7-9665c6bfa327/work-queues/work-queue/2aa024db-13b8-4203-a89b-2db6487959ad
Prefect Notifications | Today at 10:10