Details
-
Type:
Enhancement
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 22.0.3, Meridian-2018.1.0
-
Component/s: Event Reception - Syslog
-
Security Level: Default (Default Security Scheme)
-
Sprint:Horizon - May 23rd 2018, Horizon - May 30th 2018, Horizon - June 6th 2018, Horizon - August 8th 2018
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.