lordmilko
commented
2 years ago Hi @schoenm1,
Previously I would have said this is a problem with PRTG rather than PrtgAPI specifically, and there's nothing that can be done about it. My general recommendation when doing "memory intensive" operations like this is to spread it out a bit, introducing artificial delays between each item that is processed (e.g. you could do sleep 60 to sleep for 60 seconds after each device that is added). By spreading things out more PRTG may be able to better deal with its memory issues.
Recently, Paessler alerted me to a secret parameter PrtgAPI can include in some of its API calls which should reduce memory usage, however much testing/exploration needs to be done on this so this is not something that will be incorporated into PrtgAPI any time soon. As such, for now I would say "slowing down your script" may be the best course of action
schoenm1
What's going on?
Hi @lordmilko We created a fully automated Script (Powershell) with your PRTGAPI Module. We create devices from an excel input. For each device, multiple sensors will be added: ping, system uptime, memory, cpu.... In PRTG Version 21.3.71.1416+ (not sure if PRTG Version Issue) the PRTG Core Server Free Memory will decrease until Server is unreachable and has to be restarted. (Server has >30GB Memory). Our Script will connect to PRTG Server, then ... Add-Group / Add-Device / Add-Sensor ... Do I need to free up any memory again after this commands? It seems that the used memory during this Add-XYZ Task are reserved for ever until the server runs out of memory. I tested more than one time. Each time I use PRTGAPI, the memory will decrease (in 10minute script memory from 46% free to 1% free)
Due Dilligance