/series calls stuck if redis is not running

[andreasgerstmayr]

I was just testing for common misconfigurations, and noticed if I temporary stop the redis server and run for example

curl  "http://localhost:44322/series/query?expr=disk.dev.read"

the request stays open forever, i.e. no response is sent. I guess pmproxy is waiting for some callback (with the response) to be executed, which never happens as the connection to redis wasn't established. Can we return some HTTP 50x response here?

Interestingly I get

$ curl -s "http://localhost:44322/series/ping"
{"success":true}

however - is the response cached (redis was running when I started pmproxy initially)?

[andreasgerstmayr]

Interestingly I get

$ curl -s "http://localhost:44322/series/ping"
{"success":true}

however - is the response cached (redis was running when I started pmproxy initially)?

Looking at the code /series/ping always returns true, and doesn't ping the redis server. This functionality would be nice to have for the redis backfilling in Grafana.

[martinpitt]

This gave me headaches as well. I just filed issue #1296 with a proposal to make this Just Work and more elegant.