Clone
Gonzalo Correa <gonzalo.correa@hp.com>
committed
on 12 Mar 15
Monitor components use of log4cpp.
Incorporated code review changes.

Monitor message categories:

Category File Prefix Description
MO… Show more
Monitor components use of log4cpp.

Incorporated code review changes.

Monitor message categories:

Category   File Prefix   Description

MON        mon.          Monitor messages

MON-SNMP   mon.snmp.     Monitor critical messages

PSD        pstartd.      Process Startup Daemon messages

WDG        wdg.          SQWatchdog process messages

WDG-SMP    wdg.snmp      SQWatchdog process critical messages

Configuration files:

log4cpp.monitor.mon.config

log4cpp.monitor.mon.snmp.config

log4cpp.monitor.psd.config

log4cpp.monitor.wdg.config

log4cpp.monitor.wdg.snmp.config

File names created:

The file name format is:

   <file-prefix>.<timestamp>.<hostname>[.<nid].<pid>.log

The monitor process does not have a <pnid> when the logging object is

created

and <nid> does not apply.

The primitive processes follow the same filename pattern except that

they

use the .<nid> in the file name.

Example:

 mon.150311.07.52.04.g4t2968.houston.hp.com.4809.log

 mon.150311.07.52.04.g4t2968.houston.hp.com.4810.log

 mon.snmp.150311.07.52.04.g4t2968.houston.hp.com.4809.log

 mon.snmp.150311.07.52.04.g4t2968.houston.hp.com.4810.log

 pstartd.150311.07.52.05.g4t2968.houston.hp.com.0.6107.log

 pstartd.150311.07.52.05.g4t2968.houston.hp.com.1.6105.log

 wdg.150311.07.52.05.g4t2968.houston.hp.com.0.6104.log

 wdg.150311.07.52.05.g4t2968.houston.hp.com.1.6102.log

 wdg.snmp.150311.07.52.05.g4t2968.houston.hp.com.0.6104.log

 wdg.snmp.150311.07.52.05.g4t2968.houston.hp.com.1.6102.log

Conversion pattern:

layout.ConversionPattern=%d, %p, %c, %m

Monitor message format:

"Node Number: <pnid>,, PIN: <pid> , Process Name: <process-name>,,,

TID: <thread-id>, Message ID: <message-id>, <message-string>"

 - Notice the absence of 'CPU:' since it does not apply to the monitor.

 - <process-name> also does not apply, but the string '$MONITOR' stands

   out.

   However, the string is the same in every node, but the

   'Node Number: <pnid>' indicates which physical node.

Primitive processes message format:

"Node Number: <pnid>, CPU: <nid>, PIN: <pid> , Process Name:

<process-name>,,, TID: <thread-id>, Message ID: <message-id>,

<message-string>"

The message formats add:

- the <thread-id> which has been useful for debugging problems

- the <message-id> which is a unique identifier of each messages

  generated. The

  number takes you to a specific source code location where the message

is generated.

Change-Id: I1422aeb499d3e0cd03720d174dc5e6db8003fdc3

Show less

default + 9 more