All Apps and Add-ons

cisco:asa sourcetype not parsing fields correctly

tross33
Explorer

I am having issues with consistent field extraction using the cisco:asa sourcetype. The fields are very inconsistently parsed, many times making 4 or 5 events out of a single event, even separating a line in the middle of a word.

I am currently accepting syslog for these devices using rsyslog, and I am monitoring the file generated for the specific device on the local filesystem. The following is an example of the inputs.conf entry I have in the Splunk_TA_cisco-asa local directory.

[monitor:///var/log/syslog/system-111.111.111.111.log]
host_segment = 4
sourcetype = cisco:asa
disabled = false

I am running version 3.2.0 of the Splunk Add-on for Cisco ASA. I am running version 3.0.3 of Cisco Security Suite. Am I missing something? Thanks in advance.

0 Karma

mzorzi
Splunk Employee
Splunk Employee

Try to add, under the stanza above,

SHOULD_LINEMERGE=false

0 Karma

tross33
Explorer

Thank you for the response mzorzi. Unfortunately, that did not work when placed in my inputs.conf file. I believe the sourcetype should pull that from my props.conf file?

########## ASA

[source::....asa]
sourcetype = cisco:asa

[cisco:asa]
SHOULD_LINEMERGE = false
KV_MODE = auto

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...