Jordan Sissel
Jordan Sissel
> To solve this use case, you can use %{@source_host}.%{@type} instead. `%{@source_host}` etc hasn't been a field since Logstash 1.1.13 We should evaluate if this paragraph (about tcp clients) is...
(This issue was originally filed by @rajacm2020 at https://github.com/elastic/logstash/issues/2789) --- I am using using logstash to receive logs from the forwarder.I am using multiline filter to match the logs and...
(This issue was originally filed by @ibigpapa at https://github.com/elastic/logstash/issues/2262) --- "Moving https://logstash.jira.com/browse/LOGSTASH-631 to Github Rails production.log has two empty lines in between each event. My multiline filter with pattern "\n\n"...
(This issue was originally filed by @coolacid at https://github.com/elastic/logstash/issues/1808) --- Multiline documentation should be clearer that it's not thread safe - and that one needs to be careful to ensure...
(This issue was originally filed by @colinsurprenant at https://github.com/elastic/logstash/issues/1425) --- the field merging details do not belong into the json filter
(This issue was originally filed by @ndelucin at https://github.com/elastic/logstash/issues/1877) --- Hi, I discovered a strange issue regarding mutate evaluation. Don-t know if its a bug or a normal behavior of...
(This issue was originally filed by @weaseal at https://github.com/elastic/logstash/issues/3197) --- I added this in a logstash config file (notice "int", not integer, thanks to torrancew on irc for catching my...
(This issue was originally filed by @VarunMaheshwari at https://github.com/elastic/logstash/issues/2797) --- example: "message" => "SolrTime,20" my configuration looks like following: filter { grok{ match => ["message","%{WORD:component},%{INT:time:int}"] } mutate{ add_field => [...