{"push_id":963967167,"size":4,"distinct_size":4,"ref":"refs/heads/use_tags","head":"0c55f2d6d5824b4610fa9bc7af086ffcb816711e","before":"d1c8875e6bb4671a8dd204267a0e202c078c14ac","commits":[{"sha":"66606f693ffd3b2f1e47e836fea99c4fe1f55ee6","author":{"email":"40ce4379f5763c05b71c88f9a371809fdbce6a21@bogushome.net","name":"Ingo Dyck"},"message":"Use InfluxDBClusterClient (was InfluxDBClient)\n\nThis provides proper load distribution in case of a clustered influxdb\nsetup. InfluxDBClient has sticky and long living connections, so even\nputting a loadbalancer in between doesn't really work.","distinct":true,"url":"https://api.github.com/repos/bogus-py/graphite-influxdb/commits/66606f693ffd3b2f1e47e836fea99c4fe1f55ee6"},{"sha":"74d2026b8c1bac8851c1242fae9b088357489946","author":{"email":"40ce4379f5763c05b71c88f9a371809fdbce6a21@bogushome.net","name":"Ingo Dyck"},"message":"Introduce tn tag for improved get_leaves query\n\nThe value of the tn tag is highest N off all tN tags. In influxdb\ngraphite plugin config this means having the following templates:\n    ...\n    \"*.*.*.*.*.*.*.* t0.t1.t2.t3.t4.t5.t6.measurement tn=6\",\n    \"*.*.*.*.*.*.* t0.t1.t2.t3.t4.t5.measurement tn=5\",\n    \"*.*.*.*.*.* t0.t1.t2.t3.t4.measurement tn=4\",\n    \"*.*.*.*.* t0.t1.t2.t3.measurement tn=3\",\n    \"*.*.*.* t0.t1.t2.measurement tn=2\",\n    \"*.*.* t0.t1.measurement tn=1\",\n    \"*.* t0.measurement tn=0\",\n    \"measurement* tn=-1\"","distinct":true,"url":"https://api.github.com/repos/bogus-py/graphite-influxdb/commits/74d2026b8c1bac8851c1242fae9b088357489946"},{"sha":"192ac041e74d499dd8b60eb6be2373cdef9e32d2","author":{"email":"40ce4379f5763c05b71c88f9a371809fdbce6a21@bogushome.net","name":"Ingo Dyck"},"message":"Improve find_branches(): avoid matching on *\n\nSee comments in code for more details","distinct":true,"url":"https://api.github.com/repos/bogus-py/graphite-influxdb/commits/192ac041e74d499dd8b60eb6be2373cdef9e32d2"},{"sha":"0c55f2d6d5824b4610fa9bc7af086ffcb816711e","author":{"email":"40ce4379f5763c05b71c88f9a371809fdbce6a21@bogushome.net","name":"Ingo Dyck"},"message":"Dynamic step/resolution when fetching data\n\nBackground:\nSay you have metrics in 60s resolution. When looking at data\nover the last few days, this is all well and reasonable. But when you\nwant to see data over the last 6 months things get slightly out of hand.\nIn this scenario we're dealing with 259200 datapoints for each series\nwe're interested in.\nWhen using Whisper/Carbon we most likely storage-schemes to handle this\n(something like 1m:21d,15m:5y), and if not, it's reading from disk which\nis much faster and has lower latency then querying a remote service.\nMost of the time though we'll newer draw that many points. In my grafana\nsetup it requests a max of 2550 points from graphite-api.\n\nSo lets leverage InfluxDBs ability to GROUP BY time.\n\nThis commit introduces a new config option called min_data_points.\nSetting it to 0 (default) disables dynamic stepping.\nSetting it to a value > 0 enables dynamic calculation of the resolution.\nThe new resolution will always be a multiple of the origin resolution,\nand we'll always have at list min_data_points.\nPractically this means we'll always have somewhere between\nmin_data_points and 2xmin_data_points points.","distinct":true,"url":"https://api.github.com/repos/bogus-py/graphite-influxdb/commits/0c55f2d6d5824b4610fa9bc7af086ffcb816711e"}]}