On Tue, Mar 28, 2006 at 08:02:32PM +0100, José Miguel Pereira Tavares wrote: > > Hi Ben! > > On Tuesday, 28 March 2006 19:30, Ben Hartshorne wrote: > > Miguel, > > I look forward to trying this out. You say 'Installation requires > > ganglia to be installed using the source code.' - I am curious what > > files you require. I installed ganglia using an RPM, and would like > > to bring in only the files I need. Is this a bad idea? What do you > > recommend? (and why would a compiled C program require sources to > > run with other compiled programs?) > > It's needed mostly to linking with several libraries (libganglia, > libconfuse, lidapr-0, libmetrics, libgetopthelper) that come with > ganglia and are not required to be instaled installed on the host. At > least as far as I could tell.
Does it statically or dynamically link against those binaries? In other words, do I only need the ganglia src on the machine on which I compile JVMProbe, or will I need it to run? I ask because I would like to deploy to ~30 hosts (to see how the stats run on my cluster), and if I can avoid deploying the sources to all those hosts, I would like it better. :) One suggestion I have so far - you mention that though the tool is called JVMProbe, it can be used on other applications. however, the stats that it sends to ganglia are all named JVM_foo, which means that it cannot be used to monitor two different applications on the same host. Perhaps you could include an option to include the name of the process it's watching as part of the metric name? For example, when watching java, use JVM_java_foo as the metric name. If you then also wanted to watch abcApp on the same host, it would report those metrics as JVM_abcApp_foo and not collide namespace. One bug report - After compilation, I ran 'sudo ./JVMProbe -d' to see if it would actually work. I got the following output: > ----- [0] ----- > ----- [1] ----- > ----- [2] ----- > ----- [3] ----- and then I cancelled the process. I was confused - was this correct output? despite the fact that the --help option said that the default named of the process to watch was 'java', I added '-n java' and then got: > ----- [0] ----- > JVM_taks = 39 tasks > JVM_avgUse = 98 % > JVM_highUse = 12 % > JVM_vmPeak = 0 kB > JVM_vmSize = 1274096 kB > JVM_vmRSS = 765428 kB > JVM_vmData = 1201280 kB > JVM_vmStk = 2036 kB > JVM_vmExe = 56 kB > JVM_vmLib = 70228 kB > ----- [1] ----- > JVM_taks = 39 tasks > JVM_avgUse = 98 % > JVM_highUse = 12 % > JVM_vmPeak = 0 kB > JVM_vmSize = 1274096 kB > JVM_vmRSS = 765428 kB > JVM_vmData = 1201280 kB > JVM_vmStk = 2036 kB > JVM_vmExe = 56 kB > JVM_vmLib = 70228 kB ahhh. Much better. I don't know why it didn't work without the '-n' flag. Many Many thanks for writing this module! though I give you errors only, the fact is that it works for me, nearly out of the box, and is successfully reporting JVM stats within my framework! :) -ben -- Ben Hartshorne email: [EMAIL PROTECTED] http://ben.hartshorne.net
signature.asc
Description: Digital signature
