Subscribe for new updates? Subscribe

loGrobot / logXray

What is LoGrobot? LoGrobot (alternatively known as logXray) is an advanced Log File Monitoring tool developed for use on UNIX systems. It allows UNIX users to painlessly and reliably monitor log files on an unlimited number of hosts without having to read a ton of documentation or learn new programming languages. It is equipped with a massive arsenal of robust, versatile features capable of handling any log monitoring task given to it, no matter how complicated or customized it is. In other words, LoGrobot is a labor saving plug n play tool that automates and simplifies log monitoring. If you're a UNIX professional who works on UNIX systems, you will find this tool extremely useful!

What is the Ideal Log File Monitor?

When searching for the right utility to use to monitor and alert on log files, what features should the perfect tool have?

At the very least, the ideal log monitoring tool should be able to:

  • Monitor a directory of log files / Detect abnormal patterns in monitored logs
  • Recognize system or network abuse (through mathematical analysis of data)
  • Detect vulnerability scans (e.g. port scans) through the use of user-specified patterns
  • Detect intruders or attempted intrusions (through the use of user-specified patterns)
  • Detect resource shortages (e.g. slow response times, out-of-memory conditions etc)
  • Detect imminent application / system failures (scan several log files as needed)
  • Scan, monitor and alert on log files of any format (this is absolutely crucial)
Check features Purchase

Monitor All Logs Regardless of Format

With LoGrobot, you can monitor the log files of any application, database or system. As long as the logs you wish to monitor reside on UNIX systems or an NFS drive for windows logs, they can be monitored!

Tomcat Catalina.out log monitor

Check timestamps, scan logs for specific errors

Apache Maxclient log monitor

Monitor log files and alert on maxclient entries

Apache Access Logs

Pull out as much information as you wish from access logs

Apache Error Log

Monitored for user-defined errors / entries

OutOfMemory Log Monitor

Watch for OutOfMemory errors / exceptions

JBoss Log Monitor

Scan logs for errors indicating serious application issues

Java Log Monitor

Monitor multiple log files for any specific pattern(s)

Weblogic Log Monitor

Monitor for specific entries

Glassfish logs

Monitor logs and alert when certain entries are found...or not found

Maillog / Postfix logs

Watch for abnormalities that may impeding mailing


Monitor any database log file for any type of error

Messages logs

Scan the messages log file for known or unfamiliar fatal entries

Syslog logs

Scan for entries indicating serious application or system issues

Custom log files

If you have logs that need to be monitored in a very specific way, email us to request personalized modifications - FREE with purchase of LoGrobot

Are my logs supported?

All conceivable log files are supported. LoGrobot is versatile.


Tail log files intelligently via time frames if the logs are date and time formatted. For example, be able to pull out log entries from 5 minutes, 10 minutes, 1 hour ago till now. Avoid grabbing random number of lines.

Log File Monitoring - Alerts & Graphs

Automatically graph several log file metrics...without any extra configuration on your part!

New Log Entries

2-day Range - Aggregate of 4 different log files on 4 different hosts. This graph shows the frequency with which each log is being written to.


Log Size Monitor

2-day Range - Log Size - Trends the size of log files. Allows users to keep an eye on log rotation to ensure logs are being rolled over at the expected size and time.


Application Log Errors

2-day Range - Application Log Monitoring - Monitors applications with multiple log files - Graphs the number of user-specified errors detected in monitored logs.


Log File Growth Monitor

Monitors the size of a specific log file. Alerts if log file size remains the same as it was during the last scan. This log check can also be configured to alert if growth is beneath provided thresholds.


Single Pattern Log Monitor

Monitors a log file for a specific string. When that string is found, show the exact lines from the log file that contain the offending pattern!


Multiple Pattern Log Monitor

Uses one check to monitor several strings within a specific log file - Helps users avoid creating separate checks for each string...unless necessary!


Cool features


Monitor all types of UNIX log files without having to learn any programming languages or be a master of regexes!


Automatically convert all measurable log file metrics into simple and easy to read graphs / charts!


Utilize graphs and notification alerts to accurately identify abnormal events before they get out of hand!


Generate quick reports on past notification alerts on all monitored log files - avoid having to dig through archives!

Simplicity via Graphs

Aggregate graphs of multiple log files from several different hosts and/or servers into single graph(s) - See the logging activities of applications, dbs, servers all in one place. Beautify your log file activities - Visually inspect graphs / charts of all monitored logs - Easily identify Rises & Drops in the frequency of entries!

Detailed Alert Notifications

See detailed information on the log file being monitored i.e. log size, total number of entries in log, latest count of new error patterns, rate at which log file is being updated, percentage of error patterns in relation to total new entries, the scheduling consistency at which log check is running (helps identify when system is under heavy load!)

Multiple Patterns in one Log

With just one log check, monitor multiple patterns, strings or keywords - When an alert is generated, see the offending string(s)/pattern(s) that triggered it!

Simple. Intuitive. Powerful.

Get notifications when:

  • specific strings, patterns or keywords are dumped into your log files
  • expected patterns of strings ARE NOT found within specific log files
  • unfamiliar lines are introduced into your system and/or application logs
  • critical log files stop receiving updates after a user-specified period of time
  • a log file is moved, deleted or no longer exist where it should
  • a log file lacks the proper / expected permissions...i.e. read access
  • monitored log files begin to consume too much disk space (unusual growth spurts)
  • the size of a specific type of file in a specific directory breaches set thresholds
  • size/growth of a log goes above user-specified thresholds (warning/critical)
  • the number of specific files in a specific directory exceeds user specified thresholds
Get started today

A log file on 6 different servers is being graphed for 500 related errors. Each server in the above and below graphs is tagged with a different color for easy identification

More Features & Benefits

Versatile. Robust. Seasoned.

More reasons to download LoGrobot:

  • A proven log monitor that is maintained regularly & heavily used in Production
  • Adapts seamlessly to any custom scenario - Usable as a plugin, service or both
  • Avoid writing several scripts of your own, or downloading amateur scripts off the net
  • Monitor dynamic log files efficiently (log files with changing names / dates)
  • Get log check notifications based on values in certain columns of specific log entries
  • Intuitive log monitoring - Eliminate the need to maintain several configuration files
  • A log monitoring solution that does not require installation of nonnative modules
  • Our support team is available to accommodate your custom requirements
  • Automatically monitor rotated logs - Never miss a critical log entry!
  • Monitor multiple log files without any complex time consuming configurations
  • Access documentation (straight-forward real life examples) directly from the CLI
  • Avoid reading pages of documentation or having to train staff on new tools
Download it now!

1. Trend how frequently a particular application log(s), spread across multiple hosts, is being updated (1st/2nd graphs)

2. Monitor the rotation of logs (graph below):

3. Graph the frequency of specific error patterns:


Choose the plan that is the most convenient for you.

Get updates on our newest features?

Provide your name (or company name) and Email Address below.


San Francisco, CA, USA

What else can LoGrobot do?

Contact Us. We'd love to tell you!