Archive
Highlighted

sourcetype not getting overridden

Contributor

I have an inputs.conf
[monitor:///tmp/a.txt]
index=a
sourcetype=AA

Now,I want to over write the sourcetype in HF as mentioned in the Splunk docs.
props.conf
[source::/tmp/a.txt]
SHOUlD_LINEMERGE=false
sourcetype=BB

But, my sourcetype is not getting over written, I am getting the same sourcetype as AA in my IDX server. How to correct it

0 Karma
Highlighted

Re: sourcetype not getting overridden

SplunkTrust
SplunkTrust

You'd have to use the transforms to update the sourcetype metadata, like this

props.conf

[source::/tmp/a.txt]
SHOUlD_LINEMERGE=false
TRANSFORMS-overridest = override_st

transforms.conf

[override_st]
REGEX = .
FORMAT = sourcetype::BB
DEST_KEY = MetaData:Sourcetype

This will be your reference Splunk documentation for the same: http://docs.splunk.com/Documentation/Splunk/7.0.3/Data/Advancedsourcetypeoverrides

Highlighted

Re: sourcetype not getting overridden

Contributor

Do I have to make it HF ? or IDX ? ...

0 Karma
Highlighted

Re: sourcetype not getting overridden

SplunkTrust
SplunkTrust

Whichever comes first in data from source. Generally if you're using HF, before index, set this up in HF. A restart of splunkd service would be required and it'd only affect the new events that come after you set this up.

0 Karma
Highlighted

Re: sourcetype not getting overridden

Contributor

If I have UF---HF---IDX then ?

0 Karma
Highlighted

Re: sourcetype not getting overridden

SplunkTrust
SplunkTrust

Still in HF (first Splunk Enterprise instance in the flow, after UF first Splunk Enterprise instance is HF, so HF).

0 Karma
Highlighted

Re: sourcetype not getting overridden

Contributor

No , it is not working .

sourcetype is not getting renamed in HF. But If I do in IDX it is working ..

0 Karma
Speak Up for Splunk Careers!

We want to better understand the impact Splunk experience and expertise has has on individuals' careers, and help highlight the growing demand for Splunk skills.