cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Saurav Lahiri (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-3471) Provide an API to extract the log statements of a given jobid
Date Mon, 30 Dec 2013 06:06:05 GMT


Saurav Lahiri commented on CLOUDSTACK-3471:

As per Chiradeep:
Hi Saurav,
It looks like the feature is a little orthogonal to ACS. It is more an
adjunct. The only reason to add an API to CloudStack is to re-use the
authentication layer. Otherwise, the feature does not interact with other
parts of ACS at all.

If there was a way for a service to re-use the API layer, that would work?
So, the "LogSearchAsaService" service would be exposed on say a different
port, and run as a different app/service/servlet

> Provide an API to extract the log statements of a given jobid
> -------------------------------------------------------------
>                 Key: CLOUDSTACK-3471
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      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

View raw message