Hitachi

JP1 Version 12 JP1/Base User's Guide


2.4.1 Converting application program log files

The following figure shows how the log file trapping function converts the contents of application program log files into JP1 events and registers them in an event database.

Figure 2‒12: Overview of application log conversion to JP1 event registration

[Figure]

To perform log file trapping, create an action definition file for log file trapping, and then specify the output format of the log file you want to monitor and the conditions for converting log data into JP1 events. When you execute the command, the log-file trap management service (or daemon) generates log file traps which are then used to monitor the log files. All log entries that match the monitoring conditions are converted into JP1 events, which are then registered in the event database. Because multiple log file traps can run simultaneously, you can monitor a variety of log files using different monitoring conditions. You can also monitor multiple log files with one log file trap.

If you execute the jevlogstart command without the -m option, messages containing a maximum of 511 bytes can be registered as JP1 events. If a message exceeds this limit, the message is truncated from the 512th byte when it is converted into a JP1 event. If you want to extend the length of the message, specify the number of bytes (up to 1023) in the -m option of the jevlogstart command.