Recommendations and requirements for monitoring cloud accounts
This SolarWinds Platform topic applies only to the following products:
Hybrid Cloud Observability Essentials — Hybrid Cloud Observability Advanced
IPAM — NAM — NPM — SAM — VMAN
The following recommendations help you monitor cloud instances/VMs with the SolarWinds Platform. If you plan to deploy your SolarWinds Platform to a cloud, see SolarWinds Platform requirements.
Cloud monitoring recommendations
For optimal performance, SolarWinds recommends the following limits for cloud monitoring:
- Up to 1,000 instances/VMs
- Up to 1,000 volumes
- Up to 1,000 instances/VMs managed as nodes
Before exceeding recommended limits, consider the impact on polling load, costs incurred due to API request overages, and the possible need to expand hardware, CPU resources, memory, and so on.
Cloud monitoring requirements
|Monitor AWS EC2 cloud metrics||
An AWS account configured for cloud monitoring. You will need the following credentials to add an account to the SolarWinds Platform or deploy Orion agents to instances:
|Monitor Azure cloud metrics||
An Azure account configured for cloud monitoring. You will need the following credentials to add an account to the SolarWinds Platform or deploy Orion agents to VMs:
The SolarWinds Platform supports VMs deployed via the Azure Resource Manager but not VMs created using a classic deployment model.
The SolarWinds Platform server must be configured to communicate with public services to collect data from cloud service APIs. Use the default setting — public — in community strings for polled devices to allow read access.
After you configure a cloud account and add an initial cloud account to the SolarWinds Platform, cloud services start polling for metrics, and you can Explore cloud instances and VMs on the Cloud Summary page in the SolarWinds Platform Web Console.