Skip to content

Emit IP address on network errors #429

@csilvers

Description

@csilvers

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions