Since the Product has a nessary component to put this together, Can you consider this in upcoming version and implement it?
On Tue, Sep 1, 2020 at 10:41 PM Arshardh Ifthikar <[email protected]> wrote: > Yes, events are published to analytics per frame > > On Wed, Sep 2, 2020 at 11:08 AM Fazlan Nazeem <[email protected]> wrote: > >> AFAIK we publish an event to Analytics Server per incoming WebSocket >> frame. This can be verified by a simple test. >> >> On Wed, Sep 2, 2020 at 10:53 AM Silmy Hasan <[email protected]> wrote: >> >>> Hi vanjikumaran, >>> >>> We make use of analytics to summarize and persist the request count for >>> a certain period of time for an API, as we need an internal storage to >>> persist the request counts in order to publish it to the Billing engine >>> time to time . So If the data(Request stream) is published to analytics per >>> frame for websocket APIs , achieving this should not be a problem. I think >>> for web socket APIs, request stream is published for each frame and if so >>> the same peristing and publishing logic could be used for websocket apis >>> and this should be a minimal effort. if not we should find a way to >>> internally persist the frame count for webscoket APIs and write the logic >>> and publish it to the billing engine. >>> @Fazlan Nazeem <[email protected]> @Rukshan Premathunga >>> <[email protected]> @Arshardh Ifthikar <[email protected]> please >>> confirm whether streams are published to analytics per frame for Websocket >>> APIS. >>> >>> Also we have had discussions on whether frame or bandwidth based >>> pricing fits web socket apis better. So I think we can check the >>> feasibility of implementing it bandwidth wise as well and decide on the >>> better option >>> >>> >>> >>> On Tue, Sep 1, 2020 at 9:45 AM Vanjikumaran Sivajothy <[email protected]> >>> wrote: >>> >>>> Any update on this? >>>> >>>> On Tue, Aug 25, 2020 at 7:10 PM Vanjikumaran Sivajothy <[email protected]> >>>> wrote: >>>> >>>>> Hi Team, >>>>> >>>>> WSO2 API Manager offers a monetization functionality in the product >>>>> and It is working perfectly with HTTP Request-Response for the dynamic >>>>> pricing. However, WebSocket endpoints do not work like a typical HTTP >>>>> request-Response as once the connection is made the >>>>> communication happens via frames. >>>>> >>>>> Therefore, It is ideal to consider to implement the dynamic >>>>> pricing option for frame count rather than request count. >>>>> >>>>> >>>>> >>>>> https://github.com/wso2/product-apim/issues/9185 >>>>> >>>>> >>>>> -- >>>>> >>>>> *Vanjikumaran Sivajothy | Solution Engineer |WSO2 Inc. (m) +1 925 464 >>>>> 6816 | (e) vanji AT wso2.com <http://wso2.com>* >>>>> >>>>> >>>>> >>>> >>>> -- >>>> >>>> *Vanjikumaran Sivajothy | Solution Engineer |WSO2 Inc. (m) +1 925 464 >>>> 6816 | (e) vanji AT wso2.com <http://wso2.com>* >>>> >>>> >>>> >>> >>> -- >>> Shilmy Hasan >>> Software Engineer | WSO2 >>> >>> E-mail :[email protected] >>> Phone :0779188653 >>> web : http://www.wso2.com >>> >>> [image: https://wso2.com/signature] <https://wso2.com/signature> >>> >> >> >> -- >> Thanks & Regards, >> >> *Fazlan Nazeem | *Associate Technical Lead | WSO2 Inc >> Mobile : +94772338839 | [email protected] >> >> >> > > -- > *Arshardh Ifthikar* > Senior Software Engineer | WSO2 Inc. > > Email: [email protected] > Mobile: +94777218551 > Web: http://wso2.com > > <http://wso2.com/signature> > -- *Vanjikumaran Sivajothy | Solution Engineer |WSO2 Inc. (m) +1 925 464 6816 | (e) vanji AT wso2.com <http://wso2.com>*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
