<?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: Field extraction on all inputs in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Field-extraction-on-all-inputs/m-p/64233#M15896</link>
    <description>&lt;P&gt;Does this work for your props.conf stanza.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[(?::){0}*]
REPORT-source_combined = source_combined
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I was just looking at this.  &lt;A href="http://splunk-base.splunk.com/answers/24274/can-you-have-a-wildcard-in-a-propsconf-stanza-header-when-matching-sourcetypes"&gt;http://splunk-base.splunk.com/answers/24274/can-you-have-a-wildcard-in-a-propsconf-stanza-header-when-matching-sourcetypes&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 30 May 2012 22:56:49 GMT</pubDate>
    <dc:creator>sdaniels</dc:creator>
    <dc:date>2012-05-30T22:56:49Z</dc:date>
    <item>
      <title>Field extraction on all inputs</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-extraction-on-all-inputs/m-p/64232#M15895</link>
      <description>&lt;P&gt;Is it possible to apply a search-time field extraction to &lt;EM&gt;all&lt;/EM&gt; inputs?&lt;/P&gt;

&lt;P&gt;Our log files (across multiple hosts, sources &amp;amp; sourcetypes) are named like: &lt;CODE&gt;/some/path/[app].XX.log&lt;/CODE&gt; (where XX is a number).  Basically we have one logfile per running process.&lt;/P&gt;

&lt;P&gt;I would like to automatically extract a field like: &lt;CODE&gt;source_combined=/some/path/[app]&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;Here is my transforms.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source_combined]
CLEAN_KEYS = 1
FORMAT = 
MV_ADD = 0
REGEX = ^(?&amp;lt;source_combined&amp;gt;.*?)(\.\d+)?(\.log)?$
SOURCE_KEY = source
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Here is my props.conf that &lt;STRONG&gt;doesn't&lt;/STRONG&gt; work:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[*]
REPORT-source_combined = source_combined
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This props.conf &lt;STRONG&gt;does&lt;/STRONG&gt; work:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[rails]
REPORT-source_combined = source_combined
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;but &lt;STRONG&gt;only&lt;/STRONG&gt; provides the field to the "rails" sourcetype.  I want it to apply to all sourcetypes.  Is there any way to get my extraction to apply to all sourcetypes rather than just one sourcetype?  Is there another way of getting what I want?&lt;/P&gt;</description>
      <pubDate>Wed, 30 May 2012 20:55:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-extraction-on-all-inputs/m-p/64232#M15895</guid>
      <dc:creator>Jordan_Brough</dc:creator>
      <dc:date>2012-05-30T20:55:03Z</dc:date>
    </item>
    <item>
      <title>Re: Field extraction on all inputs</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-extraction-on-all-inputs/m-p/64233#M15896</link>
      <description>&lt;P&gt;Does this work for your props.conf stanza.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[(?::){0}*]
REPORT-source_combined = source_combined
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I was just looking at this.  &lt;A href="http://splunk-base.splunk.com/answers/24274/can-you-have-a-wildcard-in-a-propsconf-stanza-header-when-matching-sourcetypes"&gt;http://splunk-base.splunk.com/answers/24274/can-you-have-a-wildcard-in-a-propsconf-stanza-header-when-matching-sourcetypes&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 30 May 2012 22:56:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-extraction-on-all-inputs/m-p/64233#M15896</guid>
      <dc:creator>sdaniels</dc:creator>
      <dc:date>2012-05-30T22:56:49Z</dc:date>
    </item>
    <item>
      <title>Re: Field extraction on all inputs</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-extraction-on-all-inputs/m-p/64234#M15897</link>
      <description>&lt;P&gt;It does indeed!  Thank you very much!&lt;/P&gt;</description>
      <pubDate>Wed, 30 May 2012 23:59:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-extraction-on-all-inputs/m-p/64234#M15897</guid>
      <dc:creator>Jordan_Brough</dc:creator>
      <dc:date>2012-05-30T23:59:19Z</dc:date>
    </item>
    <item>
      <title>Re: Field extraction on all inputs</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-extraction-on-all-inputs/m-p/64235#M15898</link>
      <description>&lt;P&gt;It's not really any different, but you could also have just used either &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::*]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;or &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[host::*]
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 31 May 2012 05:46:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-extraction-on-all-inputs/m-p/64235#M15898</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2012-05-31T05:46:28Z</dc:date>
    </item>
  </channel>
</rss>

