showing the last run status in the scheduled table #492
Replies: 3 comments 6 replies
-
|
This is a really clever idea! I love it! Very innovative. I'll add this as a core feature in the next release (giving you full credit of course). |
Beta Was this translation helpful? Give feedback.
-
|
Hi Joseph, Daniel |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, good idea. Jenkins has something like this, always thought it would be useful for cronicle. Actually things like that are quite simple to implement, there is already a mechanism to update event via job (by populating job.update_event property). I guess it would be beneficial to add some more info about last execution, e.g. exit code, jobid and duration. Maybe even keep last N executions. I've been working on a similar feature for a job to emit short message, so it could be displayed on active job table (similar to progress), and then the last message will be kept on event, so following run would know where previous job stopped. I'll share my findings later. One more feature from this category just came to my mind - if we can calculate average duration of previous jobs then we can estimate current job progress and auto-generate progress bar |
Beta Was this translation helpful? Give feedback.
-
|
Sounds really exciting. T he only question is whether there is enough room for it in the scheduled table and whether it won't be too crowded. |
Beta Was this translation helpful? Give feedback.
-
|
Mike, you are an ocean of great ideas. I wish I had the time to implement them all! |
Beta Was this translation helpful? Give feedback.
-
|
@mikeTWC1984, I installed your latest release 1.5.9 (mainly for the filtering fix in the scheduled page from @jhuckaby) and was totally surprised, that you already implemented the the status light for every job inclusive a filtering option and a collapsing option for categories! But here it is unfortunately so that the categories open again when the page refreshes. But the status lights are really great! but for now: big thanks to both of you. |
Beta Was this translation helpful? Give feedback.
-
|
Check out version 0.9.7 guys. It has this feature built in!
You can also filter the event list based on the last run status (in the "All Events" menu), and also click on the last run status bubbles to jump to the latest job detail page. I should say here that this branch of Cronicle (v0) is in maintenance mode, and I usually never add new features. The reason is, I'm hard at work over on Cronicle v2 (Orchestra), where I will have to code this feature all over again. But this one was really low hanging fruit, easy to implement, and is such a good idea, I really couldn't resist. Thanks @dheise-rheinenergie-trading-com! |
Beta Was this translation helpful? Give feedback.
-
|
Like the new feature, however I do miss having the status column. It is now hard to see what jobs are actually running when you have several hundred of them. |
Beta Was this translation helpful? Give feedback.
-
I also agree, in that, before I could see how many processes were running, now you have to go to home to see them, if it could be implemented again it would be greatly appreciated, thanks |
Beta Was this translation helpful? Give feedback.
-
Today I had to manually rerun a lot of failed events. Here it would have been helpful to see the run status of the last run of each event in the scheduled table. So I had an idea for a little trick to show this status.
For this I use my already running webhook listener (which collects the completed messages for my monitoring system from all of my events) to change the title of the event in dependency of the return code (using the api call update_event).
The result is something like this:
with these nice side effects:
we find this pretty handy.
maybe someone can also use this idea...
Daniel
Beta Was this translation helpful? Give feedback.
All reactions