Check a Directory of Logs

OutOfMemory Log Check

Graph Logs with Cacti

Graph Logs with Cacti

Check & Alert on Log Inactivity

Checking Directory File Count

Ensure Growth of Log File

Monitor Logs w/ LoGRobot

( Linux (all flavors), HP-UX, AIX, SunOS )

ADVANCED, DETAILED LOG MONITORING & ALERTING FOR UNIX SYSTEMS. Works on all log files regardless of Log Type, Log Format or Log Size - Designed to handle all log monitoring Requirements - No matter how complex!

Get Detailed Information on All Monitored logs with logXray

Scan, Alert, Report, Analyze, Graph - Monitor logs Efficiently!


Functionality / Specialty:

Simplifies All Log Monitoring Tasks, Specializes mainly on the Monitoring of UNIX Log Files; Alerts directly off User-Specified Conditions and/or Automatically Identified Anomalies - Requires NO changes to your systems; Has NO Library/Module dependencies!


Log File Pattern Exclusions

Search via time-Frames

Watch for Expected Entries

Database Log File Check

Check Log Time Stamp

Advanced Stats on Logs

Alert on Log Time Stamp

Scanning & Monitoring Unix / Linux Log Files ; Monitor Logs, Analyze - Check Application Logs, Database Logs, System Logs, Custom Logs...Any Log file - Create Excel Reports on Past Log Alerts:  No matter the complexity of your log monitoring requirement(s), LogRobot can be trusted to handle it with convenient ease.  Each one of the NAGIOS screenshots on this page show the different ways LogRobot can be used to monitor log files quickly and easily on hundreds and even thousands of hosts.  If you do not have NAGIOS installed in your UNIX environment, please do not panic. NAGIOS can be automatically installed for you (if you want it to be) OR you can schedule LogRobot to run either as a Standalone or with other Monitoring Applications.  Alert notifications on all configured log checks can be sent in whichever fashion fits your needs (emails, traps, etc).

State of Monitored Log

Log Entr(ies) Not Found

Show Errors Found in Log

Monitor Large Log Files

Monitor Dynamic Log Files

Alert when Log Not found

Alert on Log Time Stamp

Monitor Different Patterns in One Log

Monitor Multiple Patterns in Multiple Logs

Monitor, Graph, Report, Analyze & Alert On All Log Files On Any UNIX Host:

Java, HTTP, Apache, Tomcat;catalina.out, Splunk, Mysql, Oracle, Postfix, Log4j, Mail, Weblogic, Glassfish, System Logs,

What We Do:  LogRobot / logXray provides Reliable, Efficient and Convenient ways of monitoring logs (with or without Nagios) on UNIX Systems. It ensures Prompt and Accurate notifications on all active log checks and grants users the ability to generate professional excel spreadsheets / reports on past log related events. Additionally, logrobot (alternatively known as logXray) can be configured to fire off notifications whenever anomalies are detected in monitored logs and automatically generates graphs for every measurable log related metric which in turn allows users to view historical behavior of volume of entries being logged to a file, the frequency of error patterns being logged and much more!

Cacti Screenshots:  Graph the occurrence or lack of occurrence of specific keywords, strings or patterns - Trend log file characteristics to determine and isolate abnormal behavior in the frequency of entries logged


To graph log files, you can use LogRobot with either Cacti or Graphite.  In the above Cacti graphs, LogRobot is used to scan a unique log on 4 different hosts at 5 minute intervals.  The particular log being scanned is an application log which is being written to several hundred times a minute. LogRobot scrapes the application log every 5 minutes and pulls out all entries written to it within that time frame.  From the 5 minute worth of data retrieved after scanning, LogRobot graphs the number of new entries it finds that contain the user-specified strings "hostname.*SUCCESS" or "hostname.*FAILURE" ("hostname" = name of a server) NOTE:  If using Graphite, graphs for new log files are automatically generated and updated without any time consuming configuration.  Also, logs can be polled and graphed as frequently as you desire.

LogXray is a UNIX Fully Featured (upgraded version of LoGrobot) Used Specifically for:

Analyzing, Dissecting, Reporting, Monitoring and Performing Alert Notifications on log files.

