Re: [Architecture] [API Analytics] Health Monitoring

Hi, Are we using the same handler we publish data to DAS (AFAIU the events go through CEP before publishing to DAS)? If so I have a small doubt if we can cover the following scenario as the synapse response handlers are executed before the outSequence of the API. 1. Backend returns an invalid

Re: [Architecture] [API Analytics] Health Monitoring

+1 for API Availability Dashboard. On Thu, Mar 3, 2016 at 10:03 PM, Janaka Ranabahu wrote: > Hi Maheshakya, > > On Thu, Mar 3, 2016 at 4:30 PM, Maheshakya Wijewardena < > mahesha...@wso2.com> wrote: > >> Hi, >> >> Due to the potential security issues and complexity issues arose

Re: [Architecture] [API Analytics] Health Monitoring

Hi Maheshakya, On Thu, Mar 3, 2016 at 4:30 PM, Maheshakya Wijewardena wrote: > Hi, > > Due to the potential security issues and complexity issues arose in the > discussions among APIM analytics team members, we have decided to get rid > of the separate Java client for API

Re: [Architecture] [API Analytics] Health Monitoring

Hi, We have decided not to include the HTTP methods that affects the backends of APIs, such as POST, DELETE since the health checker should not cause any differences in the backend. Best regards. On Tue, Feb 23, 2016 at 10:53 AM, Maheshakya Wijewardena < mahesha...@wso2.com> wrote: > Hi, > >

Re: [Architecture] [API Analytics] Health Monitoring

Maheshakya, Can you check the status of cloud status monitor with Cloud team first? This was originally written for Stratos. It's doing the same thing (endpoint monitoring) We had a similar discussion sometime ago and conclusion was we will share the same functionality. At that time status

[Architecture] [API Analytics] Health Monitoring

Hi, We have discussed (APIM team and analytics team) and came to a decision to implement the health monitor for APIM as a separate Java client. The following diagram depicts the architecture of the health monitor. ​ - Health checker incorporates the full life cycle of an API, therefore