Folks, Following a chat I had with Anjana and Shankar, some thoughts for improving the "BAM Message Tracer".
As of now, a message is traced by a unique ID that is assigned by the the tracer handler (if not already set). This unique ID is what BAM Activity Dashboard uses for grouping all correlated messages (in/out). However, there can be situations where we might need to use a more business related parameter for grouping (take a mobile device ID + session ID for example) which is likely to exist on the header or the message body. To support this, we can use two options. 1. Provide a feature on Message Tracer to let users specify expressions to extract this uniqueID or a combination of them. 2. Let users specify which parameters are 'group-able' (either from header or payload), and use them in the stream definition so that on the Dashboard we can support multiple grouping options. We created an Axis2 module to do something similar (more closer to Option 1) for a PoC, so we can reuse some of that stuff. Regards, Manoj -- Manoj Fernando Director - Solutions Architecture Contact: LK - +94 112 145345 Mob: +94 773 759340 www.wso2.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
