:tz not working on a .read call?

[brandon-shannon]

I have a .read call like:

@some_data_sets = @client.read start, stop, :attributes => some_attributes, :tags => some_tags, :tz => '-07:00'

, but may data points are coming back in UTC. I've also tried:

@some_data_sets = @client.read start, stop, :attributes => some_attributes, :tags => some_tags, :tz => 'America/Denver'

...with the same result. Am I misunderstanding how this parameter is to be used?

[myagley]

Thanks for the bug report! We really appreciate it.

Currently, the server only applies the timezone during a rollup, and in this case it only adjusts the utc offset of the returned timestamps. The data that comes back is correct, it just has a 00:00 utc offset. We are fixing this on the server shortly to return iso8601 times with the utc-time set to the proper value for the requested time zone (default utc).

If you apply a rollup (for instance):

@some_data_sets = @client.read start, stop, :attributes => some_attributes, :tags => some_tags, :interval => '1min', :function => 'avg', :tz => 'America/Denver'

You should see the timestamps come back with the proper offset.

However, this doesn't completely solve the problem. The client library should attach a tz object to each datetime based on the requested tz. We are in the process of updating the client libraries to do just this. The ruby library should be updated shortly. I'll get a more accurate timing for when this will be ready.