Closed GoranP closed 12 years ago
I have a problem with gauges. Eg. http://localhost:9292/graph#gauges=somehost.system.sda1.disk_ops.write&start=1344874680&stop=1344874800 This is just last 2 minutes of gauge. When I click on view - batsd-dash goes to 100% and blocks. Same thing when I use http://localhost:9292/data?gauges=.....etc
With simple ruby script I receive this few records from batsd-server (last two minutes)
{:timestamp=>2012-08-13 18:20:25 +0200, :value=>0.22} {:timestamp=>2012-08-13 18:21:25 +0200, :value=>0.21} {:timestamp=>2012-08-13 18:21:35 +0200, :value=>0.21} {:timestamp=>2012-08-13 18:21:45 +0200, :value=>0.21} {:timestamp=>2012-08-13 18:21:55 +0200, :value=>0.21}
What am I doing wrong?
Graphs with counters are OK
Fixed by d87d7f76; We can't zero-fill gauges since there is no even interval for the data (no aggregation).
Thanks for reporting this!
I have a problem with gauges. Eg. http://localhost:9292/graph#gauges=somehost.system.sda1.disk_ops.write&start=1344874680&stop=1344874800 This is just last 2 minutes of gauge. When I click on view - batsd-dash goes to 100% and blocks. Same thing when I use http://localhost:9292/data?gauges=.....etc
With simple ruby script I receive this few records from batsd-server (last two minutes)
{:timestamp=>2012-08-13 18:20:25 +0200, :value=>0.22} {:timestamp=>2012-08-13 18:21:25 +0200, :value=>0.21} {:timestamp=>2012-08-13 18:21:35 +0200, :value=>0.21} {:timestamp=>2012-08-13 18:21:45 +0200, :value=>0.21} {:timestamp=>2012-08-13 18:21:55 +0200, :value=>0.21}
What am I doing wrong?
Graphs with counters are OK