Since the introduction of native support for multiple named caches a need emerged to better identify to which named cache a log messages may be referring to.
Right now that is not possible, since the CacheName is not present anywhere in the log messages.
Also, when investigating potential problems with backplane activity, it would be nice to also log the InstanceId of the remote cache which generated the notification.
Right now this is also not possible.
Solution
Add the CacheName to the begenning of every log message generated in FusionCache.
Additionally, for log messages related to incoming backplane notifications, also add the InstanceId of the remote cache.
Problem
Since the introduction of native support for multiple named caches a need emerged to better identify to which named cache a log messages may be referring to.
Right now that is not possible, since the
CacheName
is not present anywhere in the log messages.Also, when investigating potential problems with backplane activity, it would be nice to also log the
InstanceId
of the remote cache which generated the notification.Right now this is also not possible.
Solution
Add the
CacheName
to the begenning of every log message generated in FusionCache.Additionally, for log messages related to incoming backplane notifications, also add the
InstanceId
of the remote cache.