VMware Aria Operations SaaS, Aria Operations for Logs SaaS, and their Cloud Proxys
VMware Aria Operations SaaS and VMware Aria Operations for Logs SaaS Services have been activated, you've deployed Cloud Proxys (CP) for each, and now want to monitor CP health. There are a few ways to do this and it's different for each Service, we'll explore them here.
First, a quick look back at VMware Aria SaaS CPs and their place in your environment.
Effectively, CPs act as a gateway, allowing Aria SaaS Services to see your private cloud vSphere vCenters. I blogged previously about Aria Operations for Logs CPs here. Documentation for each group of CPs can be found here:
Let's explore the Aria Operations SaaS CP first, which can be found here.
I only have a single CP, you will likely have more and can create Collector Groups for them, much like you did for your on-prem Aria Operations deployments. Just so we're all on the same page, here's a list of old names and new names.
Aria Operations - vRealize Operations (vROps)
Aria Operations Saas - vRealize Operations Cloud (vROps Cloud)
Aria Operations for Logs - vRrealize Log Insight (vRLI)
Aria Operations for Logs SaaS - vRealize Log Insight Cloud (vRLI Cloud)
Sizing of your Aria Operations SaaS CPs can be found here, note that you can double vCPU and RAM as necessary. You can also enable Data Persistence on your CPs, which will cache data for 24 hours or up to 10GB of data, whichever comes first. To see the details of your CP, click the Name.
From here you can see a bit more detail around CP health: Status, Last Heartbeat, CPU, and Memory usage.
There are also three Alert/Symptom combinations defined against the Aria Operations CP in Aria Operations SaaS itself.
The "Disk space on cloud proxy is low" alert will trigger if /storage/db or /storage/log is low on capacity remaining.
The "One or more vRealize Operations services on a cloud proxy are down" alert will trigger if/when an Event containing "Collector is down" is received.
The "One or more vRealize Operations services on a cloud proxy were restarted" alert triggers if/when one of these symptoms triggers.
Finally, the Aria Operations Cloud Proxy is just another VM, so it'll be monitored by all of the Alert/Symptom combinations in Aria Operations SaaS, things like CPU, Memory, and Disk. You can create your own Alert/Symptom combination for any available VM metrics on the CP itself.
Now, what about the Aria Operations for Logs SaaS CPs? They can be seen under Configurations - Cloud Proxies.
Selecting the Name you will see Details.
You'll see CP State, CPU, Memory, and Storage usage. You also have the ability to execute commands against it via the dropdown on the right, things like reboot, check status, and more. Check Status gives you great detail.
In the CP Details page, you'll also notice a line for the Service Proxies, in my case it looks like this.
The Service Proxy (also known as the Log Forwarder) runs on the CP, I blogged about it here. Here, you can find the State and CPU and Memory usage. You can also now adjust the Service Proxy resources via the dropdown on the right. Selecting Manage Resources, you'll be prompted for adjustments.
By default, Aria Operations for Logs CPs are 4 vCPU and 12GB RAM. This allows us to assign 4 vCPU and 11GB RAM to the Service Proxy itself. So, what about the health of the Aria Operations for Logs CP? We can enable alerts and notifications in several different spots. First, back on the Configuration - Cloud Proxies page, you'll find CONFIGURE NOTIFICATIONS.
Click that and you'll be able to configure three notifications.
This allows you to be notified when your CP is inactive, when there is an available update, and when your Service Proxy is unhealthy.
Another way to monitor health of your Aria Operations for Logs CP is via Configuration - System Alerts.
Here you can configure email notifications on several different conditions, including CP dropping logs, Ingestion Delays, and more.
Finally, the Aria Operations for Logs CP is just another VM, so it'll be monitored by all of the VM Alert/Symptom combinations in Aria Operations, things like CPU, Memory, and Disk. You can create your own Alert/Symptom combination for any available VM metrics on the CP itself.