* Store jobs that waited for too long
* Add warnings as badges for long waited jobs
* Separate into self_wait_time and aggregate
Change the UI accordingly
* Prepare sqlx
* Update backend/windmill-queue/src/jobs.rs
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
* Fix incorrect query
* Prepare sqlx
* Move insert to pull + UI fixes
Insert as soon as the job is pulled and therefore started.
Add a badge on the lfow timeline to show the self wait time
* Move to after the pull in the worker
Move the logic to after the pull in the worker in the case its not a
noop
* Remove weird line
* Remove unnecessary async
---------
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
Co-authored-by: Ruben Fiszel <ruben@windmill.dev>
* add jobs_duration to /api/w/*/users/list
A few improvements on this might be considered.
- Adding the duration to /whoami and /whois
- Optionally fetching duration conditional on a query parameter.
- Using the query parameter value to select how far back to look,
`created_at > now() - $2 * '1 day'::interval`.
Subquery might not be optimal, but performance is a bit weird to test
right now as I haven't done much with my development database to get it
to resemble a typical (production) database. And there aren't many
indexes currently either.
And I think my rust rustfmt doesn't run because unstable options in the
rustfmt.toml or something so the formatting might be a bit wonky.
* duration -> duration_ms for completed_job
sqlx reordered keys in sqlx-data.json so the diff is quite noisy. I'm
not sure if I did it wrong or if this tool is obnoxious that way.
* don't double count job duration in flows
* job_duration_ms to Usage duration_ms jobs flows
rustfmt got carried away sorry
Ruben Fiszel
HugoCasa
Faton Ramadani
sqwishy