-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
No logs from tcp input #588
Comments
Kibana doesn't have an knowledge of logstash config or inputs, in fact it doesn't require logstash at all. I don't really don't have enough information to help you debug here. #logstash on freenode is really the best place to debug config issues, though I can see from here that you're missing a } to close your input section |
I had } in there it was next a commented block so it didn't get copied. I will try to debug tomorrow. Maybe I will find something else. |
Such a stupid mistake. So I had changed the default dashboard to @timestamp with @fields.timestamp because all of our linux log lines have timestamp in them and I sort and filter on that rather than timestamp of logstash server. |
Hi Rashid,
kibana3 has been working flawlessly until today. I am trying to get logs from windows servers via nxlog > logstash > elastic > kibana.
I can see the logs are making it to elastic search for tcp input but I can't see anything in kibana. I tried source filters, messages,type. No dice!
I can see other logs in kibana that are coming from linux boxes via logstash > redis > elastic >kibana.
Here is what logstash server config looks like. I don't think there is anything wrong with the config else the logs wouldn't make it to elastic.
I am using logstash-1.1.13.
I have run out of options. Any help is much appreciated.
input {
redis {
host => "127.0.0.1"
type => "redis-input"
data_type => "list"
key => "logstash"
}
tcp {
mode => "server"
charset => "UTF-8"
host => "192.168.128.146"
port => "5672"
type => "geostream_logs"
}
output {
#stdout {debug => "true" }
elasticsearch { host => "127.0.0.1" }
}
The text was updated successfully, but these errors were encountered: