Documentation forOrion Platform

Recommendations and requirements for monitoring cloud accounts

The following recommendations help you monitor cloud instances/VMs with the Orion Platform. If you plan to deploy your Orion Platform to a cloud, see Orion 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

Functionality 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 Orion Platform or deploy Orion agents to instances:

  • Access Key ID
  • Secret Access Key
Monitor Azure cloud metrics

An Azure account configured for cloud monitoring. You will need the following credentials to add an account to the Orion Platform or deploy Orion agents to VMs:

  • Subscription ID
  • Tenant/Directory ID
  • Client/Application ID
  • Application Secret Key

The Orion Platform supports VMs deployed via the Azure Resource Manager but not VMs created using a classic deployment model.

The Orion 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 Orion Platform, cloud services start polling for metrics, and you can Explore cloud instances and VMs on the Cloud Summary page in the Orion Web Console.