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
Make sure we have exception handling in place to ensure that unhandled exceptions are at least logged (even when we swallow them to avoid a user-facing crash). Catch missing command/event registration in tests #2884 is an example of this.
Include routing slip information in the logs.
Several interesting fields on commands and events (such as TargetKernelName, OriginUri and DestinationUri) are missing in the logs. It would be great to log this information at least once for each command / event that is sent / received.
It may be nice to include logging for when commands are serialized deserialized on each side (i.e., in the sender and receiver). I think that would help us know what information is flowing over the wire even if this information were not being routed correctly to a particular kernel (or if there was some other crash that prevented this routing) ...
The text was updated successfully, but these errors were encountered:
The following PRs have addressed most of the above tasks. The main remaining task is to ensure that all exceptions that we care about are captured in the logging.
The text was updated successfully, but these errors were encountered: