1 / 7

Visualizing JuxMem and DIET with Log4j: Enhancing Peer Interaction and Event Monitoring

This document presents ongoing research on visualizing JuxMem and DIET using Log4j as an event logging tool. It covers hierarchical logging mechanisms, various logging levels, and how JuxMem utilizes Log4j for generating logs specific to JXTA protocol events. Key components include setting up loggers, appender configurations, and developing a visualization tool (JuxMemView) to dynamically show peer interactions and system topology using OpenJGraph. The document discusses the integration of logging events, remote peer control, and future steps to enhance visualization capabilities.

macy
Télécharger la présentation

Visualizing JuxMem and DIET with Log4j: Enhancing Peer Interaction and Event Monitoring

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Visualizing DIET and JuxMem Mathieu Jan PARIS Research Group IRISA INRIA & ENS Cachan / Brittany Extension Rennes Lyon, July 2004

  2. Logging for Java: log4j • Rich and generic tool for logging events • Hierarchical loggers • Different levels: debug, info, warn, fatal, etc • How to use Log4j: • If (LOG.isDebugEnabled()) LOG.debug(“Ca va planter !!!!! :-)”); • Several appenders: • Text, XML, HTML files • Socket • Mail • Other bindings: C/C++, PHP, C#, etc

  3. Log4j in JuxMem • JuxMem uses Log4j • JXTA uses Log4j • Configured to generate a log.jxta and log.juxmem file on each peer • JDF collects log files • Configuration file: log4j.properties log4j.rootCategory=FATAL, jxta log4j.category.juxmem=DEBUG, juxmem log4j.category.net.jxta.impl.document=FATAL log4j.appender.jxta=org.apache.log4j.FileAppender log4j.appender.jxta.File=log.jxta log4j.appender.jxta.append=false log4j.appender.jxta.layout=org.apache.log4j.PatternLayout log4j.appender.jxta.layout.ConversionPattern=%d %p <-%l-> \n %m%n

  4. JuxMemView • Ongoing work from Chester Tse (MIT) • Based on OpenJGraph and log4j • Goal: • Dynamically visualize JuxMem peers • Get informations about each peer • Rlogin on the peer to modify its behavior • JDF and JXTA shells • Current status • Get Logging events from a file thanks to Log4j • Display the topology of JuxMem • After an execution

  5. Dynamic visualization using Log4j • Minor modifications • Appender: File -> Socket log4j.appender.jxta=org.apache.log4j.net.SocketAppender log4j.appender.jxta.remoteHost=131.254.202.77 log4j.appender.jxta.port=9700 • The same API is used • LoggingEvent • Sample files given to Chester Tse are made from a real execution

  6. Visualizing DIET and JuxMem • 2 different formats are used • Log4j • DIET • Common format? • DIET should be able to read log4j files? • Simple way: 2 different graphs • A SeD is a JuxMem client • Mapping can be done?

  7. Conclusion • JuxMemView • Display JuxMem topology • Launching peers via JDF • Remote control via JXTAshell • Based on log4j and OpenJGraph • Common visualization tool • Not a priority • Not clear how to do it • Ideas?

More Related