<?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: Inexplicable extra chart data point? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Inexplicable-extra-chart-data-point/m-p/160213#M45274</link>
    <description>&lt;P&gt;I believe this is the behavior for the &lt;CODE&gt;partial=true&lt;/CODE&gt;, which is the default. From the &lt;CODE&gt;timechart&lt;/CODE&gt; documentation:&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;partial&lt;/STRONG&gt;&lt;BR /&gt;
Syntax: partial=&lt;BR /&gt;
Description: Controls if partial time buckets should be retained or not. Only the first and last bucket could ever be partial. Defaults to True|T, meaning that they are retained.&lt;/P&gt;

&lt;P&gt;Try to use:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;base search | timechart partial=f span=1month dc(foo) 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;or&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;base search | bucket span=1mon _time | timechart span=1month dc(foo) 
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Wed, 17 Dec 2014 01:17:29 GMT</pubDate>
    <dc:creator>musskopf</dc:creator>
    <dc:date>2014-12-17T01:17:29Z</dc:date>
    <item>
      <title>Inexplicable extra chart data point?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Inexplicable-extra-chart-data-point/m-p/160212#M45273</link>
      <description>&lt;P&gt;I have multiple searches over a year's date range, similar to:&lt;BR /&gt;
&lt;CODE&gt;base search | timechart span=1month dc(foo)&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;and they are all reproducing the same strange statistics, and in turn visualization...&lt;/P&gt;

&lt;P&gt;all of the data is grouped by month, but the very last month is repeated twice, time stamps 7 hours apart, and the values for the first of those points being incomplete &lt;BR /&gt;
&lt;CODE&gt;_time                         count&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;2013-12-01 00:00 100&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;2013-12-01 08:00 200&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;2014-01-01 08:00 300&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;2014-02-01 08:00 400&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;2014-03-01 08:00 500&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;2014-04-01 07:00 600&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;2014-05-01 07:00 700&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;2014-06-01 07:00 800&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;2014-07-01 07:00 900&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;2014-08-01 07:00 1000&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;2014-09-01 07:00 1100&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;2014-10-01 07:00 1200&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;2014-11-01 00:00 250&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;2014-11-01 07:00     1300&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;Is this expected behavior? If so, I would greatly appreciate any assistance with cleaning it up!&lt;/P&gt;

&lt;P&gt;Thanks very much&lt;/P&gt;</description>
      <pubDate>Wed, 17 Dec 2014 01:10:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Inexplicable-extra-chart-data-point/m-p/160212#M45273</guid>
      <dc:creator>arichman</dc:creator>
      <dc:date>2014-12-17T01:10:48Z</dc:date>
    </item>
    <item>
      <title>Re: Inexplicable extra chart data point?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Inexplicable-extra-chart-data-point/m-p/160213#M45274</link>
      <description>&lt;P&gt;I believe this is the behavior for the &lt;CODE&gt;partial=true&lt;/CODE&gt;, which is the default. From the &lt;CODE&gt;timechart&lt;/CODE&gt; documentation:&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;partial&lt;/STRONG&gt;&lt;BR /&gt;
Syntax: partial=&lt;BR /&gt;
Description: Controls if partial time buckets should be retained or not. Only the first and last bucket could ever be partial. Defaults to True|T, meaning that they are retained.&lt;/P&gt;

&lt;P&gt;Try to use:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;base search | timechart partial=f span=1month dc(foo) 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;or&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;base search | bucket span=1mon _time | timechart span=1month dc(foo) 
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 17 Dec 2014 01:17:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Inexplicable-extra-chart-data-point/m-p/160213#M45274</guid>
      <dc:creator>musskopf</dc:creator>
      <dc:date>2014-12-17T01:17:29Z</dc:date>
    </item>
    <item>
      <title>Re: Inexplicable extra chart data point?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Inexplicable-extra-chart-data-point/m-p/160214#M45275</link>
      <description>&lt;P&gt;That appears to do the trick. Thank you!&lt;/P&gt;</description>
      <pubDate>Wed, 17 Dec 2014 01:40:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Inexplicable-extra-chart-data-point/m-p/160214#M45275</guid>
      <dc:creator>arichman</dc:creator>
      <dc:date>2014-12-17T01:40:31Z</dc:date>
    </item>
    <item>
      <title>Re: Inexplicable extra chart data point?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Inexplicable-extra-chart-data-point/m-p/160215#M45276</link>
      <description>&lt;P&gt;Specifically, the second example worked for me.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Dec 2014 22:13:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Inexplicable-extra-chart-data-point/m-p/160215#M45276</guid>
      <dc:creator>arichman</dc:creator>
      <dc:date>2014-12-17T22:13:58Z</dc:date>
    </item>
  </channel>
</rss>

