Hi Rajeev, Wouldn't the 2nd approach be more useful in terms of flexibility and getting real time data? Since CEP is designed to handle large amounts of data in real time, it might be actually more effective to do the pre-processing stuff at CEP side as well without burdening the APIM with pre-processing stats (or is it BAM that will pre-process these stats and store to DB?).
We can go ahead with approach #1, but if new use cases come in where we need the raw data to derive the stats/analytics, then we might find that data sent by approach #1 is too limited one day. WDYT? Thanks, Lasantha On 3 March 2015 at 21:24, Rajeev Sampath <[email protected]> wrote: > Hi, > > I'm currently working on the $subject where the idea is to let users to > configure alert conditions (such as response time exceeds 100 ms etc) > through statistics UI's and to eliminate the need to manually configure CEP > deployment artifacts to trigger alerts. > > For generating alerts, there are couple of ways to fetch data from the > APIM side: > > 1. Through the apimgt.usage.client, which reads already processed data > from a DB. In this case we get statistics such as usage per user etc, which > eliminates the need for CEP to calculate those. However, this is not > real-time. > > 2. Pointing data publisher to publish request/response data directly to > CEP. In this case CEP has to derive the necessary values, but this will be > real-time. > > I've been developing the backend assuming the 1st approach. Appreciate any > suggestions or better alternatives on this. > > > Thanks > Rajeev > > -- > Rajeev Sampath > Senior Software Engineer > WSO2, Inc.; http://www.wso2.com. > > Mobile: > * +94716265766 <%2B94716265766>* > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: [email protected] mobile: (+94) 71 5247551
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
