<?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: Alias bug that merge &amp;quot;NEW&amp;quot; word into new field in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Alias-bug-that-merge-quot-NEW-quot-word-into-new-field/m-p/444193#M125981</link>
    <description>&lt;P&gt;@sonsee78 use the option &lt;CODE&gt;Overwrite field values&lt;/CODE&gt; while creating &lt;CODE&gt;Field Alias&lt;/CODE&gt; otherwise above is expected behavior.&lt;/P&gt;</description>
    <pubDate>Fri, 28 Jun 2019 03:19:47 GMT</pubDate>
    <dc:creator>niketn</dc:creator>
    <dc:date>2019-06-28T03:19:47Z</dc:date>
    <item>
      <title>Alias bug that merge "NEW" word into new field</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Alias-bug-that-merge-quot-NEW-quot-word-into-new-field/m-p/444191#M125979</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;
I have been watching a problem when I was using alias function through the SPLUNK Web.&lt;BR /&gt;
That problem was merged "NEW" word, both have Web and CLI.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;WEB UI
Field aliases
Fields » Field aliases

Name    Field aliases   Owner   App Sharing Status  Actions
syslog : FIELDALIAS-process_to_pcs  process ASNEW pcs  admin  search Global | Permissions   Enabled Clone | Move | Delete
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;CLI &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;/opt/splunk/etc/system/local/props.conf
[syslog]
FIELDALIAS-process_to_pcs = process ASNEW pcs
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Best Regards&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jun 2019 01:23:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Alias-bug-that-merge-quot-NEW-quot-word-into-new-field/m-p/444191#M125979</guid>
      <dc:creator>sonsee78</dc:creator>
      <dc:date>2019-06-28T01:23:19Z</dc:date>
    </item>
    <item>
      <title>Re: Alias bug that merge "NEW" word into new field</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Alias-bug-that-merge-quot-NEW-quot-word-into-new-field/m-p/444192#M125980</link>
      <description>&lt;P&gt;I saw bug at the SPLUNK Enterprise version 7.3.0.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jun 2019 01:29:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Alias-bug-that-merge-quot-NEW-quot-word-into-new-field/m-p/444192#M125980</guid>
      <dc:creator>sonsee78</dc:creator>
      <dc:date>2019-06-28T01:29:45Z</dc:date>
    </item>
    <item>
      <title>Re: Alias bug that merge "NEW" word into new field</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Alias-bug-that-merge-quot-NEW-quot-word-into-new-field/m-p/444193#M125981</link>
      <description>&lt;P&gt;@sonsee78 use the option &lt;CODE&gt;Overwrite field values&lt;/CODE&gt; while creating &lt;CODE&gt;Field Alias&lt;/CODE&gt; otherwise above is expected behavior.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jun 2019 03:19:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Alias-bug-that-merge-quot-NEW-quot-word-into-new-field/m-p/444193#M125981</guid>
      <dc:creator>niketn</dc:creator>
      <dc:date>2019-06-28T03:19:47Z</dc:date>
    </item>
  </channel>
</rss>

