<?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: Matching Windows path in props.conf in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Matching-Windows-path-in-props-conf/m-p/253910#M48738</link>
    <description>&lt;P&gt;Hi matthewjohnson,&lt;/P&gt;

&lt;P&gt;you can use something like this in your &lt;CODE&gt;inputs.conf&lt;/CODE&gt; :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; [monitor://D:\syslog\...\*.syslog]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;which will recurses through the directories in side of &lt;CODE&gt;syslog&lt;/CODE&gt;. &lt;/P&gt;

&lt;P&gt;Hope this helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
    <pubDate>Tue, 26 Jan 2016 00:23:51 GMT</pubDate>
    <dc:creator>MuS</dc:creator>
    <dc:date>2016-01-26T00:23:51Z</dc:date>
    <item>
      <title>Matching Windows path in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Matching-Windows-path-in-props-conf/m-p/253909#M48737</link>
      <description>&lt;P&gt;I'm trying to set up the Splunk for A10 Networks app. &lt;/P&gt;

&lt;P&gt;It expects syslog data on UDP port 514. &lt;/P&gt;

&lt;P&gt;My data is collected by NXLog, spit out into a file, and then consumed by Splunk. &lt;/P&gt;

&lt;P&gt;As such, I'm trying to edit a props.conf stanza in the app's directory from it's default, &lt;STRONG&gt;[source::udp:514]&lt;/STRONG&gt; to match my file path.&lt;/P&gt;

&lt;P&gt;Example path: &lt;/P&gt;

&lt;P&gt;&lt;EM&gt;D:\syslog\a10networks&amp;amp;adc_a10networks\[device name]\[file name].syslog&lt;/EM&gt;.&lt;/P&gt;

&lt;P&gt;How would I construct my source stanza?&lt;/P&gt;

&lt;P&gt;I've tried many variations along the lines of, &lt;STRONG&gt;[source::D:\\...\\a10networks&amp;amp;adc_a10networks\\....syslog]&lt;/STRONG&gt; (I have tried escaping the ampersand in my path). I'm running Splunk on Windows if it matters.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jan 2016 23:24:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Matching-Windows-path-in-props-conf/m-p/253909#M48737</guid>
      <dc:creator>matthewjohnson</dc:creator>
      <dc:date>2016-01-25T23:24:53Z</dc:date>
    </item>
    <item>
      <title>Re: Matching Windows path in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Matching-Windows-path-in-props-conf/m-p/253910#M48738</link>
      <description>&lt;P&gt;Hi matthewjohnson,&lt;/P&gt;

&lt;P&gt;you can use something like this in your &lt;CODE&gt;inputs.conf&lt;/CODE&gt; :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; [monitor://D:\syslog\...\*.syslog]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;which will recurses through the directories in side of &lt;CODE&gt;syslog&lt;/CODE&gt;. &lt;/P&gt;

&lt;P&gt;Hope this helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jan 2016 00:23:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Matching-Windows-path-in-props-conf/m-p/253910#M48738</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2016-01-26T00:23:51Z</dc:date>
    </item>
    <item>
      <title>Re: Matching Windows path in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Matching-Windows-path-in-props-conf/m-p/253911#M48739</link>
      <description>&lt;P&gt;I think that this is what you need in props.conf if there is only one layer of directories represented by &lt;EM&gt;[device name]&lt;/EM&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::D:\syslog\a10networks&amp;amp;adc_a10networks\*\*.syslog]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This will work if the directory structure is more complicated&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::D:\syslog\a10networks&amp;amp;adc_a10networks\...\*.syslog]
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 26 Jan 2016 00:24:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Matching-Windows-path-in-props-conf/m-p/253911#M48739</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2016-01-26T00:24:30Z</dc:date>
    </item>
    <item>
      <title>Re: Matching Windows path in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Matching-Windows-path-in-props-conf/m-p/253912#M48740</link>
      <description>&lt;P&gt;Yes, this is good for inputs.conf, but I think he may be editing an app, in which case he probably needs to edit props.conf as well...&lt;/P&gt;

&lt;P&gt;That's a little different.&lt;/P&gt;

&lt;P&gt;PS. I corrected the typo in your monitor stanza (missing &lt;CODE&gt;]&lt;/CODE&gt;)&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jan 2016 00:27:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Matching-Windows-path-in-props-conf/m-p/253912#M48740</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2016-01-26T00:27:16Z</dc:date>
    </item>
    <item>
      <title>Re: Matching Windows path in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Matching-Windows-path-in-props-conf/m-p/253913#M48741</link>
      <description>&lt;P&gt;HeHe, twice good spotting @lguinn &lt;/P&gt;</description>
      <pubDate>Tue, 26 Jan 2016 00:51:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Matching-Windows-path-in-props-conf/m-p/253913#M48741</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2016-01-26T00:51:26Z</dc:date>
    </item>
    <item>
      <title>Re: Matching Windows path in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Matching-Windows-path-in-props-conf/m-p/253914#M48742</link>
      <description>&lt;P&gt;How about the &lt;CODE&gt;&amp;amp;&lt;/CODE&gt; in the path name, does this work? I can remember a bug which did not like &lt;CODE&gt;$&lt;/CODE&gt; in path names.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jan 2016 00:52:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Matching-Windows-path-in-props-conf/m-p/253914#M48742</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2016-01-26T00:52:22Z</dc:date>
    </item>
    <item>
      <title>Re: Matching Windows path in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Matching-Windows-path-in-props-conf/m-p/253915#M48743</link>
      <description>&lt;P&gt;I tried your example, with and without escaped backslashes, and still couldn't get it to work. I'm wondering if it isn't related to the '&amp;amp;' in the path. In the end, I assigned a source type (a10) via Splunk file &amp;amp; folder monitoring, and replaced my [source::...] stanza with [a10]. Now everything is working.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jan 2016 22:44:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Matching-Windows-path-in-props-conf/m-p/253915#M48743</guid>
      <dc:creator>matthewjohnson</dc:creator>
      <dc:date>2016-01-26T22:44:47Z</dc:date>
    </item>
    <item>
      <title>Re: Matching Windows path in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Matching-Windows-path-in-props-conf/m-p/253916#M48744</link>
      <description>&lt;P&gt;Thanks for the input. @lguinn is correct, I'm editing an app and am working with props.conf&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jan 2016 22:46:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Matching-Windows-path-in-props-conf/m-p/253916#M48744</guid>
      <dc:creator>matthewjohnson</dc:creator>
      <dc:date>2016-01-26T22:46:48Z</dc:date>
    </item>
  </channel>
</rss>

