<?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: Timechart Using Too Few Bins in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Timechart-Using-Too-Few-Bins/m-p/82838#M21034</link>
    <description>&lt;P&gt;Hmm. I wonder if its just specific to my data, but when I do bins 300, I also get 5 min intervals -- except I only have data every 10 min, so I get data point, then null, then a datapoint, creating a ton of valleys. Is this expected, and I should address it with the connect option? It seems like it should be able to bin up to that number (in case I have 7 days of data), but have it just use the minimum reasonable bucketing for 4 hours of data.&lt;/P&gt;</description>
    <pubDate>Sat, 16 Apr 2011 04:01:53 GMT</pubDate>
    <dc:creator>David</dc:creator>
    <dc:date>2011-04-16T04:01:53Z</dc:date>
    <item>
      <title>Timechart Using Too Few Bins</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Timechart-Using-Too-Few-Bins/m-p/82836#M21032</link>
      <description>&lt;P&gt;I have a timechart covering data from every 10 minutes. If I look at the last 24 hours, that would generate 144 bins. The docs say that timechart defaults to&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;bins=300. This finds the smallest bucket size that results in no more than 300 distinct buckets.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;As I have fewer than 300 buckets, I would expect that it would represent the data with 144 buckets covering ten minute intervals. In reality, though, it's summarizing to every 30 minutes. I could force the issue with bins=144, but then that becomes problematic if the user switches the timepicker to 4 hours (gaps), or 48 hours (less accurate).&lt;/P&gt;

&lt;P&gt;How can I make Timechart use all the way up to 300 bins, without destroying the graph at other time windows?&lt;/P&gt;</description>
      <pubDate>Sat, 16 Apr 2011 00:33:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Timechart-Using-Too-Few-Bins/m-p/82836#M21032</guid>
      <dc:creator>David</dc:creator>
      <dc:date>2011-04-16T00:33:02Z</dc:date>
    </item>
    <item>
      <title>Re: Timechart Using Too Few Bins</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Timechart-Using-Too-Few-Bins/m-p/82837#M21033</link>
      <description>&lt;P&gt;It seems like 300 is not actually the default. &lt;/P&gt;

&lt;P&gt;I just ran a test search, and indeed it seems to bucket too low -- last 24 hours gets 49 buckets of 30mins each.   &lt;/P&gt;

&lt;P&gt;However when I add &lt;CODE&gt;bins=300&lt;/CODE&gt; to the same timechart clause, suddenly I get 293 buckets of 5 minutes each.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;your search&amp;gt; | timechart count bins=300
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sat, 16 Apr 2011 01:24:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Timechart-Using-Too-Few-Bins/m-p/82837#M21033</guid>
      <dc:creator>sideview</dc:creator>
      <dc:date>2011-04-16T01:24:40Z</dc:date>
    </item>
    <item>
      <title>Re: Timechart Using Too Few Bins</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Timechart-Using-Too-Few-Bins/m-p/82838#M21034</link>
      <description>&lt;P&gt;Hmm. I wonder if its just specific to my data, but when I do bins 300, I also get 5 min intervals -- except I only have data every 10 min, so I get data point, then null, then a datapoint, creating a ton of valleys. Is this expected, and I should address it with the connect option? It seems like it should be able to bin up to that number (in case I have 7 days of data), but have it just use the minimum reasonable bucketing for 4 hours of data.&lt;/P&gt;</description>
      <pubDate>Sat, 16 Apr 2011 04:01:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Timechart-Using-Too-Few-Bins/m-p/82838#M21034</guid>
      <dc:creator>David</dc:creator>
      <dc:date>2011-04-16T04:01:53Z</dc:date>
    </item>
    <item>
      <title>Re: Timechart Using Too Few Bins</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Timechart-Using-Too-Few-Bins/m-p/82839#M21035</link>
      <description>&lt;P&gt;the connect option wont help you because there literally is a datapoint at zero. Connect will only draw a connection across null points.  It's expected, it's just a fact of life when there's only so much granularity in the actual data.  You could use svutils to embed a customBehavior in JS whereby it outputs a span="30m" / span="10m"  term as appropriate,  but I'm not sure it'd be worth the extra surface area.&lt;/P&gt;</description>
      <pubDate>Sat, 16 Apr 2011 06:00:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Timechart-Using-Too-Few-Bins/m-p/82839#M21035</guid>
      <dc:creator>sideview</dc:creator>
      <dc:date>2011-04-16T06:00:11Z</dc:date>
    </item>
    <item>
      <title>Re: Timechart Using Too Few Bins</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Timechart-Using-Too-Few-Bins/m-p/82840#M21036</link>
      <description>&lt;P&gt;Here's the implementation of this method, using sideview_utils to dynamically size the number of bins for timechart. Note: for anyone who might stumble upon this -- it is reasonably complex, not for the brave of heart, and should be tested extensively. &lt;/P&gt;

&lt;P&gt;&lt;A href="http://pastebin.com/jqDktMhC"&gt;http://pastebin.com/jqDktMhC&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Apr 2011 23:41:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Timechart-Using-Too-Few-Bins/m-p/82840#M21036</guid>
      <dc:creator>David</dc:creator>
      <dc:date>2011-04-18T23:41:57Z</dc:date>
    </item>
  </channel>
</rss>

