Task management service event logger

Task management service event logger

We can enable an event logger that logs all Java Management Extensions (JMX) notifications from the TaskManagement MBean into its own log file.

The event logger addition to the task management service logs all JMX notifications: tasknew, taskstatechange, taskserveritychange, taskstatuschange.
The log for every task event contains the following fields:

Field Description
timestamp The time when the event was received and logged.
taskID The global ID of the task that the event concerns.
originatedTime The time the task was originated.
cell The cell that the task event was received in.
notification The type of JMX event / notification that was received.
submitter The originator of the event.
reasonMsg The task's reason message.
taskType The type of task.
severity The global severity of the task.
actions Any actions associated with the task (if applicable).
state The task's lifecycle state.
status The status of a terminated task.
statusMsg The status message related to the status of a terminated task.

Enable and configure the event logger

The event logger must be enabled and can be configured through cell level custom properties. To access the event logger, go to...
System Administration > Cell > Custom properties

The following table describes the name and default values for the event logger.

Property Name Default value Description
tmslog.delim | The delimeter to use between fields in the log file.
tmslog.enable false Whether or not to enable logging of task management service events.
tmslog.fileLocation ${LOG_ROOT} The location of where the log file will be written out to.
tmslog.maxFiles 1 The maximum number of historic files to keep.
tmslog.maxSize 20 The maximum log file size to allow before rolling log files (in MB)
tmslog.timeFormat empty string: "" The format to use when logging timestamp and originatedTime. Reference the javadoc for SImpleDateFormat for information on how to construct a timestamp pattern. If we want the time to span fields, such as to separate date and time into different columns, then use the delimiter in the pattern. If we do not specify a value for the custom property, the epoch time format is used.

The custom properties are not recognized during runtime. Restart the deployment manager to pick up any changes to the custom properties.

Monitor Intelligent Management operations
Manage runtime tasks

Field	Description
timestamp	The time when the event was received and logged.
taskID	The global ID of the task that the event concerns.
originatedTime	The time the task was originated.
cell	The cell that the task event was received in.
notification	The type of JMX event / notification that was received.
submitter	The originator of the event.
reasonMsg	The task's reason message.
taskType	The type of task.
severity	The global severity of the task.
actions	Any actions associated with the task (if applicable).
state	The task's lifecycle state.
status	The status of a terminated task.
statusMsg	The status message related to the status of a terminated task.

Property Name	Default value	Description
tmslog.delim	\|	The delimeter to use between fields in the log file.
tmslog.enable	false	Whether or not to enable logging of task management service events.
tmslog.fileLocation	${LOG_ROOT}	The location of where the log file will be written out to.
tmslog.maxFiles	1	The maximum number of historic files to keep.
tmslog.maxSize	20	The maximum log file size to allow before rolling log files (in MB)
tmslog.timeFormat	empty string: ""	The format to use when logging timestamp and originatedTime. Reference the javadoc for SImpleDateFormat for information on how to construct a timestamp pattern. If we want the time to span fields, such as to separate date and time into different columns, then use the delimiter in the pattern. If we do not specify a value for the custom property, the epoch time format is used.