+14Hi All,
I have a block for log collection, where I am using a flow to check whether the UDM action JSON is not empty. If it isn't, I add a CSV case wall attachment. However, I noticed that the UDM result is empty, yet it is still routing to branch one, even though the condition is set to proceed only if the JSON is not empty.
Best answer by ylandovskyy
I'm seeing an example where neither not empty or != "" works correctly for a JSON result. It's with the Chronicle UDM Query. I'm wondering if something has changed with this since your reply in January. Thanks
JSON Result might still exist as empty list, which I believe is the situation here. So, if you want to create a stable condition, then my suggestion would be to do:
As "{" will only exist if JSON Result contains an actual JSON object inside of it.
+7That condition should evaluate correctly if you change it to ` != "" `
+7The empty and notempty conditions rely on a field existing to properly evaluate the contents. In this case the 'Execute UDM Query' action only calls siemplify.result.add_result_json if events are returned in the result, so when there aren't events the json result field doesn't get created, which causes the condition to not evaluate properly.
Unfortunately this behavior isn't standardized between all actions. Some will call the add_result_json function with no results, which will create the field and leave it blank; and your original condition would work.
To differentiate whether those empty results are actually created you can either look in the IDE at the action and try to understand logic around the siemplify.result.add_result_json command or use the Siemplify - Case Comment action with the json results placeholder in a playbook.
With the Case Comment action the the comment will return an empty string if the results exist but are empty, or will put the placeholder string as the comment if the field doesn't exist.
+4The empty and notempty conditions rely on a field existing to properly evaluate the contents. In this case the 'Execute UDM Query' action only calls siemplify.result.add_result_json if events are returned in the result, so when there aren't events the json result field doesn't get created, which causes the condition to not evaluate properly.
Unfortunately this behavior isn't standardized between all actions. Some will call the add_result_json function with no results, which will create the field and leave it blank; and your original condition would work.
To differentiate whether those empty results are actually created you can either look in the IDE at the action and try to understand logic around the siemplify.result.add_result_json command or use the Siemplify - Case Comment action with the json results placeholder in a playbook.
With the Case Comment action the the comment will return an empty string if the results exist but are empty, or will put the placeholder string as the comment if the field doesn't exist.
I'm seeing an example where neither not empty or != "" works correctly for a JSON result. It's with the Chronicle UDM Query. I'm wondering if something has changed with this since your reply in January. Thanks
+16I'm seeing an example where neither not empty or != "" works correctly for a JSON result. It's with the Chronicle UDM Query. I'm wondering if something has changed with this since your reply in January. Thanks
JSON Result might still exist as empty list, which I believe is the situation here. So, if you want to create a stable condition, then my suggestion would be to do:
As "{" will only exist if JSON Result contains an actual JSON object inside of it.
+4JSON Result might still exist as empty list, which I believe is the situation here. So, if you want to create a stable condition, then my suggestion would be to do:
As "{" will only exist if JSON Result contains an actual JSON object inside of it.
Awesome. Thanks so much
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
