Well, if you don't have access to process statistics, then maybe you could go in through the weblogs? Perhaps you could have a script, run by cron every ten minutes or so, to check up on the weblogs and restart it if it's accumulated too many (if the server gets bogged down by many rapid-fire requests) or too few (if you want to limit visible downtime to the end-user) requests since the last cron check. You wouldn't have to check the actual /data/ in the weblogs, just find out how many linefeeds there are, since there's one linefeed per server event.
Quick, dirty, and you don't need to figure out a new module, at least...?