<?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: Why are field values lost using the table command after the transaction command? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Why-are-field-values-lost-using-the-table-command-after-the/m-p/240382#M71438</link>
    <description>&lt;P&gt;Smart mode&lt;/P&gt;</description>
    <pubDate>Fri, 22 Jan 2016 06:57:57 GMT</pubDate>
    <dc:creator>tenorway</dc:creator>
    <dc:date>2016-01-22T06:57:57Z</dc:date>
    <item>
      <title>Why are field values lost using the table command after the transaction command?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-are-field-values-lost-using-the-table-command-after-the/m-p/240378#M71434</link>
      <description>&lt;P&gt;Hi all!&lt;/P&gt;

&lt;P&gt;I am using the &lt;CODE&gt;transaction&lt;/CODE&gt; command to group events based on an identifier occuring in separate indexes. Works nicely. The events shows up with all the information. In the left of the Splunk window, all expected fields from both indexes have values. &lt;/P&gt;

&lt;P&gt;However, when trying to display some of the fields using the &lt;CODE&gt;table&lt;/CODE&gt; command, only the fields from one of the indexes have values. The others are empty. &lt;/P&gt;

&lt;P&gt;Piping the output from the &lt;CODE&gt;transaction&lt;/CODE&gt; command through the &lt;CODE&gt;fields&lt;/CODE&gt; command fixes the problem, but why is this happening?&lt;/P&gt;

&lt;P&gt;Doesn't work (Path is blank): &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=* | rename correlationId as CID | transaction CID | table host, path
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Works (Both fields have values): &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=* | rename correlationId as CID | transaction CID | fields * | table host,path
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Thanks for any assistance!&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jan 2016 08:04:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-are-field-values-lost-using-the-table-command-after-the/m-p/240378#M71434</guid>
      <dc:creator>tenorway</dc:creator>
      <dc:date>2016-01-21T08:04:31Z</dc:date>
    </item>
    <item>
      <title>Re: Why are field values lost using the table command after the transaction command?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-are-field-values-lost-using-the-table-command-after-the/m-p/240379#M71435</link>
      <description>&lt;P&gt;Not sure why both searches are not returning the same results but for the sake of performance I would use the following anyway:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=* 
| rename correlationId as CID
| fields host, path, CID
| stats values(path) as path, values(host) as host by CID
| table host, path
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 21 Jan 2016 09:54:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-are-field-values-lost-using-the-table-command-after-the/m-p/240379#M71435</guid>
      <dc:creator>javiergn</dc:creator>
      <dc:date>2016-01-21T09:54:28Z</dc:date>
    </item>
    <item>
      <title>Re: Why are field values lost using the table command after the transaction command?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-are-field-values-lost-using-the-table-command-after-the/m-p/240380#M71436</link>
      <description>&lt;P&gt;Are your search results set to 'Fast Mode'?  If so, Splunk will only extract the fields that it needs (like the default host, source, sourcetype, _time, etc) and the fields that you explicitly state in your search. If you want most or all fields extracted you will need to use either 'Smart Mode' or 'Verbose Mode'.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jan 2016 14:05:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-are-field-values-lost-using-the-table-command-after-the/m-p/240380#M71436</guid>
      <dc:creator>wpreston</dc:creator>
      <dc:date>2016-01-21T14:05:57Z</dc:date>
    </item>
    <item>
      <title>Re: Why are field values lost using the table command after the transaction command?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-are-field-values-lost-using-the-table-command-after-the/m-p/240381#M71437</link>
      <description>&lt;P&gt;Thanks for the reply. The path variable will not be present in all events. &lt;BR /&gt;
The web will log the path, and the middleware will log other fields. &lt;BR /&gt;
Will I then be able to display the whole "transaction" in one row using stats? &lt;/P&gt;</description>
      <pubDate>Fri, 22 Jan 2016 06:57:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-are-field-values-lost-using-the-table-command-after-the/m-p/240381#M71437</guid>
      <dc:creator>tenorway</dc:creator>
      <dc:date>2016-01-22T06:57:24Z</dc:date>
    </item>
    <item>
      <title>Re: Why are field values lost using the table command after the transaction command?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-are-field-values-lost-using-the-table-command-after-the/m-p/240382#M71438</link>
      <description>&lt;P&gt;Smart mode&lt;/P&gt;</description>
      <pubDate>Fri, 22 Jan 2016 06:57:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-are-field-values-lost-using-the-table-command-after-the/m-p/240382#M71438</guid>
      <dc:creator>tenorway</dc:creator>
      <dc:date>2016-01-22T06:57:57Z</dc:date>
    </item>
  </channel>
</rss>

