In nutshell I'm interested in monitoring coherence cache.
Seems like remote JMX would be to best solution without impacting performance of the coherence cache.
If anybody using Wily to monitor coherence cache cluster/s, please share.

Take a look at the JMX agent written by LinkedIn community member Jens Riboe in the Field Extensions section of the Community Documents.
You can reach out to him directly if you have any questions or concerns.

Looked at the JMXAgent in field extensions, but it looks like it's not EPAgent based, rather agent to load with java application when it starts.
So I see no difference between this and build in JMX feature of Wily java agent.
Or am I missing something?

Anybody got custom coherence pbd to share?
I'd be interested to get basic metrics for Coherence cache GETs and PUTs, from Introscope.
Or everybody is using just JMX metrics?
Can anybody share JMX filter from their Introscope java agents running on Coherence?

I was the developer for this RemoteJMX Agent feature. This agent will take care of the Server restart. You could experiment this with a single server and restarting it.
The agent will read the properties file (RemoteJMXAgent.properties) only once for performance reasons. It can be modified such that it reads the properties file every 15 seconds so that any new server configured can also be picked up with out agent restart.

While looking at Coherence JMX metrics, I've notice there are many important once, which are float type (java.lang.Float) attributes.
Wily shows/supports only the integer part of them. So for example PublisherSuccessRate = 0.9956239 in Jconsole, but in Wily it's = "0".
Any ideas how to workaround this?