<?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 How can we access perfect json events after applying the transaction command? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-can-we-access-perfect-json-events-after-applying-the/m-p/372207#M67547</link>
    <description>&lt;P&gt;With lots of help here, we adjusted the incoming data to be perfect json structures and name value pairs are extracted nicely now that each json document is mapped to one Splunk event. &lt;/P&gt;

&lt;P&gt;We would like know to proceed and use the &lt;CODE&gt;transaction&lt;/CODE&gt; command. But by applying the &lt;CODE&gt;transaction&lt;/CODE&gt; command, we'll lose the perfect json structure, right? &lt;/P&gt;

&lt;P&gt;What can be done?&lt;/P&gt;</description>
    <pubDate>Fri, 09 Feb 2018 20:53:44 GMT</pubDate>
    <dc:creator>ddrillic</dc:creator>
    <dc:date>2018-02-09T20:53:44Z</dc:date>
    <item>
      <title>How can we access perfect json events after applying the transaction command?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-we-access-perfect-json-events-after-applying-the/m-p/372207#M67547</link>
      <description>&lt;P&gt;With lots of help here, we adjusted the incoming data to be perfect json structures and name value pairs are extracted nicely now that each json document is mapped to one Splunk event. &lt;/P&gt;

&lt;P&gt;We would like know to proceed and use the &lt;CODE&gt;transaction&lt;/CODE&gt; command. But by applying the &lt;CODE&gt;transaction&lt;/CODE&gt; command, we'll lose the perfect json structure, right? &lt;/P&gt;

&lt;P&gt;What can be done?&lt;/P&gt;</description>
      <pubDate>Fri, 09 Feb 2018 20:53:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-we-access-perfect-json-events-after-applying-the/m-p/372207#M67547</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2018-02-09T20:53:44Z</dc:date>
    </item>
    <item>
      <title>Re: How can we access perfect json events after applying the transaction command?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-we-access-perfect-json-events-after-applying-the/m-p/372208#M67548</link>
      <description>&lt;P&gt;When you use &lt;CODE&gt;transaction&lt;/CODE&gt;, that will create multi-value fields out of fields that exist in multiple events that are being combined. But that's always true when you use &lt;CODE&gt;transaction&lt;/CODE&gt;, so it's really no different than using it with events of other structures. Or am I missing what you're saying here?&lt;/P&gt;</description>
      <pubDate>Fri, 09 Feb 2018 22:08:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-we-access-perfect-json-events-after-applying-the/m-p/372208#M67548</guid>
      <dc:creator>elliotproebstel</dc:creator>
      <dc:date>2018-02-09T22:08:10Z</dc:date>
    </item>
    <item>
      <title>Re: How can we access perfect json events after applying the transaction command?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-we-access-perfect-json-events-after-applying-the/m-p/372209#M67549</link>
      <description>&lt;P&gt;My question would be, "what do you want to do with the JSON structures after you've run &lt;CODE&gt;transaction&lt;/CODE&gt;?  Could you accomplish what you need without transaction (often possible, but not always)?  And perhaps do you really need the JSON structures of individual events at the end of all of that?&lt;/P&gt;</description>
      <pubDate>Sat, 10 Feb 2018 02:54:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-we-access-perfect-json-events-after-applying-the/m-p/372209#M67549</guid>
      <dc:creator>micahkemp</dc:creator>
      <dc:date>2018-02-10T02:54:27Z</dc:date>
    </item>
  </channel>
</rss>

