<?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: Index Time Sourcetyping in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129959#M26728</link>
    <description>&lt;P&gt;Can you post a couple of your events.  Typically this is regex related because the rest of what you have looks good.&lt;/P&gt;</description>
    <pubDate>Tue, 05 Nov 2013 23:31:05 GMT</pubDate>
    <dc:creator>sdaniels</dc:creator>
    <dc:date>2013-11-05T23:31:05Z</dc:date>
    <item>
      <title>Index Time Sourcetyping</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129958#M26727</link>
      <description>&lt;P&gt;props.conf:&lt;BR /&gt;
[pan_event]&lt;BR /&gt;
TRANSFORMS-traffic = traffic_source&lt;/P&gt;

&lt;P&gt;transforms.conf:&lt;BR /&gt;
[traffic_source]&lt;BR /&gt;
REGEX = (,TRAFFIC,)&lt;BR /&gt;
FORMAT = sourcetype::pan_traffic&lt;BR /&gt;
DEST_KEY = MetaData:Sourcetype&lt;/P&gt;

&lt;P&gt;I've got data being indexed as sourcetype=pan_event. I have distributed the above props and transforms to the indexers and restarted them, but I am unable to create a pan_traffic sourcetype. Where am I going wrong?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 15:12:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129958#M26727</guid>
      <dc:creator>tprzelom</dc:creator>
      <dc:date>2020-09-28T15:12:53Z</dc:date>
    </item>
    <item>
      <title>Re: Index Time Sourcetyping</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129959#M26728</link>
      <description>&lt;P&gt;Can you post a couple of your events.  Typically this is regex related because the rest of what you have looks good.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Nov 2013 23:31:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129959#M26728</guid>
      <dc:creator>sdaniels</dc:creator>
      <dc:date>2013-11-05T23:31:05Z</dc:date>
    </item>
    <item>
      <title>Re: Index Time Sourcetyping</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129960#M26729</link>
      <description>&lt;P&gt;Nov  5 15:32:38 hostname.net 1,2013/11/05 15:32:38,0002C100698,TRAFFIC,end,1,2013/11/05 15:32:37,IP_ADDR,IP_ADDR,IP_ADDR,IP_ADDR,firewall_rule,,,incomplete,vsys1,trust,untrust,ethernet1/2,ethernet1/1,anycast_vip_IP_ADDR,2013/11/05 15:32:37,159998,1,47031,3978,47031,3978,0x400000,tcp,allow,74,74,0,1,2013/11/05 15:32:33,0,any,0,12676624,0x0,IP_RANGE,IP_RANGE,0,1,0&lt;/P&gt;

&lt;P&gt;hot off the press&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 15:12:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129960#M26729</guid>
      <dc:creator>tprzelom</dc:creator>
      <dc:date>2020-09-28T15:12:56Z</dc:date>
    </item>
    <item>
      <title>Re: Index Time Sourcetyping</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129961#M26730</link>
      <description>&lt;P&gt;I think you can skip the parenthesis in the REGEX.&lt;/P&gt;

&lt;P&gt;/k&lt;/P&gt;</description>
      <pubDate>Wed, 06 Nov 2013 00:58:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129961#M26730</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-11-06T00:58:09Z</dc:date>
    </item>
    <item>
      <title>Re: Index Time Sourcetyping</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129962#M26731</link>
      <description>&lt;P&gt;Yep, forget those and it seems like you might have a space with the comma before traffic?  Not sure though. You could remove those or go with REGEX= ,\sTRAFFIC,&lt;/P&gt;</description>
      <pubDate>Wed, 06 Nov 2013 14:08:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129962#M26731</guid>
      <dc:creator>sdaniels</dc:creator>
      <dc:date>2013-11-06T14:08:53Z</dc:date>
    </item>
    <item>
      <title>Re: Index Time Sourcetyping</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129963#M26732</link>
      <description>&lt;P&gt;I'm using&lt;BR /&gt;
REGEX = ,TRAFFIC,&lt;BR /&gt;
with no success&lt;/P&gt;

&lt;P&gt;There is no space after the comma. This feels like something more sinister that just a regex. I had a much more complex system in place that all of a sudden stopped working, so I dialed it back to basics to try and uncover the problem.  These logs are coming through an rsyslog tier, could there be some kind of metadata affecting the logs?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Nov 2013 16:09:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129963#M26732</guid>
      <dc:creator>tprzelom</dc:creator>
      <dc:date>2013-11-06T16:09:51Z</dc:date>
    </item>
    <item>
      <title>Re: Index Time Sourcetyping</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129964#M26733</link>
      <description>&lt;PRE&gt;&lt;CODE&gt;REGEX= \,TRAFFIC\,
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 08 Nov 2013 03:19:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129964#M26733</guid>
      <dc:creator>ShaneNewman</dc:creator>
      <dc:date>2013-11-08T03:19:52Z</dc:date>
    </item>
    <item>
      <title>Re: Index Time Sourcetyping</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129965#M26734</link>
      <description>&lt;P&gt;You don't need parens, nor do you need to escape the commas: &lt;CODE&gt;REGEX= TRAFFIC&lt;/CODE&gt; would be fine. &lt;/P&gt;

&lt;P&gt;Is the data &lt;STRONG&gt;coming&lt;/STRONG&gt; to the indexers with sourcetype=pan_event or is it transformed to be &lt;STRONG&gt;become&lt;/STRONG&gt; that? If the latter, you need to scope the transform on source instead. Is it perhaps coming from a heavy forwarder?&lt;/P&gt;</description>
      <pubDate>Fri, 08 Nov 2013 03:58:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129965#M26734</guid>
      <dc:creator>_d_</dc:creator>
      <dc:date>2013-11-08T03:58:01Z</dc:date>
    </item>
    <item>
      <title>Re: Index Time Sourcetyping</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129966#M26735</link>
      <description>&lt;P&gt;The issue was the light forwarder was being managed by cfengine3 and was transitioned to chef and something was lost in the transition which resulted in partial functionality.&lt;/P&gt;

&lt;P&gt;My solution was rip all that out and use a universal forwarder that has a deploymentclient.conf sent to it by chef. Then use the deployment server from there. &lt;/P&gt;</description>
      <pubDate>Fri, 15 Nov 2013 17:02:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Index-Time-Sourcetyping/m-p/129966#M26735</guid>
      <dc:creator>tprzelom</dc:creator>
      <dc:date>2013-11-15T17:02:09Z</dc:date>
    </item>
  </channel>
</rss>

