[infinispan-dev] Log message categories

[Alan Field]

Hey Dan, 

I know there aren't too many messages today, but I was thinking that status and statistics messages would be good to show. (Map/Reduce task ID ### has started the map phase, Map/Reduce task ID ### has completed the map phase + stats, etc., Query ID ### executed in x.xx secs) 

Thanks, 
Alan 

----- Original Message -----

> From: "Dan Berindei" <dan.berindei at gmail.com>
> To: "infinispan -Dev List" <infinispan-dev at lists.jboss.org>
> Sent: Tuesday, August 12, 2014 2:37:45 PM
> Subject: 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 at 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 at redhat.com >
> 
> > > To: "infinispan -Dev List" < infinispan-dev at 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 at lists.jboss.org
> 
> > > https://lists.jboss.org/mailman/listinfo/infinispan-dev
> 
> > >
> 
> > _______________________________________________
> 
> > infinispan-dev mailing list
> 
> > infinispan-dev at lists.jboss.org
> 
> > https://lists.jboss.org/mailman/listinfo/infinispan-dev
> 

> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20140812/c5bae827/attachment.html