You only have 5 days to get your early-bird discount for SpiceWorld 2023! Spiceworks.These sensors use a lot of RAM, in particular, so if you have any other RAM-hungry processes on the same machine, you'll notice an impact.īoth sensor will share the same data stream coming in, but the toplists are held in RAM as they're being built. Really long intervals (such as 6h and 24h) generate a lot of load on the machine where PRTG is running, so you'll want to turn these sensors off once you've found the source of the problem. I think the day starts at the time you created the sensor - was it around 10AM that you set up the 24h sensor? If setting up the 24h and 6h sensors don't catch the culprit within the first few days, you might need to try one of the other netflow tools that save the entire flows, so you can analyse the flows in more detail, after the fact. Sorry, but no, you can't set it to run midnight to midnight. Is there any way to fix that so it runs midnight to midnight? I'm in time zone +10, so I assume it's working to UTC. It looks like they're going to run in 'days' that start at 10am. I've created one for 24 hours and one for 6 hours on the original sensor instead of using a new one. I see now - it's the interval setting of the Period setting of the toplist that determines how long it aggregates for. Why is it aggregating in 15 minute blocks? The first one I set up was left on the default, which turns out to be 60 seconds. I'm a bit confused about how the scanning interval works.

Best netflow analyzer