<?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 Renaming fields after transform.conf regex in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Renaming-fields-after-transform-conf-regex/m-p/418796#M5948</link>
    <description>&lt;P&gt;We use a transform.conf file with regex to extract the field values. However, the field name in the data input is not in human-readable format. But each value is predictable and we have a reference csv that would allow us to correlate these data together.&lt;/P&gt;

&lt;P&gt;uadhshuasdfiuh = Server1&lt;BR /&gt;
xcoijcxvboijcxvb = Server2  &lt;/P&gt;

&lt;P&gt;These fields are created on the fly and there are hundreds of them. My question is how would automatically rename these fields, to be more usable in the Splunk ui? &lt;/P&gt;</description>
    <pubDate>Tue, 03 Jul 2018 14:24:50 GMT</pubDate>
    <dc:creator>arrowecssupport</dc:creator>
    <dc:date>2018-07-03T14:24:50Z</dc:date>
    <item>
      <title>Renaming fields after transform.conf regex</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Renaming-fields-after-transform-conf-regex/m-p/418796#M5948</link>
      <description>&lt;P&gt;We use a transform.conf file with regex to extract the field values. However, the field name in the data input is not in human-readable format. But each value is predictable and we have a reference csv that would allow us to correlate these data together.&lt;/P&gt;

&lt;P&gt;uadhshuasdfiuh = Server1&lt;BR /&gt;
xcoijcxvboijcxvb = Server2  &lt;/P&gt;

&lt;P&gt;These fields are created on the fly and there are hundreds of them. My question is how would automatically rename these fields, to be more usable in the Splunk ui? &lt;/P&gt;</description>
      <pubDate>Tue, 03 Jul 2018 14:24:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Renaming-fields-after-transform-conf-regex/m-p/418796#M5948</guid>
      <dc:creator>arrowecssupport</dc:creator>
      <dc:date>2018-07-03T14:24:50Z</dc:date>
    </item>
    <item>
      <title>Re: Renaming fields after transform.conf regex</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Renaming-fields-after-transform-conf-regex/m-p/418797#M5949</link>
      <description>&lt;P&gt;use FIELDALIAS in props.conf-&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;FIELDALIAS-&amp;lt;class&amp;gt; = (&amp;lt;orig_field_name&amp;gt; AS &amp;lt;new_field_name&amp;gt;)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;UL&gt;
&lt;LI&gt;Use this to apply aliases to a field. The original field is not removed.
This just means that the original field can be searched on using any of
its aliases.&lt;/LI&gt;
&lt;LI&gt;You can create multiple aliases for the same field.&lt;/LI&gt;
&lt;LI&gt;&lt;CODE&gt;&amp;lt;orig_field_name&amp;gt;&lt;/CODE&gt; is the original name of the field.&lt;/LI&gt;
&lt;LI&gt;&lt;CODE&gt;&amp;lt;new_field_name&amp;gt;&lt;/CODE&gt; is the alias to assign to the field.&lt;/LI&gt;
&lt;LI&gt;You can include multiple field alias renames in the same stanza.&lt;/LI&gt;
&lt;LI&gt;Field aliasing is performed at search time, after field extraction, but
before calculated fields (EVAL-* statements) and lookups.
This means that:
    * Any field extracted at search time can be aliased.
    * You can specify a lookup based on a field alias.
    * You cannot alias a calculated field.&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Tue, 03 Jul 2018 14:48:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Renaming-fields-after-transform-conf-regex/m-p/418797#M5949</guid>
      <dc:creator>493669</dc:creator>
      <dc:date>2018-07-03T14:48:05Z</dc:date>
    </item>
  </channel>
</rss>

