As to the SSH modeling, it is far more limited I believe in 2.3.3 than
SNMP, but is supposed to be much improved in 2.4, one of the main areas
updated for 2.4.
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
jcurry wrote, On 4/15/2009 2:10 PM:
> Zenoss 2.3.3 on SLES 10 (but I doubt that makes much difference!)
>
> If I want to monitor for specific processes on a box, typically the box
> supports SNMP so if I put it in a class like /Device/Server/Linux it will
> automatically have MODELING data collector "plugins" applied, including
> zenoss.snmp.HRSWRunMap (use table drop-down menu for device and select More
> -> "Collector plugins"). If you turn up debug on zenmodeler you can see this
> information being collected using the SNMP Host Resources MIB (just run
> zenmodeler run -v 10 -d <your device name> ).
>
> If you go to the device's OS page, you can see configured Processes and
> clicking on the Process Name entry takes you (hopefully) to graphs of cpu,
> memory and count for that process. From the graphs page, if you go to the
> template tab it show that the standard /Devices/OSProcess template is used to
> collect this data. However the Data Sources for OSProcess are rather strange
> - the type is SNMP but there is no MIB OID to supply the data! I expected
> this to be getting data from the Host Resources hrSWRunPerf table?? What
> actually populates these graphs ('cos there IS data there and it looks
> reasonable)?
>
> Next step. Suppose you can't use SNMP to get process info from a box. You
> can assign it to /Devices/Server/Cmd and it gets a bunch of MODELING data
> collector "plugins", including zenoss.cmd.linux.process. Now if you run
> zenmodeler in debug you can see that simple operating system commands are run
> over ssh (provided your ssh authorization is all setup). You can see a line
> like:
>
>
>> DEBUG:zen.SshClient:command ps axho comm,args
>>
>
> followed by a whole bunch of lines which is obviously output from the above
> ps command (note that there are no Nagios plugins involved here - it's just
> the ps command run over ssh). However, if processes die, they never get
> reported in Zenoss - status always stays green (and I don't think it is the
> "display bug reported in ticket 3780 and I have restarted zenprocess....). I
> have turned up debugging in zenprocess and can see reports on other processes
> on other devices that are performing process checks with SNMP but there
> appears to be no reference whatsoever to the process being checked on my ssh
> device.
>
> Next problem, if I drill into the process name to see graphs of cpu, memory
> and count for this process, the cpu and mem have no graph at all between the
> < and > bars. The count graph exists but has "nan" values - not available.
> Not surprising really as it is still using the single /Devices/OSProcess
> template described above which "suggests" it using SNMP.
>
> So,
> 1) Is this process monitoring by ssh commands working as designed and,
> basically, it doesn't work (even though it does get the data)
> 2) Has anyone got this to work?
> 3) Even with standard SNMP process modelling using the HRSWRunMap data
> collector, what is actually populating the OSProcess performance data
> template?
> 4) Is there any chance of getting the performance data if you are using the
> zenoss.cmd.linux.process collector?
>
> Cheers,
> Jane
>
>
>
>
> -------------------- m2f --------------------
>
> Read this topic online here:
> http://forums.zenoss.com/viewtopic.php?p=33416#33416
>
> -------------------- m2f --------------------
>
>
>
> _______________________________________________
> zenoss-users mailing list
> [email protected]
> http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
