Re: [Architecture] [Dev] APIM C5 Analytics - Designing Event streams

Hi Rukshan, There have been requests in the past to include all available CGI variables[1] to give more flexibility when it comes to stats. We are already capturing some of these above. I dont know for sure how useful or relevant it might be to capture them all though. [1]

Re: [Architecture] Deployment automation for Carbon 5 based products

Hi Lasantha, Great work! Please find few comments inline: On Mon, Dec 5, 2016 at 5:31 PM, Lasantha Samarakoon wrote: > > > Following endpoints are available in this API (Please see the attached > Swagger definition for detailed description). > > *POST /deployments * > -

[Architecture] APIM C5 Analytics - Designing Event streams

Hi All, As part of the new APIM C5 release we are start to design analytics Streams. Here is the list of streams we decided to publish from APIM components. Even though here we listed separate event streams we hope to merge all the event streams except *org.wso2.apimgt.statistics.workflow* to one

Re: [Architecture] Moving XACML to C5

On Dec 6, 2016 3:19 AM, "Prabath Siriwardana" wrote: On Thu, Dec 1, 2016 at 12:08 AM, Senthalan Kanagalingam wrote: > ​When moving XACML from C4 to C5, we have concerned following key aspect > to change and improve. > > 1. Remove multi tenancy from

Re: [Architecture] Moving XACML to C5

On Thu, Dec 1, 2016 at 12:08 AM, Senthalan Kanagalingam wrote: > ​When moving XACML from C4 to C5, we have concerned following key aspect > to change and improve. > > 1. Remove multi tenancy from ​entitlement engine. > > In C4, we have tightly coupled with the multi tenancy.

Re: [Architecture] Moving XACML to C5

Hi Sidath, Thank you for your feedback. Yes, we can use cluster communication for database. But we are planned to use file based storage to store the polices. If all the nodes in the cluster use one directory, then their will be no need for notifying other nodes about the policy change. Because

[Architecture] [PROPOSAL] Distribute internal machine states

Introduction This proposal is to address the CEP internal state distribution at Pattern/Sequence rules. Currently, you need to use SiddhiQL event tables in order to share states across multiple Siddhi instances. You can do this using Hazelcast or using RBDMS event tables. In both cases there