You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The LogParser is not able to parse comma separated timestamps like "2017-12-10 12:05:11,962".
It would be helpful to add support for this timestamp format, since ISO 8601 defines the decimal separator as either "a comma or a dot".
Timestamps like "2017-12-10 12:05:11,962" should be parsed by the Telegraf LogParser. Parsing error should not appear.
Use case: [Why is this important (helps with prioritizing requests)]
Logfiles written by third party applications cannot be parsed if they use commas instead of dots to separate fractions of seconds. Since ISO 8601 defines that "a comma or a dot" can be used as a decimal mark, the Telegraf LogParser should support this.
The text was updated successfully, but these errors were encountered:
Feature Request (Workaround)
The LogParser is not able to parse comma separated timestamps like "2017-12-10 12:05:11,962".
It would be helpful to add support for this timestamp format, since ISO 8601 defines the decimal separator as either "a comma or a dot".
Proposal:
As suggested by daniel the LogParser could substitute dot for comma while parsing the file.
See: https://community.influxdata.com/t/timestamp-format-error/3363
Current behavior:
If you try to parse a log file with entries (lines) like this ...
... with a telegraf.conf that looks like this ...
... you will get the following output:
Desired behavior:
Timestamps like "2017-12-10 12:05:11,962" should be parsed by the Telegraf LogParser. Parsing error should not appear.
Use case: [Why is this important (helps with prioritizing requests)]
Logfiles written by third party applications cannot be parsed if they use commas instead of dots to separate fractions of seconds. Since ISO 8601 defines that "a comma or a dot" can be used as a decimal mark, the Telegraf LogParser should support this.
The text was updated successfully, but these errors were encountered: