Hi Maheshakya,
On Mon, Feb 15, 2016 at 11:59 AM, Maheshakya Wijewardena < mahesha...@wso2.com> wrote: > Hi, > > After discussing with API analytics team, the health monitor component for > API analytics has been decided to be implemented as a separate java client. > What is the reason for this decision? The load on the APIM server if a stat publishing agent is run? Thanks. > This is essentially a scheduled program which pings the APIs to check > their statuses. > The conventional way of implementing this is by adding it as a scheduled > task in the ESB. But in the point view of deployment, this adds the > complexity of having an ESB just to host the health monitor for APIM. > > What would be the most appropriate solution to implement this health > monitor, considering both the intricacy of deployment and the standards. > > Best regards. > -- > Pruthuvi Maheshakya Wijewardena > mahesha...@wso2.com > +94711228855 > > > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- -- Lahiru Sandaruwan Committer and PMC member, Apache Stratos, Senior Software Engineer, WSO2 Inc., http://wso2.com lean.enterprise.middleware phone: +94773325954 email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/ linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
