Getting Data In

After renaming a sourcetype, why is it only being applied to new data and not already indexed data?

OMohi
Path Finder

Hi Guys:

I have renamed a sourcetype, but after renaming the sourcetype and recycling the indexers, I only see new data being allocated to the new sourcetype. Historical data still seems to be allocated to the old sourcetype.

How do I address this problem? Do I need to clean all the eventdata from index on the indexer, stop Universal Forwarder, delete the fishbucket folder, start the indexer, and restart the forwarder? Please let me know.

Thanks

Tags (2)
0 Karma
1 Solution

tskinnerivsec
Contributor

sourcetype is an indexed field, so when you change to a new sourcetype, it will not apply to any historical events. If you don't care about your old data, you can just clear all the eventdata in the index where that particular historical data resides. After you clear the eventdata out of the index, if you still have the source data, you would have to re-index it and it should pick up the new sourcetype that you have configured.

View solution in original post

tskinnerivsec
Contributor

sourcetype is an indexed field, so when you change to a new sourcetype, it will not apply to any historical events. If you don't care about your old data, you can just clear all the eventdata in the index where that particular historical data resides. After you clear the eventdata out of the index, if you still have the source data, you would have to re-index it and it should pick up the new sourcetype that you have configured.

bmacias84
Champion

tskinnerivsec is correct. _time, host,index, splunk_server, sourcetype, and source are all fields performed during ingestion (index time).

Get Updates on the Splunk Community!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...