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

Fix drop_fields when the first field is unknown #2685

Merged
merged 1 commit into from
Oct 5, 2016

Conversation

monicasarbu
Copy link
Contributor

This PR is meant to fix the issue #2664 that appears in case the first field from the drop_fields is not known. The following configuration example should work now:

processors:
  - drop_fields:
       fields: ["foo.bar", "proc.sss", "proc.cpu"]

In this example, the Beats are printing a debugging message on the screen that foo and sss from proc.sss were unknown, and it will remove only proc.cpu from the exported event.

Copy link
Contributor

@tsg tsg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@monicasarbu monicasarbu added the needs_backport PR is waiting to be backported to other branches. label Oct 5, 2016
@tsg tsg merged commit b2a640b into elastic:master Oct 5, 2016
monicasarbu added a commit to monicasarbu/beats that referenced this pull request Oct 5, 2016
@monicasarbu monicasarbu deleted the fix_processors_unknown_first_field branch October 5, 2016 19:31
@monicasarbu monicasarbu removed the needs_backport PR is waiting to be backported to other branches. label Jan 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants