Generate Live Log Monitoring Graphs on Existing/New Log Checks...all with a simple ONE liner! No complex coding, No complicated configuration file changes!

Aggregate Multiple log file Graphs into ONE - Utilize logs to Visualize Application, System & Database Health - Analyze security related events with a simple Glance!

Fully Loaded Solution for Monitoring Log Files - Monitor, Report, Analyze, Alert & Graph

(fully featured, 5 log monitoring tools in ONE - Use as a plugin, standalone, or as a monitoring system)

No time-consuming configurations, Plug n Play - Start monitoring logs in just seconds after download!

24 / 7 Support Included ; Contact us for Assistance / Custom Development Requests!

Why is LoGrobot the Log Monitoring Tool for you?

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

Trend day-to-day overall log behavior / activities

Monitoring & Graphing Apache / HTTP Status Codes

Monitoring & Graphing Apache / HTTP Status Codes

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, Custom logs and much more!

Automatically Send Log File Data to Graphite Directly from the Monitoring Server - Setup Checks in Nagios, Crontab or Any Application, see them in Graphite

Quick References to some of logXray's most popular Log File Monitoring 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 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 - Set thresholds per string

  9. Monitor A Directory of Log Files - Avoid specifying each log file separately

  10. Directory File Count Monitoring - Monitor the number of files in a directory

  11. Show X number of lines before and/or after matching pattern is found

  1. Automatically Generate Live Graphs for all Log File Monitors / Log File Checks

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

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

  4. Automated install of Nagios on Red Hat/CentOS/Ubuntu Hosts (avoid manual steps)

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

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

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

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

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

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

Common Log Monitoring Scenarios

 

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

Case Scenario:

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'. 

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.

Command:

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

 

Back to Top

 


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

Case Scenario:

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.

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!

Command:

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

 

Back to Top


  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.

Command:

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

 

Back to Top


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.

 

 Example:

[root@monitor jbowman]#  ./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 to find out how many lines contain certain strings and patterns, you can run a command similar to this:

 

Example:

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

 

Notice the [ 2w ].  And also, notice the strings being searched for.  I repeated the strings ‘ERROR|error|panic|fail’ twice because there is no need to specify different search terms to look for.  You don't have to repeat the first string.  You can just enter a dot in its place for the second string..i.e:

 

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

 

From this specific example, I'm telling logrobot that I care about EVERY single line that contains any of the keywords I provided.  The [ 2w ] of course means 2 weeks. 

 

 See below for the different ways of specifying the 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)

 

Back to Top


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

 

 

Command:

 

[root@monitor jbowman]#  ./logxray localhost /var/tmp/logXray autonda /var/log/syslog 60m 'kernel|panic' 'abrt'  3 5 syslog_check -ndshow

 

Explanation:

  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

 

 

Back to Top


Reason for Specifying Exclusions in LogChecks

Suppose you inherit a UNIX environment at a new job and you're unfamiliar on 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.  Therefore, if a log file is stripped of the familiar and unwanted, whatever is left will be unfamiliar, thus requiring investigation.
 

[root@nagios-primary ~]# logrobot autofig /var/log/messages 24h '.' 'nagios-primary nagios|not responding|synchronized to' 1 5 -showexcl

 

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

Back to Top

 

 

Frequently Asked Questions

 

  1. What exactly can I do with with LoGrobot log monitoring system?

  2. Is it safe and easy to install the LoGrobot log monitoring system?

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

  4. How Big is the LoGrobot Log Monitoring 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 the LoGrobot log monitoring system handle log rotation?

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

  13. Can LoGrobot monitor log files that do not 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 application?

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

  1. What exactly is the NagiosLogMonitor?

  2. How much is the LoGrobot log monitoring plugin / monitoring system?

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

  4. Is there a Money Back Guarantee?

  5. Can I submit requests for custom / personalized Log Monitoring features?

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

  7. Can I generate Reports on the history of log monitoring alerts received?

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

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

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

  11. What is logXray?

  12. How fast is logXray?

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

  14. Additional Benefits

  15. Can I View logs of a remote host without having to log in to the host?

  16. Will my log file type be supported?

Back to Top


 

What exactly can I do with LoGrobot?

If you can think up a log monitoring necessity, LoGrobot / logXray  can accommodate it.  Visit the following link for a full list of features available:

http://www.logrobot.com/log-file-monitoring-features-options.htm

The massive log monitoring capabilities of logXray include, but surely aren't limited to:

  1. Monitoring & Alerting on the contents of system log files (errors, strings, keywords, patterns etc)

  2. Monitoring & Alerting on custom Application log files (mysql, oracle, apache/http and much more)

  3. Alerting if certain keywords / patterns ARE NOT found inside a specific log within a specific timeframe

  4. Monitoring & Alerting on the timestamps of log files (verify files are being updated regularly)

  5. Monitoring several log files at the same time - (very useful if you have multiple logs to scan)

  6. The capability to monitor both live and rotated logs to ensure nothing is missed

  7. Graphing the frequency with which user-specified patterns occur in log files

    1. Or graph for anomalies

  8. Monitoring & Alerting on the size of log files (ensure logs do not consume too much disk space)

  9. Monitor log files no matter how big they are (even logs that are GIGABYTES in size)

  10. Conditional Monitoring..i.e:

    1. Alert if a certain column of a newly added log entry has a value greater than or less than x

  11. View logs on all your servers from one Web Interface (avoid having to ssh to each host)

  12. Analysis - Easily identify which minute or hour of the day had the most entries recorded

 

 

