<?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: Splunk Deployment Server Whitelist- How to write a regex that matches only for the first instance? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Deployment-Server-Whitelist-How-to-write-a-regex-that/m-p/633056#M108393</link>
    <description>&lt;P&gt;Figured it out...acceptable format is as follows:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;\bT-*&lt;/LI&gt;&lt;LI&gt;\bL-*&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Thu, 02 Mar 2023 20:44:16 GMT</pubDate>
    <dc:creator>qcjacobo2577</dc:creator>
    <dc:date>2023-03-02T20:44:16Z</dc:date>
    <item>
      <title>Splunk Deployment Server Whitelist- How to write a regex that matches only for the first instance?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Deployment-Server-Whitelist-How-to-write-a-regex-that/m-p/632862#M108362</link>
      <description>&lt;P&gt;Community,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Looking for some assistance on "serverclass.conf" file and the ability to utilize a whitelist regex pattern matching such that we can target specific devices in our network.&lt;/P&gt;
&lt;P&gt;We are seeking to include &lt;U&gt;&lt;STRONG&gt;only&lt;/STRONG&gt;&lt;/U&gt; devices with this naming schema: &lt;STRONG&gt;&lt;EM&gt;T-&amp;lt;some string&amp;gt;&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Separately, we want to match on &lt;STRONG&gt;&lt;U&gt;only&lt;/U&gt;&lt;/STRONG&gt; devices with another naming schema: &lt;EM&gt;&lt;STRONG&gt;L-&amp;lt;some string&amp;gt;&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;We are pushing different configurations to each of those devices (hence the need for separation).&lt;/P&gt;
&lt;P&gt;What we started with in each case is using a whitelist of:&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;L-*&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;AND&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;T-*&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;This all works fine....until....we found that we have devices in our environment with the naming schema of: &lt;STRONG&gt;&lt;EM&gt;T-&amp;lt;some string&amp;gt;L-&amp;lt;some string&amp;gt;&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;We attempted to leverage some regex matching, but believe our syntax to be wrong as the respective app and its configuration are no longer being deployed to the system(s) to be managed.&lt;/P&gt;
&lt;P&gt;Looking for some assistance on how to properly write regex matching for devices where is only matches on the &lt;STRONG&gt;&lt;U&gt;first&lt;/U&gt; &lt;/STRONG&gt;instance of a single letter followed by a dash as this does not seem to be well documented.&lt;/P&gt;
&lt;P&gt;Thank you in advance.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 15:26:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Deployment-Server-Whitelist-How-to-write-a-regex-that/m-p/632862#M108362</guid>
      <dc:creator>qcjacobo2577</dc:creator>
      <dc:date>2023-03-02T15:26:26Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Deployment Server Whitelist- How to write a regex that matches only for the first instance?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Deployment-Server-Whitelist-How-to-write-a-regex-that/m-p/633056#M108393</link>
      <description>&lt;P&gt;Figured it out...acceptable format is as follows:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;\bT-*&lt;/LI&gt;&lt;LI&gt;\bL-*&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Thu, 02 Mar 2023 20:44:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Deployment-Server-Whitelist-How-to-write-a-regex-that/m-p/633056#M108393</guid>
      <dc:creator>qcjacobo2577</dc:creator>
      <dc:date>2023-03-02T20:44:16Z</dc:date>
    </item>
  </channel>
</rss>

