You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While debugging an issue with Curator not deleting for space (#10464), I noticed hundreds of lines like:
2023-06-01 14:10:38,175 ERROR Unable to complete action "close". No actionable items in list: <class 'curator.exceptions.NoIndices'>
2023-06-01 14:10:52,986 ERROR Unable to complete action "close". No actionable items in list: <class 'curator.exceptions.NoIndices'>
They were all the close and warm actions, whereas the delete actions all showed something like:
2023-06-01 14:10:06,118 INFO Skipping action "delete_indices" due to empty list: <class 'curator.exceptions.NoIndices'>
Obviously, this is an expected outcome, and not a true error, but it appears the delete action uses ignore_empty_list: True whereas the close and warm actions use continue_if_exception: False.
Security Onion Solutions devs, is there a reason behind this? If not, would it make sense to use ignore_empty_list: True on all actions? In my testing, changing selected close actions to ignore_empty_list: True removes the error and I haven't noticed any ill effects. Being able to search the log for 'ERROR' and only see actual errors would make troubleshooting easier.
While debugging an issue with Curator not deleting for space (#10464), I noticed hundreds of lines like:
They were all the close and warm actions, whereas the delete actions all showed something like:
Obviously, this is an expected outcome, and not a true error, but it appears the delete action uses
ignore_empty_list: True
whereas the close and warm actions usecontinue_if_exception: False
.Security Onion Solutions devs, is there a reason behind this? If not, would it make sense to use
ignore_empty_list: True
on all actions? In my testing, changing selected close actions toignore_empty_list: True
removes the error and I haven't noticed any ill effects. Being able to search the log for 'ERROR' and only see actual errors would make troubleshooting easier.Originally posted by @petiepooo in #10496
The text was updated successfully, but these errors were encountered: