Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

Weblogic Log Track not catching entire line and date is set to 0 if timestamp cannot be parsed.

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 4.5.1.2
  • Fix Version/s: 4.5.2, 4.6
  • Component/s: Plugins
  • Environment:
    WebLogic
  • Case Links:
    none
  • Regression:
    No
  • Tags:

Description

  1. If the timestamp cannot be parsed due to it being in a different format, it will set the timestamp to 0 (which is Dec 31 in 1969).
  2. The entire LogEvent message is not being added to the message attribute.

This makes it so the user does not know the reason for the Event.

For example:

Log file text:

####<4/05/2011 07:59:45 AM EST> <Info> <Health> <ecsydtst01> <tandcTestServer1> <weblogic.GCMonitor> <<anonymous>> <> <> <1304459985815> <BEA-310002> <64% of the total memory in the server is free>
####<4/05/2011 08:01:45 AM EST> <Info> <Health> <ecsydtst01> <tandcTestServer1> <weblogic.GCMonitor> <<anonymous>> <> <> <1304460105826> <BEA-310002> <85% of the total memory in the server is free>
####<4/05/2011 09:03:45 AM EST> <Info> <Health> <ecsydtst01> <tandcTestServer1> <weblogic.GCMonitor> <<anonymous>> <> <> <1304463825888> <BEA-310002> <74% of the total memory in the server is free>
####<4/05/2011 10:06:45 AM EST> <Info> <Health> <ecsydtst01> <tandcTestServer1> <weblogic.GCMonitor> <<anonymous>> <> <> <1304467605990> <BEA-310002> <85% of the total memory in the server is free>
####<3/05/2011 10:29:01 AM EST> <Critical> <Health> <ecsydtst01> <tandcTestServer1> <weblogic.GCMonitor> <<anonymous>> <> <> <1291875019751> <BEA-310003> <Free memory in the server is 3,704,096 bytes. There is danger of OutOfMemoryError>
####<3/05/2011 10:29:02 AM EST> <Error> <Health> <ecsydtst01> <tandcTestServer1> <weblogic.GCMonitor> <<anonymous>> <> <> <1291875019751><BEA-310003> <Free memory in the server is 3,704,096 bytes. There is danger of OutOfMemoryError>
####<3/05/2011 10:29:03 AM EST> <Warning> <Health> <ecsydtst01> <tandcTestServer1> <weblogic.GCMonitor> <<anonymous>> <> <> <1291875019751> <BEA-310003> <Free memory in the server is 3,704,096 bytes. There is danger of OutOfMemoryError>
####<3/05/2011 10:29:04 AM EST> <Info> <Health> <ecsydtst01> <tandcTestServer1> <weblogic.GCMonitor> <<anonymous>> <> <> <1291875019751> <BEA-310003> <Free memory in the server is 3,704,096 bytes. There is danger of OutOfMemoryError>
####<3/05/2011 10:39:01 AM EST> <Critical> <Health> <ecsydtst01> <tandcTestServer1> <weblogic.GCMonitor> <<anonymous>> <> <> <1291875019751> <BEA-310003> <Free memory in the server is 3,704,096 bytes. There is danger of OutOfMemoryError>
####<3/05/2011 10:39:02 AM EST> <Error> <Health> <ecsydtst01> <tandcTestServer1> <weblogic.GCMonitor> <<anonymous>> <> <> <1291875019751><BEA-310003> <Free memory in the server is 3,704,096 bytes. There is danger of OutOfMemoryError>
####<3/05/2011 10:39:03 AM EST> <Warning> <Health> <ecsydtst01> <tandcTestServer1> <weblogic.GCMonitor> <<anonymous>> <> <> <1291875019751> <BEA-310003> <Free memory in the server is 3,704,096 bytes. There is danger of OutOfMemoryError>
####<3/05/2011 10:39:04 AM EST> <Info> <Health> <ecsydtst01> <tandcTestServer1> <weblogic.GCMonitor> <<anonymous>> <> <> <1291875019751> <BEA-310003> <Free memory in the server is 3,704,096 bytes. There is danger of OutOfMemoryError>

Plugin Output:

[Wed Dec 31 18:00:00 CST 1969] (Health) 1304459985815> <BEA-310002> <64% of the total memory in the server is free
[Wed Dec 31 18:00:00 CST 1969] (Health) 1304460105826> <BEA-310002> <85% of the total memory in the server is free
[Wed Dec 31 18:00:00 CST 1969] (Health) 1304463825888> <BEA-310002> <74% of the total memory in the server is free
[Wed Dec 31 18:00:00 CST 1969] (Health) 1304467605990> <BEA-310002> <85% of the total memory in the server is free
[Wed Dec 31 18:00:00 CST 1969] (Health) 1291875019751> <BEA-310003
[Wed Dec 31 18:00:00 CST 1969] (Health) 1291875019751><BEA-310003
[Wed Dec 31 18:00:00 CST 1969] (Health) 1291875019751> <BEA-310003
[Wed Dec 31 18:00:00 CST 1969] (Health) 1291875019751> <BEA-310003
[Wed Dec 31 18:00:00 CST 1969] (Health) 1291875019751> <BEA-310003
[Wed Dec 31 18:00:00 CST 1969] (Health) 1291875019751><BEA-310003
[Wed Dec 31 18:00:00 CST 1969] (Health) 1291875019751> <BEA-310003
[Wed Dec 31 18:00:00 CST 1969] (Health) 1291875019751> <BEA-310003

Activity

Hide
Jason Konicki added a comment -

Fixed the nextField method from unintentionally stripping off the event message in certain scenarios.

Show
Jason Konicki added a comment - Fixed the nextField method from unintentionally stripping off the event message in certain scenarios.
Hide
Jason Konicki added a comment -
  1. The date format is now configurable in the case of the log file is configured differently from the defaulted date format.
    1. Agent property can be used to set the date format to match the weblogic timestamp format. The default is "MMMM d, yyyy h:mm:ss a z", but the property can be configured using
      weblogic.parser.datetime.format
    2. If the format is not able to be parsed a warning message will be added to the agent log describing how to fix the date format and it will set the event to the "current system time" until the date format is fixed.
  2. The full message will not be added to the event object.
Show
Jason Konicki added a comment -
  1. The date format is now configurable in the case of the log file is configured differently from the defaulted date format.
    1. Agent property can be used to set the date format to match the weblogic timestamp format. The default is "MMMM d, yyyy h:mm:ss a z", but the property can be configured using
      weblogic.parser.datetime.format
    2. If the format is not able to be parsed a warning message will be added to the agent log describing how to fix the date format and it will set the event to the "current system time" until the date format is fixed.
  2. The full message will not be added to the event object.
Hide
Jason Konicki added a comment -

The previous comment should have been "2. The full message will now be added to the event object."

Show
Jason Konicki added a comment - The previous comment should have been "2. The full message will now be added to the event object."

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    2 years, 49 weeks, 1 day ago