<?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 How to specify source stanza for non-file input types in props.conf in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-specify-source-stanza-for-non-file-input-types-in-props/m-p/366214#M66616</link>
    <description>&lt;P&gt;I am trying to write some source:: stanzas in props.conf to forward data to another system. For file inputs (e.g., monitor type inputs), I can write [source::/path/to/file] and it works. However, I am wondering what would the  part of source:: be for other source types such as windows event logs. For example, when I tried [source::Application] for matching Windows Application Event logs, it didn't work, but when I tried [source::WinEventLog:Application], it worked. &lt;/P&gt;

&lt;P&gt;My question is, is there a list of prefixes such as WinEventLog for input types other than file? For example, what would be the prefix patterns for Local Performance Monitoring, TCP/UDP, Registry Monitoring, Local Windows Host, Printer, Network monitoring etc? In lieu of prefix patterns, how would I write the source:: stanza for the above types?&lt;/P&gt;</description>
    <pubDate>Fri, 11 Aug 2017 03:42:12 GMT</pubDate>
    <dc:creator>anton085</dc:creator>
    <dc:date>2017-08-11T03:42:12Z</dc:date>
    <item>
      <title>How to specify source stanza for non-file input types in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-specify-source-stanza-for-non-file-input-types-in-props/m-p/366214#M66616</link>
      <description>&lt;P&gt;I am trying to write some source:: stanzas in props.conf to forward data to another system. For file inputs (e.g., monitor type inputs), I can write [source::/path/to/file] and it works. However, I am wondering what would the  part of source:: be for other source types such as windows event logs. For example, when I tried [source::Application] for matching Windows Application Event logs, it didn't work, but when I tried [source::WinEventLog:Application], it worked. &lt;/P&gt;

&lt;P&gt;My question is, is there a list of prefixes such as WinEventLog for input types other than file? For example, what would be the prefix patterns for Local Performance Monitoring, TCP/UDP, Registry Monitoring, Local Windows Host, Printer, Network monitoring etc? In lieu of prefix patterns, how would I write the source:: stanza for the above types?&lt;/P&gt;</description>
      <pubDate>Fri, 11 Aug 2017 03:42:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-specify-source-stanza-for-non-file-input-types-in-props/m-p/366214#M66616</guid>
      <dc:creator>anton085</dc:creator>
      <dc:date>2017-08-11T03:42:12Z</dc:date>
    </item>
    <item>
      <title>Re: How to specify source stanza for non-file input types in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-specify-source-stanza-for-non-file-input-types-in-props/m-p/366215#M66617</link>
      <description>&lt;P&gt;No there aren't any fix values.  You can set source as required in the inputs.conf and then use the same in props.conf file.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Aug 2017 05:14:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-specify-source-stanza-for-non-file-input-types-in-props/m-p/366215#M66617</guid>
      <dc:creator>hardikJsheth</dc:creator>
      <dc:date>2017-08-11T05:14:49Z</dc:date>
    </item>
    <item>
      <title>Re: How to specify source stanza for non-file input types in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-specify-source-stanza-for-non-file-input-types-in-props/m-p/366216#M66618</link>
      <description>&lt;P&gt;Hi anton085,&lt;BR /&gt;
you can use also other default fields as sourcetype instead source.&lt;BR /&gt;
I always prefer to use sourcetype instead source to make this.&lt;BR /&gt;
Bye.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Fri, 11 Aug 2017 07:27:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-specify-source-stanza-for-non-file-input-types-in-props/m-p/366216#M66618</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2017-08-11T07:27:45Z</dc:date>
    </item>
    <item>
      <title>Re: How to specify source stanza for non-file input types in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-specify-source-stanza-for-non-file-input-types-in-props/m-p/366217#M66619</link>
      <description>&lt;P&gt;What if I wanted to forward only a particular source of a sourcetype? Setting a sourcetype would mean all sources will be forwarded, and I don't want that. I assumed there would be predefined values for sources that Splunk supports out of the box.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Aug 2017 13:23:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-specify-source-stanza-for-non-file-input-types-in-props/m-p/366217#M66619</guid>
      <dc:creator>anton085</dc:creator>
      <dc:date>2017-08-11T13:23:20Z</dc:date>
    </item>
    <item>
      <title>Re: How to specify source stanza for non-file input types in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-specify-source-stanza-for-non-file-input-types-in-props/m-p/366218#M66620</link>
      <description>&lt;P&gt;I assumed there would be predefined values for sources (and sourcetypes) that Splunk supports out of the box.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Aug 2017 13:24:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-specify-source-stanza-for-non-file-input-types-in-props/m-p/366218#M66620</guid>
      <dc:creator>anton085</dc:creator>
      <dc:date>2017-08-11T13:24:43Z</dc:date>
    </item>
  </channel>
</rss>

