[overlord-issues] [JBoss JIRA] (RTGOV-582) Configure Event submitters per ActivityUnits o Activity Types

Jorge Morales (JIRA) issues at jboss.org
Fri Sep 26 06:33:02 EDT 2014


    [ https://issues.jboss.org/browse/RTGOV-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006407#comment-13006407 ] 

Jorge Morales commented on RTGOV-582:
-------------------------------------

I think that we should be exploring options with real use cases examples. I have done a project with similar concept as RTGov where I was submitting different types of events, those that model SOA events, which at the end provide with system behavior, and those customer/application specific events, which provided business behavior. Criticity of those are different in the sense that OPs needed to know how system was behaving, but they could live without having the business information in an scenario where the system was under heavy load, as they could do a replay of those events from logs at a later stage (batched business event replaying).
I think they could be both, collection source and switchyard application, depending on the Activity Collector.

> Configure Event submitters per ActivityUnits o Activity Types
> -------------------------------------------------------------
>
>                 Key: RTGOV-582
>                 URL: https://issues.jboss.org/browse/RTGOV-582
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>            Reporter: Jorge Morales
>            Assignee: Gary Brown
>            Priority: Minor
>             Fix For: 2.1.0.Final
>
>
> If more than one protocols can be used to communicate/submit events to the Activity Server, it should be configurable which Event Submitter to use per ActivityUnits or ActivityTypes, so this way we use a reliable transmission protocol for ActivityUnits/Types of high interest, and non reliable transmission protocols for low priority ActivityUnits/Types.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


More information about the overlord-issues mailing list