Yes, EP1 and EP2 send their proxy to a 3rd application (Ice.Application) in a server that is in charge of making the pub/subscription of both in the icestorm instance and so EP1 and EP2 are already communicated.

I want to see the messages and communications that are passed between EP1 and EP2 using icestorm pub/subscription. Messages are defined by slice interfaces.

It is for statistical purposes (see the interfaces that are most used and with what content).

Did you consider enabling Ice metrics in IceStorm to gather this information?

Ice metrics will allow you to obtain information on the dispatch and invocations that are going through IceStorm. It can for example provide the number of dispatch for a given operation on a given Ice publisher object.

While this will allow you to get statistical information on how many times a given operation is called (and the size of the request), you won't be able to get information on the content... I you need this, you would need to intercept all the requests published by publishers before forwarding them to IceStorm. Let us know if you need more information on this.

I was looking the metrics a long time ago but they don't work for me since the interesting information to statistics are in the content of the messages.

you won't be able to get information on the content... I you need this, you would need to intercept all the requests published by publishers before forwarding them to IceStorm. Let us know if you need more information on this.

This I think can help me to get the information I want. Can you explain how I could do it?

If you need to extract information from the request parameters, you will need to implement a service that receives the requests from the publishers and forward them to IceStorm. Your application, instead of providing the topic's publisher proxy to publishers, would provide a proxy on your publisher interceptor object and the implementation of your publisher interceptor would forward the requests to the IceStorm publisher.

Another option could be to implement a subscriber that receives all the updates that are going through IceStorm and whose sole purpose would be to gather statistical information on the messages that are going through IceStorm.