LogXray provides detailed information about the log files it monitors:

During each scan of a log file, LogXray provides details on:

  • If the log file being monitored exists and is readable by the user LogXray is running under

    • If it isn't, an alert notification will be generated describing the issue

  • NEW instance(s) of the user-specified list of error patterns found in the most recent scan

  • Total number of NEW entries added to the log file since the last time a check was ran on it

  • Scan time (time range) within which the latest status of a log file check is based upon

  • The most recent size of the monitored log file during each check

  • Performance Data on the log file and each pattern being monitored in the log

  • Statistical reporting on log file behavior - Helps detect abnormal data trends

LogXray does not require any dependencies or libraries in order to function:

Whenever LogXray is introduced to a new UNIX system, here's what happens:

  • A new directory will be auto created on the host based on information provided by the user

  • The ownership of the new directory will be assigned to whichever user LogXray is first run as

    • Ownership is configurable and can be changed to that of any user

  • After the new directory is created, LogXray will run a scan on the log file given to it

  • A "NEW CHECK" alert is displayed so a record exists of when that log check was put in place

  • Subsequent checks on that log file from this point on will be to watch for legitimate issues.

LogXray combines file and directory monitoring features into one tool:

In addition to monitoring logs for error patterns, it can also be used to:

  • Monitor a directory of logs

    • Specify types of files in a directory to include in or exclude from monitoring

    • Specify different thresholds to each file type

    • Get performance data (graphs) on each log being monitored.

  • Monitor the size of specific types of files in a user specified directory

  • Monitor file timestamp (alert if file's last update-time is older than X number of minutes)

  • Monitor the size of a file (alert if file size exceeds X MB or GB)

  • Detect deviations in log growth rate, update times and content - Upgraded Feature!

    • Highly effective in helping to determine the right thresholds - Removes human factor

    • Identifies issues mathematically and can act as predictive application monitoring


  • Uses unique algorithms to ensure the size of a log file is irrelevant

    • Log size does not affect the speed with which a log check completes!

    • Monitors files that are several gigabytes in size without imposing heavy system load

  • Allows users to specify string-file(s) when listing lengthy error patterns

  • Alerts if expected records of events are missing from monitored log files

    • Watches for those entries and IF NOT found, alert notifications are generated.



  Monitor Specific Log Files in A Specific Directory for New Occurrences of Specific Strings 

Case Scenario:

  1. Monitor all log files in the /var/log directory that have the word 'messages' in their names.  Check each log found matching this criteria for new entries containing the string 'ERROR'. 

  2. If the number of entries found in any 'messages' file in the directory is less than 5, exit with an OK status.  If above 5 but less than 10, alert as Warning.  If above or equal to 10, alert as Critical.



root@logxray-01 #  ./logxray  localhost  /var/tmp/logXray  autoblz  /var/log,include:messages  30m  'ERROR'   '.'  5  10  log_mon_3  -ndfoundn



Monitor log files for user-specified entries, then EXCLUDE specific lines from the results  

Case Scenario:

  1. Within the last 30 minutes, find out how many lines in the log file [ /var/log/app.log ] contained both entries of "ERROR" and "Client". If any lines are found containing these two strings (ERROR.*Client), take note of that.

  2. From the list of lines found, see if there are any lines that also contain the keywords "error 404" OR "updateNumber".  If there are, remove them from the list.  After removing them, show me what is left.  If the number of lines left is between 5 and 9, alert as WARNING.  If equal to or over 10, alert as CRITICAL.  If below 5, do not alert!



root@logxray-01 #  ./logxray  localhost  /var/tmp/logXray  autonda  /var/log/app.log  30  ‘ERROR.*Client’  '(error 404|updateNumber)'  5  10  applog_tag  -ndshowexcl



  Monitor log files for certain entries - ALERT IF those entries are NOT found!  

Case Scenario:

For instance, within the last 30 minutes, if logrobot does not find at least 2 lines containing the words "Success" and "Client"  and "returned 200" OR "update:OK" in the log file, it must alert.  So in other words, the lines to search for MUST contain both words of Success & Client (Success.*Client) AND one or both of the strings returned 200 and update:OK.



root@logxray-01 #  ./logxray  localhost  /var/tmp/logXray   autonda   /var/log/app.log  30  ‘SUCCESS.*Client’  '(returned 200|update:OK)'  2  2  expected_entry_tag  -ndnotfoundn



Monitor Log files for specific entries - When found, display all offending lines in alert  


This is particularly helpful in cases where you might want to see the actual lines that contain the patterns you instructed the tool to search for.




root@logxray-01 #  ./logxray  localhost  /var/tmp/logXray  autonda  /var/log/app.log  30  ‘ERROR.*Client’  '(returned 200|update:OK)'  5  10 error_exceptions  -ndshow



  Scan log files for minutes, hours, days, weeks or months worth of data  


For instance, to pull out 2 weeks of information from within a large log file and identify many lines contain certain patterns, you can run a command similar to this:




root@logxray-01 #  ./logxray  localhost  /var/tmp/logXray  autofig  /var/log/app.log  2w  ‘ERROR|panic|fail’  ‘ERROR|error|panic|fail’  5  10  -show


Notice the [ 2w ].  And also, notice the strings being searched for.  The pattern ‘ERROR|error|panic|fail’ is repeated twice because there is no need to specify filters. 


You actually don't have to repeat the first string.  You can just enter a dot in its place..i.e:


root@logxray-01 #  ./logxray  localhost  /var/tmp/logXray  autofig  /var/log/app.log  2w  ‘ERROR|panic|fail’   ‘.’   5  10  -foundn


From this specific example, logrobot is being instructed to grab every single line it finds containing either of the 3 strings 'ERROR' or 'panic' or 'fail'.


See below for the different ways of specifying date range:

5m = 5 minutes (changeable to any number of minutes)

10h = 10 hours (changeable to any number of hours)

2d = 2 days (changeable to any number of days)

2w = 2 weeks (changeable to any number of weeks)

3mo = 3 months (changeable to any number of months)


Monitor log file for specific patterns, use user-specified strings to filter out lines to alert on:  




  • ./logxray   localhost   /var/tmp/logXray   autonda   /var/log/syslog   60m   'kernel|panic'   'abrt'   3   5   syslog_check   -ndshow


  1. Monitor the /var/log/syslog file

  2. Scan the log for any line containing "kernel" or "panic".

  3. When the above lines are found, from those lines select only the lines that also contain the pattern/keyword "abrt"

    • Ignore all lines which do not have 'abrt' on them

  4. If the number of lines found is less than 3, exit with an OK

  5. If the number of lines found is greater than or equal to 3, and less than 5, exit with a WARNING

  6. If the number of lines found is greater than or equal to 5, exit with a CRITICAL

  7. The name of this log check is syslog_check

  8. From the list of lines found containing 'kernel' or 'panic', exclude/ignore lines that have the string 'abrt' in them

    1. Indicated with the -ndshow

  9. While trying to scan this log file, if it is detected that the timestamp of the log itself is older than 60 minutes, abort immediately



 Specifying Pattern Exclusions in LogChecks

Suppose you inherit a UNIX environment at a new job and you're unfamiliar with exactly what to look for within the logs of a particular application, here's an idea; instead of worrying about what to watch for, why not force the logs to reveal their hidden contents?


In the example below, logrobot is instructed to search the entire messages file (denoted with the '.').  Then, it is to ignore every line that contains any one of these specific strings: 'nagios-primary nagios' OR 'not responding' OR 'synchronized to'.  Whichever lines are left after these THREE patterns are ignored should be alerted on.


The logic here is; if you can identify which entries in the logs are of NO importance to you, you can exclude them from being monitored.  And, if a log file is stripped of the familiar and unwanted, whatever is left will be unfamiliar, thus requiring investigation.
[root@nagios-primary]# ./logxray  localhost  /var/tmp/logXray  autonda /var/log/messages 24h
'.' 'nagios-primary nagios|not responding|synchronized to'  1  5  syslog_check  -ndshowexcl



root@logxray-01 #  ./logxray localhost /var/tmp/logXray autonda /var/log/messages 24h '.' 'nagios-primary nagios|not responding|synchronized to' 1 5 syslog_check -ndshowexcl


Jun 13 13:40:04 nagios-primary abrt[8269]: saved core dump of pid 8128 (/prod/nagios-core/sbin/status.cgi)
Jun 13 13:40:04 nagios-primary abrtd: Directory 'ccpp-2012-06-13-13:40:04-8128' creation detected
Jun 13 13:40:04 nagios-primary abrtd: Executable '/prod/nagios-core/sbin/status.cgi' doesn't belong to any
Jun 13 13:40:04 nagios-primary abrtd: Corrupted or bad dump /var/spool/abrt/ccpp-2012-06-13-13:40:04
Jun 14 02:20:41 nagios-primary auditd[5813]: Audit daemon rotating log files



Professional Consultation for the Monitoring of Log Files


Professional consultation (or outsourcing) is NOT necessary in most cases.  This is because both the installation of logrobot/logxray and its day to day usage are easy to understand.  You DO NOT have to be an experienced UNIX user to get this log monitoring tool up and running.  We've already done all the hard work to make sure of that.  You only need to follow the basic instructions provided.  The few commands you will need to run are simplistic in nature and do not require any technical sophistication. 

This means, unlike other tools, there isn't a lengthy complicated manual for you to read up on. There are no classes for you to force your employees to take.  All the complex steps you would have had to carry out yourself have already been programmed into the logrobot tool.  All you have to do is run it.

While professional consultation may not be necessary in most cases, there is a variety of reasons some may still wish to delegate the task of monitoring logs to an outside entity.  Whatever the reasons may be, if you need help configuring log checks on any of your UNIX hosts, the logrobot support team will handle it for you.  We are specialized in this particular area and have in our arsenal an enormous collection of automated tools built specifically to execute, on a large scale, a wide range of tasks. 

If this option is of interest to you, Contact Us.

Back to Top


Quick References to some of LoGrobot's most popular functions

  1. Exclusions - Specify a List of Patterns to Exclude via Filtering

  2. Monitor Log Files for Expected Record of Events - Alert If Not Found!

  3. Detailed Alerting - Show Offending Entries from Monitored Log Files

  4. Less Detailed Alerting - Do NOT show the Offending entries in alerts

  5. Check Dynamic Logs - Take into account Log Rotation and monitor accordingly

  6. Timeframe - Pull out information from logs using user specified Time Frame

  7. Apache Log File Analysis (Nagios) - Alert / Report / Graph Apache Access logs

  8. Use one check to monitor multiple strings within a log file - Set thresholds per string

  1. Monitor Directory of Log Files - Avoid Specifying Each log file separately

  2. Setup Log Checks for Directory File Count - Monitor the number of files in a directory

  3. Automatically Generate Graphs for all Log File Monitors Configured via Nagios

  4. Check Log Time Stamps - Set up Monitoring Checks to Alert when logs stop updating

  5. Check Log File Size - Monitor the disk space consumption of specific files

  6. Automatically Install Nagios on Red Hat, CentOS, Ubuntu Hosts (avoid manual installs!)

  7. Log Analysis - Alert when a deviation is identified in overall behavior of a log file

  8. Automatically Generate Color-Coded Excel Reports on Log Alert History

Simplified Log Monitoring:  Monitor Logs of Any Application or Database regardless of Format or Size, Generate Quick & Easy Reports on Past Log Check Alerts, See Offending log entries in all dispatched Alert Notifications

Who needs logrobot?


Download logrobot if you wish to:

  • Monitor unlimited logs from various Application / Database servers - Alert on specific errors

  • Implement a log monitoring solution that does not require the installation of nonnative modules

  • Monitor & Alert on any log file regardless of size, date and/or time format

  • Monitor multiple log files without any complex time consuming configurations

  • Obtain an automated tool that is configured and ready to go right out of the box

  • Use Nagios or Icinga or Crontab/Emails to Manage the Monitoring of All UNIX Logs

  • Automatically generate Nagios log check configs for several log files on multiple hosts

  • Outsource Log Monitoring or do it yourself with FREE support from our 24/7 Customer Service!

    • Have a technical support team on standby to accommodate all custom requirements

  • Generate automatic color-coded Excel Reports on the alert history of all log checks

  • Avoid writing several scripts of your own, or downloading amateur scripts off the net

  • Utilize a reliable log monitor that is maintained regularly & used heavily in production environments

  • Analyze Logs: Get Notified when unfamiliar lines are introduced into system / application logs

  • Get alerts when critical log files stop getting written to after a specified period of time

  • Utilize an efficient log monitoring tool that eliminates the need to maintain several configuration files

  • Scan logs for specific entries and exclude a list of user specified patterns from the result

  • Allows for monitoring of all log files, even Windows files (mounted through NFS on a UNIX server)

  • Inform through each alert how long ago a particular string / pattern / keyword was last found in a monitored log

  • Remote Agent Included to enable monitoring of logs on several hosts FROM ONE master

    • This is for users who don't currently have NRPE installed in their environment

      • Allows complete control of log checks on all remote hosts / servers

  • Automatically figures out conditions on which to recover alerts, based on log content & other variables

  • Automatically detects log file type and format without user intervention

  • Get notified via email of all events related to your log of choice on any server(s) you specify

  • Updated regularly to meet new demands from various clients / companies

See Complete list of Features


Graphing Log Files:



Example 1:

Using Cacti, a log file on 6 different servers is being graphed for 500 related errors

Each server below is tagged with a different color for easy identification:


Example 2:

Using Cacti, a log file on 8 different servers is being graphed for 500 related errors

Each server below is tagged with a different color for easy identification:


Download Now

More information on Log File Monitoring using LoGrobot / LoGXray

  1. Monitoring logs - Performing reporting and analysis of log information

  2. Emails Alerts & Notifications - Monitor logs - Receive email alerts on every issue

  3. Different Scenarios for log monitoring - Use logrobot / logxray anyway to monitor logs

  4. NRPE - Monitor logs using the very common nagios NRPE monitoring agent

  1. Custom Monitoring Agent - Monitor logs with our unique Perl monitoring agent

  2. All about log monitoring - Understand the science of Monitoring UNIX log files

  3. Log Monitoring Options - Use any one of our monitoring features to alert on logs

  4. Log monitoring made tremendously easy - What makes logrobot / logxray unique!


Frequently Asked Questions


  1. What exactly can I do with LoGrobot?

  2. Is it safe and easy to install LoGrobot / logXray?

  3. How many lines of Code is LoGrobot made of?

  4. How Big is the LoGrobot tool?

  5. Does LoGrobot run locally on each host?

  6. Is LoGrobot completely separate from the front end?

  7. How long does it take for LoGrobot to execute on a host?

  8. With what frequency does it run?

  9. What happens if the log file is several GIGABYTES in size?

  10. What do I do if search strings won't fit on the command line?

  11. Can LoGrobot handle log rotation?

  12. Is it easy to setup log checks for log files using LoGrobot?

  13. Can LoGrobot monitor log files that don't have dates?

  14. After downloading LoGrobot will you help me if I need any help?

  15. Do I have to use LoGrobot with any specific monitoring app?

  1. Can you provide help with the automated install of Nagios or Cacti

  2. What exactly is the NagiosLogMonitor?

  3. How much is LoGrobot?

  4. Are there any situations LoGrobot will not be able to handle?

  5. Is there a Money Back Guarantee?

  6. Can I submit requests to add custom / personalized features?

  7. What must I do to monitor log files on ALL my UNIX servers?

  8. Can I generate Excel Reports on the history of log alerts received?

  9. Can I scan for multiple strings in a log file at the same time?

  10. Is Nagios and/or Cacti free to use?

  11. What makes LoGrobot Superior to other Log Monitoring tools?

  12. What is logXray?

  13. How fast is logXray?

  14. What options do I have to purchase LoGrobot / logXray?

  15. Additional Benefits of Monthly / Yearly Subscriptions!



What exactly can I do with LoGrobot?

You can do absolutely everything as long as the tasks you have in mind are related to monitoring of logs.

In other words, if you can think up a log monitoring necessity, LoGrobot can and will accommodate it.

Back to Top



Is it Safe and easy to install LoGrobot / logXray?


With logrobot, there's very little you have to do.  We are very proud to announce that, unlike other tools, LoGrobot does not require users to install packages, libraries or modules that are unnatural to the UNIX system in order to get it work.  It just works!

Just drop it in the same directory as the rest of your plugins.  Define nagios configurations for it (commands.cfg, services.cfg), set it up to begin monitoring your log of choice, and that's really all there is to it.  When Nagios or Crontab goes to run your checks, logXray will automatically install itself in the default directory you specified and will from that point on begin to monitor any log file (or directory) you tell it to watch. 

Click here to see a demonstration!


Back to Top



How many lines of Code is LoGrobot composed of?

The lines of code that make up LoGrobot is about 200,000+.  Does it affect the efficiency with which it completes checks?  Absolutely not!

Back to Top



How Big is the LoGrobot tool?

The current size of the log tool is a little over 12MB.  This isn't a utility that was slapped together over the span of just a couple of hours, days or even weeks.  This is a well maintained, high-performance tool that has been in development for several years.

Back to Top



Does LoGrobot run locally on each host on which logs are being checked?

Yes, it runs locally on each host but can be easily controlled entirely from the monitoring master server.

If using LoGrobot to monitor your logs, simply place the tool on the host(s) on which you have log files to monitor

Back to Top



Is LoGrobot completely separate from the management front end (but can be controlled by it)?

Yes.  Originally, the LoGrobot log monitoring utility was built to work with Nagios. However, over the years, and due to varying customer needs, we have added functionalities that allows it to fully function without Nagios. 

If you need LoGrobot to operate in a very specific fashion, let us know.

Back to Top



How long does it take for LoGrobot to execute a log file check on a host? With what frequency does it run?

0.3 - 1.8 seconds.  It can be scheduled to run at any interval.



Back to Top



Can LoGrobot monitor log files that are over 1 GIGABYTE in size?

Yes. The size of a log file doesn't matter.  LoGrobot scans most log files from the previous point it left off.  If the log file is rotated, it will scan the unread entries from the rotated log, then continue scanning the new live log, thereby ensuring entries aren't missed.

Back to Top



Can I use LoGrobot to monitor a huge list of strings which won't fit on the command line?

Yes. If your list of strings is too long or too many to fit nicely on the command line, you can instruct LoGrobot to use configuration files instead.  All you need to put in the config file(s) is the list of strings (one string per line) you want to monitor.  Nothing more.

Back to Top



Can LoGrobot handle log rotation?:

Yes. LoGrobot automatically watches for signs of log rotation and proceeds to monitor the recently rotated log when it is detected, in addition to monitoring the fresh log.

Back to Top



How easy is it to setup log file checks / log file monitoring for log files using LoGrobot?

It is very easy to setup log file checks through LoGrobot.  The LoGrobot tool is designed to handle by itself all the several little steps other tools would have had you do on your own...i.e. compilations, editing a bazillion files, searching for ReadMe text files, having to read those text files, troubleshooting issues...etc.

You can literally start monitoring your logs within seconds of purchasing, downloading and unzipping the tool.  Yes, it really is as simple as it sounds!

Back to Top



Some of my Log files do not have a date format.  Can LoGrobot monitor these types of logs?

Yes! Just pass the “autonda” option to LoGrobot, instead of autofig.  "autonda" is a newer, far more powerful feature with an entirely different set of capabilities.


Back to Top



After downloading LoGrobot / logXray will you assist me if I need any help?

Absolutely!  Support is already included in the purchase we recommend taking advantage of it.

Back to Top



Do I Have to use LoGrobot with Nagios or Cacti or any specific monitoring application?

Absolutely not.  LoGrobot does not rely on any other application to function.  However, if you wish to have a web interface from which to view & manage all configured log checks, Nagios is the way to go.

Nagios will allow you to manage the complete monitoring of all local and remote log files from one server, using one web interface.  Also, if you would like to generate Microsoft Excel Reports from the history of alerts received on all monitored log files on a list of hosts, this is possible, if using Nagios or Cron.

Graphing:  To graph log files, you will need to install Cacti, Graphite or a similar application.  LoGrobot can help with the automated install of Cacti.  Just run "kinglazy".

Back to Top



If I want to install Nagios Or Cacti, will you provide help with the installation?

Absolutely! We have an automated utility (kinglazy) in our arsenal that will install both applications for you.  This will relieve you of the tedious responsibility of having to labor over complex configuration procedures.


Back to Top



What exactly is the NagiosLogMonitor (nlm) tool?

NagiosLogMonitor (nlm) is the plugin that interprets the output produced by LoGrobot.  Please note, you do not have to have Nagios installed in order to use it.  You can run it through CRONTAB as well.

UPDATE:  In the latest version of LoGrobot (logXray), NagiosLogMonitor has been decommissioned.  logXray is built with its own interpreter which renders the old NagiosLogMonitor unnecessary.

In other words, the previous versions of LoGrobot basically needed an additional script (NagiosLogMonitor) to interpret the responses received from the actual LoGrobot tool.  Overtime we realized that this additional script is a bit of a nuisance.  We didn't want to have our users worrying about installing both scripts.  So we addressed our concerns by combining the NagiosLogMonitor into logXray.  That way, all log monitoring tasks imaginable can now be handled by only ONE tool.

Back to Top



How much is LoGrobot?

Please see the table at the bottom of the home page for a list of available options.

Back to Top



Are there any log monitoring situations LoGrobot will not be able to handle?

No.  LoGrobot / logXray has years of real life situations built into it. It has been heavily tested in QA, DEV, PrePROD and PROD environments. The tool as it is, is more than enough to handle any situation you throw at it.

If you happen upon a unique situation that isn't already accounted for, however remote the possibility of that may be, just let us know.  Our support team will make sure LoGrobot is customized & upgraded specifically for you, at no additional cost.

Back to Top



Is there a Money Back Guarantee?

Yes.  There is a 60 Day Money Back Guarantee.  If you're not satisfied for any reason with the LoGrobot tool, by all means, please let us know.

We have never had to issue a refund, but we will if asked.  We stand proudly by our product and the time-saving/labor-eliminating services it delivers.

Back to Top



After downloading LoGrobot, can I submit requests to add custom / personalized features?

Absolutely.  We usually complete custom requests within 24 to 72 hours of submission. 

If your request isn't of an urgent nature, please state so in your email. 

NON-Urgent email requests will be completed within 5 business days.  Contact us for more information.

Back to Top



I want to monitor log files on ALL my UNIX servers  - What must I do?

Here are the Simple steps you need to take for that to happen:

Place LoGrobot on all your UNIX machines.  Installation is very simple:

  • Copy the file to each one of the hosts that you have log files on.

  • Unzip the file, then run the installation command.

Basically, here’s all you have to do on each of your UNIX Hosts / Servers:

  1. unzip ; cd LoGrobot

  2.     /apps/magent     5666     master

Explanation of the parameters:

  • /apps/magent is where LoGrobot will be installed.

  • 5666 is the TCP port number on which the MASTER server will connect to each remote hosts

  • will be the IP of the MASTER server (the primary monitoring server)

  • Master means the host on which LoGrobot will report its log information to the Master

To install LoGrobot on the MASTER server, just run this:

  •     /apps/magent     5666     master

    • Change the port number and/or IP address to match your environment

Installation Completed!

If you have multiple hosts on which you wish to install LoGrobot, there is an automated feature you can use.  For this automated feature to function, you will need to install the "expect" utility on only ONE host.  This host must be a host from which you can ssh to all other hosts under your control.

Back to Top



Can I generate professional Excel Reports on the history of log file alerts received?

Yes.  If you wish to generate a report on a specific timeframe, run a command similar to either of these:

If you dislike the idea of having to type or remember syntaxes, run "kinglazy" at the command prompt.  Pick option 15.  Yes, we thought of you :)

