You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sonal Ojha (JIRA)" <ji...@apache.org> on 2014/03/19 13:43:43 UTC

[jira] [Created] (CLOUDSTACK-6256) Enhance the cloudstack events to include more information

Sonal Ojha created CLOUDSTACK-6256:
--------------------------------------

             Summary: Enhance the cloudstack events to include more information
                 Key: CLOUDSTACK-6256
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6256
             Project: CloudStack
          Issue Type: Improvement
      Security Level: Public (Anyone can view this level - this is the default.)
    Affects Versions: 4.4.0
            Reporter: Sonal Ojha
            Assignee: Sonal Ojha


Currently the event logged in CloudStack doesn't give detailed information about the event that has occurred. The information provided in each event shown on the cloudstack ui doesn't provide specifics, particularly in case of errors. For example, the message shown on the cloudstack ui is just "Error while starting Vm. Vm Id: <id>" in case of failure to start a vm , which doesnt help much.

I would like to propose some changes to enhance the events to be more informative. Like:

1) Instead of just showing resource database id in the event details it should also display resource UUID. Since all the cloudstack apis take input as resource uuid it would be helpful to see the same on the ui as well. Like in the quickview mode introduce another field as resource UUID which would specify the UUID for the resource on which the event occurred.

2) Enhance the events and listEvents API to include the resource UUID so that it can be queried by the resource UUID as well.

3) Currently, the event description messages are specified in the *Cmd.java file instead, all of them should be externalize to a resource file. This would be helpful even for internationalization.

4) Provide more detailed messages in case of error events. Messages such as "Error while starting VM" are generic to take any action.

These changes could be taken forward in phases, some suggestion like

Phase I -
	include 2 and 3 point mentioned above
Phase II - 
	include 1 and 4 point mentioned above



--
This message was sent by Atlassian JIRA
(v6.2#6252)