Support > Administrator's guide (R7) > View system log

You can browse the contents of the log file (system.log) on ​​the screen by specifying the date, log level, and keywords.

Select "Browse system log" from the management processing menu.
You can narrow down the display according to conditions such as "log date", "type" and "keyword".Standard "type" is "ERROR".

The "Message" displayed is limited to 128 characters.If there are more characters, "... (see system.log file)" is added at the end.

Figure 1 System log display (narrowing down by type "ERROR")

There is the concept of "type" in the log.The following five types are available in Wagby.

type Description
INFO This is a message during normal processing.
ERROR This is a message at error handling.Processing is aborted.
WARN It means warning.Processing is continuing.
FATAL It means a fatal error.It is necessary to restart the application.
DEBUG This is a debug message.It is prepared for developers.

The following example is an example of narrowing logs with "type" as "INFO" and with the word "logon" as keywords.

Figure 2 System log display (type "INFO" and narrowing down by keyword "logon")

The log file of the day is output as "system.log" in the wagbyapp \ logs folder.
The log file of the past day contains the date in the file name.By doing this, you can check all past logs.

Wagby does not automatically delete log files.Deletion of the log file is the judgment of the administrator, please do it manually.

When deleting the log file, we recommend that you save it to another media.

Wagby does not delete log files during normal operation, but if you rebuild or replace the system, the log file will be deleted.Specifically, it is the case as follows.

  • When you do a build, the wagbyapp \ logs folder and so on are also initialized, so the previous log file will be deleted.Therefore, there will be no log files before a specific date.
  • If you change applications, the wagbyapp \ logs folder will also be replaced, so there will be no log files before the specified date.

For long-term keeping of the log file, when rebuilding or system replacement, existing logs foldermanuallyPlease backup.

You can also view zip compressed log files.This will save disk space.

R7.11 or later

日付時刻 [ログレベル クラス名 メソッド名] (アカウント@ホスト名またはIPアドレス|ブラウザ) 画面名|イベント名

Here is an example.

2017-04-04 09:00:00 [INFO jp.jasminesoft.jfc.controller.DbShowListBaseController perform_db] (admin@0:0:0:0:0:0:0:1|Chrome) showListCustomer|Search 

The date and time are expressed as yyyy - MM - dd HH: MM: ss.It is the year, month, day, hour, minute, second.

The log levels are "INFO", "ERROR", "WARN", "FATAL", "DEBUG".

The class name is the Java class that output this log.The method name is a method in the class.

For the account, "@" is followed by the host name of the operation terminal (IP address if the host name is unknown).However, for system level logs, this value is omitted.

The browser is the same as the value returned by the BROWSERTYPE function. The screen name is the same as the SCREENID function. The event name is the same as the EVENT function.

The log shows "when, who (from which terminal), what screen, what kind of action did you do".

R 7.0 to R 7. 10.3

There is no browser information up to R7.10.3.

日付時刻 [ログレベル クラス名 メソッド名] (アカウント@ホスト名またはIPアドレス) 画面名|イベント名