Hi,
Using the ruby client I get the following weird results:
1.9.3p327 :024 > Time.now
=> 2013-06-26 18:32:31 +0200
1.9.3p327 :025 > batsd = BatsdReportingClient.new
=> #<BatsdReportingClient:0x0000000382ef30 @ipaddr="127.0.0.1", @PORT=8127, @timeout=2000, @Remote=#<TCPSocket:fd 11>>
1.9.3p327 :026 > batsd.values("counters:pushes.830.opened", 10.days.ago.to_i, Time.now)
=> [{:timestamp=>2013-06-26 16:20:00 +0200, :value=>1.0}]
1.9.3p327 :027 > batsd.values("counters:pushes.830.opened", 1.days.ago.to_i, Time.now)
=> []
With a retention configuration file looking like:
retentions:
1: 600 #1 hour
10: 360 #1 hour
60: 10080 #1 week
600: 52594 #1 year
Requesting data with a retention within the 2nd retention interval doesn't return anything, while asking for one within the 3rd interval does. The point is about 2 hours old so both should work.
Any idea why could that happen, and how to debug this? Thank you.
Hi,
Using the ruby client I get the following weird results:
1.9.3p327 :024 > Time.now
=> 2013-06-26 18:32:31 +0200
1.9.3p327 :025 > batsd = BatsdReportingClient.new
=> #<BatsdReportingClient:0x0000000382ef30 @ipaddr="127.0.0.1", @PORT=8127, @timeout=2000, @Remote=#<TCPSocket:fd 11>>
1.9.3p327 :026 > batsd.values("counters:pushes.830.opened", 10.days.ago.to_i, Time.now)
=> [{:timestamp=>2013-06-26 16:20:00 +0200, :value=>1.0}]
1.9.3p327 :027 > batsd.values("counters:pushes.830.opened", 1.days.ago.to_i, Time.now)
=> []
With a retention configuration file looking like:
retentions:
1: 600 #1 hour
10: 360 #1 hour
60: 10080 #1 week
600: 52594 #1 year
Requesting data with a retention within the 2nd retention interval doesn't return anything, while asking for one within the 3rd interval does. The point is about 2 hours old so both should work.
Any idea why could that happen, and how to debug this? Thank you.