I really like the idea!

Would it be possible to forward raw data (not aggregated) to the ELK stack [1]? 
This aspect might be important for production systems with centralized logging. 

[1] http://wildfly.org/news/2015/07/25/Wildfly-And-ELK/

On Fri, Nov 13, 2015 at 1:57 PM, Tristan Tarrant <ttarrant@redhat.com> wrote:
Hi guys,

in order to keep track of notable events (nodes joining, leaving,
rebalances, availability, task execution) and present them in the
console I was thinking of using specific logging categories. These logs
would be then collected by dedicated appenders on each node. The idea
would then be to have some distexec tasks exposed to the management
interface (console/CLI) which can query and aggregate the data.
Initially I was thinking about using a local cache per-node with a SFCS,
eviction, expiration and indexing and creating a log4j appender which
writes to this cache, but probably a simpler lucene-based appender would
suffice.

WDYT ?

Tristan
--
Tristan Tarrant
Infinispan Lead
JBoss, a division of Red Hat
_______________________________________________
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev