AI OnAI Off
CMS Admin - Scheduled jobs improvements
Some of the feature could be available via interactive overview plugin :)
http://blog.tech-fellow.net/2013/10/17/overview-your-episerver-scheduled-jobs-interactively/
Jul 13, 2016 11:35
You're a star - as always, Valdis :)
No problem using the tool in Epi9 I presume?!
Jul 13, 2016 11:44
[To episerver team]
Our client is keep in letting the suggested functionality be a part of episerver CMS. Any take if that would be a reality?
Jul 14, 2016 8:39
Jonas, wait a bit. I'm planning a feature for the plugin. Your needs are acheivable. And I hope others might benefit from this as well! :)
Jul 27, 2016 15:57
Playing around with interceptors... Came to conclusion that it's possible to measure only duration of the jobs that are eecuted on scheduled basis (started by job scheduler). other cases - like manual execution - would not be supported. Basically - there is no easy way to intercept ScheduledJob type and add telemetry around its exeuction method.
Would limited solution be still interesting - or we just wait.. Maybe EPiServer will fix that in the platform..?!
Jul 28, 2016 13:36
"Duration" is now measured and stored in the log, should show up in a release the coming weeks.
Nov 22, 2016 15:42
Will be part of my plugin as well when released, + sorting capabilites in the table.
Not competing with EPiServer here, just extending.. hahaaha :)
Cheers!
Nov 22, 2016 15:45
If magic happens and you can jump on v10.3 - some nice additions to scheduled jobs might become handy :)
http://blog.tech-fellow.net/2016/12/28/scheduled-jobs-updates/
Dec 28, 2016 21:44
Your request
"1. It would be great if there was a log for scheduled jobs showing what job was run and how long it tool to enable historical analysis regarding performance."
was introduced in Episerver.CMS.Core 10.3.0 (release note) (in addition to several other improvements to the scheduled jobs log).
Edited,
Jan 05, 2017 13:38
This thread is locked and should be used for reference only.
1. It would be great if there was a log for scheduled jobs showing what job was run and how long it tool to enable historical analysis regarding performance.
2. Be able to choose how long the tblScheduledItemLog can be. Today maximum 100 entries, but jog running often (every second minute) makes it hard to see patterns.
3. Sorting abilities over scheduled jobs in Admin View.