#logstash

<http://tinyurl.com/o2dvfbo>; (at www.elasticsearch.org)

somehow, hard-coding a list of fields was not the solution i was hoping for... especially since some of the inputs have dynamic fields...

one index per type would probably make more sense, but ES will puke with so many open indexes. rock, meet hard place.

rastro: this is only an issue with conflicting types of fields for different events

otherwise you have dynamic mapping

new fields are added to the mapping as they come

jsvd: then maybe the problem is with kibana4, because even if i refresh the field mapping there, I still can't use the fields.

"no cached mapping for this field", and refreshing doesn't help.

Hello All -- New to logstash, but managing an existing install. I'm seeing multiple log-lines per logstash message in some searches -- What would be the cause of behavior like that?

jherbst: What do you mean by that?

volter: When I search for a specific tag in kibana I get some results and looking through the 'message' field for the results I'm seeing multiple server log lines per 'message'