<?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: how to maintain order in stats  command in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/how-to-maintain-order-in-stats-command/m-p/742827#M240958</link>
    <description>&lt;P&gt;values() sorts (and dedups) - use the list() function (which neither sorts nor dedups)&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;|makeresults
|eval token_id="c75136c4-bdbc-439b"|eval doc_no="GSSAGGOS_QA-2931"|eval key=2931|eval keyword="DK-BAL-AP-00613"
|append [| makeresults |eval token_id="c75136c4-bdbc-439b"|eval doc_no="GSSAGGOS_QA-2932"|eval key=2932|eval keyword="DK-Z13-SW-00002"]
|append [| makeresults |eval token_id="c75136c4-bdbc-439b"|eval doc_no="GSSAGGOS_QA-2933"|eval key=2933|eval keyword="DK-BAL-AP-00847"]
| stats list(key) as key list(keyword) as keyword list(doc_no) as doc_no by token_id
| eval row=mvrange(0,mvcount(doc_no))| mvexpand row| foreach doc_no keyword key
[| eval &amp;lt;&amp;lt;FIELD&amp;gt;&amp;gt;=mvindex(&amp;lt;&amp;lt;FIELD&amp;gt;&amp;gt;,row)]|fields - row&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 27 Mar 2025 15:17:20 GMT</pubDate>
    <dc:creator>ITWhisperer</dc:creator>
    <dc:date>2025-03-27T15:17:20Z</dc:date>
    <item>
      <title>how to maintain order in stats  command</title>
      <link>https://community.splunk.com/t5/Splunk-Search/how-to-maintain-order-in-stats-command/m-p/742815#M240955</link>
      <description>&lt;P&gt;Fields value of 2nd and 3rd events are enter changing. please suggest how to maintain order in Splunk status command. I can't use any other fields in stats by clause than&amp;nbsp;token_id.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;Sample Event:&lt;/STRONG&gt;&lt;/U&gt;&lt;/P&gt;&lt;P&gt;|makeresults&lt;BR /&gt;|eval token_id="c75136c4-bdbc-439b"|eval doc_no="GSSAGGOS_QA-2931"|eval key=2931|eval keyword="DK-BAL-AP-00613"&lt;BR /&gt;|append [| makeresults |eval token_id="c75136c4-bdbc-439b"|eval doc_no="GSSAGGOS_QA-2932"|eval key=2932|eval keyword="DK-Z13-SW-00002"]&lt;BR /&gt;|append [| makeresults |eval token_id="c75136c4-bdbc-439b"|eval doc_no="GSSAGGOS_QA-2933"|eval key=2933|eval keyword="DK-BAL-AP-00847"]&lt;BR /&gt;| stats values(key) as key values(keyword) as keyword values(doc_no) as doc_no by token_id&lt;BR /&gt;| eval row=mvrange(0,mvcount(doc_no))| mvexpand row| foreach doc_no keyword key&lt;BR /&gt;[| eval &amp;lt;&amp;lt;FIELD&amp;gt;&amp;gt;=mvindex(&amp;lt;&amp;lt;FIELD&amp;gt;&amp;gt;,row)]|fields - row&lt;/P&gt;&lt;TABLE width="417"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="416.333px"&gt;&lt;STRONG&gt;Search Result output&lt;/STRONG&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="110.427px"&gt;toke_id&lt;/TD&gt;&lt;TD width="49.0729px"&gt;key&lt;/TD&gt;&lt;TD width="115.938px"&gt;keyword&lt;/TD&gt;&lt;TD width="140.896px"&gt;doc_no&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="110.427px"&gt;c75136c4-bdbc-439b&lt;/TD&gt;&lt;TD width="49.0729px"&gt;2931&lt;/TD&gt;&lt;TD width="115.938px"&gt;DK-BAL-AP-00613&lt;/TD&gt;&lt;TD width="140.896px"&gt;GSSAGGOS_QA-2931&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="110.427px"&gt;c75136c4-bdbc-439b&lt;/TD&gt;&lt;TD width="49.0729px"&gt;2932&lt;/TD&gt;&lt;TD width="115.938px"&gt;&lt;STRONG&gt;DK-BAL-AP-00847&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD width="140.896px"&gt;GSSAGGOS_QA-2932&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="110.427px"&gt;c75136c4-bdbc-439b&lt;/TD&gt;&lt;TD width="49.0729px"&gt;2933&lt;/TD&gt;&lt;TD width="115.938px"&gt;&lt;STRONG&gt;DK-Z13-SW-00002&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD width="140.896px"&gt;GSSAGGOS_QA-2933&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="110.427px"&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD width="49.0729px"&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD width="115.938px"&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD width="140.896px"&gt;&amp;nbsp;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="416.333px"&gt;&lt;STRONG&gt;Expected Output&lt;/STRONG&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="110.427px"&gt;toke_id&lt;/TD&gt;&lt;TD width="49.0729px"&gt;key&lt;/TD&gt;&lt;TD width="115.938px"&gt;keyword&lt;/TD&gt;&lt;TD width="140.896px"&gt;doc_no&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="110.427px"&gt;c75136c4-bdbc-439b&lt;/TD&gt;&lt;TD width="49.0729px"&gt;2931&lt;/TD&gt;&lt;TD width="115.938px"&gt;DK-BAL-AP-00613&lt;/TD&gt;&lt;TD width="140.896px"&gt;GSSAGGOS_QA-2931&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="110.427px"&gt;c75136c4-bdbc-439b&lt;/TD&gt;&lt;TD width="49.0729px"&gt;2932&lt;/TD&gt;&lt;TD width="115.938px"&gt;&lt;STRONG&gt;DK-Z13-SW-00002&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD width="140.896px"&gt;GSSAGGOS_QA-2932&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="110.427px"&gt;c75136c4-bdbc-439b&lt;/TD&gt;&lt;TD width="49.0729px"&gt;2933&lt;/TD&gt;&lt;TD width="115.938px"&gt;&lt;STRONG&gt;DK-BAL-AP-00847&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD width="140.896px"&gt;GSSAGGOS_QA-2933&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Thu, 27 Mar 2025 13:49:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/how-to-maintain-order-in-stats-command/m-p/742815#M240955</guid>
      <dc:creator>RSS_STT</dc:creator>
      <dc:date>2025-03-27T13:49:20Z</dc:date>
    </item>
    <item>
      <title>Re: how to maintain order in stats  command</title>
      <link>https://community.splunk.com/t5/Splunk-Search/how-to-maintain-order-in-stats-command/m-p/742816#M240956</link>
      <description>&lt;P&gt;The output of the &lt;FONT face="courier new,courier"&gt;values&lt;/FONT&gt; &lt;STRIKE&gt;and &lt;FONT face="courier new,courier"&gt;list&lt;/FONT&gt;&lt;/STRIKE&gt; functions are always in lexicographical order.&amp;nbsp; That destroys any relationship that might exist between/among fields.&lt;/P&gt;&lt;P&gt;The solution is to combine related fields into a single field before &lt;FONT face="courier new,courier"&gt;stats&lt;/FONT&gt; and then break them apart again afterwards.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| eval tuple = mvzip(keyword, doc_no)
| stats values(tuple) as tuple by token_id
| eval pairs = split(tuple, ",")
| eval keyword = mvindex(pairs,0), doc_no = mvindex(pairs, 1)
| fields - tuple, pairs&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Mar 2025 16:10:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/how-to-maintain-order-in-stats-command/m-p/742816#M240956</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2025-03-27T16:10:24Z</dc:date>
    </item>
    <item>
      <title>Re: how to maintain order in stats  command</title>
      <link>https://community.splunk.com/t5/Splunk-Search/how-to-maintain-order-in-stats-command/m-p/742819#M240957</link>
      <description>&lt;P&gt;split function proving error.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Mar 2025 14:27:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/how-to-maintain-order-in-stats-command/m-p/742819#M240957</guid>
      <dc:creator>RSS_STT</dc:creator>
      <dc:date>2025-03-27T14:27:55Z</dc:date>
    </item>
    <item>
      <title>Re: how to maintain order in stats  command</title>
      <link>https://community.splunk.com/t5/Splunk-Search/how-to-maintain-order-in-stats-command/m-p/742827#M240958</link>
      <description>&lt;P&gt;values() sorts (and dedups) - use the list() function (which neither sorts nor dedups)&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;|makeresults
|eval token_id="c75136c4-bdbc-439b"|eval doc_no="GSSAGGOS_QA-2931"|eval key=2931|eval keyword="DK-BAL-AP-00613"
|append [| makeresults |eval token_id="c75136c4-bdbc-439b"|eval doc_no="GSSAGGOS_QA-2932"|eval key=2932|eval keyword="DK-Z13-SW-00002"]
|append [| makeresults |eval token_id="c75136c4-bdbc-439b"|eval doc_no="GSSAGGOS_QA-2933"|eval key=2933|eval keyword="DK-BAL-AP-00847"]
| stats list(key) as key list(keyword) as keyword list(doc_no) as doc_no by token_id
| eval row=mvrange(0,mvcount(doc_no))| mvexpand row| foreach doc_no keyword key
[| eval &amp;lt;&amp;lt;FIELD&amp;gt;&amp;gt;=mvindex(&amp;lt;&amp;lt;FIELD&amp;gt;&amp;gt;,row)]|fields - row&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Mar 2025 15:17:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/how-to-maintain-order-in-stats-command/m-p/742827#M240958</guid>
      <dc:creator>ITWhisperer</dc:creator>
      <dc:date>2025-03-27T15:17:20Z</dc:date>
    </item>
    <item>
      <title>Re: how to maintain order in stats  command</title>
      <link>https://community.splunk.com/t5/Splunk-Search/how-to-maintain-order-in-stats-command/m-p/742843#M240960</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/261968"&gt;@RSS_STT&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;split function proving error.&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I'm not sure what to make of that, but take it you get an (undescribed) error with the code I provided.&amp;nbsp; I found a missing argument so please try the revised SPL.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Mar 2025 16:11:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/how-to-maintain-order-in-stats-command/m-p/742843#M240960</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2025-03-27T16:11:48Z</dc:date>
    </item>
  </channel>
</rss>

