[
https://issues.apache.org/jira/browse/CLOUDSTACK-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588093#comment-13588093
]
Chiradeep Vittal commented on CLOUDSTACK-1047:
----------------------------------------------
We can use NDC
http://lstierneyltd.com/blog/development/log4j-nested-diagnostic-contexts-ndc/
There should be a NDC.push(jobid) in AsyncJobMgrImpl before handing it over to
the service
> tracking in logs using job id
> -----------------------------
>
> Key: CLOUDSTACK-1047
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1047
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc, Management Server
> Affects Versions: 4.1.0
> Reporter: Nitin Mehta
> Assignee: Kelven Yang
> Labels: logging,, troubleshooting, usability
>
> Entire conversation @
> http://www.mail-archive.com/[email protected]/msg18501.html
> Update the Docs as well @
> http://incubator.apache.org/cloudstack/docs/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/troubleshooting-working-with-server-logs.html
> 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)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
