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 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 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? *Maninda Edirisooriya* Senior Software Engineer *WSO2, Inc.*lean.enterprise.middleware. *Blog* : http://maninda.blogspot.com/ *E-mail* : [email protected] *Skype* : @manindae *Twitter* : @maninda
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
