Thanks for the reply - I will try this and see if it solves the problem.
This may work with virtual machines, but it does not work with "external" nodes.
I'm trying to monitor a hostname that's based off of a F5 GTM device. The ip address changes based on datacenter availability, so it's a requirement that our monitoring app perform a DNS lookup each time it attempts to connect to the service. This does not seem to be happening, even with DHCP enabled.
Nagios seems to be the only work around at the moment, unfortunately. Anyone have a work around for this?
1 of 1 people found this helpful
I use dynamic DNS to access our remote networks around the country (roughly 100 remote sites). I typically only need to monitor one critical resource, the server. I use dyndns to update our public IP and I'm able to add a node based on hostname.
Then problem is that once added, Orion wants to store the IP address. Why?? Orion should always use the hostname. In this day and age where DNS is becoming more important (just ask anyone who's gone through a VMWare migration about the importance of proper DNS configuration) why would Orion store an IP address??
Is there a setting somewhere that I'm missing? If you edit a node, replace the IP with the hostname and select the dynamic IP option , you get an error that suggest you enter a valid IP. WHY?????
Any thoughts? Thanks in advance.