webhead404

As discussed I believe a good place to look for this issue is in the lighttpd proxy config. I confirmed this in 7.11 but didn't test 7.12. Here is a...

You can modify package.json in the plugin to represent 7.2.0. ie ``` { "name": "elastalert-kibana-plugin", "version": "1.0.4", "description": "Create, test and edit ElastAlert rules within Kibana.", "main": "index.js", "license": "SEE...

I might have got lucky. All Kibana does is extract the zip to the proper directory and my cluster was already on 7.1. after upgraded my cluster I changed the...

I was using 7.1 and upgraded to Kibana 7.2. This broke the plugin so once stopping Kibana again I edited the file and restarted it. Then it worked fine. On...

Still experiencing this with latest plugin for Kibana 7.1.0

FYI we are using the elastalert 3.0.0-beta.0. Running that command didn't seem to work for me.

sudo docker run -d -p 3030:3030 -p 3333:3333 -v `pwd`/config/elastalert.yaml:/opt/elastalert/config.yaml -v `pwd`/config/elastalert-test.yaml:/opt/elastalert/config-test.yaml -v `pwd`/config/config.json:/opt/elastalert-server/config/config.json -v `pwd`/opt/elastalert/rules:/opt/elastalert/**rules:rw** -v `pwd`/rule_templates:/opt/elastalert/rule_templates --net="host" --name elastalert bitsensor/elastalert:3.0.0-beta.0 Adding the :rw option didn't work for me.

My config was pointed at /opt/elastalert/rules instead of the current directory with /rules. It made perfect sense after I quit screwing around with Docker. https://media.giphy.com/media/xT5LMzIK1AdZJ4cYW4/giphy.gif