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
I would expect errors from subgraphs to be propagated to the federated server, but this does not seem to be the case.
In my set up all my subgraphs require headers to be provided as part of the request, so I have a middleware function that checks for the presence of the headers and if they are not present it returns an error.
When headers are missing I see a nice error in the subgraph log Error: service missing request headers: X-Customer-Is : or X-SOB : are not provided in the headers. However this is not propagated to the federation graph.
Is there a way of doing this? i.e. intercepting the error from the subgraph and logging it in the federation layer?
The text was updated successfully, but these errors were encountered:
I would expect errors from subgraphs to be propagated to the federated server, but this does not seem to be the case.
In my set up all my subgraphs require headers to be provided as part of the request, so I have a middleware function that checks for the presence of the headers and if they are not present it returns an error.
When headers are missing I see a nice error in the subgraph log
Error: service missing request headers: X-Customer-Is : or X-SOB : are not provided in the headers
. However this is not propagated to the federation graph.Is there a way of doing this? i.e. intercepting the error from the subgraph and logging it in the federation layer?
The text was updated successfully, but these errors were encountered: