Perhaps I'm missing something but is there any way to enrich these error log messages with more context? I know that the logger can be supplied at startup but I'm looking to add some dynamic/runtime context related to the currently executing request, maybe similar to how envelop offers a useErrorHandler configuration
In our personal circumstance we use an apollo koa server, and we keep a KoaContext with a requestId on it that gets generated by the client - this lets us track requests across our ecosystem of microservices. Ideally, we would love to enrich the error thrown here with our context. This way, any error can be easily associated with the particular HTTP request logs that triggered the error
At the very least, it would be great if the error call included the query document that it was trying to parse.
Hey there 👋
This is related to / a follow-up https://github.com/kamilkisiela/graphql-hive/issues/1220
Perhaps I'm missing something but is there any way to enrich these error log messages with more context? I know that the
logger
can be supplied at startup but I'm looking to add some dynamic/runtime context related to the currently executing request, maybe similar to howenvelop
offers auseErrorHandler
configurationIn our personal circumstance we use an apollo koa server, and we keep a
KoaContext
with arequestId
on it that gets generated by the client - this lets us track requests across our ecosystem of microservices. Ideally, we would love to enrich the error thrown here with our context. This way, any error can be easily associated with the particular HTTP request logs that triggered the errorAt the very least, it would be great if the error call included the query document that it was trying to parse.