unclear logging when grpc endpoint is down

[conorsch]

Received a report about an instance of the dex explorer not displaying the route book info. It looked like this:

The logs for the instance showed:

⨯ Error: Error retrieving route book: ConnectError: [unknown] fetch failed
    at cf (/var/task/.next/server/app/api/book/route.js:1:308815)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async Promise.all (index 0)
    at async cw (/var/task/.next/server/app/api/book/route.js:1:308361)
    at async /var/task/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:38410
    at async e_.execute (/var/task/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:27879)
    at async e_.handle (/var/task/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:39744)
    at async en (/var/task/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:16:25332)
    at async ea.responseCache.get.routeKind (/var/task/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:17:1028)
    at async r6.renderToResponseWithComponentsImpl (/var/task/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:17:508)

The root of the problem turned out to be that the pd grpc endpoint for the deployment was down. That's the kind of information that should be made quite clear in error logging. Can we add contextual information to the specific fetch that's failing, at least in the case of the grpc endpoint lookups?