Logger View

The Logger view displays messages from the application, including the type, date, and time of the message. If the application does not behave as expected, especially with respect to generating data, check this tab to see whether an internal error occurred.

The following message types, in order of severity, may be used:

  1. DEBUG: A message of interest to programmers.

  2. INFO: High-level program status or progress information.

  3. WARNING: A message about problem involving data. This message type does not indicate a problem with the program's operation.

  4. ERROR: Information about an internal error.  This message type usually indicates a bug in the program or a major configuration problem.

  5. CRITICAL: Information about an error so severe that it impairs the program's ability to continue, and may cause the program to exit (for example, running out of memory).

If you double-click an entry in the Logger view, a window appears, displaying the full text of the message. If you have enabled it in Logger Preferences, the window is a Quality Agent dialog box; otherwise, it is a Log Message Detail window. This window is useful for viewing long messages, such as Python traceback error messages. You can also use the Quality Agent dialog box  for reporting errors to Enthought.

To clear all the entries in the Logger view, right-click anywhere in the list of messages. click Reset Logs.

Messages are also written to a file, envisage.log, in your home directory. (On MS Windows, your home directory is typically C:\Documents and Settings\username.) When this file grows to about 1000 KB, it "overflows" to a back-up file, envisage.log.1; up to 3 back-up files are maintained, for a total of up to 4 MB of log entries for the current session

Messages are also written to a log file, ets.log, located under your user application data folder. On MS Windows, this folder is typically C:\Documents and Settings\username\ApplicationData. On Unix, it is your home directory. The exact location of the log depends on the vendor and identifier for the application.

When the log file grows to about 1000 KB, it "overflows" to a back-up file, ets.log.1; up to 3 back-up files are maintained, for a total of up to 4 MB of log entries.