Hi David, Probably I didn’t get the point, the new architecture of OTRS will enable the scheduler to perform different kind of tasks that are currently delegated to Cron and other parts of OTRS itself, in OTRS 5 you will only need to monitor the process that controls the scheduler is up and running to make sure that the service will be working. For sure you still need to monitor you http server and your DB.
You will get more details about the new scheduling mechanism and other new features when OTRS 5 Beta 1 gets GA. ((enjoy)) Carlos Rodríguez > On May 5, 2015, at 7:56 AM, David Boyes <dbo...@sinenomine.net> wrote: > > *sigh* > > This approach really makes it tedious to do comprehensive/predictive > monitoring of the OTRS services from a central point. Do you *really* need to > invent your own job scheduler? Yes, there are limitations to cron, but it’s > one big piece of scripting to get Yet Another Workload Scheduler tied into a > decent monitor. > > Also please consider that OTRS 5 will not use all the CronJobs as OTRS 4 and > before, a new Scheduler daemon will take care to handle all this repetitive > tasks like close pending tickets, escalations, delete old cache and sessions, > etc. Only the a CronJob to make sure the Scheduler and other daemons are > running will be executed. > > _______________________________________________ > OTRS mailing list: dev - Webpage: http://otrs.org/ <http://otrs.org/> > Archive: http://lists.otrs.org/pipermail/dev > <http://lists.otrs.org/pipermail/dev> > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev > <http://lists.otrs.org/cgi-bin/listinfo/dev>
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
