Please sign in to comment.
Improve error when ES ingest node plugins are not loaded
We're parsing the Elasticsearch JSON error and try to produce an error message that is as helpful as possible. The following cases are detected: * A plugin providing a processor is missing. In case the plugin is one of `ingest-geoip` or `ingest-user-agent`, we can also suggest the command that installs them. * Elasticsearch < 5.0. We now detect this and tell the user that ES 5.0 is required by FBM. A drawback of this approach is that if both the GeoIP and User-Agent plugins are missing, only one will be reported. This might get solved by including the user-agent one in ES, or by improving the error we get from ES, or by us querying the node stats API Note: this contains a change in the ES client, which makes it return the body in case of errors. I think we need that part anyway, otherwise we often show errors like `400 Bad request` without any other details. I tried to do a minimal change there, I hope I didn't introduce any changes in behaviour.
- Loading branch information...
Showing with 126 additions and 17 deletions.