<?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: apply apache field extractions to nonstandard sourcetype in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/apply-apache-field-extractions-to-nonstandard-sourcetype/m-p/404367#M116973</link>
    <description>&lt;P&gt;From UI:&lt;BR /&gt;
You will find Sourcetype Renaming option in Settings --&amp;gt; Fields menu path. Select the Destination App and provide the name of current sourcetype, _newname in your case, and the new sourcetype as newname and click Save.&lt;/P&gt;

&lt;P&gt;From CLI:&lt;BR /&gt;
You can use rename field in props.conf and change the source-type.&lt;/P&gt;</description>
    <pubDate>Mon, 14 Jan 2019 22:04:21 GMT</pubDate>
    <dc:creator>pruthvikrishnap</dc:creator>
    <dc:date>2019-01-14T22:04:21Z</dc:date>
    <item>
      <title>apply apache field extractions to nonstandard sourcetype</title>
      <link>https://community.splunk.com/t5/Splunk-Search/apply-apache-field-extractions-to-nonstandard-sourcetype/m-p/404362#M116968</link>
      <description>&lt;P&gt;Hello, &lt;/P&gt;

&lt;P&gt;I have some apache access logs coming in that I'd like to label &lt;CODE&gt;sourcetype="aem:access"&lt;/CODE&gt; instead of &lt;CODE&gt;sourcetype=access_combined&lt;/CODE&gt;. How do I apply the &lt;CODE&gt;sourcetype=access_combined&lt;/CODE&gt; default extractions to &lt;CODE&gt;sourcetype="aem:access"&lt;/CODE&gt; ? &lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jan 2019 18:52:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/apply-apache-field-extractions-to-nonstandard-sourcetype/m-p/404362#M116968</guid>
      <dc:creator>zhatsispgx</dc:creator>
      <dc:date>2019-01-14T18:52:51Z</dc:date>
    </item>
    <item>
      <title>Re: apply apache field extractions to nonstandard sourcetype</title>
      <link>https://community.splunk.com/t5/Splunk-Search/apply-apache-field-extractions-to-nonstandard-sourcetype/m-p/404363#M116969</link>
      <description>&lt;P&gt;You'd need to copy the field extractions from &lt;CODE&gt;access_combined&lt;/CODE&gt; sourcetype to yoru custom &lt;CODE&gt;aem:access&lt;/CODE&gt; sourcetype. &lt;/P&gt;</description>
      <pubDate>Mon, 14 Jan 2019 20:03:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/apply-apache-field-extractions-to-nonstandard-sourcetype/m-p/404363#M116969</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2019-01-14T20:03:32Z</dc:date>
    </item>
    <item>
      <title>Re: apply apache field extractions to nonstandard sourcetype</title>
      <link>https://community.splunk.com/t5/Splunk-Search/apply-apache-field-extractions-to-nonstandard-sourcetype/m-p/404364#M116970</link>
      <description>&lt;P&gt;where are those field extractions located on my search head? &lt;/P&gt;</description>
      <pubDate>Mon, 14 Jan 2019 20:26:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/apply-apache-field-extractions-to-nonstandard-sourcetype/m-p/404364#M116970</guid>
      <dc:creator>zhatsispgx</dc:creator>
      <dc:date>2019-01-14T20:26:13Z</dc:date>
    </item>
    <item>
      <title>Re: apply apache field extractions to nonstandard sourcetype</title>
      <link>https://community.splunk.com/t5/Splunk-Search/apply-apache-field-extractions-to-nonstandard-sourcetype/m-p/404365#M116971</link>
      <description>&lt;P&gt;This is an in-built sourcetype, so you'd find it in $SPLUNK_HOME/etc/system/default/props.conf. When you're going to create your custom sourcetype, place your props.conf on $SPLUNK_HOME/etc/apps under some app. Do not modify $SPLUNK_HOME/etc/system/default/props.conf.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 22:42:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/apply-apache-field-extractions-to-nonstandard-sourcetype/m-p/404365#M116971</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2020-09-29T22:42:22Z</dc:date>
    </item>
    <item>
      <title>Re: apply apache field extractions to nonstandard sourcetype</title>
      <link>https://community.splunk.com/t5/Splunk-Search/apply-apache-field-extractions-to-nonstandard-sourcetype/m-p/404366#M116972</link>
      <description>&lt;P&gt;if I add to &lt;CODE&gt;$SPLUNK_HOME/etc/system/local/props.conf&lt;/CODE&gt; will that be global so all apps can use those extractions?&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jan 2019 21:16:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/apply-apache-field-extractions-to-nonstandard-sourcetype/m-p/404366#M116972</guid>
      <dc:creator>zhatsispgx</dc:creator>
      <dc:date>2019-01-14T21:16:16Z</dc:date>
    </item>
    <item>
      <title>Re: apply apache field extractions to nonstandard sourcetype</title>
      <link>https://community.splunk.com/t5/Splunk-Search/apply-apache-field-extractions-to-nonstandard-sourcetype/m-p/404367#M116973</link>
      <description>&lt;P&gt;From UI:&lt;BR /&gt;
You will find Sourcetype Renaming option in Settings --&amp;gt; Fields menu path. Select the Destination App and provide the name of current sourcetype, _newname in your case, and the new sourcetype as newname and click Save.&lt;/P&gt;

&lt;P&gt;From CLI:&lt;BR /&gt;
You can use rename field in props.conf and change the source-type.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jan 2019 22:04:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/apply-apache-field-extractions-to-nonstandard-sourcetype/m-p/404367#M116973</guid>
      <dc:creator>pruthvikrishnap</dc:creator>
      <dc:date>2019-01-14T22:04:21Z</dc:date>
    </item>
    <item>
      <title>Re: apply apache field extractions to nonstandard sourcetype</title>
      <link>https://community.splunk.com/t5/Splunk-Search/apply-apache-field-extractions-to-nonstandard-sourcetype/m-p/404368#M116974</link>
      <description>&lt;P&gt;Right,  but &lt;CODE&gt;$SPLUNK_HOME/etc/apps/search/local/props.conf&lt;/CODE&gt; is probably a better place for global app settings.&lt;/P&gt;

&lt;P&gt;Please keep in mind that &lt;CODE&gt;access_combined&lt;/CODE&gt; in &lt;CODE&gt;$SPLUNK_HOME/etc/system/default/props.conf&lt;/CODE&gt; refers to &lt;CODE&gt;$SPLUNK_HOME/etc/system/default/transforms.conf&lt;/CODE&gt; as well.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jan 2019 23:28:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/apply-apache-field-extractions-to-nonstandard-sourcetype/m-p/404368#M116974</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2019-01-14T23:28:38Z</dc:date>
    </item>
    <item>
      <title>Re: apply apache field extractions to nonstandard sourcetype</title>
      <link>https://community.splunk.com/t5/Splunk-Search/apply-apache-field-extractions-to-nonstandard-sourcetype/m-p/404369#M116975</link>
      <description>&lt;P&gt;You could go to  &lt;CODE&gt;props.conf&lt;/CODE&gt; and copy the settings of access combined to your sourcetype.&lt;/P&gt;

&lt;P&gt;Here's the documentation on props.conf&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.2.3/Admin/Propsconf"&gt;https://docs.splunk.com/Documentation/Splunk/7.2.3/Admin/Propsconf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jan 2019 08:13:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/apply-apache-field-extractions-to-nonstandard-sourcetype/m-p/404369#M116975</guid>
      <dc:creator>bangalorep</dc:creator>
      <dc:date>2019-01-15T08:13:02Z</dc:date>
    </item>
  </channel>
</rss>

