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
It would be useful to be able to override the ServiceRouter's exception logging. Would also be useful to provide the override with access to the request header. This would allow the customized log event to include request context for tracing, etc...
It seems that this is not currently supported, as of Lagom 1.3.8.
Not super familiar with the Lagom code, but it looks to me like moving ServiceRouter's logException to LagomServiceApiBridge (and passing the request header) and then working through that customization might be a reasonable approach.
Thoughts?
The text was updated successfully, but these errors were encountered:
It would be useful to be able to override the ServiceRouter's exception logging. Would also be useful to provide the override with access to the request header. This would allow the customized log event to include request context for tracing, etc...
It seems that this is not currently supported, as of Lagom 1.3.8.
Not super familiar with the Lagom code, but it looks to me like moving ServiceRouter's logException to LagomServiceApiBridge (and passing the request header) and then working through that customization might be a reasonable approach.
Thoughts?
The text was updated successfully, but these errors were encountered: