dungbeetle
dungbeetle copied to clipboard
[Feature Request] Debug Shell for dungbeetle
dungbeetle currenly has client api and HTTP endpoints for doing things like
- Posting task
- Scheduling job
- Getting task status
Use Case:
Lets consider case when one of the queue started reporting some error or if a system is running 40 workers but still we see delays in requests.
Now if we want to see
- how many jobs are running?
- how many jobs are there in queue?
- what was the execution time of last queue?
Then we have only the option to do HTTP calls which is not the most efficient way and requires technical knowledge about endpoints etc.
What if we have something and we run command like this
dungeecli workers --wide
Sugegsted output
worker queue length last_exectution_time health
worker1 10 2.5s OK
worker2 20 3.5s NOT_OK
this would make debugging so easy
And I guess you would have guessed it , it's very similar to oc
command for openshift or kubectl
for kubernetes
Extra info: In our projects we pin processes to particular core , like process1 to run only on core0 , core1. But somehow the core changes for some random reason like crash. In this case the debug shell tells us which process is being run on which core and when it was last changes. Doing this using linux commands was not efficient , hence the debug shell.
@knadh What is your opinion on this? is it something which could be explored?