Have you ever needed to monitor the following vRealize products from outside without an agent installed? Below I detail all the useful URL’s / CLI’s, example output and some permissions needed to check and monitor vRA, vCenter, vRO, NSX Manager, vRops, vRLI and vRNI

vROPS – vRealize Operations Manager

This one is simple, just check for ONLINE within <status>

Permissions: No permissions required to access the URL.

URLS:

Output:

 

 

vRNI – vRealize Network Insight

vRLI does not have a URL to check the status of the appliance, the only way I found to do this was by SSHing to the Platform VM and checking via a CLI.

Basically the expected state is everything is running.

Permissions: SSH with consoleuser and password (default) ark1nc0ns0l3

Command: show-service-status (check out my powershell script here which i use to monitor this on a schedule)

Output:

 

vCenter – Virtual Center (appliance)

Below are several URL’s to monitor, with the vCenter API you will need to first call the auth url to get a session ID before you can call the Health URLS below.

Permissions: The user will require administrator permissions to the vCenter

URL:

OUTPUT:

 

URL:

OUTPUT:

 

URL:

OUTPUT:

 

URL:

OUTPUT:

 

URL:

OUTPUT:

 

vRA – vRealize Automation

Useful information for all the services that make up vRA.

Permissions: No permissions required to access the URL

URLS: 

The URL above will give you the following information

 

another useful url to hit for vRA

The URL above will give you the following information which is useful to track the serviceInitializationStatus

 

vRO – vRealize Orchestrator (appliance)

Below is a useful vRO Health URL to query

URL:

OUTPUT:

vRLI – vRealize Log Insight

To access the vRLI API a sessionid will need to be generated first, below is an example of the body that will need to be posted to https://~VRLIServer/api/v1/sessions that returns the sessionid

Permissions: The user will require admin permissions to access this area of the API.

When calling the URL below make sure to use the header with the session id (Note: this times out every X minutes)

In my case I needed to make sure the VIP was up and AVAILABLE

OUTPUT:

NSX Manager

To get access to the URL’s below you will need to create a user by following the method here

example output

 

another useful url to track the storage of the NSX manager

example output

hope this is helpful!

vMan