<?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 What to do when json field conflicts with Splunk metadata? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/What-to-do-when-json-field-conflicts-with-Splunk-metadata/m-p/346213#M63599</link>
    <description>&lt;P&gt;A user is reporting that their indexed json data has a 'source' key that is being extracted.&lt;/P&gt;

&lt;P&gt;"source": "[{label:'Tree'},{label:'two'},{label:'Three'}]", &lt;/P&gt;

&lt;P&gt;When they search their data, they see:&lt;BR /&gt;
&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/3062i346801FAE1A85611/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;They'd like the original source kept intact. Is there a transforms that I can add to my indexers to rename ONLY the json source?&lt;/P&gt;

&lt;P&gt;The raw json looks like: [ snipped ]&lt;/P&gt;

&lt;P&gt;&lt;EM&gt;"toggleMode":"click", &lt;BR /&gt;
"_toggleMode": {&lt;BR /&gt;
    "desc": "Gets or sets user interaction used for expanding or collapsing any item.",&lt;BR /&gt;
    "type": "enum",&lt;BR /&gt;
    "keys": ["click","dblclick"],&lt;BR /&gt;
    "values": ["click","dblclick"]&lt;BR /&gt;
    },&lt;BR /&gt;
*&lt;/EM&gt;"source": "[{label:'Tree'},{label:'two'},{label:'Three'}]",** &lt;BR /&gt;
"_source": {&lt;BR /&gt;
    "desc": "Sets the initial contents. Easier to do at runtime.",&lt;BR /&gt;
    "type": "css",&lt;BR /&gt;
    "language": "JavaScript"&lt;BR /&gt;
    },*&lt;/P&gt;</description>
    <pubDate>Wed, 14 Jun 2017 14:46:20 GMT</pubDate>
    <dc:creator>pkeller</dc:creator>
    <dc:date>2017-06-14T14:46:20Z</dc:date>
    <item>
      <title>What to do when json field conflicts with Splunk metadata?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-to-do-when-json-field-conflicts-with-Splunk-metadata/m-p/346213#M63599</link>
      <description>&lt;P&gt;A user is reporting that their indexed json data has a 'source' key that is being extracted.&lt;/P&gt;

&lt;P&gt;"source": "[{label:'Tree'},{label:'two'},{label:'Three'}]", &lt;/P&gt;

&lt;P&gt;When they search their data, they see:&lt;BR /&gt;
&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/3062i346801FAE1A85611/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;They'd like the original source kept intact. Is there a transforms that I can add to my indexers to rename ONLY the json source?&lt;/P&gt;

&lt;P&gt;The raw json looks like: [ snipped ]&lt;/P&gt;

&lt;P&gt;&lt;EM&gt;"toggleMode":"click", &lt;BR /&gt;
"_toggleMode": {&lt;BR /&gt;
    "desc": "Gets or sets user interaction used for expanding or collapsing any item.",&lt;BR /&gt;
    "type": "enum",&lt;BR /&gt;
    "keys": ["click","dblclick"],&lt;BR /&gt;
    "values": ["click","dblclick"]&lt;BR /&gt;
    },&lt;BR /&gt;
*&lt;/EM&gt;"source": "[{label:'Tree'},{label:'two'},{label:'Three'}]",** &lt;BR /&gt;
"_source": {&lt;BR /&gt;
    "desc": "Sets the initial contents. Easier to do at runtime.",&lt;BR /&gt;
    "type": "css",&lt;BR /&gt;
    "language": "JavaScript"&lt;BR /&gt;
    },*&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jun 2017 14:46:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-to-do-when-json-field-conflicts-with-Splunk-metadata/m-p/346213#M63599</guid>
      <dc:creator>pkeller</dc:creator>
      <dc:date>2017-06-14T14:46:20Z</dc:date>
    </item>
    <item>
      <title>Re: What to do when json field conflicts with Splunk metadata?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-to-do-when-json-field-conflicts-with-Splunk-metadata/m-p/346214#M63600</link>
      <description>&lt;P&gt;transforms.conf&lt;BR /&gt;
[change_source]&lt;BR /&gt;
REGEX = "source":\s"[(\S+)]&lt;BR /&gt;
FORMAT = source::$1&lt;BR /&gt;
DEST_KEY = MetaData:Source&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 14:27:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-to-do-when-json-field-conflicts-with-Splunk-metadata/m-p/346214#M63600</guid>
      <dc:creator>GauravSplunxter</dc:creator>
      <dc:date>2020-09-29T14:27:42Z</dc:date>
    </item>
  </channel>
</rss>

