<?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 Does props.conf support wildcards? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Does-props-conf-support-wildcards/m-p/255030#M48979</link>
    <description>&lt;P&gt;All, &lt;/P&gt;

&lt;P&gt;I found myself writing this props.conf today. &lt;/P&gt;

&lt;P&gt;Say I have this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tomcat:src:server]
EXTRACT-springapp_name = /var/log/containerlogs/(?.+)/\d in source
EXTRACT-containerid = /var/log/containerlogs/.+/(?.+)/ in source

[tomcat:src:access]
EXTRACT-springapp_name = /var/log/containerlogs/(?.+)/\d in source
EXTRACT-containerid = /var/log/containerlogs/.+/(?.+)/ in source
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I could I just do this?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tomcat:src:*]
EXTRACT-springapp_name = /var/log/containerlogs/(?.+)/\d in source
EXTRACT-containerid = /var/log/containerlogs/.+/(?.+)/ in source
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Wed, 13 Jul 2016 18:40:22 GMT</pubDate>
    <dc:creator>daniel333</dc:creator>
    <dc:date>2016-07-13T18:40:22Z</dc:date>
    <item>
      <title>Does props.conf support wildcards?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-props-conf-support-wildcards/m-p/255030#M48979</link>
      <description>&lt;P&gt;All, &lt;/P&gt;

&lt;P&gt;I found myself writing this props.conf today. &lt;/P&gt;

&lt;P&gt;Say I have this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tomcat:src:server]
EXTRACT-springapp_name = /var/log/containerlogs/(?.+)/\d in source
EXTRACT-containerid = /var/log/containerlogs/.+/(?.+)/ in source

[tomcat:src:access]
EXTRACT-springapp_name = /var/log/containerlogs/(?.+)/\d in source
EXTRACT-containerid = /var/log/containerlogs/.+/(?.+)/ in source
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I could I just do this?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tomcat:src:*]
EXTRACT-springapp_name = /var/log/containerlogs/(?.+)/\d in source
EXTRACT-containerid = /var/log/containerlogs/.+/(?.+)/ in source
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 13 Jul 2016 18:40:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-props-conf-support-wildcards/m-p/255030#M48979</guid>
      <dc:creator>daniel333</dc:creator>
      <dc:date>2016-07-13T18:40:22Z</dc:date>
    </item>
    <item>
      <title>Re: Does props.conf support wildcards?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-props-conf-support-wildcards/m-p/255031#M48980</link>
      <description>&lt;P&gt;Not officially. Should it? Yes! But no, it does not.&lt;/P&gt;

&lt;P&gt;An unofficial/unsupported/could break in the future solution is this:&lt;BR /&gt;
&lt;A href="http://blogs.splunk.com/2014/07/31/quick-tip-wildcard-sourcetypes-in-props-conf/"&gt;http://blogs.splunk.com/2014/07/31/quick-tip-wildcard-sourcetypes-in-props-conf/&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;So you would use something like:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[(?::){0}tomcat:src:*]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Again, this is an undocumented way of doing this, so Splunk could take that away at any point, so keep that in mind.&lt;/P&gt;

&lt;P&gt;Dave&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jul 2016 18:53:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-props-conf-support-wildcards/m-p/255031#M48980</guid>
      <dc:creator>dshpritz</dc:creator>
      <dc:date>2016-07-13T18:53:43Z</dc:date>
    </item>
    <item>
      <title>Re: Does props.conf support wildcards?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-props-conf-support-wildcards/m-p/255032#M48981</link>
      <description>&lt;P&gt;I believe the stanza for sourcetype doesn't support wild-card/regular expression. The stanza for host:: and source:: do.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.4.2/Admin/Propsconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.4.2/Admin/Propsconf&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[&amp;lt;spec&amp;gt;]
&amp;lt;spec&amp;gt; can be:
1. &amp;lt;sourcetype&amp;gt;, the source type of an event.
2. host::&amp;lt;host&amp;gt;, where &amp;lt;host&amp;gt; is the host, or host-matching pattern, for an
                 event.
3. source::&amp;lt;source&amp;gt;, where &amp;lt;source&amp;gt; is the source, or source-matching
                     pattern, for an event.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 13 Jul 2016 18:54:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-props-conf-support-wildcards/m-p/255032#M48981</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2016-07-13T18:54:28Z</dc:date>
    </item>
    <item>
      <title>Re: Does props.conf support wildcards?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-props-conf-support-wildcards/m-p/255033#M48982</link>
      <description>&lt;P&gt;I have seen wildcards in source are buggy and don't work as expected.  File bugs.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jul 2016 19:05:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-props-conf-support-wildcards/m-p/255033#M48982</guid>
      <dc:creator>the_wolverine</dc:creator>
      <dc:date>2016-07-13T19:05:21Z</dc:date>
    </item>
    <item>
      <title>Re: Does props.conf support wildcards?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-props-conf-support-wildcards/m-p/746288#M118617</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/1674"&gt;@dshpritz&lt;/a&gt;&amp;nbsp;looks like this is "officially" documented at&amp;nbsp;&lt;A href="https://splunk.my.site.com/customer/s/article/How-To-Use-Wildcards-with-Sourcetype" target="_blank"&gt;https://splunk.my.site.com/customer/s/article/How-To-Use-Wildcards-with-Sourcetype&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 16 May 2025 07:24:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-props-conf-support-wildcards/m-p/746288#M118617</guid>
      <dc:creator>splunkreal</dc:creator>
      <dc:date>2025-05-16T07:24:55Z</dc:date>
    </item>
    <item>
      <title>Re: Does props.conf support wildcards?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-props-conf-support-wildcards/m-p/746331#M118620</link>
      <description>Yes this has added recently into official documentation. But currently there are still e.g. appinspector which didn't accept it in Cloud vetting. What I have heard this will be fixed soon, so then you could use it officially with Cloud too.</description>
      <pubDate>Fri, 16 May 2025 14:20:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-props-conf-support-wildcards/m-p/746331#M118620</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2025-05-16T14:20:26Z</dc:date>
    </item>
  </channel>
</rss>

