<?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: How to configure search-time fields in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-to-configure-search-time-fields/m-p/28463#M5641</link>
    <description>&lt;P&gt;Looks like you already figured out the first part, but just in case, here's a good reference:
&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
&lt;A href="http://www.splunk.com/base/Documentation/latest/Knowledge/Createandmaintainsearch-timefieldextractionsthroughconfigurationfiles#First.2C_define_a_field_transform" rel="nofollow"&gt;http://www.splunk.com/base/Documentation/latest/Knowledge/Createandmaintainsearch-timefieldextractionsthroughconfigurationfiles#First.2C_define_a_field_transform&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;If you want the extraction to apply to &lt;I&gt;all&lt;/I&gt; sourcetypes, then just &lt;B&gt;create your entry in props.conf at the top of the file&lt;/B&gt;, outside of any stanza heading. Entries in the file that are not beneath a &lt;CODE&gt;[stanza]&lt;/CODE&gt; header are considered to be global.&lt;/P&gt;

&lt;P&gt;There's no way to do a wildcard like &lt;CODE&gt;[log4j-*]&lt;/CODE&gt;, at least as of Splunk 4.1. There are three main options:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Define the extraction globally, putting your &lt;CODE&gt;EXTRACT-xxx&lt;/CODE&gt; or &lt;CODE&gt;REPORT-xxx&lt;/CODE&gt; line at the top of props.conf.&lt;/LI&gt;
&lt;LI&gt;Define the extraction multiple times, with a separate stanza for each sourcetype&lt;/LI&gt;
&lt;LI&gt;Define the extraction for sourcetype &lt;CODE&gt;[log4j]&lt;/CODE&gt;, and &lt;A href="http://www.splunk.com/base/Documentation/4.1.6/Admin/Renamesourcetypes" rel="nofollow"&gt;rename&lt;/A&gt; each log4j-xxx sourcetype. Going forward, manually assign the sourcetype so that you don't get the variations.&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Option 3 is usually preferable.&lt;/P&gt;</description>
    <pubDate>Wed, 19 Jan 2011 23:57:32 GMT</pubDate>
    <dc:creator>southeringtonp</dc:creator>
    <dc:date>2011-01-19T23:57:32Z</dc:date>
    <item>
      <title>How to configure search-time fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-configure-search-time-fields/m-p/28460#M5638</link>
      <description>&lt;P&gt;I cannot find in the manual how to configure search-time field extraction. I would like to define some fields that apply across all sourcetype. I was told by a splunk trainer that you can't do that using the interactive field extraction tool but can do it in the configuration files.&lt;/P&gt;

&lt;P&gt;Anyway I've search through the documentation and can't find either an example of description of how to do this.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jan 2011 08:57:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-configure-search-time-fields/m-p/28460#M5638</guid>
      <dc:creator>mburbidg</dc:creator>
      <dc:date>2011-01-19T08:57:15Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure search-time fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-configure-search-time-fields/m-p/28461#M5639</link>
      <description>&lt;P&gt;I found the documentation in the knowledge worker manual. I put the following in etc/system/local/props.conf&lt;/P&gt;

&lt;P&gt;[log4j*]&lt;BR /&gt;
EXTRACT-magazineTitle = (?i) magazineTitle:(?P&lt;MAGAZINETITLE&gt;.+?)\s+\w+:&lt;/MAGAZINETITLE&gt;&lt;/P&gt;

&lt;P&gt;The extractions shows up in the fields manager, but when I do searches it does not show up in the field picker. Is that normal?&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jan 2011 10:04:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-configure-search-time-fields/m-p/28461#M5639</guid>
      <dc:creator>mburbidg</dc:creator>
      <dc:date>2011-01-19T10:04:40Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure search-time fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-configure-search-time-fields/m-p/28462#M5640</link>
      <description>&lt;P&gt;I discovered that if the sourcetype is log4j-100, which is a single instances of a set of rolling logs then the field shows up in the field picker and works. Can't I wildcard the sourcetype?&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jan 2011 10:13:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-configure-search-time-fields/m-p/28462#M5640</guid>
      <dc:creator>mburbidg</dc:creator>
      <dc:date>2011-01-19T10:13:41Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure search-time fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-configure-search-time-fields/m-p/28463#M5641</link>
      <description>&lt;P&gt;Looks like you already figured out the first part, but just in case, here's a good reference:
&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
&lt;A href="http://www.splunk.com/base/Documentation/latest/Knowledge/Createandmaintainsearch-timefieldextractionsthroughconfigurationfiles#First.2C_define_a_field_transform" rel="nofollow"&gt;http://www.splunk.com/base/Documentation/latest/Knowledge/Createandmaintainsearch-timefieldextractionsthroughconfigurationfiles#First.2C_define_a_field_transform&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;If you want the extraction to apply to &lt;I&gt;all&lt;/I&gt; sourcetypes, then just &lt;B&gt;create your entry in props.conf at the top of the file&lt;/B&gt;, outside of any stanza heading. Entries in the file that are not beneath a &lt;CODE&gt;[stanza]&lt;/CODE&gt; header are considered to be global.&lt;/P&gt;

&lt;P&gt;There's no way to do a wildcard like &lt;CODE&gt;[log4j-*]&lt;/CODE&gt;, at least as of Splunk 4.1. There are three main options:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Define the extraction globally, putting your &lt;CODE&gt;EXTRACT-xxx&lt;/CODE&gt; or &lt;CODE&gt;REPORT-xxx&lt;/CODE&gt; line at the top of props.conf.&lt;/LI&gt;
&lt;LI&gt;Define the extraction multiple times, with a separate stanza for each sourcetype&lt;/LI&gt;
&lt;LI&gt;Define the extraction for sourcetype &lt;CODE&gt;[log4j]&lt;/CODE&gt;, and &lt;A href="http://www.splunk.com/base/Documentation/4.1.6/Admin/Renamesourcetypes" rel="nofollow"&gt;rename&lt;/A&gt; each log4j-xxx sourcetype. Going forward, manually assign the sourcetype so that you don't get the variations.&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Option 3 is usually preferable.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jan 2011 23:57:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-configure-search-time-fields/m-p/28463#M5641</guid>
      <dc:creator>southeringtonp</dc:creator>
      <dc:date>2011-01-19T23:57:32Z</dc:date>
    </item>
  </channel>
</rss>

