ipMonitor 6.1
History Events Overview
< BackIndexNext >


A record of all events that occur within ipMonitor is written to an industry standard CSV (comma separated variables) log file. Events are listed chronologically from oldest to newest. They are most often used for diagnostic purposes.

Topics Discussed on this Page...

Actions Logged by ipMonitor

The "History Event" log lists all actions taken by ipMonitor on behalf of configured monitors. It provides an ideal way to determine that ipMonitor is doing what it was configured to do. Events are broken down into several categories:

  • Monitor failures
  • Monitor recoveries
  • Failure notifications
  • Recovery notifications
  • Successful monitor tests
  • Security
History Events Button Bar: - The following actions are accessible from the button bar located at the top of the ipMonitor interface.

Button Comment
Export Log To export the entire Activity Log as a CSV file (comma separated variable) select the "Export" button located on the ipMonitor button bar. Most popular graphing and database packages support CSV imports.
Full Screen A full screen page containing only a "Back" button will be generated. This view makes it possible to display monitors without the surrounding interface.
Clear Log To permanently delete the entire Activity Log, select the "Clear Log" option located on the ipMonitor button bar.
Refresh The auto refresh interval is set on the "General Settings" page. The Activity Log can be refreshed manually at any time by clicking the "Refresh" button located on the ipMonitor button bar.

The ipMonitor log file lists all "testing actions" taken and "reactions" recorded by ipMonitor on behalf of configured Monitors. With the many configuration options possible, this provides the data required to determine that ipMonitor is in fact acting as configured.

Location of Current Log File:

The current log file is located in the same directory in which ipMonitor is installed. The exact location varies according to the drive letter selected at time of installation.

x:\ipmonitor\ids\probe.log
Location of Archived Log Files:

Both log files and reports grow at the same rate making it easy to monitor log file growth. When it becomes necessary to maintain the log file, you can "Clear" or "Archive" it. Clearing the log file permanently deletes the current log file whereas archiving saves it for possible future use. Location of archived (saved) log files.

x:\ipmonitor\logfiles\
Logging Successful Monitor Tests:

By default, successful Monitor tests are not logged thus preventing log files from quickly growing to large sizes.

If required, successful Monitor tests can be recorded within the History Event log file as follows:

  1. Open "em60.ini" with Microsoft Notepad.
  2. Change "LogSuccessful=0" to "LogSuccessful=1". Create the "LogSuccessful" line if it isn't there already.

Logging Individual Monitors:

In addition to this "History Event" log, ipMonitor is able to log activity to a text file on behalf of an individual Monitor using the "Text Log" Alert function. This provides an easy way to create a report for a single Monitor. For more information, refer to the section titled Profiles/Alert: Record to Log File.

Related Topics...