LogWatch FAQ

  1. What is LogWatch?
  2. What are LogWatch’s benefits?
  3. I already have MOMI or Prognosis, why do I need LogWatch?
  4. Why should I use LogWatch instead of EMS to monitor application logs?
  5. LogWatch Use Case – Monitoring TeleMail

What is LogWatch?
LogWatch helps you prevent extended outage because of undetected issues.

  • LogWatch monitors log files for anomalies and alerts you when errors are detected.
  • LogWatch runs as a Guardian process, but can monitor OSS files, Guardian files, EMS and VHS logs.
  • You can configure one or more LogWatch processes to run at the same time.


LogWatch diagram


What are LogWatch’s benefits?
Prevents production outage by minimizing your down time as errors are detected by LogWatch and acted upon immediately

  • Helps Operation team 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


LogWatch who can benefit

Different departments can benefit from the use of LogWatch


I already have MOMI or Prognosis, why do I need
LogWatch?
LogWatch is designed to monitor log files for error patterns
and is a great complementary tool to MOMI and Prognosis. MOMI and Prognosis are
great tools to monitor system resources, but they are not designed for
monitoring application disk log files
.LogWatch
focuses on monitoring logs content and is easier to use for catching errors in
log files.

  • You have “out of the box” solution for monitoring OSS files with LogWatch
  • LogWatch does not need messages to be routed to EMS
  • LogWatch has sophisticated pattern matching that allows you to catch errors in many different formats, include multi-line messages (e.g. MQ)
  • You can start multiple instances of LogWatch for scalability

jigsaw_puzzles


Why should I use LogWatch instead of EMS to monitor application logs?

3 Quick Good Reasons

EMS_mess

EMS

Funnels

LogWatch

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

LogWatch TeleMail

Check out LogWatch blog

Sign up for TIC Talk

Download Datasheet

Request for Product Info