As @Vijeta mentioned, you can also disable it by adding the disabled = true to your indexes.conf.
In an index cluster I would add the line in the indexes.conf in your app on the Cluster Master, that is used to configure all indexes in your Cluster (in $SPLUNK_HOME/etc/master-apps/), and than push your new configuration bundle.
On a single instance you could use the CLI
... View more
You could use Heavy Forwarder or build a App for Splunk Cloud to filter your Logs. If you know, how your unnecessary Logs look like, you can filter it:
add in props.conf
TRANSFORMS-asa_filter_cloud = filterAsaLogs
add in transforms.conf
[filterAsaLogs]
SOURCE_KEY = _raw
DEST_KEY = queue
FORMAT = nullQueue
REGEX = (your regex to detect them)
... View more
something like 200 0 0 140 or 403 0 0 455 is the end of every line?
-> add in props.conf in your apache Sourcetype:
EXTRACT-http_statuscode = (?<statuscode>\d+)\s\d+\s\d+\s\d+$
-> If your data is already in Splunk, you can use this in your search to test it:
<your search> | rex field=_raw "(?<statuscode>\d+)\s\d+\s\d+\s\d+$"
-> explanation:
https://regex101.com/r/ct4C7D/1
-> After extracting the field (either in props.conf or in your search) you can use
<your search and extraction> | timechart count by statuscode
or
<your search and extraction> | stats count by statuscode
-> or use Splunk built in extractions for default access logs
<your search> | extract access-extractions | stats count by statuscode
... View more