I want to set up a traceroute sensor for external destinations like say for example, google.com. In the traceroute sensor settings, there is no option to specify URL.
the traceroute sensor will always use its parent device as target. So you will have to create a device in PRTG which represents google.com and place the sensor on this device.
Thanks a lot, Wolff. I have a few questions; 1). So, if I need to create the traceroute sensors for different external websites, I need to create a device for each of them? 2) . I go with the same procedure as adding a new device, only in the IPv4/DNS Name I enter www.google.com? 3). Is there no other way to create traceroute sensors for external websites under one device?
please see my answers below:
1). So, if I need to create the traceroute sensors for different external websites, I need to create a device for each of them?
2) . I go with the same procedure as adding a new device, only in the IPv4/DNS Name I enter www.google.com?
3). Is there no other way to create traceroute sensors for external websites under one device?
No I'm afraid this is not possible.
Perfect! I was able to add a traceroute to google. However, it just shows the number of hops. Is it possible to see the actual hops to determine which hop is having latency issues? Like you see in the tracert?
I'm afraid the sensor does only show the hop count and is not able to show the single hops. If you are in need to show the hops, you might use a own script and run the same with an EXE/Script Sensor.
EDIT: An example for a powershell script can be found here but it has to be adjusted.
I copied the script and saved it as .ps1 and added it to the /Custom Sensors/EXE sub-directory of the probe system's PRTG program directory. But, when I go to add sensor, that file isn't displayed for selection.
Was able to add in the custom sensor. But, it throws out the error Handle is invalid (0x6).
Please make sure that the Custom Sensor follows the 'rules' for the format of the return value and message
Further Details can be discerned in your very own PRTG under "Setup"->"PRTG API"->"Custom Sensors".
Please also consider implementing debug log output into the script, so that you can see where it might fail/break.