Open mukeshchouhan opened 5 years ago
you are using the bitsensor-fork of elastalert, and I too encountered these errors on using it. The Yelp Official Elastalert is working fine though.
Thanks @abhishekjiitr for the reply.
Did you find any workaround to fix it? I preferred bitsensor-fork of elastalert as it was easy to setup and comes with kibana plugin.
Couldn't find any fix for it. It worked fine though, but kept on displaying the ERROR messages. I was just experimenting and now using the official ElastAlert. You can close this issue here, and open it on the Bitsensor fork Git Repo if you want.
Hey @mukeshchouhan , Did you resolve this problem at least workaround on your environments? I got same problem. Especially, an alert's filter query took long time. The other rules working correct and doesn't have time problem.
@hazelcakli
07:06:02.218Z ERROR elastalert-server: ProcessController: ERROR:root:Error writing alert info to Elasticsearch: TransportError(429, u'es_rejected_execution_exception', u'rejected execution of org.elasticsearch.transport.TransportService$7@61f5f91d on EsThreadPoolExecutor[name = server.********.com/bulk, queue capacity = 200, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@1f0b4b9a[Running, pool size = 56, active threads = 56, queued tasks = 294, completed tasks = 2310423249]]')
this error was resolved by setting up below in elastalert.yaml file
es_send_get_body_as: POST
I am still getting below errors but my alerts are coming fine. so that can be ignored.
07:06:02.219Z ERROR elastalert-server: ProcessController: WARNING:root:Querying from 2018-12-27 06:59 UTC to 2018-12-27 07:06 UTC took longer than 0:00:05!
I am getting below error in ElastAlert. I am using latest ElastAlert Image My Elastic search Version is 6.2.3 I have around 48 Rules Configured in ElastAlert