Hi Sean,
This question was not asked before. And yes, that feature for Jenkins slaves is supported, but it needs a trick.
If you run the optional collect server like the following, you can add one or several jenkins master(s) like you have already done:
java -jar javamelody-collector-server.war
(It just needs parameters in the Jenkins master for security as said in the advanced user's guide.)
Then, if you run another collect server like the following, you can add Jenkins instances like before and it will collect the monitoring data of the Jenkins nodes (slaves in general) including builds, instead of the monitoring data of the Jenkins masters:
java -Djavamelody.monitoring-path=/monitoring/nodes -jar javamelody-collector-server.war --httpPort=8081
I have used a different httpPort to be able to have both the default 8080 for the first one and 8081 for the second one, at the same time.
When adding the Jenkins slaves, do to not use the same application names as the ones for Jenkins masters, in order to avoid conflicts on storage.
Now, we need to find a simple way to have both masters and slaves in the same collect server. The code will need to be changed a bit for that.
bye,
Emeric