Nagios Support Forum

Hi all, We have to monitor the Azure servers for one of our client for availability, CPU, Memory etc. I understand we have to install the NRPA client on the machine we want to be monitored. Looks like the NRPA client needs the IP address of the host server hosting the nagios. Could we provide the public IP address of our nagios server? Will a public IP address do?

Hi @Kush,

I would recommend using the Azure Configuration Wizard in Nagios XI to get started. You'll need to install NCPA ( Nagios Cross Platform Agent ) on the VM to be monitored.

Follow the installation instructions below for NCPA below. You''ll need to open up a port for the Nagios XI server to communicate with NCPA and then when setting up checks in Nagios XI, you'll need the ip address of the device (vm) your monitoring.

NCPA Agent Installation Instructions

Let me know if you're able to get up and running.

Hi Benjamin, Thank you for your message. I am in the same boat. I am trying to monitor azure VM in Nagios XI as well.
I have followed the document you mentioned above and created a test machine in azure and installed NCPA on it.
I am able to ope the NCPA GUI using https://<Private IP>:5693 but UNABLE to open using the https://<public ip>: 5693

Even when I try to go to cofifuration >> azure vm and put the public ip and token , the validation fails.
I verified that port http, https , rdp and 5693 are open in azure machine

Looks like it has to do Azure security settings I guess. could you please suggest further?

This could be multiple things, I would run this command against your public/external azure IP from an external host to see if the port is listening:
What is the output of this command on the Azure server?
You will need to work with Azure support for any Azure configuration support as I've never worked with it.

Please attach a sanitized copy of your ncpa.cfg file for review.
- Mainly I'm looking at the allowed_hosts = ?and ip = ? directives but please attach the entire file.

Thanks...Actually this got resolved. Had to get it checked with the networking team..they said antivirus was blocking something.

Kush wrote:Thanks...Actually this got resolved. Had to get it checked with the networking team..they said antivirus was blocking something.

Great!

Locking thread