Alex your idea makes sense but I thought we wanted to log everything in UUID now even though its MS log and available to admin only - is that not the case ? Or we need to be careful for this only in case when we are popping the exception to the end user ?
Filed bug https://issues.apache.org/jira/browse/CLOUDSTACK-1047 Thanks, -Nitin On 24/01/13 12:31 AM, "Alex Huang" <alex.hu...@citrix.com> wrote: >You should log a bug for this. All this means is there should be a log >statement before any job that says "job-[id]=[uuid]". I personally like >the ids because uuids are tough to type and extends the logs but I'm okay >both ways. > >--Alex > >> -----Original Message----- >> From: Nitin Mehta [mailto:nitin.me...@citrix.com] >> Sent: Tuesday, January 22, 2013 10:59 PM >> To: cloudstack-dev@incubator.apache.org >> Cc: Kelven Yang; Jessica Tomechak; Radhika Puthiyetath >> Subject: Re: jobid tracking in logs >> >> Thanks so much. I have been wanting to bring this up for so long >> Kelven - what is the guidance ? Do we start logging the UUID instead of >> the job id in the MS logs ? >> >> This needs to be updated in the docs as well - >> http://incubator.apache.org/cloudstack/docs/en- >> US/Apache_CloudStack/4.0.0-i >> ncubating/html/Admin_Guide/troubleshooting-working-with-server- >> logs.html >> >> -Nitin >> >> On 23/01/13 12:17 PM, "Prasanna Santhanam" <t...@apache.org> wrote: >> >> >I would use the job-id returned in API responses to track the >> >progress of a job. With the switchover to uuids all async APIs return a >> >jobid as uuid. The logs however do not have this uuid making it hard >> >to track a failed job and extract the stacktrace. >> > >> >What's the suggested way to workaround/fix this? >> > >> >(PS: I know I can query the async_job table) >> > >> > >> >-- >> >Prasanna., >
