One clarification gleaned from the Zenoss devs - Zenoss is using Python verbosity levels, which oddly enough go something like this: 50 - critical 40 - error 30 - warning 20 - info 10 - debug
Zenoss defaults to 20, so 10 is really the only valid choice for more info, though you could tune it down I guess with 30 - 50, but it's pretty sparse by default. -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University thomas wrote, On 2/25/2009 9:51 AM: > Yes that is possible, you just have to raise the debuglevel of zencommand, > > However, when I'm testing new monitor-commands, then I invoke zencommand > myself, ie, change to the zenoss user, and use > > zencommand run -d <your-device-id> run -v3 > > Then it will run the zencommand tests and because you use -v3 (or maybe even > -v10) then it will show the commands that is used. > > Thomas > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://forums.zenoss.com/viewtopic.php?p=31678#31678 > > -------------------- 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
