[Hawkular-dev] MiQ log/middleware.log

mike thompson mithomps at redhat.com
Wed Oct 12 22:36:01 EDT 2016


> On Oct 12, 2016, at 7:18 PM, mike thompson <mithomps at redhat.com> wrote:
> 
> So currently, we aren’t  really logging anything to this middleware.log (as far as I can tell). Should we be? What is our policy around using this log (versus evm.log)?
> This may be more important once we are in CFME and have to debug some customer issues.
> 
> Should all of our logging goto this log? Should some? If so what? 
> 
> Sorry, just a bit confused about the purpose of this log since it shows empty for me.

Seems to me we should be using it more. Since it much easier and relevant to look through this than the huge evm.log (which has also has worker thread traces every X seconds as well).

> 
> 
> — Mike
> 
> 
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161012/d0d3b902/attachment.html 


More information about the hawkular-dev mailing list