-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errno 99 when testing rule with "Send real alerts" #196
Comments
Hi, @scott-oit Fixed issues
I'm continuously testing for merging my fixes to original repo. |
@daichi703n That is working! Thank you! |
@scott-oit Great! |
I tried it, but I get the following error when testing rules, now. I'm swapped back to
|
@scott-oit Thanks. Hmm... I'll re-test. Please use |
It appears this is broken in ElastAlert itself. In Old definition:
|
I'm closing this issue since Praeco isn't the issue. |
I found that the problem that occurs in the @scott-oit environment can be solved by changing the source code of ElastAlert as follows. test_rules.py Line86 res = es_client.search(index, size=1, body=query, ignore_unavailable=True) Line112 res = es_client.count(index, doc_type=doc_type, body=count_query, ignore_unavailable=True) Line 156 res = es_client.search(index, size=args.max_query_size, body=query, ignore_unavailable=True) |
|
If I enable "Send real alerts", I get the following:
If I save the rule, it seems to function just fine. I still get alerts like normal. I'm using basic SMTP, no auth, no special port. This is the only thing set in my base_rule.config. I've also tried the IP.
I'm running it Praeco via Docker. Any ideas? Where can I look for logs? I'm hoping it's simple.
Thank you!
The text was updated successfully, but these errors were encountered: