@jonesnadiam wrote: Has anyone had issues with the Splunk Add-on for F5 BIG-IP setting/separating the sourcetypes? According to the documentation, if the sourcetype is set to f5:bigip:syslog, the data should be separated into its specific sourcetypes (f5:bigip:apm:syslog, f5:bigip:asm:syslog, f5:bigip:icontrol, etc), but all of our sourcetypes are still coming in as f5:bigip:syslog. Is there anything specific that I need to change in the configuration files so that these sourcetypes are automatically updated? Thanks. yes , i have fixed it by asking System administrator to change the 1st part of raw data from F5-Logging profile to the one which match with "f5_asm" format and it work =====> but found another issue with Addon (( Addone -F5 BigIp) didnot tag ASM-logs which will not be presented on Datamodels Or dashboards so i make a new files at local folder props.conf ### ASM ### [f5:bigip:asm:syslog] EVAL-attack_type = if(isnull(attack_type) or attack_type="" or attack_type="N/A" or attack_type="-", null, attack_type) EVAL-category = if(isnull(attack_type) or attack_type="" or attack_type="N/A" or attack_type="-", null, attack_type) and tags.conf ### ASM ### [eventtype=f5_bigip_asm_syslog_attack] web = enabled communicate = enabled network = enabled attack = enabled ids = enabled [eventtype=f5_bigip_asm_syslog] web = enabled communicate = enabled network = enabled AND eventtypes.conf [f5_bigip_asm_syslog] search = sourcetype="f5:bigip:asm:syslog" (attack_type="N/A" OR NOT attack_type=*) [f5_bigip_asm_syslog_attack] search = sourcetype="f5:bigip:asm:syslog" (attack_type!="N/A" AND attack_type=*) and now everything is working fine and data are tagged this should be added to addons in the next release
... View more