<?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: Applying Field Extractions to Several Sourcetypes in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118087#M31487</link>
    <description>&lt;P&gt;Thanks for your replies, JHowkins; I'll see how i can make this fit. With some 20-odd sourcetypes and a projected 5 or 6 extractions per sourcetype, anything I can do to avoid creating them manually will be blessing.&lt;/P&gt;</description>
    <pubDate>Tue, 08 Apr 2014 16:04:35 GMT</pubDate>
    <dc:creator>niall_munnelly</dc:creator>
    <dc:date>2014-04-08T16:04:35Z</dc:date>
    <item>
      <title>Applying Field Extractions to Several Sourcetypes</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118083#M31483</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;
Per a policy I've inherited, we're separating our business groups' web server logs into separate sourcetypes. It seems it would be easier if I could create a transform and use tags, but the dude running the show is averse to these solutions.&lt;/P&gt;

&lt;P&gt;So we have maybe 20 sourcetypes, named&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;foo_apache_access&lt;/LI&gt;
&lt;LI&gt;bar_apache_access&lt;/LI&gt;
&lt;LI&gt;baz_apache_access&lt;/LI&gt;
&lt;LI&gt;quux_apache_access&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;...and so on. This has made creating a standard collection of extracted fields tricky; it seems like I have to create the extractions within every sourcetype, which is manual and slow. I'm also not getting consistent results for some of the extracted fields in one sourcetype vs another, so I may have to break my combined regex patterns into several individual extractions, making the whole process way slower and sloppier, still.&lt;/P&gt;

&lt;P&gt;Wildcard characters appear to be parsed literally, so *_apache_access didn't work as hoped. Have I missed something? Is there a wildcard or UI command I can use to effect this? Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2014 21:16:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118083#M31483</guid>
      <dc:creator>niall_munnelly</dc:creator>
      <dc:date>2014-04-02T21:16:13Z</dc:date>
    </item>
    <item>
      <title>Re: Applying Field Extractions to Several Sourcetypes</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118084#M31484</link>
      <description>&lt;P&gt;I ran into a similar issue where I have 60 different sourcetypes all belonging to the same host.&lt;/P&gt;

&lt;P&gt;Depending on the contents of your files, you could create a transform and/or extraction that captures similar things contained within each file. When you create your regex pattern, just make sure it qualifies something within the data that distinguishes it from everything else.&lt;/P&gt;

&lt;P&gt;If you can provide an example of the file contents and your intentions, I can provide a better answer.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2014 23:08:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118084#M31484</guid>
      <dc:creator>jhowkins</dc:creator>
      <dc:date>2014-04-02T23:08:54Z</dc:date>
    </item>
    <item>
      <title>Re: Applying Field Extractions to Several Sourcetypes</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118085#M31485</link>
      <description>&lt;P&gt;To answer your question, yes there is a way to use wildcards to use a single extraction against multiple sourcetypes. See my answer below.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Apr 2014 00:50:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118085#M31485</guid>
      <dc:creator>jhowkins</dc:creator>
      <dc:date>2014-04-08T00:50:50Z</dc:date>
    </item>
    <item>
      <title>Re: Applying Field Extractions to Several Sourcetypes</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118086#M31486</link>
      <description>&lt;P&gt;If you would rather create an extraction by sourcetype and using a wildcard, you can do it but it requires a little regex trickery...&lt;/P&gt;

&lt;P&gt;To capture the sourcetypes you provided, you can use the following as your sourcetype;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;(?::){0}*_apache_access
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 08 Apr 2014 02:15:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118086#M31486</guid>
      <dc:creator>jhowkins</dc:creator>
      <dc:date>2014-04-08T02:15:02Z</dc:date>
    </item>
    <item>
      <title>Re: Applying Field Extractions to Several Sourcetypes</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118087#M31487</link>
      <description>&lt;P&gt;Thanks for your replies, JHowkins; I'll see how i can make this fit. With some 20-odd sourcetypes and a projected 5 or 6 extractions per sourcetype, anything I can do to avoid creating them manually will be blessing.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Apr 2014 16:04:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118087#M31487</guid>
      <dc:creator>niall_munnelly</dc:creator>
      <dc:date>2014-04-08T16:04:35Z</dc:date>
    </item>
    <item>
      <title>Re: Applying Field Extractions to Several Sourcetypes</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118088#M31488</link>
      <description>&lt;P&gt;This totally worked! Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 23 Apr 2014 15:35:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118088#M31488</guid>
      <dc:creator>niall_munnelly</dc:creator>
      <dc:date>2014-04-23T15:35:33Z</dc:date>
    </item>
    <item>
      <title>Re: Applying Field Extractions to Several Sourcetypes</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118089#M31489</link>
      <description>&lt;P&gt;I have the same problem.  I need a regular expression to identify several sourcetypes.  Examples of the source types are as follows:&lt;/P&gt;

&lt;P&gt;application-ucop-topcop-pub:default-2&lt;BR /&gt;
application-ucop-bft-nais-sub:default&lt;BR /&gt;
application-ucop-bft-pub:default&lt;/P&gt;

&lt;P&gt;I know that "application-ucop" and ":default" will remain constant, but in between them will be different one word or two words separated by a "-".  Also some of them have nothing after :default and some have a "-" followed by a number.&lt;/P&gt;

&lt;P&gt;I have never worked with regular expressions and I am trying to simplify my field extractions.  Thank you.&lt;/P&gt;</description>
      <pubDate>Thu, 26 May 2016 13:40:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118089#M31489</guid>
      <dc:creator>UCOP</dc:creator>
      <dc:date>2016-05-26T13:40:19Z</dc:date>
    </item>
    <item>
      <title>Re: Applying Field Extractions to Several Sourcetypes</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118090#M31490</link>
      <description>&lt;P&gt;have you ever find out the answer for this?&lt;/P&gt;</description>
      <pubDate>Mon, 26 Jun 2017 17:01:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118090#M31490</guid>
      <dc:creator>ss026381</dc:creator>
      <dc:date>2017-06-26T17:01:45Z</dc:date>
    </item>
    <item>
      <title>Re: Applying Field Extractions to Several Sourcetypes</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118091#M31491</link>
      <description>&lt;P&gt;What if the soucetype is not in the text where you want to do the extraction?&lt;/P&gt;

&lt;P&gt;2 source types &lt;BR /&gt;
XBSN&lt;BR /&gt;
QSN&lt;/P&gt;

&lt;P&gt;need 2 extractions on each sourctype:&lt;BR /&gt;
^[^/\n]&lt;EM&gt;/\w+:(?P[^"]+)&lt;BR /&gt;
^[^/\n]&lt;/EM&gt;/\w+:(?P[^"]+)&lt;/P&gt;

&lt;P&gt;Where do I specify the sourcetype?  &lt;/P&gt;</description>
      <pubDate>Sun, 03 Sep 2017 22:47:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Applying-Field-Extractions-to-Several-Sourcetypes/m-p/118091#M31491</guid>
      <dc:creator>HattrickNZ</dc:creator>
      <dc:date>2017-09-03T22:47:25Z</dc:date>
    </item>
  </channel>
</rss>