Back to Top



Can I monitor multiple strings in the same log file instead of searching for them separately?

Yes. If you want to monitor your logs for multiple strings, you can run LoGrobot this way:

Basic Example:

Monitor log for strings “Error” and “imuxsock” and “ERROR” and “failed”

LoGrobot  autonda  /var/log/syslog  60m  'ERROR|failed|Error|imuxsock'  '.'  3  5  mul_log_entries_2  -ndfoundmul

Whenever LoGrobot finds any line that contains any of these strings, it will alert.

In other words, NO, you do not have to run several instances of LoGrobot for different strings.  LoGrobot can monitor them all in one go. 

If all your search strings cannot fit nicely on the command line, substitute a config file in their place.



Back to Top



What is logXray?

logXray is the latest upgraded version of LoGrobot which can be used on any UNIX system (Linux, AIX, SunOS, HP-UX).  To purchase the full version of it, click here.

Back to Top



How Fast is logrobot / logXray?

Very fast!  LoGrobot completes its periodic scanning of log files within 0.4 to 1 second.  Listed below are some of the information provided each time a log check runs:

  • number of errors found,

  • total number of lines in the log,

  • log size at the latest log check

  • range of lines scanned within the log file

  • timeframe within which the status of the latest log check is based upon

  • seconds within which the latest errors / entries in log file were detected

  • automatically detects log rollover - prevents missing errors between checks

  • equipped with several features that does MORE than just monitor log content

