Hmmm, I've had my Linux guy look at the crontab, we've created a shell script to load the Zenoss environment and then launch the python script. We've also set cron to launch our shell script.
I feel like I'm missing something with 2.2.4 and this script because I'm still getting NAN... -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University James Pulver wrote, On 12/22/2008 10:41 AM: > Hmmm, so far I'm getting NAN - I'm wondering, does this script handle 0 > licenses checked out? Holidays are slow, so few licenses are checked out > (often 0). Alternatively, I've messed up my cron - how does this look: > 0,5,10,15,20,25,30,35,40,45,50,55 * * * * zenoss python > /opt/zenoss/libexec/licenseEventCheck.py > > I'm also assuming the search string will find "MATLAB" from the line > WHERE summary LIKE '%%MATLAB%%'" > > or do I need the double quotes in ther also? > -- > James Pulver > Information Technology Area Supervisor > LEPP Computer Group > Cornell University > > > > Chet Luther wrote, On 12/20/2008 8:38 PM: >> On Dec 18, 2008, at 1:46 PM, James Pulver wrote: >>> I'm not sure if this has been discussed before, but I'm currently >>> getting syslog events from a license server when a license is >>> checked in >>> and out. Now that I have the events showing up and then clearing when >>> checked back in, it would be nice if I could graph use of the >>> licenses - >>> that is how many are currently checked out. >>> >>> I'm not sure if I can graph # of a specific type of event mapping >>> active >>> (not in history) though. Any ideas how to go about doing this? >> >> You could do this with a script running out of cron every 5 minutes >> and the "Built-in" type of data source. Create a template that will be >> applied to your license server(s) and add a built-in data source to it >> called "licenses" and a gauge data point within it called "checkedOut". >> >> Then you can check out an example of the script that could be run out >> of cron at the following URL. This should be very easily adaptable to >> your specific need just by changing the "my license string" to match >> something in your event summaries. The nice thing about this script is >> that it will automatically handle however many of the license servers >> you have. The built-in data source doesn't do any collection. It >> simply makes use of RRD files that are being created by other processes. >> >> http://www.zenoss.com/Members/cluther/licenseEventCheck.py >> >> _______________________________________________ >> 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 _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
