On Thu, 1 Feb 2018 10:06:41 +0000 Andreas Dobloug andreas.dobloug@usit.uio.no wrote:
We have done extensive debugging on this, and our graphite server is not the culprit.
I did not say the Graphite server was the culprit. The graphite server returns "400 BAD REQUEST", which is why I asked you to inspect its logs. Specifically, I would be interested in knowing which request from NAV that caused it to report this.
According to the sysadmin responsible for graphite, the request never reaches the graphite api.
But according to your traceback, it does.
This is the faulty request which generates the errors: https://nav.uio.no/graphite/render?format=json&from=-5min&until=now
The request does not contain a target.
That's interesting on several levels.
Firstly, the NAV request is obviously botched, but where does it come from? Did NAV generate it, or did something else? You neglected to include the rest of the e-mail sent by Django. Do your NAV webserver logs contain referrer information for the failing request?
Secondly: Which version of graphite-web are you running? I'm unable to make this request crash on any NAV installation I have access to. It simply returns an empty JSON response. 0.9.12 is the running version on those I have access to.