<?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: deprecated 'stats' command syntax notification on a sample Splunk search in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/deprecated-stats-command-syntax-notification-on-a-sample-Splunk/m-p/514793#M144502</link>
    <description>&lt;P&gt;Turns out this particular example is a bug. Splunk 8.0.0 through 8.0.6 generates this "info message" when you use sparkline without an argument (such as sparkline(count) or sparkline(count(cpu)). This isn't supposed to happen. The bug is fixed in upcoming versions of Splunk.&amp;nbsp;&lt;/P&gt;&lt;P&gt;As for supporting deprecated syntax - well, sometimes we do that for backwards-compatibility, when people are upgrading from older versions of the product.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 18 Aug 2020 23:06:57 GMT</pubDate>
    <dc:creator>mattness</dc:creator>
    <dc:date>2020-08-18T23:06:57Z</dc:date>
    <item>
      <title>deprecated 'stats' command syntax notification on a sample Splunk search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/deprecated-stats-command-syntax-notification-on-a-sample-Splunk/m-p/513951#M144246</link>
      <description>&lt;P&gt;Running a sample search suggested by&amp;nbsp;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.5/Search/Addsparklinestosearchresults" target="_blank" rel="noopener nofollow noopener noreferrer"&gt;Add sparklines to search results&lt;/A&gt;&lt;SPAN&gt;" in Splunk Documentation for the latest version (8.0.5 as of this writing):&lt;/SPAN&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=_internal | chart sparkline count by sourcetype&lt;/LI-CODE&gt;&lt;P&gt;&lt;SPAN&gt;...&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;results in the following "green" job notification:&lt;/SPAN&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;This search uses deprecated 'stats' command syntax. This syntax implicitly translates '&amp;lt;function&amp;gt;' or '&amp;lt;function&amp;gt;()' to '&amp;lt;function&amp;gt;(*)', except for cases where the function is 'count'. Use '&amp;lt;function&amp;gt;(*)' instead.&lt;/LI-CODE&gt;&lt;P&gt;&lt;SPAN&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Splunk info msg - Screen Shot 2020-08-11 at 8.48.55 AM.png" style="width: 333px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/10200iC3457D61A9278ABB/image-size/large?v=v2&amp;amp;px=999" role="button" title="Splunk info msg - Screen Shot 2020-08-11 at 8.48.55 AM.png" alt="Splunk info msg - Screen Shot 2020-08-11 at 8.48.55 AM.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;(This is reproduced in Splunk Enterprise versions 8.02, 8.04.1, 8.05.)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Questions:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Does this happen for you, too (in Splunk Enterprise versions 8.x)?&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Why does Splunk use deprecated syntax in their docs? (Is there a good reason for it, or is this simply a benign case of a slightly stale documentation that's just not worth of an update?)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;How would one modify the above search to (1) eliminate the "deprecated syntax" message while (2) retaining both the sparkline and the count fields, and optionally, (3) making it at least as performant as the "deprecated" one?&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;P&gt;(This question is a more generic follow up to&amp;nbsp;&lt;SPAN&gt;"&lt;A href="https://community.splunk.com/t5/Splunk-Search/quot-This-search-uses-deprecated-stats-command-syntax-quot/m-p/513702" target="_self"&gt;This search uses deprecated 'stats' command syntax.&lt;/A&gt;"&lt;/SPAN&gt;&amp;nbsp; that was answered by&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/213957"&gt;@richgalloway&lt;/a&gt;&amp;nbsp;(thank you).)&lt;/P&gt;</description>
      <pubDate>Thu, 13 Aug 2020 17:00:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/deprecated-stats-command-syntax-notification-on-a-sample-Splunk/m-p/513951#M144246</guid>
      <dc:creator>mitag</dc:creator>
      <dc:date>2020-08-13T17:00:04Z</dc:date>
    </item>
    <item>
      <title>Re: deprecated 'stats' command syntax notification on a sample Splunk search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/deprecated-stats-command-syntax-notification-on-a-sample-Splunk/m-p/514793#M144502</link>
      <description>&lt;P&gt;Turns out this particular example is a bug. Splunk 8.0.0 through 8.0.6 generates this "info message" when you use sparkline without an argument (such as sparkline(count) or sparkline(count(cpu)). This isn't supposed to happen. The bug is fixed in upcoming versions of Splunk.&amp;nbsp;&lt;/P&gt;&lt;P&gt;As for supporting deprecated syntax - well, sometimes we do that for backwards-compatibility, when people are upgrading from older versions of the product.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Aug 2020 23:06:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/deprecated-stats-command-syntax-notification-on-a-sample-Splunk/m-p/514793#M144502</guid>
      <dc:creator>mattness</dc:creator>
      <dc:date>2020-08-18T23:06:57Z</dc:date>
    </item>
  </channel>
</rss>

