Re: [infinispan-dev] Log message categories
I don't think we have a lot of INFO map/reduce or dist exec, but perhaps
some DEBUG messages' level could be increased. Actually, that is also true
for state transfer and rebalancing messages...
I agree in principle with the idea, my only concern is that we'll spend too
much time managing which messages should be moved to these special
categories (and sometimes moved from DEBUG to INFO).
Cheers
Dan
On Tue, Aug 12, 2014 at 3:20 PM, Alan Field <afield(a)redhat.com> wrote:
I would also propose these categories for log messages:
org.infinispan.QUERY
org.infinispan.MAPREDUCE
org.infinispan.DISTEXEC
Thanks,
Alan
----- Original Message -----
> From: "Tristan Tarrant" <ttarrant(a)redhat.com>
> To: "infinispan -Dev List" <infinispan-dev(a)lists.jboss.org>
> Sent: Tuesday, August 12, 2014 10:35:34 AM
> Subject: [infinispan-dev] Log message categories
>
> Dear all,
>
> currently the Infinispan log messages "fall" in the categories named
> from the originating class. While this isfine for TRACE/DEBUG messages,
> there are some high-level INFO events which warrant their own specific
> categories. I think that user-triggered events (such as JMX ops) should
> also be treated like this.
> Examples:
>
> org.infinispan.CLUSTER (for important view change, state transfer and
> rebalancing messages)
> org.infinispan.CACHE (for cache lifecycle events)
> org.infinispan.PERSISTENCE
>
> What do you think ?
> Any other suggestions ?
>
> Tristan
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
Attachments:
- attachment.html (text/html — 2.8 KB)