Hi Rajani,
Thanks!! your feedback is very helpful for our project.
On Mon, Jul 7, 2014 at 9:59 AM, Rajani Karuturi
wrote:
> Hi Ashish,
>
> It does have timestamp, log level, thread name etc. though we do not
> use the level appropriately at some places.
> Here is a sample log line:
> 2014-0
Hi Ashish,
It does have timestamp, log level, thread name etc. though we do not use the
level appropriately at some places.
Here is a sample log line:
2014-07-04 09:00:19,456 WARN [o.a.c.f.j.AsyncJobExecutionContext]
(StatsCollector-3:ctx-0090dd87) Job is executed without a context, setup psud
Ashish,
It seems to me a discussion, albeit interesting to users, that should
take place on [email protected]. Would you agree?
regards,
Daan
On Sun, Jul 6, 2014 at 8:23 AM, Ashish Sureka wrote:
> We [Professor and PhD Student in Software Engineering at a State University
> in India] are working toward
We [Professor and PhD Student in Software Engineering at a State University
in India] are working towards a source code analysis tool which can assist
practitioners in writing effecting log statements. There are more than
1 log statements in CloudStack (s_logger.error, s_logger.warn,
s_logger.t
