I'm looking at configuring inputs for the Cisco ASA add-on on my UF as per;
My understanding was that the best practice was to send any Syslog streams to a Syslog server and then read the resulting output files with a file monitor.
This seems to suggest you just sent directly to Splunk.
How can I set up this add-in to use an inputs.conf file containing appropriate file monitors? Is that supported?
although your link is missing, I assume you mean THIS.
Actually, it doesn't matter if you use direct TCP/UDP input, or file monitors (although the latter is preferred best practice), it just matters that you put the right sourcetype on it.
You can choose the approriate one from this list.
Hope that helps - if it does I'd be happy if you would upvote/accept this answer, so others could profit from it. 🙂
So just to I'm clear, it would be acceptable to create an /local/inputs.conf within the App structure and monitor files so long as I define the correct sourcetype within the monitor stanza?
Or would it be considered against best practice to modify a pre-built Apps structure? In this case would it be better to create a new app?
No, it's perfectly fine.
Just to make sure: If you download somebody else's app, you should never change the
default configs, because you'll loose those changes on an update - but it's perfectly fine to add stuff to
local. Actually, it's good practice for app developers to not ship any active inputs with an app, because an app shouldn't start inputs, create indexes or other stuff - that should be part of the install guide and a conscious action by the admin who installs it.
So - create an
inputs.conf in the
local directory of the app, and then deploy it. 🙂