You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At my place of work we are using Horizon to monitor our queues one thing we found lacking is that there is very little insights in to what job is currently being run and how much system resources it is taking.
To solve this we are working on extending Horizon to give us this information and some grater control over what is running, once it's working we would be happy to contribute it back to Laravel Horizon. To that end we would like to know if you would be interested in this, and also what your opinions are regarding how this should be done?
Some of the planned features:
Phase 1:
Add "Running" status to Recent Jobs
Show current CPU/mem load for a job/process
Show current CPU/mem load for a scheduler
Phase 2:
Terminate a running job (UI similar to Retry for failed jobs)
Detect job failure via job<->process association instead of waiting for the timeout
The text was updated successfully, but these errors were encountered:
At my place of work we are using Horizon to monitor our queues one thing we found lacking is that there is very little insights in to what job is currently being run and how much system resources it is taking.
To solve this we are working on extending Horizon to give us this information and some grater control over what is running, once it's working we would be happy to contribute it back to Laravel Horizon. To that end we would like to know if you would be interested in this, and also what your opinions are regarding how this should be done?
Some of the planned features:
Phase 1:
Phase 2:
The text was updated successfully, but these errors were encountered: