<?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: Internal field `_serial` is gone in v6.2.3; why? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Internal-field-serial-is-gone-in-v6-2-3-why/m-p/155402#M185688</link>
    <description>&lt;P&gt;Based on the comment by @acharlieh I went back and played around and have concluded that &lt;CODE&gt;_serial&lt;/CODE&gt; only exists for the first set of events that are returned (whatever is under the &lt;CODE&gt;events&lt;/CODE&gt; tab).  Evidently &lt;CODE&gt;_serial&lt;/CODE&gt; is destroyed by doing any other commands which modify the initial result-set in any way, never to be recalculated.  This is extremely unfortunate since this makes &lt;CODE&gt;_serial&lt;/CODE&gt; pretty much useless.  My situation was that I was hoping to use it after doing a &lt;CODE&gt;stats&lt;/CODE&gt; command but it is gone by then.  To remedy this, I regenerated &lt;CODE&gt;_serial&lt;/CODE&gt; myself like this instead:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;... | streamstats current=f count AS _serial
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Sat, 13 Jun 2015 21:04:58 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2015-06-13T21:04:58Z</dc:date>
    <item>
      <title>Internal field `_serial` is gone in v6.2.3; why?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Internal-field-serial-is-gone-in-v6-2-3-why/m-p/155399#M185685</link>
      <description>&lt;P&gt;I only just found out about the existence of the internal &lt;CODE&gt;_serial&lt;/CODE&gt; field which should be equal to the row-number less 1 (e.g. first row has &lt;CODE&gt;_serial&lt;/CODE&gt; value of 0, second row has &lt;CODE&gt;_serial&lt;/CODE&gt; value of 1, etc.) but no matter what I do, I cannot get examples that have been posted here before that use &lt;CODE&gt;_serial&lt;/CODE&gt; to work.  What is the deal with &lt;CODE&gt;_serial&lt;/CODE&gt;?  When did it go away and was it deliberate or a bug?&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jun 2015 13:29:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Internal-field-serial-is-gone-in-v6-2-3-why/m-p/155399#M185685</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-06-12T13:29:43Z</dc:date>
    </item>
    <item>
      <title>Re: Internal field `_serial` is gone in v6.2.3; why?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Internal-field-serial-is-gone-in-v6-2-3-why/m-p/155400#M185686</link>
      <description>&lt;P&gt;I never heard of this field. What is the notion of row number in splunk ?&lt;BR /&gt;
was it for CSV files ? Because this is gone since the 6.* and the INDEXED_EXTRACTIONS.&lt;/P&gt;

&lt;P&gt;In case the field is there but hidden, try :&lt;BR /&gt;
- try to cast it in a field with an eval first.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;my search&amp;gt; | eval serial=_serial | table serial _raw
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;or maybe try to add it to the fields.conf&lt;/P&gt;</description>
      <pubDate>Sat, 13 Jun 2015 12:56:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Internal-field-serial-is-gone-in-v6-2-3-why/m-p/155400#M185686</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2015-06-13T12:56:42Z</dc:date>
    </item>
    <item>
      <title>Re: Internal field `_serial` is gone in v6.2.3; why?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Internal-field-serial-is-gone-in-v6-2-3-why/m-p/155401#M185687</link>
      <description>&lt;P&gt;I upgraded a 6.2.1 instance to 6.2.3 and I'm able to still see &lt;CODE&gt;_serial&lt;/CODE&gt; and other hidden fields in results doing a search like &lt;CODE&gt;index=_internal | fields - _raw | rename _* as *_x | table *_x&lt;/CODE&gt;  That said, _serial and other hidden fields can be altered and destroyed by transforming commands. So the question is what examples are you trying that seem to not be working?&lt;/P&gt;</description>
      <pubDate>Sat, 13 Jun 2015 20:40:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Internal-field-serial-is-gone-in-v6-2-3-why/m-p/155401#M185687</guid>
      <dc:creator>acharlieh</dc:creator>
      <dc:date>2015-06-13T20:40:23Z</dc:date>
    </item>
    <item>
      <title>Re: Internal field `_serial` is gone in v6.2.3; why?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Internal-field-serial-is-gone-in-v6-2-3-why/m-p/155402#M185688</link>
      <description>&lt;P&gt;Based on the comment by @acharlieh I went back and played around and have concluded that &lt;CODE&gt;_serial&lt;/CODE&gt; only exists for the first set of events that are returned (whatever is under the &lt;CODE&gt;events&lt;/CODE&gt; tab).  Evidently &lt;CODE&gt;_serial&lt;/CODE&gt; is destroyed by doing any other commands which modify the initial result-set in any way, never to be recalculated.  This is extremely unfortunate since this makes &lt;CODE&gt;_serial&lt;/CODE&gt; pretty much useless.  My situation was that I was hoping to use it after doing a &lt;CODE&gt;stats&lt;/CODE&gt; command but it is gone by then.  To remedy this, I regenerated &lt;CODE&gt;_serial&lt;/CODE&gt; myself like this instead:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;... | streamstats current=f count AS _serial
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sat, 13 Jun 2015 21:04:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Internal-field-serial-is-gone-in-v6-2-3-why/m-p/155402#M185688</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-06-13T21:04:58Z</dc:date>
    </item>
  </channel>
</rss>

