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
{{ message }}
This repository has been archived by the owner on Dec 14, 2024. It is now read-only.
"All EVAL- configurations within a single props.conf stanza are processed in parallel, rather than in any particular sequence. This means you can't "chain" calculated field expressions, where the evaluation of one calculated field is used in the expression for another calculated field."
Describe the bug
For the
pan:threat
sourcetype we are observing, un-parsedsender
andrecipient
field values in theuser
field.This is due to the fact the Splunk does not allow for chained Field Calculations.
https://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Searchtimeoperationssequence#Calculated_fields
Relevant Config from Props.conf:
Expected behavior
When
src_user
ordest_user
is null,user
will return the following:Current behavior
When
src_user
ordest_user
is null, we will observe the following onuser
:Possible solution
Merge the field calc logic from
sender
andrecipient
into theuser
coalesce logic.Steps to reproduce
Run SPL against smtp traffic that triggered signatures and filter on results that have null values for
src_user
anddest_user
.Your Environment
The text was updated successfully, but these errors were encountered: