xneo64

@grobian we also encounter this issue frequently. During a cluster member downtime, the relay can't contain all of the pending metrics in memory (even after tuning) - there is simply...

It does speak pickle protocol, from line 284. Also it does return seemingly valid data when asked for `format=pickle` Which is in line with it to be "a drop-in replacement"...

No worries :) I used treejson for illustration purposes only. The flow usually is like this: Webclient (web-based graphite metric browser) issues: `GET /metrics/find/?_dc=1479381707026&query=*&format=treejson&path=&node=GraphiteTree` or Grafana issues: `GET /metrics/find/?query=*` This...

Seconded. I run my servers using a non-UTC timezone (BST), and the collected metrics are 1 hour in the future in the summer months :) Ideally as per Collectd spec...

Same here. I think the culprit is https://github.com/graphite-project/graphite-web/blob/622830db42f392ce2f1f7fb4a1ddf0dbfd16185c/webapp/graphite/logger.py#L39 I usually patch my graphite installations with the above set to False. As @Kenterfie said, this used to quickly fill up docker...

@deniszh the problem @SilentHunter44 is mentioning usually occurs when a relay would be caching metrics for a carbon store that is currently down (e.g. for maintenance) - on starting the...

@dgryski why not make `cacheTimeout := int32(60)` duration user configurable? Graphite-web implements DEFAULT_CACHE_DURATION which is very useful in my use case as we collect metrics at an interval of 10s....

Just got to know about this project a couple of days ago, and converted my preproduction environments. While very easy to read, unfortunately I'm inexperienced with Go code, so I'll...

@jblaine @ChrisHeerschap had the same issue on RHEL 7.4 - try `FSType "rootfs"` it worked for us straight away