This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

monitoring a http site in AWS environment with constantly changing IP

How can we monitor a website that resides in AWS cloud which changes its IP address constantly.  Each time I ping, the URL resolves a different IP, and it looks like SAM uses IP address to monitor HTTP sites.

Is there an option to change, so that SAM would track based on URLs?

In the Web Browse Template, the default choice is http://{{ HrefIPAddress }}, and I'm getting the below error:

Access denied, authorization failed. HTTP 403. Forbidden. The remote server returned an error: (403) Forbidden.

  • Have you tried using the DHCP option (from Edit Node view)?

    pastedImage_0.png

  • Or here (edit the applied template and hard code the URL in)?

    pastedImage_0.png

  • I tried the DHCP option, and it didn't work.  The odd thing is that even though I check the box for Dynamic IP Address, I have to put an IP address in the Polling IP address box.  Without a valid IP address, the DHCP or BOOTP option doesn't work.

    After choosing the DHCP option, when I navigate to Application Component Details for HTTP monitor, URL: under Component Settings shows http://x.x.x.x/ and not the actual URL.  So, it seems like SAM uses IP address even though the DHCP option is chosen.

    I've also tried to revise the URL: box with the actual URL, but that doesn't seem to work either.

    I know it's a valid website as I can add the URL to another monitoring tool (Netreo OmniCenter), and it works fine.

  • Is this setup as an external node or ICMP?  The way I understand how the DHCP option works for node polling is Solarwinds has to be able to successfully resolve the hostname by pinging it.  I don't believe the external nodes will do this since they don't check status by default.

    On a possibly related note, you'll also need to make sure the AWS security group inbound rules will accept ICMP from your Solarwinds host.