Getting Data In

Convert a Sourcetype

dwilson333
New Member

All,

I only use Splunk about once a month, tops. So Please help me out if I use the wrong terms.

I have a "app" which was written by my boss that is pulling in logs from our Siebel CRM servers. it does not specify a sourcetype in the inputs.conf file. My boss would like me to create a sourcetype for Siebel data.

1) How do I create a "sourcetype"
2) How do I convert the old automagically created sourcetype to my new one?

Tags (1)
0 Karma
1 Solution

rroberts
Splunk Employee
Splunk Employee

1.Splunk automagically sourcetypes some input methods (not all ie TCP, UDP) as data comes into Splunk at Index time. Check out:

http://docs.splunk.com/Documentation/Splunk/latest/Data/Whysourcetypesmatter

However, as you state, one of the places you can override automatic sourcetyping is in your inputs.conf file.

2.Since sourcetype is an indexed field you would have to clean out the index and re-index the data with your inputs.conf edits. This may not be practical in a production environment, original data sources, missing, etc ...

You should probably leverage sourcetype renaming (aliasing) instead for your boss. This can done via your Manager view -> Fields view -> sourcetype renaming. It is retroactive and takes place at search time. This "renamed field" would also be a knowledge object that could be private just for your boss, anyone with access to the app or global.

http://docs.splunk.com/Documentation/Splunk/5.0.3/Data/Renamesourcetypes

View solution in original post

rroberts
Splunk Employee
Splunk Employee

1.Splunk automagically sourcetypes some input methods (not all ie TCP, UDP) as data comes into Splunk at Index time. Check out:

http://docs.splunk.com/Documentation/Splunk/latest/Data/Whysourcetypesmatter

However, as you state, one of the places you can override automatic sourcetyping is in your inputs.conf file.

2.Since sourcetype is an indexed field you would have to clean out the index and re-index the data with your inputs.conf edits. This may not be practical in a production environment, original data sources, missing, etc ...

You should probably leverage sourcetype renaming (aliasing) instead for your boss. This can done via your Manager view -> Fields view -> sourcetype renaming. It is retroactive and takes place at search time. This "renamed field" would also be a knowledge object that could be private just for your boss, anyone with access to the app or global.

http://docs.splunk.com/Documentation/Splunk/5.0.3/Data/Renamesourcetypes

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...