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

Provide a key=value function #38

Closed
tokred opened this Issue Jun 21, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@tokred

tokred commented Jun 21, 2016

In order to replace a key=value input extractor, I would be happy if you could provide an equivalent key=value rule function, e.g.

parse_kv( to_string($message.myfield) );

For cases where you do not control the naming of keys (or the keys are ambiguous/generic like "source", "destination", etc.), an optional prefix parameter would be helpful to make field names distinctive, e.g.

parse_kv( value: x, prefix: "myservice_" );
@jalogisch

This comment has been minimized.

Member

jalogisch commented Jul 27, 2016

get inspiration from logstash kv parser

some of the advanced could be very handy (trim, trimkey, include_key)

kroepke added a commit that referenced this issue Aug 4, 2016

kroepke added a commit that referenced this issue Aug 8, 2016

@bernd bernd closed this in #77 Aug 8, 2016

bernd added a commit that referenced this issue Aug 8, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment