Uploaded image for project: 'JBoss Log Manager'
  1. JBoss Log Manager
  2. LOGMGR-122

Syslog handler is not generating correct timestamp format

XMLWordPrintable

    • Hide
      1. Configure Wildfly to use an RFC5424 syslog handler. 
        /subsystem=logging/custom-handler=LOGSTASH:write-attribute(name=properties,value={serverHostname=myhost,port=5001,appName=wildfly,protocol=TCP,maxLength=1048576,useMessageDelimiter=true,messageDelimiter="\n[/SYSLOG]\n"})
/subsystem=logging/root-logger=ROOT:write-attribute(name=handlers,value=["CONSOLE","LOGSTASH"])
      2. Set the system clock to (or wait until) any date in October.
      3. Make Wildfly log something to the syslog handler.
      4. Check that the format should be "yyyy-MM-dd'T'HH:mm:ss.SSSXXX", but instead has an extra zero before the month.
      Show
      Configure Wildfly to use an RFC5424 syslog handler. /subsystem=logging/custom-handler=LOGSTASH:write-attribute(name=properties,value={serverHostname=myhost,port=5001,appName=wildfly,protocol=TCP,maxLength=1048576,useMessageDelimiter=true,messageDelimiter="\n[/SYSLOG]\n"}) /subsystem=logging/root-logger=ROOT:write-attribute(name=handlers,value=["CONSOLE","LOGSTASH"]) Set the system clock to (or wait until) any date in October. Make Wildfly log something to the syslog handler. Check that the format should be "yyyy-MM-dd'T'HH:mm:ss.SSSXXX", but instead has an extra zero before the month.
    • Low

      The Syslog handler is outputting an extra zero before the month in the header timestamp for RFC5424, specifically for October.

      Checking Github, I have noticed that the month number is tested for double digit before being offset, so a zero is added for October (month 9 for java.util.Calendar), then offset for proper display (month "10" for ISO8601), resulting in a three-digit month ("010").

              jperkins-rhn James Perkins
              ricardo.kagawa Ricardo Kagawa (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: