-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
added fix to support es5 #865
Conversation
I am sorry that the error still remains. INFO:elastalert:Queried rule IES crash rate Alert from 2017-01-12 02:16 CST to 2017-01-12 02:31 CST: 4960 / 4960 hits |
@Tyoshi14 That is a completely different issue. PR looks good. Thanks. |
Oops, I was too eager. This changes doesn't make sense to me. Index API is different for Elasticsearchand indices API. This is for creating an index. Can you show an actual traceback with this line? |
please find the traceback before the fix. ERROR:root:Error querying for last run: TransportError(400, u'parsing_exception', u'Unknown key for a START_OBJECT in [filter].') after this fix $ elastalert --verbose --rule example_rules/pms_frequency.yaml |
elastalert.py and create_index.py are not the same thing. These functions are not the same thing. In support_es5, that line has already been changed to use index. https://github.com/Yelp/elastalert/blob/support_es5/elastalert/elastalert.py#L1050 @sarakumap are you using the support_es5 branch?? Edit: You are using v0.1.4 not support_es5. |
yes I forked from support_es5 and created a pull request. it works fine now. |
You are not running that branch. From your traceback: |
You'll need to uninstall 0.1.4 and reinstall the support_es5 branch.
|
yes you are correct. it doesn't have the latest changes. let me pull the latest support_es5 and check it. will confirm in a while |
just did that. support_es5 works fine. thanks! |
To fix error to support ES5 issue with id while indexing "Error: elastalert an id must be provided if version type or value are set"