Jordan Sissel

Sorry for the delays in review, and thank you for helping improve fpm! This seems like a fairly significant behavioral change. I have two primary concerns so far: 1) It's...

@problematiq not sure if this helps, but I was reading the docs just now and found what may help you: https://github.com/TheHive-Project/TheHiveDocs/blob/master/admin/configuration.md Setting `search.ssl.enabled` in your `search { ... }` config,...

> Many (most?) Linux-ey text editors create backup files, named as the original filename plus a ~ suffix The last time I did research on this showed that vim, emacs,...

Based on what you've provided, I agree this is a bug.

#50 is a duplicate

The grok implementation in Ingest won't work for Logstash because: * it [combines patterns](https://github.com/elastic/elasticsearch/blob/master/modules/ingest-common/src/main/java/org/elasticsearch/ingest/common/GrokProcessor.java#L122) with regexp union `|` which prevents `break_on_match => false` from working in Logstash gork. * cannot...

I think I understand what you want (the grok pattern for a given event to be sourced from a field in that event). However, I'm not sure I understand what...

The syntax you are using (?...) is a feature provided by the library Grok is using (Joni, a regular expression engine). The error is coming from Joni and is a...

I don't know what backwards incompatibility we would cause by introducing this change. It would be useful to know if anyone is relying on trailing whitespace in their patterns.

I agree with you on the expected output. This behavior seems like a new bug, which may be expected given we did some internal changes to the grok library to...