And also tracing needs to be discouraged in production as it may log/reveal sensitive information, such as Phone Numbers, Account credentials, tokens, etc. The world is moving more towards privacy these days.
Cheers, Ruwan On Mon, Apr 2, 2018 at 5:37 AM, Gihan Anuruddha <[email protected]> wrote: > > > On Sun, Apr 1, 2018 at 9:46 PM, Lahiru Sandaruwan <[email protected]> > wrote: > >> Hi all, >> >> While I was looking at $subject, noticed that we can only enable >> statistics in production environment, not tracing. >> As Gihan mentioned at another place, tracing will generate a huge volume >> of data since it publishes payload for each mediator and performance will >> be affected as well. >> >> Couple of questions, >> >> Is it recommended to use tracing in trouble-shooting scenarios only? >> >> > Yes. Normally we encourage tracing for trouble shooting only scenarios. > But if you have lower TPS and an adequate storage then there is no harm to > use tracing in the production. This decision has to take by the end user > after doing a proper load testing with expected TPS in the production > environment. > >> >> >> >> Do we have a place listing the capabilities(what we can achieve) by >> enabling statistics and tracing separately? >> >> Thanks. >> >> -- >> -- >> >> Lahiru Sandaruwan >> WSO2 Inc., http://wso2.com >> >> lean.enterprise.middleware >> >> m: +1 901 530 2379 <+1%20901-530-2379> >> e: [email protected] b: https://medium.com/@lahirugmg >> in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >> >> > > > -- > W.G. Gihan Anuruddha > Associate Technical Lead | WSO2, Inc. > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
