Job Management Partner 1/Performance Management Planning and Configuration Guide

[Contents][Glossary][Index][Back][Next]

Appendix G.3 Format of output action log data

The action logs in Performance Management provide information related to system monitoring functions. Action logs are output to a single file on each host (physical host and logical host). The host to which the action log data is output depends on the action that was performed.

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

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

On physical hosts
  • In Windows
    installation-folder\auditlog\
  • In UNIX
    /opt/jp1pc/auditlog/

On logical hosts
  • In Windows
    environment-directory\jp1pc\auditlog\
  • In UNIX
    environment-directory/jp1pc/auditlog/

You can change the output destination for action logs in the jpccomm.ini file. For details on how to change this setting in the jpccomm.ini file, see G.4 Settings for outputting action log data.

(3) Output items

The items in an action log fall into the following two categories:

(a) Common output items

The following table lists the values output as common output items, and the content of each item.

Table G-2 Common output items in action logs

No. Output item Value Content
Item name Output attribute name
1 Common specification identifier -- CALFHM An ID indicating that the information is formatted as an action log
2 Common specification revision number -- x.x The revision number used to manage the action log
3 Sequence number seqnum sequence-number The sequence number of the action log record
4 Message ID msgid KAVExxxxx-x The message ID from the product
5 Date and time date YYYY-MM-DDThh:mm:ss.sssTZD# The time (including time zone) when the action log was output
6 Generated program name progid JP1PFM The name of the program where the event occurred
7 Generated component name compid service-ID The name of the component where the event occurred
8 Generated process ID pid process-ID The ID of the process associated with the event
9 Generated location ocp:host
  • host-name
  • IP-address
 The location where the event occurred
10 Event type ctgry
  • StartStop
  • Authentication
  • ConfigurationAccess
  • ExternalService
  • AnomalyEvent
  • ManagementAction
 The name of the category to which the event output to the action log belongs
11 Event result result
  • Success
  • Failure
  • Occurrence
 The result of the event
12 Subject identification information subj:pid process-ID Any of the following information:
  • The ID of the user-operated process
  • The ID of the process that generated the event
  • The username of the user who generated the event
  • Identification information unique to a particular user
subj:uid account-ID (PFM user or JP1 user)
subj:euid execution-user-ID (OS user)

Legend:
--: None.

#
T is used to separate the date and time.
TZD specifies the time zone. One of the following is output:
+hh:mm: Indicates a time zone hh:mm ahead of UTC.
-hh:mm: Indicates a time zone hh:mm behind UTC.
Z: Indicates a time zone equivalent to UTC.

(b) Fixed output items

The following table lists the values output as fixed output items, and the content of each item.

Table G-3 Fixed output items in action logs

No. Output item Value Content
Item name Output attribute name
1 Object information obj
  • service-ID-for-PFM-Agent-or-PFM-RM
  • name-of- added-deleted-or-updated-user (PFM user)
 The target of the operation.
obj:table alarm-table-name
obj:alarm alarm-name
2 Action information op
  • Start
  • Stop
  • Add
  • Update
  • Delete
  • Change Password
  • Activate
  • Inactivate
  • Bind
  • Unbind
 The action that generated the event.
3 Permissions information auth
  • Administrator
    Management
  • Ordinary user
    Ordinary
  • Windows
    Administrator
  • UNIX
    SuperUser
 The permission held by the user who performed the operation.
auth:mode
  • PFM authentication mode
    pfm
  • JP1 authentication mode
    jp1
  • OS user
    os
 The authentication mode of the user who performed the operation.
4 Location of output source dtp:host host-name-for-PFM-Agent-or-PFM-RM The host where the alarm was generated.
5 Origin of instructions subjp:host
  • login-host-name
  • execution-host-name (when executing the jpctool alarm command)
 The host where the instructions to perform the operation originated from.
6 Free description msg message The message output at alarm generation or at automated action execution

The fixed output items output in an action log and the content of those fixed items depends on the type of event that caused the action log to be output. The following describes the message IDs and the content of the fixed output items in action logs for each event type.

n When a PFM service starts or stops (StartStop)

n When a service enters or leaves stand-alone mode (StartStop)

n When login authentication results are received from PFM - Web Console (Authentication)

n When an alarm or action definition is created, updated, or deleted (ConfigurationAccess)

n When an alarm is bound or unbound (ConfigurationAccess)

n When a PFM user is added, deleted, or updated (ConfigurationAccess)

n When the status of the connection to PFM - Manager changes (ExternalService)

n When PFM - Agent or PFM - RM connects or disconnects (ExternalService)

n When an alarm is generated (AnomalyEvent)

n When an automated action is executed (ManagementAction)

(4) Output example

The following shows an example of action log output.

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

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.