Archive
Highlighted

Splunk for Palo Alto - Config - Different Index name than default

New Member

I've installed the Splunk for Palo Alto app and while attempting to configure it found this reference.
"In the inputs.conf file, add the following configuration. For UDP syslogs, make sure to include the line noappendingtimestamp = true.
[udp://5514]
index = panlogs
sourcetype = pan
log
connectionhost = ip
no
appending_timestamp = true"

The issue is my Palo logs are already in Splunk with the following (multiple source types).
Index=paloalto
sourcetype=pantraffic
sourcetype=pan
threat
sourcetype=pansystem
sourcetype=pan
config

How do I change the app to meet my current configuration. I guess I'm a bit lost on what exactly to do. I've tried to modify the XML but it doesn't seem to work.

Thanks,
M

0 Karma
Highlighted

Re: Splunk for Palo Alto - Config - Different Index name than default

Path Finder

Within the apps inputs.conf, you can specify the changes to the index and sourcetype to match your current environment needs.

using the network input you provided as an example

[udp://5514]
index = pan_logs
sourcetype = pan_log
connection_host = ip
no_appending_timestamp = true

you could do

[udp://5514]
index = paloalto
sourcetype = pan_<whichever sourcetype you want to put it in>
connection_host = ip
no_appending_timestamp = true
Highlighted

Re: Splunk for Palo Alto - Config - Different Index name than default

Path Finder

If this has answered your question, please consider marking this question as answered. Thank You.

0 Karma
Highlighted

Re: Splunk for Palo Alto - Config - Different Index name than default

Builder

Unfortunately the answer from scruse won't work completely because the macros and datamodel in the app all refer to the panlogs index. You can use scruse's answer for the index if you also do a find/replace of all references to the panlogs index in the app. Many customers do this when they want to rename the index from pan_logs to something else.

Another option is to rename the index to panlogs. Renaming an index in Splunk is non-trivial and I believe it requires actually creating a new index called panlogs and moving the data over to it. Google or Splunk support can provide more guidance.

Regarding the sourcetype, you don't need to modify anything there. The sourcetype from the inputs.conf (panlogs) is just a placeholder sourcetype. Splunk actually parses the logs of this sourcetype in order to move the log to the correct final sourcetype (pantraffic, panthreat, panconfig, pansystem). So just use panlog as the sourcetype in inputs.conf, and it will automatically take care of parsing and moving the events to the other sourcetypes.

0 Karma