Please note there are many additional features that haven't been listed on this page.  This is done on purpose.   If you have a particular requirement (which isn't listed), please contact our support team.  We are happy to provide details on what else LOGROBOT can do for you.  Chances are, 99% of the time, your requirement has been thought off by previous customers and provisions for it have already been built into the tool.

 

Back to Top


 

Is it Safe and easy to install LoGrobot / logXray?

Yes.

With logrobot, there's very little you have to do.  We are very proud to announce that, unlike other tools that consider themselves "log monitoring", 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.  If using Nagios, define nagios configurations for it (in 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 log checks, logXray will automatically configure 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. 

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! logXray completes scanning of logs quickly (under 1 second).

Back to Top


 

How Big is the LoGrobot tool?

The current size of the premium version of the logrobot tool (logXray) is a little over 12MB. 

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.  You can send instructions to the tool from the Master server without having to log into the host on which the tool lives.

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 a huge variety of different functionalities that allows it to fully function without Nagios. 

If you need LoGrobot to operate in a very specific fashion, do not hesitate to contact us.

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.2 - 1.5 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 patterns (one 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 when detected, it proceeds to scan the unread entries from the recently rotated log, in addition to monitoring the fresh live 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.  Click any of the following links for more information:

You can literally start monitoring your logs within seconds of purchasing, downloading and unzipping the LoGrobot tool.  That is one of the many benefits of having a versatile tool that can act either as a plugin or a standalone system, without forcing users to break a sweat!

logXray was built specifically for use by the every UNIX user (i.e. system administrators, developers, dbas, monitoring engineers) - those who interact with the command line on a frequent basis.

And if you're a web interface (point and click) kind of user, don't you worry.  We thought about you too! Click here.

Back to Top


 

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

Yes!

 

Back to Top


 

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

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

Back to Top


 

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

Absolutely not.  LoGrobot does not rely on any other application in order for it to monitor and alert on logs.

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 and Graphite.  Contact us for more information!

Back to Top


 

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

Absolutely! We have an automated utility in our arsenal called "kinglazy" which will install both applications for you.  The sole purpose of this tool is to make life tremendously simple for the stupendously lazy ones amongst us.  This tool will relieve you of the tedious responsibility of having to labor over complex configuration procedures. 

However, for the kinglazy tool to be of any use to you (as far as the Installation of the applications are concerned), all we ask is that you have a fresh install of Ubuntu (if you wish to install Graphite) or a fresh install of Red Hat/CentOS (for those wishing to install Nagios and/or Cacti). 

Once you have the freshly installed OS in place, all you have to do next, is put the shell script we give you on the new host and run it.  The script will do everything else for you.  No silly questions, No reading of confusing installation steps.  The script will handle all that for you!

Do you really have to have a fresh install of Ubuntu / Red Hat?  No. But we highly recommend it!

Back to Top


 

What exactly is the NagiosLogMonitor (nlm) tool?

NagiosLogMonitor (nlm) is the plugin that interprets the output produced by LoGrobot / logXray. 

Note, you do not have to have Nagios installed in order to use it.  You can run it through CRONTAB as well.

UPDATE:  If using Nagios with NRPE to monitor your remote hosts, the NagiosLogMonitor (nlm) is not needed.  This is because the latest version of logrobot (known as logXray) is built with its own interpreter which renders the old NagiosLogMonitor unnecessary.  If you are not using NRPE in your environment, and don't wish to set it up for whatever reason, then you can just use the free custom agent included with the logXray package.

 

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 highly versatile and able to handle any situation you throw at it.

 

Back to Top


 

Is there a Money Back Guarantee?

Yes.  There is a 30 Day Money Back Guarantee.  If you're not satisfied for any reason with the LoGrobot tool, by all means, please let us know.  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 development 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:

If using NRPE,

  1. Simply copy the logXray zip file you just purchased to the hosts on which you have log files to monitor

  2. unzip the logXray.zip file

  3. Put the unzipped tool into whichever directory you consider your plugins or scripts directory

  4. Define an entry in the nrpe.cfg file

  5. Restart the nrpe process on the host

And that's it

 

If using the Custom Monitoring Agent that comes with logXray:

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

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

  • Unzip the logXray.zip file, then run the installation command.

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

  1. unzip logXray.zip ; cd logXray

  2. ./InstallAgent.sh     /var/tmp/logXray     1040     10.20.30.40

Explanation of the parameters:

  • /var/tmp/logXray is the default location logXray will be installed.

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

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

Installation Completed!

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, simply spring up the logXray web interface and click on the button for reports.

 

Back to Top


 

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

Yes. Below is a screen shot of logXray being used to monitor 6 different strings within 1 log file.

http://logrobot.com/Critical_Out_Of_Memory_Error_Multiple_Strings.png

 

Back to Top

 


 

What makes LOGROBOT / logXray Superior to other Log Monitoring tools?

  • Simplicity - It does not require an extensive learning process to get used to. Extremely user-friendly!

    • Unlike any of our competitors, we built LoGrobot / logXray to cater directly to the everyday needs of the typical:

      • System Administrator - Watch system logs, security logs, mail logs and basically any other system related log file

      • Database Administrator - Watch as many database log files as is necessary - Alert when specific patterns/error codes are found

        • Be able to easily specify exclusion patterns in areas where you wish to eliminate unnecessary noise

      • Monitoring Engineer - Spin up new log monitoring checks very quickly without having to develop them yourself!

      • Developers - Monitor important log files for errors or activity during code testing, Get alerts and / or watch progress on live graphs

  • Versatility - It can be used either as a plugin or its own standalone monitoring system

    • It can be used directly on the command line to perform a wide range of different operations on log files & directories

    • Unlike most UNIX utilities, many of LoGrobot's functions can also be utilized from a Web Interface

      • perfect for those who prefer to just point and click, rather than type!

  • Compatibility - With either Zabbix, Zenoss, Nagios or CRONTAB, the scheduling of multiple different log checks is effortless and dependable

  • Support - All users of LOGROBOT receive free support (custom development / live assistance)

    • When it comes to the monitoring of log files and the management of alerts on them, we understand there is an infinite number of ways things can be done

      • With LoGrobot / logXray, our users are given the chance to request the development of custom features for free

        • These customer specific features will be tailored specifically towards each individual user need

          • In areas where we determine a newly requested feature will be useful to the general public, we will add it to future releases of the LoGrobot suite!

  • Command line Usability - All necessary parameters are passable directly from the command line - No configs!

  • Modules - Unlike most tools, it does not require the installation of nonnative modules or libraries to the system

    • What that means is, there is nothing complicated for you to deal with

  • Affordable - An inexpensive log monitoring tool considering the amount of work it will save you - No more scripts for you to write!

  • Maintenance - Constantly updated for added simplicity, building of new features & polishing of the old

  • Speed - Completes scanning of log files in under 1.5 second, even files that are several hundred Megabytes / Gigabytes in size

  • Alerting - Its sole purpose is to monitor log files & alert on anything about them...i.e. content, size, timestamp etc

  • UNIX BASED - Written specifically for UNIX - Only uses resources that are native to the UNIX Operating System

 

Download Now


 

What is logXray?

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

Back to Top


 

How Fast is logrobot / logXray?

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

  • number of errors found,

  • number of new lines added to the log,

  • 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?

  • To monitor an unlimited logs on unlimited number of UNIX hosts and servers, click the option for $69.95.

    • Price may change without notice.

NOTE: This is a one-time fee.  You need not worry about making recurring payments.

Back to Top


 

Additional Benefits all users of logXray/LoGrobot receive:

  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 one on one or send you detailed responses via email - the preference is yours

     

  2. Free Code 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


 

I want to be able to also VIEW log files on all my hosts from ONE Web Interface

LOGROBOT comes with a PHP Web Interface that enables you to specify which host a log file is on, what TCP port you wish to connect to on that host, and where the log file is located on the host.   The benefit of this feature is so that you DON'T have to manually log in to any server in order to view the contents of the log files on that server. 

This feature basically eliminates the tedious task of having to type passwords repetitively to gain access to several servers.  It eliminates the need to generate tokens or to tamper with ssh config files. None of that is necessary.  If you want to view a particular log file on host x, simply bring up the PHP Web Interface, type in the host name, the location of the log file, what port to connect to, then hit submit!

Back to Top


 

Supported Log Files

  • Will all my logs be supported?

    Yes, all log types / log formats are supported. 

    Some of the supported log files are listed below:

    • Tomcat Catalina.out logs

    • Apache Maxclient logs

    • Apache access logs

    • Apache error logs

    • OutOfMemory logs

    • JBoss log files

    • Java log files

    • Weblogic logs

    • Glassfish logs

    • Syslog log monitor

    • Maillog / Postfix / Syslog log files

    • Mysqld / Oracle Alert logs

    • Log4j

    • NEW FEATURE: Monitor any type of log file regardless of format

     

Back to Top

Analyze Linux Log Files | Log File Analyzing | Log File Monitor | Log File Monitoring & Alerting | Zenoss Log Monitoring | Monitoring a Log File | Monitoring Application Log Files | Monitoring Linux Application Log Files | Monitoring Linux Log Files | Monitoring Log Files | Monitoring Log Files on Unix Systems | Monitoring Unix Log Files | Zabbix Log Monitoring | Monitoring Logs in Zenoss | Monitoring Linux Log Files | Monitor Linux System Logs / Log Files | Monitor Log Files | Nagios Log Monitoring | Monitoring Logs | Monitoring Log Files | Monitoring Application Logs | Log File Analysis | Zabbix Log File Monitoring | Zabbix Log Monitoring | Zenoss Log Monitoring | Log Monitoring Script

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