Back to Top


What options do I have to purchase LoGrobot / logXray?

Please click here to view the full list of available options.

If you wish to try out logxray on a month to month basis (rather than purchasing it all at once), make sure to subscribe to a monthly payment plan. The option for monthly payments allows you to try out the fully featured version of loxray for a month, without having to pay the full price up front.  If you wish to cancel subscription after your individually designated test period is over, simply click the Unsubscribe link right next to the payment plan you were subscribed to.

For instance, assuming you wanted to try out the option for Unlimited Licensing but do not wish to make the entire payment for it all at once, there is an alternative.  You can instead make a monthly subscription for $179.95.  During each month which you are subscribed, you will receive full customer service support including the latest updates and upgrades to the tool.

If for any reason you believe the logrobot isn't the right tool for you, you are free to Unsubscribe before the month is over.

Back to Top



Additional Benefits of Monthly (or) Yearly Subscriptions (besides access to the fully feature version):

  1. Email Support / Instant Messaging – We’ll do the work for you via Live Chat!

    • Ask us any question, we'll chat live with you or send you detailed responses via email


  2. Free Development – Ask us to develop any custom feature…just for you!

    • Send us your customization requests – Get the new version of logXray containing your requested features in under 72 hours…or less!


  3. Latest Updates / Upgrades – Get the newest features available!


