Hi Maheshakya,

   - This will incorporate full life cycle of an API tries to demonstrate
   end-to-end behavior from client perspective.

Are you going to poll the backend as well?

Thanks,

Sachith

On Tue, Feb 16, 2016 at 10:17 AM, Maheshakya Wijewardena <
[email protected]> wrote:

> Hi,
>
> Following points elaborates further about the considerations on which Java
> client for API health monitoring is based.
>
>    - This will be implemented as a separate java client which pings the
>    APIs periodically.
>    - This will incorporate full life cycle of an API tries to demonstrate
>    end-to-end behavior from client perspective.
>    - This consumes quota from the whole API, therefore client needs to
>    manage it.
>    - In deployment, DAS resides inside the firewall and it needs to have
>    a port open for the health monitor to publish. This will be done via a
>    secured channel with HTTPS.
>    - Health monitor will provide statuses such as for time intervals
>    like, last hour, last week and  summarizations.
>    - Error codes from endpoints will be tracked separately and will
>    provide drilled down descriptions based on those codes.
>    - A list of APIs that needs to be monitored will be obtained from the
>    user as a config.
>    - The DAS dashboard is similar to
>    http://apimetrics.io/check-api-health/ .
>
> Best regards.
>
>
> On Tue, Feb 16, 2016 at 5:06 AM, Dilan Udara Ariyaratne <[email protected]>
> wrote:
>
>> Hi Maheshakya,
>>
>> Can you also briefly explain how is this client going to monitor the
>> health of an API and
>> what considerations are being made to check the health?
>>
>> Thanks.
>>
>>
>> *Dilan U. Ariyaratne*
>> Software Engineer
>> WSO2 Inc. <http://wso2.com/>
>> Mobile: +94725197942
>> lean . enterprise . middleware
>>
>> On Mon, Feb 15, 2016 at 12:34 PM, Lahiru Sandaruwan <[email protected]>
>> wrote:
>>
>>> Hi Maheshakya,
>>>
>>>
>>> On Mon, Feb 15, 2016 at 11:59 AM, Maheshakya Wijewardena <
>>> [email protected]> 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
>>>> [email protected]
>>>> +94711228855
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Architecture mailing list
>>>> [email protected]
>>>> 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: [email protected] blog: http://lahiruwrites.blogspot.com/
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>> _______________________________________________
>>> Architecture mailing list
>>> [email protected]
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>> _______________________________________________
>> Architecture mailing list
>> [email protected]
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Pruthuvi Maheshakya Wijewardena
> [email protected]
> +94711228855
>
>
>
> _______________________________________________
> Architecture mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Sachith Withana
Software Engineer; WSO2 Inc.; http://wso2.com
E-mail: sachith AT wso2.com
M: +94715518127
Linked-In: <http://goog_416592669>https://lk.linkedin.com/in/sachithwithana
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to