NRDS Checks: Multiple Time Intervals

[mikew]

I am working on a project to monitor PBX systems using NRDS. The PBX systems are all on Ubuntu servers and NRDS works great for monitoring OS metrics and the asterisk server information. My problem comes with the statistics for logs. I am measuring calls, time for each call, averages, maximum, minimum, etc.(stuff customers want). All of these statistics mean parsing the logs for asterisk. When I run them with NRDS of course they all run at the same time...which drills the server into the dirt and uses 100% of CPU. In fact 1 minute load average on a 1 core (virtual test box) was 68.

So, I really want to do this with NRDS. I am experimenting with ways to use NRDS to execute commands at different times on the same server. You guys may have already done this so you may be able to save me some time but I am thinking of creating another config (on XI) with a different location for plugins, configs (in additional settings) so it does not interfere with OS metrics config. Is that a reasonable approach or is there a better way?

If this idea works it is still clumsy as I need to run log checks at 20 different schedules...as each scan for each service check is expensive as the logs for asterisk get big.

Progress:
OK so I have made some progress on this. What I did was create multiple nrds.cfg and nrds.pl files on the server. This allows me to create as many time intervals as I want and use cron jobs to issue them...here is an example that worked.

:/usr/local/nrdp/clients/nrds# /usr/local/nrdp/clients/nrds/nrds1.pl -H pbx
Sent 1 checks to http://192.168.2.131/nrdp/


As always...thanks I appreciate your time.

[sreinhardt]

Hey Mike! Well I haven't run into this particular issue before, however it sounds like you solved it in exactly the same manor I would have. Creating the additional configs, but using the same plugin dir, ideally should not be an issue, and could be cron'd separately. It seems like you've got it worked out as of now, if you run into other issues let us know!