You cannot have separate cpu and heap metrics for nodes within the same JVM. OSGI won't help either - it mostly achieves containment through complex class loaders.
You could sort of have an approximiation of CPU consumption per node by summing up the thread cpu consumption for the related dispatcher threads, but that would disregard all implicit CPU, like that of GC. Heap monitoring is yet even harder. The JVMTI API provides some basic facilities to acheive that, but the overhead is likely to kill your application. Plus it's a huge amount of work, so you'd be better off paying for a commercial monitoring product (which still doesn't resolve the issue of overhead and probably doesn't give you exactly what you want). Much cheaper to run several JVMs... -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
