Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Mon, 20 Jan 2014 19:39:23 +0000 (UTC)
From: "Nitin Mehta (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12654709.1372161008314.35799.1390246763010@arcas>
In-Reply-To: <JIRA.12654709.1372161008314@arcas>
References: <JIRA.12654709.1372161008314@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-3190) action events message
 published on 'event bus' should have the UUID of the entity for which event
 generated and event type
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876771#comment-13876771 ] 

Nitin Mehta commented on CLOUDSTACK-3190:
-----------------------------------------

Hi Alex,
This isn't resolved because I see that for many action events the UUID is isnt logged yet. 
Example - deployVm, ActionEvent type: VM.EXPUNGE etc.
Is there no way of resolving this generically, do I need to this for every API ?

> action events message published on 'event bus' should have the UUID of the entity for which event generated and event type
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3190
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3190
>             Project: CloudStack
>          Issue Type: Task
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.1.0
>         Environment: action events message published on 'event bus' should have the UUID of the entity for which event generated and entity type details. as well
> Events bus framework with current AMQP default implementation, has routing key with format 'Eventsource.EventCategory.EventType.EntityType.EntityUUID'. For action events, EntityUUDI is not populated. Fix would required to ensure entity UUID is used in forming the routing key.
>            Reporter: Murali Reddy
>            Assignee: Alex Ough
>              Labels: newbie
>


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)