<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: TCP input override in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/TCP-input-override/m-p/505731#M86139</link>
    <description>&lt;P&gt;Yes, it is possible. Note, it may cause excessive CPU usage on the indexer / heavy forwarder.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&lt;BR /&gt;props.conf and transforms.conf (most likely on indexer, but if you have the data coming to a heavy forwarder, then put the props and transforms there as well)&lt;BR /&gt;&lt;BR /&gt;In the transforms example below, adjust the regex to grab the field you are looking for.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;For More details, see:&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.4/Data/Advancedsourcetypeoverrides" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.4/Data/Advancedsourcetypeoverrides&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;props.conf&lt;BR /&gt;[&amp;lt;sourcetype&amp;gt;]&lt;BR /&gt;TRANSFORMS-changedatasource = datasource_finder&lt;/P&gt;&lt;P&gt;transforms.conf&lt;BR /&gt;[datasource_finder]&lt;BR /&gt;SOURCE_KEY = _raw&lt;BR /&gt;REGEX = datasource=(\w+)&lt;BR /&gt;DEST_KEY = MetaData:Sourcetype&lt;BR /&gt;FORMAT = sourcetype::$1&lt;/P&gt;</description>
    <pubDate>Tue, 23 Jun 2020 12:52:40 GMT</pubDate>
    <dc:creator>The_Simko</dc:creator>
    <dc:date>2020-06-23T12:52:40Z</dc:date>
    <item>
      <title>TCP input override</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TCP-input-override/m-p/505707#M86138</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am using a TCP input in splunk to receive WSUS data, gathered and pushed to splunk by a powershell script.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;My question is if it is possible to use the same input, and override source type based on a field value in the received data? I have field called "datasource" in my data.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jun 2020 11:26:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TCP-input-override/m-p/505707#M86138</guid>
      <dc:creator>hethu</dc:creator>
      <dc:date>2020-06-23T11:26:09Z</dc:date>
    </item>
    <item>
      <title>Re: TCP input override</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TCP-input-override/m-p/505731#M86139</link>
      <description>&lt;P&gt;Yes, it is possible. Note, it may cause excessive CPU usage on the indexer / heavy forwarder.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&lt;BR /&gt;props.conf and transforms.conf (most likely on indexer, but if you have the data coming to a heavy forwarder, then put the props and transforms there as well)&lt;BR /&gt;&lt;BR /&gt;In the transforms example below, adjust the regex to grab the field you are looking for.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;For More details, see:&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.4/Data/Advancedsourcetypeoverrides" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.4/Data/Advancedsourcetypeoverrides&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;props.conf&lt;BR /&gt;[&amp;lt;sourcetype&amp;gt;]&lt;BR /&gt;TRANSFORMS-changedatasource = datasource_finder&lt;/P&gt;&lt;P&gt;transforms.conf&lt;BR /&gt;[datasource_finder]&lt;BR /&gt;SOURCE_KEY = _raw&lt;BR /&gt;REGEX = datasource=(\w+)&lt;BR /&gt;DEST_KEY = MetaData:Sourcetype&lt;BR /&gt;FORMAT = sourcetype::$1&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jun 2020 12:52:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TCP-input-override/m-p/505731#M86139</guid>
      <dc:creator>The_Simko</dc:creator>
      <dc:date>2020-06-23T12:52:40Z</dc:date>
    </item>
  </channel>
</rss>

