Iain Buclaw

Maybe post the carbon config in graphite-api.yaml? It may be reproducible in the testsuite given the right environment conditions.

Ceres is not only compatible with master carbon, it runs using half the CPU! I think megacarbon should be considered dead, as the various PRs I raised last year pretty...

Yep. Although I use graphite-api here, the last test I did using graphite-web appeared to be successful with a cursory test (https://github.com/graphite-project/graphite-web/pull/1719#issuecomment-274126421). I think there are some known problems with...

Confirmed, however this would only apply if you request the data outside of graphite, as normally if a node does not `hasDataForInterval()` then graphite won't bother looking it up.

Just to repeat what I said in #31 here. 1. Carbon master has full ceres support - graphite-project/carbon#484, graphite-project/carbon#508, and graphite-project/carbon#596. 2. Megacarbon has performance issues - it consumes about...

> My highly biased opinion would be to deprecate Ceres in favor of BigGraphite. I think my counter opinion would be that if carbon can be made more pluggable, that...

I can't reproduce this, but then again I am running with #32 applied, which affects data returned to graphite. There was a change in graphite-web which also would help too...

Still doesn't seem to work. ``` auth_request /oauth2/auth; error_page 401 = /oauth2/start; location = /oauth2/auth { internal proxy_pass http://127.0.0.1:4180; proxy_set_header X-Auth-Request-Redirect $request_uri; } location /oauth2/ { auth_request off; proxy_pass http://127.0.0.1:4180;...

Yeah, I've already had a look around before concluding this. I'm not building a custom version of nginx. :-)

Just FYI, the sign_in page is not affected by this, hence re-using X-Auth-Request-Redirect header.