TimeZone arg get capsed in parse_date call

Graylog2 / graylog-plugin-pipeline-processor

[DEPRECATED] Graylog Pipeline Message Processor Plugins

https://www.graylog.org/

GNU General Public License v3.0

21 stars 15 forks source link

TimeZone arg get capsed in parse_date call #100

Closed hc4 closed 8 years ago

hc4 commented 8 years ago

Problem description

It was OK before update.

Environment

Graylog Version: 2.1.0 (62db7e0)
Pipeline Processor plugin version: 1.1.0

hc4 commented 8 years ago

Actualy I can't configure correct timezone now. Where can I get list of all timezones?

UTC+3 not working GMT+3 not working Etc/GMT+3 not working

I'm lost :)

hc4 commented 8 years ago

Found solution. Set timezone to "+03"

kroepke commented 8 years ago

The issue is that we chose to uppercase the timezone because the parser requires exact matches for "UTC", e.g. I guess we need a lookup table for the zones :/

joschi commented 8 years ago

@kroepke I don't get the reason for using the upper case version of the timezone. Could you please elaborate on that?

kroepke commented 8 years ago

@joschi people were trying utc and expected that to work. That lead me to the mistake of simply uppercasing the timezone ID, but I forgot about the geographic names. I've replaced it with a static lookup map now and added tests (see PR)