Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Emit IP address on network errors #429

Open
csilvers opened this issue Sep 24, 2024 · 0 comments
Open

Emit IP address on network errors #429

csilvers opened this issue Sep 24, 2024 · 0 comments

Comments

@csilvers
Copy link

csilvers commented Sep 24, 2024

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:

Error: hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }))

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant