Hi Dimuthu, On Tue, Feb 23, 2016 at 11:28 AM, Dimuthu Leelarathne <[email protected]> wrote:
> > On Tue, Feb 23, 2016 at 11:25 AM, Dimuthu Leelarathne <[email protected]> > wrote: > >> Hi all, >> >> I am seeing the below three mails on architecture@ for "Analytics for >> APIM". >> >> Health Monitoring >> Unusual request IP detection >> Abnormal tier usage (Analytics for APIM) >> >> From the content of all of the above mails I see that, these are driven >> as separate efforts and don't have a unified way of notifying the user when >> something goes wrong. >> > Even though the implementation work happen separately, the alerting architecture is common across. We'll have an alert dashboard at 'Analytics for APIM' where you could see all alerts that are got generated. I think we need to design the alerting as a uniform experience for >> APIM analytics when it comes to the end user. This doesn't mean use the >> "same way for alerting", this means give the correct user experience. The >> questions is, do we want alerting to be configured per feature, for each of >> the above features? >> > Yes, each alert should be able to configure independently as the parameters required are feature/alert dependent. Did I answer your question? > >> thanks, >> Dimuthu >> >> -- >> Dimuthu Leelarathne >> Director >> >> WSO2, Inc. (http://wso2.com) >> email: [email protected] >> Mobile : 0773661935 >> >> Lean . Enterprise . Middleware >> > > > > -- > Dimuthu Leelarathne > Director > > WSO2, Inc. (http://wso2.com) > email: [email protected] > Mobile : 0773661935 > > Lean . Enterprise . Middleware > -- Thanks & regards, Nirmal Team Lead - WSO2 Machine Learner Associate Technical Lead - Data Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
