Support customizing the default time zone when parsing dates in syslog messages

Description

Currently, when the date from a syslog message is parsed by OpenNMS and this date does not include a time zone, we assume that the date is in the same timezone as the OpenNMS system is currently configured.

Such a message may look like:

<11>Mar 22 14:24:49 node1 last message repeated 25 times

It should be possible to configure this behavior and set a specific timezone to use in this case. This should work when using either the CustomSyslogParser, or the RadixTreeParser.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Patrick Schweizer August 10, 2018 at 11:07 PM

Jesse White August 1, 2018 at 5:28 PM

Reopening this one, the functionality does work with the CustomSyslogParser, but does not currently work with the RadixTreeParser.

Patrick Schweizer June 1, 2018 at 1:26 AM

Patrick Schweizer June 1, 2018 at 1:24 AM

@j-white, you are right. I changed the code accordingly. I used syslogd-configuration.xml to make the TimeZone configurable.

Jesse White May 28, 2018 at 2:15 AM

I found https://github.com/OpenNMS/opennms/pull/1368 which seems to explain the current behavior.

Ideally the option would be wired through syslogd-configuration.xml.

Fixed

Details

Assignee

Reporter

Sprint

Priority

PagerDuty

Created May 23, 2018 at 1:27 PM
Updated August 14, 2018 at 12:22 AM
Resolved August 14, 2018 at 12:22 AM

Flag notifications