Discussions

News: XpoLog Center 2.8 Released – Root Cause Analysis for production

  1. Version 2.8 of XpoLog Center, an enterprise log management and technical support station that enables a Web view of log files, quick remote access for analysis and data collection capabilities, has been released. XpoLog Center helps to pinpoint specific text patterns in logged data through root cause analysis. Keeping the technical knowledge as filters and SQL statements creates a technical knowledge base. XpoLog Center enables a common language between players that can reduce maintenance and MTTR periods. New features of XpoLog Center 2.8 include:
    • Advanced reports on any log
    • Enhanced log viewer - tail, filter and merge several logs into one view
    • Transaction analysis and monitoring across log events
    • Cross system search with automatic events correlations
    • Log events trend analysis
    • Security enhancements to SSO and LDAP
    XpoLog's out of the box support includes:
    • IIS, Apache, BEA Weblogic, IBM WebSphere, Apache Tomcat, JBoss, Apache Netscape/iPlanet
    • Oracle types, Windows Event Log, MS Exchange, SQL server, FTP
    • Checkpoint FW-1
    • Cisco, Linksys
    • Syslog formats, Kiwi syslog, Linux logs
    • J2EE - LOG4J, JAVA Logging; C/C++ - LOG4C, .NET : LOG4NET
    • XML log files, Delimited, Text-based
    What are your thoughts on XpoLog and its system for log management?
  2. any usefull url?
  3. http://www.xpolog.com
  4. An interesting approach to monitoring IMHO. If I read correctly, this tool is based on parsing log files and extracting information from there. My own monitoring tool, MessAdmin, uses a different and complementary approach: keeping live data about J2EE applications, for real-time displaying. (For those of you curious about it, there is a live demo on the web site.) Should I put my own data in a log file for future analysis by XpoLog Center?
  5. I think it would be extremely strange to keep "live data" in a log file format. I also find it hard to associate "live" and "real-time" with log entries. Outputting any reasonable amount of session data every few seconds would surely add significant overhead for little value (only when issues arise). If a tool already has a comprehensive model than flatting that model into log entries just pushes more work both on the monitoring tool and the log file tool which then needs to be configured to perform event recognition and correlation. Log analysis tools as certainly a valid component (adapter) of an overall CEP or RCA solution. In a RAC model the two most important elements are Events (logs) and Conditions (state). Only one aspect is being addressed. When you have a rich and comprehensive JVM runtime model the difference is presentation and navigation is very apparent. MessAdmin: http://messadmin.sourceforge.net/ss_detail.html http://messadmin.sourceforge.net/ss_webapp.html JXInsight: http://blog.jinspired.com/?p=16 http://blog.jinspired.com/?p=17 Regards, William Louth JXInsight Product Architect CTO, JInspired "Java EE tuning, testing, tracing, and monitoring with JXInsight" http://www.jinspired.com
  6. I think it would be extremely strange to keep "live data" in a log file format. I also find it hard to associate "live" and "real-time" with log entries. Outputting any reasonable amount of session data every few seconds would surely add significant overhead for little value (only when issues arise). If a tool already has a comprehensive model than flatting that model into log entries just pushes more work both on the monitoring tool and the log file tool which then needs to be configured to perform event recognition and correlation.
    Agreed. I was more thinking of outputting significant events (a bit like the new ClickStream plugin, see the live demo) in a log file. While this won't make it for the soon-to-be-released 4.0, I will certainly add to possibility to output data to external storage (be it log files or a database) in the future.
    MessAdmin:
    http://messadmin.sourceforge.net/ss_detail.html
    http://messadmin.sourceforge.net/ss_webapp.html

    JXInsight:
    http://blog.jinspired.com/?p=16
    http://blog.jinspired.com/?p=17
    I know, I know... those screen shots are out of date... O:-) Please see the live demo for the current look and capabilities of MessAdmin. Cédrik ________ MessAdmin, J2EE administration made easy
  7. Hi, The situation is that most of the critical live IT data is in log files,maybe 2 millisecs after it was real time :-). Sure you can log critical events from monitoring system and add them to the log analysis. This will provide important information to the RCA process. Profiling product JVM, J2EE server on production is very expensive, there for using a non intrusive technology on the logs can boost performance of the J2EE server. while keeping vsibility into the cluster. Never the less, J2EE diagnostics tools are another important information source in the RCA process. BTW, due to regulatory issues, logging critical business events are obligatory for most financial, medical, telco and other industries.