The hourly performance
log file is a summary of each message performance from the start of PMG or for
the last hour, on the hour. The hourly performance log files are output to the
file "pmg-perf-periodic.csv", and are stored in the directory
/rms/log/pmg.
The hourly performance
log file is in the CSV format and begins with a header row followed by a
performance summary for each message.
An example of the
messages in the file for the hourly performance logs is shown below:
2011-12-13T00:00:00.034Z,1400,Block,362,60461,236,19,0
2011-12-13T00:00:00.034Z,1400,GetStoredData,199,199,199,1,0
2011-12-13T00:00:00.034Z,1400,Update,60564,60564,60564,1,0
2011-12-13T00:00:00.034Z,1400,GetLiveData,360941,360941,360941,1,0
2011-12-13T00:00:00.034Z,1400,Reboot,232,236,228,2,0
2011-12-13T00:00:00.034Z,1400,Unknown,2,6,8,2,0
2011-12-13T00:00:00.034Z,1400,Unknown Content,2,6,8,2,0
2011-12-13T00:00:00.034Z,1400,XML Parse error,2,6,8,2,0
2011-12-13T01:00:00.034Z,3600,Block,362,60461,236,19,0
2011-12-13T01:00:00.034Z,3600,GetStoredData,199,199,199,1,0
2011-12-13T01:00:00.034Z,3600,Update,60564,60564,60564,1,0
2011-12-13T01:00:00.034Z,3600,GetLiveData,360941,360941,360941,1,0
2011-12-13T01:00:00.034Z,3600,Reboot,232,236,228,2,0
2011-12-13T01:00:00.034Z,3600,Unknown,2,6,8,2,0
2011-12-13T01:00:00.034Z,3600,Unknown Content,2,6,8,2,0
2011-12-13T01:00:00.034Z,3600,XML Parse error,2,6,8,2,0
The headers for the
fields in the hourly performance summary file are described here:
- period end-the summary
period end timestamp in the ISO 8601 format. The timestamp is in the format
"YYYY-MM-DDThh:mm:ss.fffZ", where time is represented in milliseconds
-
summary period
sec-the time interval in milliseconds, for receiving the messages during
the summary period
-
msg name-the
message name received during the summary period
-
avg response time
ms-the average response time in milliseconds
-
max response time
ms-the maximum response time in milliseconds
-
min response time
ms-the minimum response time in milliseconds
-
num msgs-the
total number of messages received during the summary period
-
num errors-the
number of errors occurred during the summary period
To track the
performance of unknown messages, messages with XML parser errors and messages
that are not of XML content are also rolled up in the hourly performance
summary file.
Following are some of
the logging details for unknown messages:
- All unknown messages have
the message name as "Unknown".
- All message XMLs that fail
to parse have the message name as "XML Parse error".
- All messages that are not of
content type application/xml or text/xml have the message name as "Unknown
Content".
 Note |
The hourly
performance log files will be maintained on the RDU for 30 days, at which time
the log files are backed up and removed from the RDU. Each hourly performance
log file will be rotated at 12 a.m. each day, or if the file size exceeds 250
MB. 2.1.2 Audit Logs
|
The audit logging is
output to the file "pmg-audit.log" and is stored in the directory
/rms/log/pmg.
The audit logs are used to identify the workflow from the receipt of a PMG
message to the response back to the OSS. The audit logs will be rotated at 12
a.m. each day or if larger than 250 MB in size.
 Note |
The individual logs
are maintained on the RDU for 60 days, at which time they are backed up and
removed from the RDU.
|