Ease process to troubleshoot Graphite errors

[dutchiechris]

Currently a red bar is shown with "Oops! Graphite HTTP Error Request" when Graphite hits a problem. As far as I can tell, there is no way to see what the error was without additional troubleshooting such as using inspect like in this example:

Request is for Grafana to somehow allow access to the error info natively. Maybe if you click on the ! icon it would open a new window with just the render post so you could see the exact error straight away?

[syepes]

+1 That would be nice

[torkelo]

Yes, this would be great. High prio :)

[torkelo]

Started this today. Initial version (can always be improved) should be done tomorrow or this weekend.

[torkelo]

The full graphite html error page is visible in the response tab (see screenshot in comment before this)

[syepes]

Great work, this is going to be really useful.

[frejsoya]

Doesn't this require setting DEBUG=True in graphite? I guess it's an issue in graphite not reporting errors in json.

[torkelo]

@frejsoya good point. I am not sure what the error page looks like when DEBUG=False.

[brutasse]

It's HTML as well but with a different style & less information. So it'll keep working.

Graphite-api sometimes returns 400 responses in JSON, for instance when there is no target parameter. In this case displaying that in an iframe doesn't work.

Ultimately I'd like graphite-api to validate inputs and return proper error messages in 400 responses instead throwing server errors for arity issues.

I can probably write a patch to support JSON errors as well as HTML ones if you're willing to accept it :)

[torkelo]

JSON errors would be great. Especially with some simple generic schema that is easy to render as html.