[jira] [Commented] (STRATOS-112) Integrate Stratos with a CEP Engine in order to aggregate/summarize various events

["Nirmal Fernando (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/STRATOS-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799117#comment-13799117 ] 

Nirmal Fernando commented on STRATOS-112:
-----------------------------------------

WSO2 CEP Engine will be used for the initial integration. 

> Integrate Stratos with a CEP Engine in order to aggregate/summarize various events
> ----------------------------------------------------------------------------------
>
>                 Key: STRATOS-112
>                 URL: https://issues.apache.org/jira/browse/STRATOS-112
>             Project: Stratos
>          Issue Type: New Feature
>            Reporter: Nirmal Fernando
>            Assignee: Nirmal Fernando
>            Priority: Critical
>             Fix For: 4.0.0 M1
>
>
> With the new architecture, real-time events such as in-flight requests of a load balancer, health of a Cartridge instance etc. would get published directly to a Complex Event Processor (CEP). It's the duty of the CEP to emit an aggregated version of the events it received, to the reliable message broker so that auto-scaler could act upon the aggregated events.
> So, what would be these aggregated events? Certainly it is not primitive as in-flight requests count at a given time and also not to the extreme of deciding whether to spawn a new instance, but some critical information, lies in between. Some examples would be,
>     Average requests-in-flight count / load-average of an instance.
>     Gradient of requests-in-flight / load-average of an instance.
>     Second Derivative of requests-in-flight / load-average of an instance. (to detect whether the gradient is increasing or decreasing over a time period)
>     Summarize failed requests.
>     Pattern detection.
> etc.



--
This message was sent by Atlassian JIRA
(v6.1#6144)