Databases
StackOverflow2013
Postsdbo
POGraphite returning incorrect datapoint
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGraphite returning incorrect datapoint
    primarykey
    data
    text
    <ul> <li>I downloaded statsd and graphite 0.9.x</li> <li>I used the stats-client provided with source of statsd as follows: <ul> <li><code>./statsd-client.sh 'development.com.alpha.operation.testing.rate:1|c'</code></li> </ul></li> <li>I did the above operation 10 times.</li> </ul> <p>Then I tried querying for a summary for last 24 hours:</p> <blockquote> <p><a href="http://example.com/render?format=json&amp;target=summarize(stats.development.com.alpha.operation.testing.rate" rel="nofollow">http://example.com/render?format=json&amp;target=summarize(stats.development.com.alpha.operation.testing.rate</a>, "24hours", "sum",true)&amp;from=-24hours&amp;tz=UTC</p> </blockquote> <p>I get 1 datapoint as follows:</p> <pre><code>"datapoints": [[0.0, 1386277560]]}] </code></pre> <p>Why I am getting 0.0? Even Graphite Composer does not display anything</p> <p>I was expecting a value of "10" as I performed the operation 10 times. What did I do wrong?</p> <p><strong>storage-schemas.conf</strong></p> <pre><code>[carbon] pattern = ^carbon\. retentions = 60:90d [default_1min_for_1day] pattern = .* retentions = 60s:1d </code></pre> <p>Please help me understand the problem.</p> <p>EDIT:</p> <p>As per answer below, I changed storage-aggregation and I get following response after running whisper-info on metric_file.wsp. But I am still getting "0.0" as value in datapoint and Graphite browser does not display anything.</p> <pre><code>maxRetention: 86400 xFilesFactor: 0.0 aggregationMethod: sum fileSize: 17308 Archive 0 retention: 86400 secondsPerPoint: 60 points: 1440 size: 17280 offset: 28 </code></pre> <p>I also looked at stats_counts Tree as suggested in another answer, but its the same.</p> <p>What is wrong with my setup. I am using default setting for everything but the changes suggested by an answer below in storage-aggregation</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USGJain
    1. USGJain
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COUse carbon's debug logs. Refer- http://stackoverflow.com/questions/20406789/where-are-my-logstash-metrics-in-graphite/20417377#20417377
      singulars
      1. POGraphite returning incorrect datapoint
      1. USerbdex
    2. CO`1.` It means that graphite will store one data-point every 60 seconds for 1 day. So technically, the data that you send across to graphite is chipped into 60s intervals and stored. Here, according to your config, the expected behavior is that Graphite sums up whatever it gets within that 60s window. xfilesfactor means that do write to the file even if you receive very few datapoints in the window.
      singulars
      1. POGraphite returning incorrect datapoint
      1. USerbdex
    3. CO`2.` If you do not apply `summarize()`, what is the nature of the graph? All zeroes?
      singulars
      1. POGraphite returning incorrect datapoint
      1. USerbdex
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload