Has anyone successfully configured the EP Ops agent to monitor the Apache server-status URL?
When using Hyperic, it was possible to configure monitoring via 127.0.0.1/server-status. However, I've been unable to identify what hostname to configure in the Remote-Checks URL monitoring of vROps
I have essentially followed this guide:
But the hostname field is where I'm struggling. (I've tried many variants such as http://127.0.0.1/server-status, localhost etc).
Apache httpd.conf configuration hasn't changed and is as follows:
Deny from all
Allow from 127.0.0.1
Thanks in advance
I'm guessing you will have to use the DNS name or the IP to monitor the status. Localhost and 127.0.0.1 might not work.
Check with the IP and I too will check in my lab on how to get this working.
With Hyperic it works fine - it uses the locally installed Hyperic agent to perform the checks to the URL.
I was expecting EP Ops to be able to do the same - we select the correct locally installed EP Ops agent to perform the check, so should be no need to access it externally.
We also do not want to enable external access to the URL as it poses a security risk.
Follow the guide vROPs 6.1 – How to monitor Websites, URLs, IP Addresses, and Ports using EPOPs | VM IGNITEhttp://www.vmignite.com/2016/03/vrops-6-1-how-to-monitor-websites-urls-ip-addresses-and-ports-using-... and use HTTP Check. Hit the Advance drop down and where it says "path" enter server-status since your URL is 127.0.0.1/server-status
rolled the edits into one clean post. Sorry folks.
I just attempted this and it seems to be working for me granted I'm just taking for availability of the web page.
The method defaults to HEAD instead of GET which made it work. Also, localhost did NOT seem to work for me.
Hostname seemed to take a little longer to work but the following settings work as well. Hostname by itself in the hostname field did not seem to work.
(This one was strange because it still detected the page as up even though technically the parameters are http://hostname/server-status/server-status)
Thanks - this is a great reply!
I have tried the same settings and they still don't work - but just wanted to confirm some other areas with you first?
I set this up using "Remote Checks -> HTTP Check" - I select the agent running on the server I wish to monitor.
Is the above correct?
If so, I think this could perhaps be down to firewalls in our infrastructure - although I'd hope that by using the local agent so wouldn't need additional external access.