LogMX is an intuitive and cross-platform tool, for developers and administrators reading log files.
Using a nice and powerful graphical interface, LogMX parses, displays and monitors any logs from any source.
LogMX will save you a lot of time and effort when analyzing logs:
No need to use several tools if you have several log formats from many sources. LogMX is not just reading log files, it parses log events from any file or data stream, in order to display a structured view of your logs. No need to install a web server or update your logs producers, LogMX is a standalone application weighing only about 5 MB (but does a lot for you!)
Using LogMX, you can quickly locate events in your logs, filter some events, monitor your logs in real-time, make time calculations, monitor a merged view of several interlaced logs, and many more... Once you have used LogMX, you will not want to read logs without it!
You will always be able to use LogMX no matter how the logs are formated or where they are:
LogMX uses a set of Parsers in order to read any log format. You can easily create new LogMX parsers to open your own log files, if they are not in a 'standard' format (LogMX comes with default parsers handling Log4j v1/v2, Java Logging, Logback, LogFactor5, Eclipse RCP, and Syslogs formats). LogMX auto-detects the Parser to use while the file is loading, you don't have to select a format to open a log file.
If LogMX does not find a suitable Parser for a file, it will show you the file content in plain-text.
LogMX uses a set of log Managers in order to access logs anywhere they are. LogMX comes with a local file manager and several remote-file managers (SCP/SFTP/FTP/FTPS/HTTP). Like for Parsers, you can create your own Managers to read your logs anywhere they are (Oracle DB, TCP, POP3, ...).
To create a new Manager, you will just have to write a single Java Class implementing some abstract methods (build scripts and development environment already included).
When 'AutoRefresh' mode is turned on, LogMX will display the log file content in real-time: you can now monitor your software by directly looking at its logs in real-time. This mode avoids several full file reloads to look at logs while written. A 'tail' option can also be activated in AutoRefresh mode to display only the last log entries (useful for saving RAM with huge files).
With just a click, you can hide or show log entries matching one or more conditions on any log entry field (emitter, log level, thread, ...). For example, you can display only log entries that are ERRORs or WARNINGs written by a thread containing 'oracle' in its name.
LogMX also provides a powerful Search feature: you can search a simple text or a regular expression in the scope of your choice (all file entries, only displayed entries, only selected entries) and in the entry field(s) of your choice (date, text, level, ...).
In order to work with very large log files (from 100MB to several gigabytes) LogMX can display, in real-time, only the end of the log file thanks to its AutoRefresh feature. If you want to completely load the file, LogMX gives you a graphical state of your memory usage (you can choose the maximum amount of memory LogMX is allowed to use).
LogMX can compute the time elapsed between two log entries and the time elapsed since an entry was generated. No more painful and inaccurate mental calculations! Used accuracy depends on log file format (will be in milli-seconds if the log format uses milli-seconds, very useful for your benchmarks!).
If your logs are produced by a distributed application (clustered environment) or if this application produces several log files, LogMX can open these files in a single merged view. You can then perform actions in a single file instead of processing all of them one by one. Two merge modes are available: entries sequentially appended, or entries interlaced to be sorted by date.
If you don't want to monitor your log files for long periods, you can define alerts that will be triggered when the event you described occurs (e.g. "level is WARNING or more critical", "emitter is 'my_emitter'", "message contains 'fail'", ...). You can choose action(s) to be performed when such events occur: play a sound, give the focus to LogMX window, execute a program, or send a mail. You can set a limit so that too many alerts are not processed, but all these triggered alerts are logged so that you can see which entry produced this event.
When you think your log file becomes too big, or when you want to re-start a logging session from scratch, you can empty it or delete it directly in LogMX (if you try to delete a file locked by another process, LogMX will tell you and ask you if you want to flush it instead)
LogMX can export any log file to a CSV, HTML, XML, or JSON file. You can also export only displayed, selected, marked, or found log entries, and choose which entry field(s) to export (very useful to export logs without dates in order to compare two log files).
This software is not reviewed yet.