-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Logstash => MQ => Logstash-index-server => ES => kibana #2395
Comments
Hi! Thanks for reporting, we're going to investigate. Is this a different situation than the one you reported yesterday in #2387? |
Hi, Yes both are same scenario . |
Hi, Could you please update me the status. Thanks On Thursday, January 22, 2015, João Duarte [email protected] wrote:
|
Could you please confirm is it bug? or my mistake. Please guide me. Thanks On Saturday, January 24, 2015, Karthi Keyan [email protected] wrote:
|
Hi, Any update. |
For Logstash 1.5.0, we've moved all plugins to individual repositories, so I have moved this issue to logstash-plugins/logstash-input-gelf#11. Let's continue the discussion there! :) |
Hi,
I am using logstash 1.4.2 on centos 6.5
My input format is gelf
input {
gelf {
host => "127.0.0.1"
port => 12201
type => "gelf"
}
}
filter {
}
output {
MQ details
}
It has to pass the data to MQ . But the error indicate it couldn't parse the data from the json input . And the data not going to MQ servers. It get dropped with the below error.
:message=>"Gelfd failed to parse a message skipping", :exception=>#, :backtrace=>["/opt/logstash/vendor/bundle/jruby/1.9/gems/gelfd-0.2.0/lib/gelfd/parser.rb:14:in parse'", "/opt/logstash/lib/logstash/inputs/gelf.rb:83:inudp_listener'", "/opt/logstash/lib/logstash/inputs/gelf.rb:60:in run'", "/opt/logstash/lib/logstash/pipeline.rb:163:ininputworker'", "/opt/logstash/lib/logstash/pipeline.rb:157:in `start_input'"], :level=>:warn}
Test input data is ,
echo '{"version": "1.1","host":"example.org","short_message":" what is going on","full_message":"Hello ","level":1,"_user_id":9001,"_some_info":"foo","_some_env_var":"bar"}' | nc -w 1 -u localhost 12201
Am not sure what is the wrong in this . could you please guide me to fix this issue .
Thanks .
The text was updated successfully, but these errors were encountered: