<?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: Input.Conf  with Version numbers in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Input-Conf-with-Version-numbers/m-p/749925#M119147</link>
    <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/28010"&gt;@PrewinThomas&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just confirming Will it capture&lt;/P&gt;&lt;PRE&gt;warcraft-9.&lt;SPAN class=""&gt;0&lt;/SPAN&gt;.&lt;SPAN class=""&gt;78\logs\*&lt;/SPAN&gt;&lt;/PRE&gt;</description>
    <pubDate>Wed, 16 Jul 2025 19:46:58 GMT</pubDate>
    <dc:creator>Cheng2Ready</dc:creator>
    <dc:date>2025-07-16T19:46:58Z</dc:date>
    <item>
      <title>Input.Conf  with Version numbers</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Input-Conf-with-Version-numbers/m-p/749861#M119131</link>
      <description>&lt;PRE&gt;[monitor://\\njros1bva0597\d$\LogFiles\warcraft-9.&lt;SPAN class=""&gt;0&lt;/SPAN&gt;.&lt;SPAN class=""&gt;71&lt;/SPAN&gt;\logs\*]
disabled = false
host = NJROS1BVA0621
alwaysOpenFile = 1
sourcetype = Image Importer Logs&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;Is there a way to add a Wild card for any upcoming version updates like below? will this work?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;[monitor://\\njros1bva0597\d$\LogFiles\warcraft-9.*\logs\*]&lt;BR /&gt;&lt;BR /&gt;Or does it have to be like this?&lt;BR /&gt;&lt;BR /&gt;[monitor://\\njros1bva0597\d$\LogFiles\warcraft-9.[0-9].[0-9][0-9]\logs\*]&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 22:09:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Input-Conf-with-Version-numbers/m-p/749861#M119131</guid>
      <dc:creator>Cheng2Ready</dc:creator>
      <dc:date>2025-07-15T22:09:19Z</dc:date>
    </item>
    <item>
      <title>Re: Input.Conf  with Version numbers</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Input-Conf-with-Version-numbers/m-p/749866#M119132</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/256484"&gt;@Cheng2Ready&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can use wildcard for future versions of 9 with the below,&lt;BR /&gt;Eg:&lt;BR /&gt;[monitor://\\njros1bva0597\d$\LogFiles\warcraft-9.*\logs\*]&lt;BR /&gt;disabled = false&lt;BR /&gt;host = NJROS1BVA0621&lt;BR /&gt;alwaysOpenFile = 1&lt;BR /&gt;sourcetype = Image Importer Logs&lt;/P&gt;&lt;P&gt;But i'm just curious that you have alwaysOpenFile = 1, I hope you have valid reason for the same.&lt;BR /&gt;&lt;STRONG&gt;Just FYI&lt;/STRONG&gt; - Enabling this option increases resource consumption and can slow down indexing.&lt;BR /&gt;#&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.4.2/Admin/Inputsconf" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.4.2/Admin/Inputsconf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Prewin&lt;BR /&gt;Splunk Enthusiast | Always happy to help! If this answer helped you, please consider marking it as the solution or giving a Karma. Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jul 2025 04:24:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Input-Conf-with-Version-numbers/m-p/749866#M119132</guid>
      <dc:creator>PrewinThomas</dc:creator>
      <dc:date>2025-07-16T04:24:27Z</dc:date>
    </item>
    <item>
      <title>Re: Input.Conf  with Version numbers</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Input-Conf-with-Version-numbers/m-p/749871#M119135</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/256484"&gt;@Cheng2Ready&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can use a * for any value in the current directory/segment or ... to recursively wildcard. Therefore you can do the following:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[monitor://\\njros1bva0597\d$\LogFiles\warcraft-9.*\logs\*]
disabled = false
host = NJROS1BVA0621
alwaysOpenFile = 1
sourcetype = Image Importer Logs&lt;/LI-CODE&gt;&lt;P&gt;Check out&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Data/Specifyinputpathswithwildcards" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Data/Specifyinputpathswithwildcards&lt;/A&gt;&amp;nbsp;for more info on this and&amp;nbsp;&lt;A href="https://community.splunk.com/t5/Getting-Data-In/What-is-the-proper-use-of-wildcard-in-a-file-monitor-path/m-p/347282" target="_blank"&gt;https://community.splunk.com/t5/Getting-Data-In/What-is-the-proper-use-of-wildcard-in-a-file-monitor-path/m-p/347282&lt;/A&gt;&amp;nbsp;for other good examples.&lt;/P&gt;&lt;P&gt;Is there any particular reason you're using&amp;nbsp;&lt;EM&gt;alwaysOpenFile=1?&amp;nbsp;&lt;/EM&gt;This is only useful for files that do not update modification time or size and adds resource overhead, so wanted to check.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":glowing_star:"&gt;🌟&lt;/span&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Did this answer help you?&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;If so, please consider:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Adding karma to show it was useful&lt;/LI&gt;&lt;LI&gt;Marking it as the solution if it resolved your issue&lt;/LI&gt;&lt;LI&gt;Commenting if you need any clarification&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Your feedback encourages the volunteers in this community to continue contributing&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jul 2025 06:19:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Input-Conf-with-Version-numbers/m-p/749871#M119135</guid>
      <dc:creator>livehybrid</dc:creator>
      <dc:date>2025-07-16T06:19:30Z</dc:date>
    </item>
    <item>
      <title>Re: Input.Conf  with Version numbers</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Input-Conf-with-Version-numbers/m-p/749922#M119144</link>
      <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/28010"&gt;@PrewinThomas&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I see yeah I just copied somonelses post for thier input.conf example&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://community.splunk.com/t5/Getting-Data-In/Inputs-conf-with-wildcards/m-p/59916" target="_blank"&gt;https://community.splunk.com/t5/Getting-Data-In/Inputs-conf-with-wildcards/m-p/59916&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;but my main focus was the Monitor line&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jul 2025 19:41:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Input-Conf-with-Version-numbers/m-p/749922#M119144</guid>
      <dc:creator>Cheng2Ready</dc:creator>
      <dc:date>2025-07-16T19:41:00Z</dc:date>
    </item>
    <item>
      <title>Re: Input.Conf  with Version numbers</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Input-Conf-with-Version-numbers/m-p/749923#M119145</link>
      <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/170906"&gt;@livehybrid&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I see yeah I just copied someone else post for their input.conf example&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.splunk.com/t5/Getting-Data-In/Inputs-conf-with-wildcards/m-p/59916" target="_blank"&gt;https://community.splunk.com/t5/Getting-Data-In/Inputs-conf-with-wildcards/m-p/59916&lt;/A&gt;&lt;/P&gt;&lt;P&gt;but my main focus was the Monitor line&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jul 2025 19:42:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Input-Conf-with-Version-numbers/m-p/749923#M119145</guid>
      <dc:creator>Cheng2Ready</dc:creator>
      <dc:date>2025-07-16T19:42:05Z</dc:date>
    </item>
    <item>
      <title>Re: Input.Conf  with Version numbers</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Input-Conf-with-Version-numbers/m-p/749924#M119146</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/170906"&gt;@livehybrid&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Just confirming Will it capture&lt;/P&gt;&lt;PRE&gt;warcraft-9.&lt;SPAN class=""&gt;0&lt;/SPAN&gt;.&lt;SPAN class=""&gt;78\logs\*&lt;/SPAN&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 16 Jul 2025 19:46:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Input-Conf-with-Version-numbers/m-p/749924#M119146</guid>
      <dc:creator>Cheng2Ready</dc:creator>
      <dc:date>2025-07-16T19:46:42Z</dc:date>
    </item>
    <item>
      <title>Re: Input.Conf  with Version numbers</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Input-Conf-with-Version-numbers/m-p/749925#M119147</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/28010"&gt;@PrewinThomas&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just confirming Will it capture&lt;/P&gt;&lt;PRE&gt;warcraft-9.&lt;SPAN class=""&gt;0&lt;/SPAN&gt;.&lt;SPAN class=""&gt;78\logs\*&lt;/SPAN&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 16 Jul 2025 19:46:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Input-Conf-with-Version-numbers/m-p/749925#M119147</guid>
      <dc:creator>Cheng2Ready</dc:creator>
      <dc:date>2025-07-16T19:46:58Z</dc:date>
    </item>
  </channel>
</rss>

