Issues
- Snmp collect reversing to unticked after a few hoursNMS-15117Resolved issue: NMS-15117Alex May
- Password in collectd.log fileNMS-13183Resolved issue: NMS-13183Christian Pape
- RRD files for SNMP data are not created until a Service RestartNMS-12974Resolved issue: NMS-12974Chandra Gorantla
- Node level menu option to turn on/off debug level logging of collected and pollerd for nodeNMS-11886
- SNMP sysID not recognizedNMS-11728
- Wrong data type for certain Cassandra JMX countersNMS-10352Resolved issue: NMS-10352Brynjar Eide
- MBean "TasksCompleted" for Collectd and Pollerd returns wrong countersNMS-9741Resolved issue: NMS-9741Benjamin Reed
- Add ability to collect data from syslog messagesNMS-9400
- config-tester doesn't validate missing XML attributesNMS-7882
- XML collector in JSON mode assumes all element content is StringNMS-7243Resolved issue: NMS-7243Alejandro Galue
- multiple wmi-collection definitions not supported in wmi-datacollection-config.xmlNMS-5655
- Not seeing mib2 interface threshold alerts (Draytek Vigor 2710/2830)NMS-5303
- Enhance JMXSecureCollector with RMI protocol supportNMS-5205Resolved issue: NMS-5205Ronny Trommer
13 of 13
SyslogParser should not assume UTC timestamps
Fixed
Description
Acceptance / Success Criteria
None
Lucidchart Diagrams
Details
Assignee
Seth LegerSeth LegerReporter
Seth LegerSeth LegerComponents
Sprint
NoneFix versions
Affects versions
Priority
Critical
Details
Details
Assignee
Seth Leger
Seth LegerReporter
Seth Leger
Seth LegerComponents
Sprint
None
Fix versions
Affects versions
Priority
CriticalPagerDuty
PagerDuty
PagerDuty
Created March 8, 2017 at 10:56 AM
Updated March 15, 2017 at 10:29 AM
Resolved March 15, 2017 at 10:22 AM
Activity
Show:
Seth LegerMarch 15, 2017 at 10:22 AM
PR merged, marking as fixed.
commit 5b0b2f3dc95500447ede89e8ef183a3b06ae523b
The SyslogParser code assumes that all timestamps without a timezone (ie. Feb 28 12:00:00) are in the UTC timezone. This is incorrect: all syslog messages are sent with the local time of the sending system. If all of your syslog agents are operating in UTC, then we parse the dates correctly but if they have a different time zone, the timestamps will be skewed.
We should change the code to use the local timezone of the OpenNMS machine when parsing timestamps which, in most cases, will match the timezone of the sending systems. Note that if you want to use UTC, you can continue to do so by setting the timezone of the OpenNMS machine and all syslog systems to UTC.
If you are operating syslog systems in different timezones than the OpenNMS machine, you should migrate to a syslog timestamp format that includes the timezone (ISO 8601).