Grok custom pattern problem (Can't start with a number) - Logstash 1.5 · elastic/logstash#3353

(0 comments) (0 reactions) (0 assignees)Ruby (14,197 stars) (3,496 forks)batch import

bughelp wanted

説明

Hi,

it was previously OK with Logstash 1.4.2 it now BUG with Logstash 1.5

My pattern file contain a grok pattern with a name starting with a number

Step to reproduce :

1 - Add this pattern to grok patterns :

2 - Start Logstash with the following commands :

./logstash agent -e 'filter { grok { match => ["message","%{123_DATE:year}"] } }'
./logstash agent -e 'filter { grok { match => ["message","%{YEAR_DATE:year}"] } }'

3 - RESULTS

Please correct this or just write it somewhere in red inside the documentation.

EDIT : Please note that a name like this : DATE_123_CUSTOM is ok because the name is not starting with a number. (I've just made the test)

M0dM

技術スタック: ruby
領域: backend
Issue 種別: bug
難度: 3
推定時間: 1-3 hours
活動状況: stale
明確さ: clear
前提条件: familiarity with Logstash grok filterunderstanding of Ruby regex named groups
初心者向け度: 70
調査方針: Investigate the Logstash grok filter code, likely in the Logstash Ruby source (e.g., lib/logstash/filters/grok.rb). The error 'invalid group name' suggests the regex generation rejects pattern names starting with a digit. A fix could involve allowing such names or adding a note in documentation. Check the changelog between 1.4.2 and 1.5 to identify the change that introduced this limitation.