I think this is a very good idea. There are some third party libraries that might be worth evaluating:
https://code.google.com/p/parfait/ http://jamonapi.sourceforge.net/ Paul On 26 September 2014 08:01, Sajith Ravindra <[email protected]> wrote: > > IMHO, CEP is another product where this kind of probes can be really > useful as we have to deal with performance related requirements. As there's > a major refactoring going on in siddhi I think we can we plant probes like > this into the Siddhi engine. It will be useful to evaluate the re-factored > Sindhi engines performance as well as to figure out performance bottlenecks > in the future. > > > Thanks > *,Sajith Ravindra* > Senior Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 77 2273550 > blog: http://sajithr.blogspot.com/ > <http://lk.linkedin.com/pub/shani-ranasinghe/34/111/ab> > > On Fri, Sep 26, 2014 at 8:38 AM, Srinath Perera <[email protected]> wrote: > >> We have some pretty nice probes already in ESB, that let you look into >> what is going in the same running in production. I think we need to do >> this generally and build it to other products. That should reduce time we >> spent debugging issues significantly. >> >> My proposal is to build a probe Lib that looks like following. >> >> There are two kinds of things you need to collect. >> >> 1. Throughput at give point of code (how fast calls goes though) >> 2. Latency between two points. >> >> >> We will have two types of Probes. Code would look like following. >> >> Probe probe = new Probe("Name", "throughput", timeDuration); >> .. >> probe.recordThroughput(); >> >> Probe probe = new Probe("Name", "latency", timeDuration, logLevel); >> ... >> long id = probe.startTicking() // this so same probe can be used by many >> threads >> ... >> probe.endTicking(id); >> >> Probe will summarise data over given duration and expose. We need >> >> >> 1. JMX bean >> 2. BAM Agent >> 3. Can turn on, off via JMX agent or via System property >> 4. Have Tool Box >> 5. Have in product UI >> 6. Can configured to write data to logs >> >> Each probe should be very small and should be able to create thousands >> without much effect. (e.g. create one for each mediator type) >> >> WDYT? >> >> --Srinath >> >> >> >> >> >> >> -- >> ============================ >> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera >> Site: http://people.apache.org/~hemapani/ >> Photos: http://www.flickr.com/photos/hemapani/ >> Phone: 0772360902 >> >> _______________________________________________ >> 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 > > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 blog: http://pzf.fremantle.org twitter.com/pzfreo [email protected] wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
