Appendix J.3 Format of output action log data

Data related to audit events is output to the Performance Management action log. Action log data is output to one file for one host. The action log data is output to a file on either of the following hosts:

The following describes the format of the action log, the output destination, and the items that are output.

Organization of this subsection
(1) Output format
(2) Output destination
(3) Output items
(4) Output example

(1) Output format

CALFHM x.x,output-item-1=value-1,output-item-2=value-2,...,output-item-n=value-n

(2) Output destination

/opt/jp1pc/auditlog/

The output destination for action log data can be changed in the jpccomm.ini file. For details about how to specify the jpccomm.ini file, see J.4 Settings for outputting action log data.

(3) Output items

There are two types of output items:

(a) Common output items

The following table lists and describes the common output items and their values. This table also includes the items and information output by PFM - Manager.

Table J-2 Common output items in action logs

No.Output itemValueExplanation
Item nameOutput attribute name
1Common specification identifier--CALFHMIndicates the action log format
2Common specification revision number--x.xRevision number for managing action logs
3Serial numberseqnumserial-numberSerial number of the action log record
4Message IDmsgidKAVExxxxx-xMessage ID of the product
5Date and timedateYYYY-MM-DDThh:mm:ss.sssTZD#Date, time, and time zone indication identifying when the action log was output
6Program nameprogidJP1PFMName of the program for which the event occurred
7Component namecompidservice-IDName of the component for which the event occurred
8Process IDpidprocess-IDProcess ID of the process for which the event occurred
9Locationocp:host
  • host-name
  • IP-address
Location where the event occurred
10Event typectgry
  • StartStop
  • Authentication
  • ConfigurationAccess
  • ExternalService
  • AnomalyEvent
  • ManagementAction
Category name used to classify the event output to the action log
11Event resultresult
  • Success
  • Failure
  • Occurrence
Result of the event
12Subject identification informationsubj:pidprocess-IDOne of the following:
  • Process ID of a process running as a user operation
  • Process ID of the process that caused the event
  • Name of the user who caused the event
  • Identification information in a one-to-one correspondence with the user
subj:uidaccount-identifier (PFM user/JP1 user)
subj:euideffective-user-ID (OS user)
Legend:
--: None
#
T is a separator between the date and the time.
TZD is the time zone specifier. One of the following values is output.
+hh:mm: The time zone is hh:mm ahead of UTC.
-hh:mm: The time zone is hh:mm behind UTC.
Z: The time zone is the same as UTC.
(b) Fixed output items

The following table lists and describes the fixed output items and their values. This table also includes the items and information output by PFM - Manager.

Table J-3 Fixed output items in action logs

No.Output itemValueExplanation
Item nameOutput attribute name
1Object informationobj
  • PFM - Agent-service-ID
  • added-deleted-or-updated-user-name (PFM user)
Intended object for the operation
obj:tablealarm-table-name
obj:alarmalarm-name
2Action informationop
  • Start
  • Stop
  • Add
  • Update
  • Delete
  • Change Password
  • Activate
  • Inactivate
  • Bind
  • Unbind
Information about the action that caused the event
3Permissions informationauth
  • Administrator:
    Management
  • General user:
    Ordinary
  • Windows:
    Administrator
  • UNIX:
    SuperUser
Permissions information of the user who executed the command or service
auth:mode
  • PFM authentication mode:
    pfm
  • JP1 authentication mode:
    jp1
  • OS user:
    os
Authentication mode of the user who executed the command or service
4Output sourceoutp:hostPFM - Manager-host-nameHost that output the action log
5Instruction sourcesubjp:host
  • login-host-name
  • execution-host-name (only when the jpctool alarm (jpcalarm) command is executed)
Host that issued the instruction for the operation
6Descriptive textmsgmessageMessage that is output when an alarm occurs or when an automated action is executed

Whether the fixed output items are output and what they contain differ depending on when the action log data is output. The following describes the message ID and output data for each case.

A PFM service starts or stops (StartStop)
Stand-alone mode starts or stops (StartStop)
Notes:
  1. No fixed output items are output.
  2. When PFM - Agent is started, PFM - Agent services connect to the PFM - Manager host, register node information, and obtain the latest alarm definition information. If a connection with the PFM - Manager host cannot be established, PFM - Agent starts in stand-alone mode, in which only part of its functionality, such as collection of operating information, is enabled. In addition, KAVE03002-I is output to indicate that PFM - Agent has started in stand-alone mode. From this point, the PFM - Agent services periodically attempt to connect to PFM - Manager. When the services are able to successfully register node information or obtain definition information, PFM - Agent leaves stand-alone mode and KAVE03003-I is output. In this way, the action log enables you to understand that PFM - Agent was running in an imperfect condition for the period from the output of KAVE03002-I to the output of KAVE03003-I.
The status of the connection with PFM - Manager changes (ExternalService)
Notes:
  1. No fixed output items are output.
  2. If the Agent Store service is unable to send an event to PFM - Manager, the Agent Store service starts queuing events, up to a maximum of three. When queuing is started after a failure to send an event, KAVE03300-I is output. When the connection with PFM - Manager is restored and all queued events have been sent, KAVE03301-I is output. In this way, the action log enables you to understand that real-time sending of events to PFM - Manager was disabled for the period from the output of KAVE03000-I to the output of KAVE03001-I.
  3. The Agent Collector service usually sends events to PFM - Manager via the Agent Store service. It directly sends events to PFM - Manager only when the Agent Store service has stopped for some reason. If sending of events fails, KAVE03300-I is output but KAVE03301-I is not output, since no events are queued. In this way, the action log enables you to understand that some events have not been sent to PFM - Manager.
An automated action is executed (ManagementAction)

(4) Output example

The following is an example of output action log data:

CALFHM 1.0, seqnum=1, msgid=KAVE03000-I, date=2007-01-18T22:46:49.682+09:00,
progid=JP1PFM, compid=UA1host01, pid=2076,
ocp:host=host01, ctgry=StartStop, result=Occurrence,
subj:pid=2076,op=Start