Getting Started with Cloud Infrastructure Monitoring
Cloud Infrastructure Monitoring provides visibility into your Amazon Web Services (AWS) cloud infrastructure including cloud EC2 instances and attached EBS volumes. This feature completes the Orion tools you need to monitor and administer hybrid environments.
Migrating your on-premise systems to the cloud gives you growing opportunities to distribute workloads, deliver applications, and expand resources for growing databases. Despite the ease of standing up cloud instances manually or through automation, your infrastructure can become difficult to map with lost resources or hidden instances in the sprawling environment.
With access to your cloud services account, Cloud Infrastructure Monitoring polls the cloud service APIs for cloud metrics and status. This data aggregates and displays through the Orion Web Console to monitor, manage, and troubleshoot issues in your cloud environment:
- Discover your EC2 cloud instances and EBS volumes in your cloud infrastructure
- Automatically discover and monitor new instances when launched from your cloud account
- Provide a consolidated view for cloud, hybrid, and on-premise systems
- Configure cloud alerts for cloud issues including AWS throttling, AWS exceeded limits, Orion cloud and global thresholds exceeded, polling issues, and health status
- Manage global cloud monitoring threshold settings to indicate warning and critical thresholds
- Poll for application and OS metrics on cloud instances using application monitors and templates
- See AWS metrics and relationships in SAM AppStack when AWS cloud instances are managed as nodes
Supported cloud monitoring
Orion Cloud Infrastructure Monitoring supports the following:
Amazon Web Services (AWS) EC2 instances and EBS volumes using Amazon APIs and Amazon CloudWatch data
The Orion server requires HTTPS protocol to communicate with Amazon Web Services APIs (CloudWatch, EC2, EBS) to collect metrics.
|Orion Platform products||
|Orion Platform guidelines||
Cloud Infrastructure Monitoring supports up to and recommends:
If you need to monitor beyond these amounts, SolarWinds recommends planning your monitoring for best performance and usage of your CloudWatch resources. The closer you meet or exceed supported Orion monitoring amounts may affect performance and poller load.
Cloud monitoring requirements
For AWS monitoring, you should have:
- AWS IAM user account with assigned permissions and group membership for CloudWatch metrics
- EC2 group policy permissions for AWS IAM user accounts
- Account Access Key ID and Secret Access Key for the AWS account. Locate these values through the AWS console.
If managing cloud instances as nodes, review any polling method requirements such as Orion agent, WMI, and SNMP. For details on managing nodes, see Manage the cloud instance as a node.
To prepare for cloud monitoring, add your cloud services account and select cloud instances to start polling data. The Getting Started resource provides information and options through the Cloud Summary page.
With the cloud account and cloud instances added, SAM and integrated VMAN immediately polls and collects data, populating the Cloud Summary page and additional resources with cloud instance and attached volume metrics.
- Configure Cloud Infrastructure Monitoring with your AWS account access IDs and select instances to monitor
- Configure cloud infrastructure monitoring settings for cloud monitoring.
- Review global cloud monitoring thresholds used to trigger Orion alerts and calculate status for warning and critical levels.
Cloud account management includes additional options to further manage your account, monitored cloud instances, and data retention settings.
How monitoring works
With Cloud Infrastructure Monitoring configured, it polls cloud service APIs to collect metrics. This data saves to the Orion SQL Database providing historical records for monitored cloud instances according to retention settings.
Monitoring instances and volumes does not consume Orion product licenses but may consume polling calls for the service. For AWS, all polling calls Amazon APIs to collect and report CloudWatch data to the Orion Web Console. CloudWatch polling consumes Amazon free polling requests, a limit of 1 million per month. Any requests beyond 1 million incur additional costs through AWS. For details, see Learn more about CloudWatch API.
SAM and integrated VMAN track and report cloud infrastructure data through the Cloud Summary page and Cloud Details pages to monitor real-time metrics, performance comparisons, instance and volume health, and potential issues occurring in the environment. For instances managed as nodes, a Cloud tab displays in the Node Details page.
As data and metrics collect, use these additional features to take action:
- Manage cloud instances as nodes to poll additional metrics
- Use Cloud instance management options, including reboot, monitor/unmonitor cloud instances, manage/unmanage, and terminate instances
- (SAM) Manage applications and OS as nodes per managed instances
- (SAM) Assign component monitors, application monitors, and templates to applications on managed cloud instance nodes
- (SAM) Continuously collect application data if CloudWatch APIs are disabled
- (SAM) Create groups with associated templates with custom scripting to expand polled metrics and support automation options
- Create and modify cloud alerts
- Create analysis project using Performance Analysis dashboard