-
Notifications
You must be signed in to change notification settings - Fork 295
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
Error generating alerts on Iris | 'NoneType' object has no attribute 'removesuffix' #1457
Comments
Thanks for reporting this @rober-fuji. I reviewed the IRIS alerter and see a problem. @malinkinsa, in the IRIS PR you submitted last year, there's a bug where the IOC fetcher loop is overwriting the rule configuration, causing subsequent alerts to throw errors and fail to alert. Specifically, this line: elastalert2/elastalert/alerters/iris.py Line 67 in 23aab84
is fetching a value from the matched document, and then storing that looked up value over the top of the original lookup key. Given this config:
If that fetched value wasn't found in the document then a
Notice how I think the code should be using a deep clone of the IOC object and modifying/appending that, rather than using the original rule config. CC: @gregorywychowaniec-zt, since you recently made a change in this area and may have some input or time to help prepare a fix. |
Unfortunately, I haven't watched it yet. I'll try to look closer to the middle of the month :( |
Any update on this? |
Unfortunately, I still haven't had the time to address this issue. :( |
Same for me, I'm not on this topic at the moment. I will reopen this topic on my side in a few weeks, so if it was not fixed at that time, I will keep an eye on it. |
Hello, I will restart IRIS project soon so I will look for this issue in the next few weeks |
Copying the record data into a new private variable resolves the issue.
Thanks you @bvirgilioamnh for taking the time to fix this issue, and for the several other IRIS alerter improvements. Your efforts are appreciated! |
Good morning,
An attempt has been made to run elastalert on Docker, version 2.2, with the following file:
The first alert pops up in Iris, including its IoCs and everything is correct, but when the second alert pops up, it appears without IoCs and the following exception pops up
In this example there is only one match and no error occurs, the alert is generated correctly.
In this example there is more than one hit and the same error is generated.
This happens when the following command is used:
elastalert-test-alert name-of-file.yaml --alert
The text was updated successfully, but these errors were encountered: