Updated: Jul 6
Your experience using the AutoMonX Azure Sensor Pack for PRTG is important to us. If you encounter any difficulties we recommend that you open a case with our support team at email@example.com. This will help us improve your experience and increase efficiency.
During the support process, we may need to collect the debug logs of our sensor. Below is an explanation how to activate the sensor debug mode.
Go to the PRTG sensor settings.
Add the argument "-debug" to the AutoMonX_AzureSensor.cmd parameters as seen below:
For versions prior to 4.2.x, that use EXE/XML sensor types use the setting below:
For versions 4.2.x and higher, that use HTTP sensor types add the following at the end of the encoded URL to enable debug: %20-debug%20-timeout%20800
This will activate the sensor debug mode upon the next run of the sensor.
For versions prior to 4.2.x The logs will be stored in the default PRTG sensor logs directory (\ProgramData\Paessler\PRTG Network Monitor\Logs\sensors)
For versions 4.2.x and higher: The logs will be available at the installation folder of the Azure Sensor in a dedicated sub-directory Azure\Logs\sensors
If you want to change the location of the debug logs, follow these steps:
Go to the AutoMonX_AzureSensor.ini file which you can find in the Azure sub-directory of the AutoMonX Azure sensor pack.
2. Change the value of the variable DEBUG_LOG_DIR to the chosen location and save
3. Let the sensor run for at least 1 hour and send us the log(s) with the collected data.
Typically, the log file name will look as the example below:
4. Don't forget to turn off debug at the end of the troubleshooting process
Enabling AutoMonX Service Debug
Change the value of the variable SERVICE_DEBUG to 1 in a file "Automonx_AzureSensor.ini" change the value of and save the file.
Restart the Automonx Azure Sensor Service. A new file will be created:
<Drive>:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML\AutoMonX\Azure\Logs\Automonx_ServiceDebugLogger.log
Don't forget to turn off debug at the end of the troubleshooting process.