The probe device reported low disk usage which was due to millions of jscript files in the temp folder:
C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Microsoft\Windows\INetCache\IE
this is related to URLs we monitor using the HTTP Full Web Page sensor. How can we avoid this issue?



I have tested it and it is indeed an issue when you use Internet Explorer as Browser Engine in the HTTP Full Web Page sensor.

The actual location of these temporary files varies. It could be one of the following:

C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5
C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5
C:\Users\%USERNAME%\AppData\Local\Microsoft\Windows\INetCache

The actual path depends on the OS version, Internet Explorer version, or the context in which the PRTG probe service is running. We are not able to avoid generating these files when using Internet Explorer as Browser Engine because this behavior is dictated by the configuration and settings of Internet Explorer.

The best way to avoid this is to switch to one of the other browser engines available in the sensor settings:

  • Chromium (default)
  • PhantomJS (Headless Webkit)

If you have a large number of sensors of this type, you can use the Multi-Edit functionality (via Sensors | By Type | H | HTTP Full Web Page) to batch change them.

If your use case does not allow the usage of a different browser engine, you might want to set up a scheduled task to clear up the folder. This can easily be done using the Task Scheduler and a Batch or PowerShell script.


More


Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.