[Adding IsuruP] Can't we use existing metrics feature for this?
Thanks *Dinesh J. Weerakkody* Software Engineer WSO2 Inc. lean | enterprise | middleware M : +94 727 868676 | E : [email protected] | W : www.wso2.com On Thu, Dec 17, 2015 at 2:18 PM, Nadeeshaan Gunasinghe <[email protected]> wrote: > Hi all, > > At the moment I am involved in implementing this feature. As the first > step I am going to capture the raw metrics related data which we need to > have in order to calculate the various latency values such as *Average > throughput, Average Latency, Average Jitter of the connections, etc. *All > the raw data captured, are going to transport via the carbon message and > then a latency calculation engine is going to be implemented for the > calculation purpose of various latency values. Then a data publisher > component is going to be implemented in order to publish data for JMX and > DAS. For further details please refer [1] > > [1] [Dev] Latency Calculation Feature in WSO2 GW > > Regards. > > *Nadeeshaan Gunasinghe* > Software Engineer, WSO2 Inc. http://wso2.com > +94770596754 | [email protected] | Skype: nadeeshaan.gunasinghe > <#151af2107f712583_> > <http://www.facebook.com/nadeeshaan.gunasinghe> > <http://lk.linkedin.com/in/nadeeshaan> <http://twitter.com/Nadeeshaan> > <http://nadeeshaan.blogspot.com/> > Get a signature like this: Click here! > <http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0=> > > On Wed, Dec 16, 2015 at 12:38 PM, Isuru Ranawaka <[email protected]> wrote: > >> Hi all , >> >> We can include feature for Latency measurement of GW requests and other >> relevant parameters related to connections. I have came up with a initial >> architecture diagram of the module as below >> >> >> >> >> - Each message going through GW should be able to store timestamps >> related to transport , message building, message formatting , mediation .. >> etc. >> - Finally after finishing the writing of response to the client >> those values need to be publish to the Data Receiver of the statistics >> component. >> - Data receiver needs to be Asynchronously collect the data without >> blocking GW threads. >> - Latency Calculation Engine should be configurable (such as per >> request updating or time based updating) >> - Scheduler is for notify the Engine to calculate latency values >> timely based. >> - There should be extension point to add event formatters in order to >> publish events in different formatters when needed. >> - As a default values are published through JMX via m beans. >> >> >> thanks >> >> IsuruR >> -- >> Best Regards >> Isuru Ranawaka >> M: +94714629880 >> Blog : http://isurur.blogspot.com/ >> > > > _______________________________________________ > 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
