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
When running fastly compute serve (for a compute@edge service, though we see the same behavior for our vcl service), when I make a request that needs to hit a backend, and the backend is not running, I'll see this in the logs:
When running
fastly compute serve
(for a compute@edge service, though we see the same behavior for our vcl service), when I make a request that needs to hit a backend, and the backend is not running, I'll see this in the logs:The problem is that we have many backends, and this gives no indication which backend is causing the problem. (Or even if it's a backend at all!)
Would it be possible to augment this error message to say the IP+port of the server that hyper failed to connect to?
The text was updated successfully, but these errors were encountered: