You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@eagle.apache.org by Hao Chen <ha...@apache.org> on 2015/11/16 11:09:59 UTC

[DISCUSS] Logic Semantics for alertExecutorId

Currently the [alertExecutorId] for alert execution seems a little confused
for both users and developers.

Let's classify about it:

1. What's the semantics of alertExecutorId for ?
2. What's the purpose?
3. How should user/developer to use it in monitoring pipeline definition on
both UI or code?

Regards,
Hao

Re: [DISCUSS] Logic Semantics for alertExecutorId

Posted by "Zhang, Edward (GDI Hadoop)" <yo...@ebay.com>.

alertExecutorId is internal name of a processing element which consumes
event stream and executes policy on event stream. In storm, it is mapped
to a bolt.
alertExecutorId exists because it may have multiple such bolts in one
single topology. 

For developer, he should understand alertExecutorId so he can connect
correct stream to this alertExecutorId.
For user, he should understand alertExecutorId so he can configure policy
on different streams.

But we can simplify the system by decoupling data preparation topology and
event evaluation topology. This is back to the discussion long time ago.

In this case, event evaluation topology is a simple topology which takes
one or multiple events from Kafka bus and evaluates them.
event prepare topology has complex business logic which emits events for
eventE evaluation topology to consume.

Edward

On 11/16/15, 2:18, "Hao Chen" <ha...@apache.org> wrote:

>4.  How to abstract the semantics as a more meaningful element for
>end-user?
>
>
>Regards,
>Hao
>
>On Mon, Nov 16, 2015 at 6:09 PM, Hao Chen <ha...@apache.org> wrote:
>
>> Currently the [alertExecutorId] for alert execution seems a little
>> confused for both users and developers.
>>
>> Let's classify about it:
>>
>> 1. What's the semantics of alertExecutorId for ?
>> 2. What's the purpose?
>> 3. How should user/developer to use it in monitoring pipeline definition
>> on both UI or code?
>>
>> Regards,
>> Hao
>>

Re: [DISCUSS] Logic Semantics for alertExecutorId

Posted by Hao Chen <ha...@apache.org>.

4.  How to abstract the semantics as a more meaningful element for end-user?


Regards,
Hao

On Mon, Nov 16, 2015 at 6:09 PM, Hao Chen <ha...@apache.org> wrote:

> Currently the [alertExecutorId] for alert execution seems a little
> confused for both users and developers.
>
> Let's classify about it:
>
> 1. What's the semantics of alertExecutorId for ?
> 2. What's the purpose?
> 3. How should user/developer to use it in monitoring pipeline definition
> on both UI or code?
>
> Regards,
> Hao
>