Hi Maninda,

On Tue, Nov 25, 2014 at 2:48 PM, Maninda Edirisooriya <[email protected]>
wrote:

> Current implementation of BAM Activity Monitoring is based on a the
> activity ID field and sorting the timestamps. It has some limitations.
>
> 1. Only one activity monitoring scenario is possible per tenant
>

Can you elaborate more on this. Do you mean that one activity can have
events from different tenants?


> 2. Activity ID the the hard coded parameter used for correlating among
> events
>
3. Ordering mechanism is based only on sorting operation of timestamp field
> 4. Tightly bound with Cassandra custom indexes
>

Yes. We have above known limitations in the current architecture basically
because indexing and searching is implemented based on Cassandra custom
index CFs which doesn't support advance sorting/searching and grouping
operations.


>
> With the introduction of custom data stores in BAM we should support
> activity monitoring for RDBMS indexes. There we can use SQL queries as
> tasks for updating indexes. This enables us to use multiple activity
> monitoring scenarios per each stream. For example all session ID,
> transaction ID and username can be considered as activities for different
> monitoring requirements at the same time. With the toolbox deployment we
> can define all the activity monitoring scenarios so that indexes are
> created for each field. And also we can make it possible to configure the
> sorting mechanism per each activity. The user can be able to select
> whatever field like timestamp or hop_number as the sorting field. This
> would enable user to introduce their own field to order the activity
> results. WDYT?
>

Multiple activity monitoring scenarios per each stream is already supported
in current implementation. Sorting and pagination are the missing pieces
which we have design properly in our next major release. And we should also
make the activity correlation field configurable via the toolbox.


>
> *Maninda Edirisooriya*
> Senior Software Engineer
>
> *WSO2, Inc.*lean.enterprise.middleware.
>
> *Blog* : http://maninda.blogspot.com/
> *E-mail* : [email protected]
> *Skype* : @manindae
> *Twitter* : @maninda
>



-- 
Regards,

Inosh Goonewardena
Associate Technical Lead- WSO2 Inc.
Mobile: +94779966317
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to