Hi Keith, On Wednesday, October 31, 2012 4:52:42 AM UTC+1, Keith Rarick wrote: > > On Tue, Oct 30, 2012 at 3:41 PM, Jurian Sluiman > <[email protected]<javascript:>> > wrote: > > how do you relate the errors from jobs to your log? > > I'd suggest making sure the logs contain enough context for > debugging failures, including the job id and possibly also a > description of what the job was trying to do. > > The idea is to avoid the need to match up log messages to > beanstalkd jobs by putting all necessary info in the logs. >
Our logs are not really suited to play nice with business logic like this. The log is beanstalk-worker specific, but in a standard log format (this makes aggregating them very easy and helps us in monitoring the complete state of our servers). That being said, I think I just store the the buried jobs in a sqlite database. There are some buried queues floating around and the sqlite database provides the context of those jobs. It creates a coupling I am not really in favour of, but it probably will do the job well (and behaves like a "log" as you interpret it probably). I can easily store job id, job data and any exception type, exception message and exception trace as I want. This database plays very well together with the business logic I need and there are no problems in parsing and relating long log files to the state of the bury queue of beanstalk. If eventually there are possibilities to do this internally in beanstalk I would love to hear it. --- Jurian Sluiman -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/beanstalk-talk/-/4l2UEot5EawJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.
