Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect coerce function with duplicate capture keys in Grok patterns #7383

Closed
micoq opened this issue Jun 8, 2017 · 1 comment
Closed

Comments

@micoq
Copy link

micoq commented Jun 8, 2017

Hello,

I'm not sure if it's the right repository to post this issue since the grok library is included in Logstash.

On any version of Logstash, if you have two or more fields (or named captures) in a grok pattern with the same name and using a coerce function (like "int" or "float"), this function si not applied all the time (even if the function is the same in each field).

Here is the complete issue with a quick fix : jordansissel/ruby-grok#29

@jsvd
Copy link
Member

jsvd commented Aug 4, 2017

there seems to already be an issue open on the grok filter side: logstash-plugins/logstash-filter-grok#119, closing this

@jsvd jsvd closed this as completed Aug 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants