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
A workaround for this issue is to call loggers with log.info(channelName + ' Message ID: ' + messageId + ' logging a message and yimeng is awsome!') . This should work with any logging tool because it is manually constructing the log message.
shows how the MetaAppender extracts the channelId and channelName. Does the raw log message already have messageId present and the MetaAppender just needs to read the value?
My idea is probably wrong. MC puts the channel name into the log by manipulating the thread name Thread.currentThread().setName(mirthServlet.getClass().getSimpleName() + " Thread (" + operation.getDisplayName() + ") < " + originalThreadName);
Sounds interesting! When the channel is known, it should also be possible to determine the current message ID. If detection is not too expensive, it should be possible to add it to the log entry.
I will have a look into that when I have some time.
The text was updated successfully, but these errors were encountered: