Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5BD2BE564 for ; Wed, 23 Jan 2013 06:48:31 +0000 (UTC) Received: (qmail 40859 invoked by uid 500); 23 Jan 2013 06:48:31 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 40819 invoked by uid 500); 23 Jan 2013 06:48:30 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 40803 invoked by uid 99); 23 Jan 2013 06:48:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Jan 2013 06:48:29 +0000 X-ASF-Spam-Status: No, hits=1.3 required=5.0 tests=RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of srivatsav.prasanna@gmail.com designates 209.85.220.42 as permitted sender) Received: from [209.85.220.42] (HELO mail-pa0-f42.google.com) (209.85.220.42) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Jan 2013 06:48:21 +0000 Received: by mail-pa0-f42.google.com with SMTP id rl6so4579516pac.15 for ; Tue, 22 Jan 2013 22:48:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:date:from:to:subject:message-id:mail-followup-to :mime-version:content-type:content-disposition:user-agent; bh=U3doSsKelwF+6wDbUYzMr3krl95cH+uTsWzepU2ENW8=; b=shzHGIooti9R5NhN9Ngy7fnhofQLfkoluTUWIaeYYtP9tswTJDBZQOBXC4OrNCXygj xfWVSL/2a/ii38kReb/cbkBiZtAXbDypqlfVIp5zHFlfeX2VoqFCW7DvMIpPl3nccTsF h5y52oQJi0a6M/iRGdWlsU0ZTfXrZshEi4PhD7dNV6/BMPonMiZkJjEYUxZigeoBwsMU 888VQDIf6lH0sAbK1FT5ZBXHSbBnwLSYKDQcyc443TulHmC3d4vtuUhlJaiuV06CPwn1 Kikfmz+9UTqMQAN/SOuwMYaTPWkV7WUzlVoRmofn9W1n9ckIqJ1sl9Gn8VaSsrN9eW1L zeNg== X-Received: by 10.68.191.5 with SMTP id gu5mr588410pbc.145.1358923681395; Tue, 22 Jan 2013 22:48:01 -0800 (PST) Received: from localhost ([202.75.201.5]) by mx.google.com with ESMTPS id nt5sm12235009pbb.59.2013.01.22.22.47.58 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Tue, 22 Jan 2013 22:48:00 -0800 (PST) Sender: prasanna Date: Wed, 23 Jan 2013 12:17:52 +0530 From: Prasanna Santhanam To: CloudStack Dev Subject: jobid tracking in logs Message-ID: <20130123064752.GB2483@cloud-2.local> Mail-Followup-To: CloudStack Dev MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Checked: Checked by ClamAV on apache.org 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.,