10.2.2 Trace log for issued JP1 events
The trace log for issued JP1 events is used to output the conversion results when NNMi incidents are converted into JP1 events. You can use this log to obtain the results of filtering by the filter conditional statements in the NNMi incident forwarding filter definition file and to obtain the JP1 event issuance status.
The default output destinations for trace logs for issued JP1 events are as follows:
- In Windows:
-
-
Physical host: EG-for-NNMi-path\log\jegnevent{1|2|3|4}.log
-
Logical host: shared-folder\JP1EG4NNMI\log\jegnevent{1|2|3|4}.log
-
- In UNIX:
-
-
Physical host: /var/opt/jp1eg4nnmi/log/jegnevent{1|2|3|4}.log
-
Logical host: shared-directory/jp1eg4nnmi/log/jegnevent{1|2|3|4}.log
-
You can use any text editor to view the trace logs for issued JP1 events. The following shows an output example of trace log information for issued JP1 events.
The tables below list and describe the header information and output items that are output to the trace logs for issued JP1 events.
Header information |
Description |
---|---|
OS information |
Information about the OS on which the trace function of JP1/IM - EG for NNMi is running |
Host name |
Name of the host at which the trace function of JP1/IM - EG for NNMi is running |
Time zone |
|
Trace function start time |
Time the trace function of JP1/IM - EG for NNMi started |
Output item |
Description |
---|---|
Number |
Trace record number (4 digits) This number is assigned to each process that outputs log information. |
Date |
Trace acquisition date: yyyy/mm/dd (year/month/date) |
Time |
Trace acquisition time (local time): hh:mm:ss.sss (hour:minute:second.millisecond) |
Application name |
Name that identifies the application (application ID name) JP1/IM - EG for NNMi outputs the following application names:
|
pid |
Process ID (assigned by the OS) |
tid |
Thread ID (used for identifying threads) |
Message text |
Message text that is output to the trace log for issued JP1 events This is a message text output by this product. |
- Format of message text
-
The following shows the format of the message texts that are output to the trace log for issued JP1 events:
conversion-resultΔ:Δacquisition-request-date-and-timeΔUUIDΔsource-node-nameΔcreation-date-and-timeΔ>Δevent-database-number
Δ indicates one or more consecutive spaces or tabs.
The following shows an output example of a message text.
Figure 10‒3: Output example of a message text in the trace log for issued JP1 events
The following table describes the items in the message text.
Item |
Description |
---|---|
Conversion result |
Result of converting an NNMi incident into a JP1 event:
|
Acquisition request date and time |
Date and time an NNMi incident acquisition request was issued to NNMi This value is expressed as the elapsed time in milliseconds since 1970-01-01 at 00:00:00 (world standard time). |
UUID |
UUID of the NNMi incident |
Source node name |
Source node name of the NNMi incident |
Creation date and time |
NNMi incident creation date and time (local time: yyyy/mm/dd hh:mm:ss (year/month/date hour:minute:second)) |
Event database number |
Serial number of the JP1 event that was issued by converting the NNMi incident This item is output only when the conversion result is FWDn. |
- Note:
-
The time of a log entry in the trace log for issued JP1 events reflects the format for the time zone of the process that outputs the log.
Therefore, if a user changes the TZ environment variable and then starts a service or executes a command, the time might be output in a different format than that used for the time zone set in the OS.