Skip to content

use the filter with Logstash 5.x#16

Closed
vktor18 wants to merge 3 commits intologstash-plugins:masterfrom
vktor18:master
Closed

use the filter with Logstash 5.x#16
vktor18 wants to merge 3 commits intologstash-plugins:masterfrom
vktor18:master

Conversation

@vktor18
Copy link

@vktor18 vktor18 commented Mar 1, 2017

I simply changed few things to make this filter supporting logstash 5.x

based on -->https://github.com/elastic/logstash/blob/5.x/docs/static/breaking-changes.asciidoc#ruby-filter-and-custom-plugin-developers

Thanks!

@vktor18
Copy link
Author

vktor18 commented Mar 1, 2017

i don't understand why travis is having trouble..

@jsvd
Copy link
Member

jsvd commented Mar 1, 2017

travis is having some issues https://www.traviscistatus.com/

@bitsofinfo
Copy link
Contributor

This PR should also be incorporated #11

@vktor18
Copy link
Author

vktor18 commented Mar 2, 2017

Hi guys, I want to report a problem that I'm facing now using the cipher filter.

As far as i use the filter with a basic configuration such as input from file, cipher filter for encrypting a field and an output file, works pretty well.

When I switch to a pipeline configuration more complex (3 inputs from rabbit, complex logic filter, output elasticsearch and file) it returns an exception

Exception catch on cipher filter {:event=>2017-03-02T10:46:47.576Z %{host} %{message}, :error=>#<NoMethodError: undefined method iv=' for nil:NilClass>}`

The fact that the filter works fine using another pipeline makes me confused about what possible error I'm facing here....

Any suggestions?

@vktor18
Copy link
Author

vktor18 commented Mar 2, 2017

Ok the issue is definitely when I use rabbitmq as input for logstash...

@vktor18
Copy link
Author

vktor18 commented Mar 2, 2017

sorry, I fixed the issue. It was missing a configuration for rabbitmq input

@vktor18 vktor18 closed this Mar 8, 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

Successfully merging this pull request may close these issues.

3 participants