Tag durable notify containers with business-oriented names

Currently durable notify container (target) could be identified in source (primary space) by host, pid and uuid.
We would like to see some "business" oriented information about target durable notify container ideally both in space logs and channel replication predefined metrics.
Such "business" oriented information could be provided by client code (optionally) when durable notify container is being created by client.

Please see example logs/metrics data where we see lack of such business information.

Example log from space:
2018-03-09 06:32:01,014 tess-space-tessZone3Space1-pu.15 [2] WARNING [com.gigaspaces.replication.backlog.primary-backup-reliable-async-mirror-15] - Replication [tessZone3Space1_container15_1:tessZone3Space1] group [primary-backup-reliable-async-mirror-15]: backlog for target replication:NotifyDur:example.com[29375]_cb65c325-bf0f-4179-bf14-038933378ebb is dropped due to backlog capacity reached [150000].

Example outgoing channel information in statistics:
OutgoingChannel(
getTargetMemberName()=replication:NotifyDur:a301-6220-5466.ldn.swissbank.com[2743157]_eebd413e-a29e-488c-a752-8c30771925f8,
getTargetUuid()=eebd413e-a29e-488c-a752-8c30771925f8,
getTargetHostname()=a301-6220-5466.ldn.swissbank.com,
getTargetDetails()=ConnectionEndpointDetails[hostName=a301-6220-5466.ldn.swissbank.com,hostAddress=a301-6220-5466.ldn.swissbank.com,pid=2743157,version=12.1.1.17100-0],
getDelegatorDetails()=ConnectionEndpointDetails[hostName=a301-6220-5466.ldn.swissbank.com,hostAddress=10.26.140.169,pid=2743157,version=12.1.1.17100-0],
getReplicationMode()=DURABLE_NOTIFICATION,
...