Continuous Monitoring Guidelines

We have some basic guidelines, although your situation will almost certainly be different than what we do here at Nessoft.

Setting up your memory footprint

If you run continuously, at some point PingPlotter will exhaust your system memory unless you give it guidelines on how much memory to keep around.

• Determine how often you want to sample. 2.5 seconds gives a good amount of accuracy without too much data. Some people use 10 seconds. Anything much longer and you might miss problems.
• We find that having 4 to 5 days of data in memory at a time works well. There are 86,400 seconds in a day, 432,000 seconds in 5 days. Divide this 432,000 by your trace interval. For 2.5 seconds, this gives us 172800 samples in 5 days.
• In PingPlotter Standard, go to Edit -> Options, General tab. In PingPlotter Pro, go to Edit -> Options, then the Auto-save section of the configuration you're interested in (Default Settings, for example). Enter your calculated number in "Maximum samples to hold in memory". 172800 samples takes up roughly 10 to 15 megs of RAM in memory, which puts the PingPlotter memory footprint around 40 megs total (it keeps multiple copies of the data in RAM at some points, and general overhead). This is workable for just about any workstation.

Setting up PingPlotter to save data

With 4 to 5 days of data in memory, each save of data will have all of this, which puts each save file around 1 to 3 megabytes. Having one file per day gives you easy access to a day's data, along with the previous 4 days for good analysis. We suggest saving every 30 to 60 minutes, with a filename like this: c:\ppdata\$dest\$dest $date.pp2

• In PingPlotter Standard, go to Edit -> Options, Auto-save tab. For PingPlotter Pro, go to Edit -> Options, then go to the Auto-save section of the configuration you're interested in.
• Turn on "Auto-save data"
• Set "Save Interval" for "30 minutes"
• Set filename to "c:\ppdata\$dest\$dest $date.pp2". If you're currently tracing to a target, floating over the filename field will show you a hint of the file that would be actually saved.

We set up "30 minutes" for a save interval. The filename controls how often we create a new save file. You can include $hour in the save file name to get a new file every hour. If the file already exists, it will be overwritten.

This will give you a new file each day with 5 days of data in it. Each day's file will be missing the last few minutes of the day as the 30 minute save interval may hit at 23:35 or 23:59, but that data will always be stored in the *next* day's file.

Feel free to tweak these settings however you want. This is just a discussion of some possible starting points.