You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
graphite-raintank should pass the error through more elegantly, so it is shown in grafana.
because people will be able to get in this situation fairly easily.
currently, graphite will http 500 and show ValueError: No JSON object could be decoded and a stack trace, and in grafana it looks like an error with the ugly stack trace.
note also that Content-Type is set to text/plain, and not application/json. if MT returns http 400 with an error, graphite-raintank should just return 400 with the same error.
The text was updated successfully, but these errors were encountered:
since grafana/metrictank@a63233c
this can happen:
I think:
because people will be able to get in this situation fairly easily.
currently, graphite will http 500 and show
ValueError: No JSON object could be decoded
and a stack trace, and in grafana it looks like an error with the ugly stack trace.note also that Content-Type is set to
text/plain
, and notapplication/json.
if MT returns http 400 with an error, graphite-raintank should just return 400 with the same error.The text was updated successfully, but these errors were encountered: