Been busy with this for quitte a while now.
We have a PRTG set up with 3 probes:
Environment 1 (on site) Environment 2 (off site) Environment 3 (off site)
On environment 2, we host 4 virtual machines: vm1, vm2, vm3, vm4. We have the PRTG probe installed on vm1. However: there is an internal webpage that I like to monitor on VM3, just a simple status code 200 "ok" will do.
Problem is: the page I want to monitor, is only available for requests sent from VM3, only from that machine you can reach that page.
I tried working with the HTTP normal and advanced sensors, but that doesnt work "Network is unreachable"
I tried using a powershell script in combination with a file content sensor, but unfortunately it isn't able to find the "200" statuscode, neither in plain string as in regular expression.
The script I used is found here: https://gallery.technet.microsoft.com/scriptcenter/Powershell-Script-for-13a551b3
Does anybody have a solution for this problem? unfortunately my powershell skills aren't good enough to eddit the script into only showing the plain errorcode, without all the fancy stuff, because I think that might work.
Article Comments
Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.
not great with PS either, but in looking at the script i think it would have to be run on the remote machine and return a result to work with, a local call to it would give the same results as the probe device
Dec, 2020 - Permalink
the answer is in the question. that page is not available from the prob location so need a work round, such as a powershell script. a remote sensor would be a good feature, as the remote probe in cases like this seems overkill
Dec, 2020 - Permalink