Back to Top


(For Individual Use)


(For Individual Use)


(Large Corporations)


(Large Corporations)+

25 UNIX Hosts / Servers

Monitor / Alert / Analyze / Graph

Unlimited Logs - Remote/Local

$249.95/year  Payment / Unsubscribe


$21.95/month  Payment / Unsubscribe

500 UNIX Hosts / Servers

Monitor / Alert / Analyze / Graph

Unlimited Logs - Remote/Local

$799.95/year  Payment / Unsubscribe


$69.95/month  Payment / Unsubscribe

50 UNIX Hosts / Servers

Monitor / Alert / Analyze / Graph

Unlimited Logs - Remote/Local

$349.95/year  Payment / Unsubscribe


$27.95/month  Payment / Unsubscribe

750 UNIX Hosts / Servers

Monitor / Alert / Analyze / Graph

Unlimited Logs - Remote/Local

$899.95/year  Payment / Unsubscribe


$79.95/month  Payment / Unsubscribe

100 UNIX Hosts / Servers

Monitor / Alert / Analyze / Graph

Unlimited Logs - Remote/Local

$549.95/year  Payment / Unsubscribe


$44.95/month  Payment / Unsubscribe

1000 UNIX Hosts / Servers

Monitor / Alert / Analyze / Graph

Unlimited Logs - Remote/Local

$1049.95/year  Payment / Unsubscribe


$89.95/month  Payment / Unsubscribe

250 UNIX Hosts / Servers

Monitor / Alert / Analyze / Graph

Unlimited Logs - Remote/Local

$699.95/year  Payment / Unsubscribe


$59.95/month  Payment / Unsubscribe

Unlimited UNIX Hosts / Servers

Monitor / Alert / Analyze / Graph

Unlimited Logs - Remote/Local

$1,895.00 / one-time fee  Payment

$179.95 / Monthly  Payment / Unsubscribe

Copyright    |    Restrictions    |    Licensed Product    |    Grant of License    |    Warranty    |    License Agreement