K.3 Operation log output format
This section describes the output format and output destination of operation logs, and the output items in operation logs.
- Organization of this subsection
(1) Output format
common-specification-identifier common-specification-revision-number, output-item-1=value-1, output-item-2=value-2, ..., output-item-n=value-n
(2) Output destination
The output destination of the operation log file is specified in the operation log definition file (imm_operationlog.conf). The initial value of the output destination is as follows:
- In Windows:
-
Manager-path\log\operationlog\imm_operation[n#].log
- In UNIX:
-
/var/opt/jp1imm/log/operationlog/imm_operation[n#].log
- #
-
n is a decimal number in the range from 1 to 16.
(3) Output items
There are two types of output items as follows:
-
Common output items
Items that are output by all JP1 products that output operation logs
-
Fixed output items
Items that are output individually by each JP1 product that output operation logs
(a) Common output items
|
No. |
Output item |
Value |
Description |
|
|---|---|---|---|---|
|
Item name |
Output attribute name |
|||
|
1 |
Common specification identifier |
-- |
CALFHM |
Log format identifier |
|
2 |
Common specification revision number |
-- |
1.0 |
Revision number for managing the log format |
|
3 |
Sequence number |
seqnum |
sequence-number |
Sequence number of a operation log record (assigned to each process) |
|
4 |
Message ID |
msgid |
KNAN3xxxx-x |
Message ID of the product#1 |
|
5 |
Date and time |
date |
YYYY-MM-DDThh:mm:ss.sssTZD#2 |
Operation log output date and time, and time zone |
|
6 |
Generated program name |
progid |
JP1IMM |
Name of the program in which the event occurred |
|
7 |
Generated component |
compid |
|
Name of the component in which the event occurred |
|
8 |
Generated process ID |
pid |
|
ID of the process in which the event occurred |
|
9 |
Generated location (host name) |
ocp:host |
|
Name of the host in which the event occurred |
|
10 |
Event type |
ctgry |
Authentication |
Category name for classifying the events that are output to operation logs |
|
11 |
Event result |
result |
|
Result of the event |
|
12 |
Subject identification information |
subj:uid |
JP1-user-name-in-JP1/IM - View |
Name of the JP1 user who caused the event |
- Legend:
-
--: No attribute names are output.
#1: The message ID of the message indicated in the free description in the fixed output items is output.
#2: T that follows YYYY-MM-DD separates the date from the time. TZD is the time zone identifier. One of the following is output:
-
+hh:mm: Indicates that the local time is ahead of UTC by hh:mm.
-
-hh:mm: Indicates that the local time is behind UTC by hh:mm.
-
Z: Indicates that the local time is the same as UTC.
(b) Fixed output items
|
No. |
Output item |
Value |
Description |
|
|---|---|---|---|---|
|
Item name |
Output attribute name |
|||
|
1 |
Object information |
obj |
Session |
Operation target |
|
2 |
Operation information |
op |
|
Operation details |
|
3 |
Request sender host |
from:ipv4 |
IPv4-address-in-JP1/IM - View |
IP address of the request sender |
|
4 |
Free description |
msg |
message-output-to-the-operation log |
Message indicating the contents of the event# |
#: The message text for the message ID in the common output items is output.
(4) Output example
Information that is output to the operation log when a user logs in to the Central Console:
CALFHM 1.0, seqnum=2, msgid=KNAN30000-I, date=2015-10-27T14:00:05.155+09:00, progid=JP1IMM, compid=CentralConsole, pid=1452, ocp:host=hostname, ctgry=Authentication, result=Success, subj:uid=System, obj=Session, op=LOGIN, from:ipv4=198.1.1.1, msg="A login operation was successful"
(5) Note
If a user opens the operation log file while JP1/Audit is monitoring the operation log data, a lock error might occur. If you want to check the contents of the operation log file during linkage with JP1/Audit, copy the operation log file to any location, and then check the copy.