LogWatch helps you prevent extended outage because of undetected issues.
LogWatch is a tool that monitors log files for anomalies and alert you as soon as they
are detected. It runs in Guardian space, but can monitor OSS and Guardian files, in
addition to VHS and EMS logs.
- Prevents production outage by minimizing your down time as errors are detected by LogWatch and acted upon immediately
- Helps Operation monitor OSS log files for errors without having to learn OSS
- Facilitates QA team in testing new code by detecting log file patterns
- Allows Developers to be notified of program problems in QA or production environments
MOMI and Prognosis are great tools to monitor system resources, but they are not designed for monitor application disk log files. In contrast, LogWatch is designed to monitor log files for error patterns and is a great complementary tool to MOMI and Prognosis.
LogWatch Focuses on monitoring logs content. Very easy to work with! Can feed log data and alerts.
Complement other software that monitors system components:
- Open View
Yes, you can have multiple instances of LogWatch running at the same time, monitoring different log files.
For Guardian files, LogWatch uses CONTROL 27. For OSS files, it uses a timer to wake and check the EOF entry to detect if there is new data.
LogWatch allows you to configure multiple files to monitor, as many as you want to. The best practice for the number of files to be monitored by one instance depends on how “busy” the file is, i.e. what is the new data arrival rate of the file. This is similar to the standard best practice in scaling servers according to the expected transaction rate. So, if you are monitoring very busy file(s), you would want to have a dedicated LogWatch instance to process the entries. Likewise, for files with infrequent insertion, a single instance of LogWatch will be able to handle many of them.
- Discover missing web pages by monitoring httpd.log or access.log
- Detect application errors by monitoring access.log for error 500
- Capture servlet errors by monitoring servlet.log
Upon catching any of these errors, LogWatch can raise an alert by:
- Sending a message to EMS (optionally routed via SNMP to an external Enterprise Manager)
- Sending an email to Operation or Support
- Writing the errors to a Guardian error file
LogWatch can be installed in 30 minutes.You can set up a configuration to monitor OSS or Guardian files in about 10 minutes.
Why should I use LogWatch instead of EMS to monitor application logs?
3 Quick Good Reasons
|EMS already overflowed with too much data, causing extensive CPU utilization in processing.
||You can assign different LogWatch processes to monitor different log files and distribute them across different CPUs.
|Setting up EMS filters requires training and management approval because they affect the whole environment.
||LogWatch can be set up quickly, and each instance does not affect other environments.
|Most OSS applications are designed to log to disk files, not EMS. Java applications need to incorporate special code to write to EMS.
||LogWatch allows applications to log to disk file in their preferred native format, Guardian or OSS.
LogWatch Use Case – Monitoring TeleMail
LogWatch can help you ensure TeleMail operates smoothly.
- Usage – How to detect issues with TeleMail jobs or environment
- Approach - Use LogWatch to monitor TeleMail log files for anomalies
- Look for error pattern in EMAILLOG to detect error occurances
- Raise alerts by sending messages to EMS and email to Support Team
- Error is detected as soon as it happens. No need to wait for Users to call up and complain about a problem
- Support teams will receive all the needed error information to resolve issue. No need to waste time hunting for an error message in large log files
- Quick detection leads to quick resolution. No need to suffer from extended downtime