We have searches for 4740 account lockouts not showing as action=lockout but instead as action=modified.
This is important to us as we are trying to configure ES but that's one dashboard where we aren't getting any results.
Where do we go to fix this?
Also whenever you get a a source or field that shows as "unknown" whats the best way to go about fixing these?
Hi @domino30,
yes, calculated fields (like the one you shared) are one of the methods to normalize data.
Let me know if you solved your issue.
Ciao.
Giuseppe
Hi @domino30,
this job is called "normalization", in other words, you have to create some sules (using reneme and calculated fields) to align yur values with the waited ones.
In your case, you have to add to your Add-On a custom calculated field like the following:
| eval action=if(EventCode=4740 AND action="lockout","modified",action)
you can find more infos at https://lantern.splunk.com/Splunk_Platform/Product_Tips/Data_Management/Normalizing_values_to_a_comm... and at https://docs.splunk.com/Documentation/CIM/5.1.1/User/Overview
Ciao.
Giuseppe
Like this?
Hi @domino30,
No, this is the possibility to add fields to a DataModel.
You have to create (usually in an Add-On) a calculated field [Settings > Fields > Calculated Fields] that makes the transformation BEFORE an event is added to a Datamodel.
In other words, the process is the following:
for more infos see at https://docs.splunk.com/Documentation/CIM/5.1.1/User/Overview
Ciao.
Giuseppe
like this? btw its working now just confirming something
Hi @domino30,
yes, calculated fields (like the one you shared) are one of the methods to normalize data.
Let me know if you solved your issue.
Ciao.
Giuseppe