You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2014/07/29 19:08:40 UTC
[jira] [Updated] (CLOUDSTACK-3471) Provide an API to extract the
log statements of a given jobid
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alena Prokharchyk updated CLOUDSTACK-3471:
------------------------------------------
Issue Type: Improvement (was: Bug)
> Provide an API to extract the log statements of a given jobid
> -------------------------------------------------------------
>
> Key: CLOUDSTACK-3471
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3471
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: API
> Affects Versions: pre-4.0.0, 4.0.0, 4.1.0
> Reporter: Prasanna Santhanam
> Fix For: Future
>
>
> With the job-id in the logs having no link to the external world that is
> interacting with the cloudstack API it is not easy to correlate a failure with
> a specific job.
> With the inclusion of uuids in the management server logs it would be nice to
> provide an API extractJobLog that takes a jobid = <uuid> as parameter so as to
> extract all log statements of the job. This will be an admin only API and
> ideally a plugin that can be turned off in favour of better log
> monitoring/analyis systems.
> Having the log makes is useful to link our automated test failures with the log
> from the management server using a simple API call.
--
This message was sent by Atlassian JIRA
(v6.2#6252)