Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Server & Application Monitor (SAM) > Server & Application Monitor Getting Started Guide > Discover > Configure Cloud Infrastructure Monitoring

Configure Cloud Infrastructure Monitoring

Table of contents
No headers

Updated: 3-14-2017

Unlike application and server discovery jobs, adding cloud instances and volumes to monitor requires configuring Cloud Infrastructure Monitoring and selecting instances.

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. 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.

Want to learn more? See the Cloud Infrastructure Monitoring guide.

AWS monitoring requires the following account information:

  • Amazon Web Services (AWS) IAM user accounts (up to 10 accounts)
  • Assigned permissions for your AWS accounts
  • AWS Access Key ID and Secret Address Key

To create an AWS account, see the Amazon documentation. To set up required permissions for AWS IAM accounts, see the Learn more about Amazon EC2 credentials for cloud monitoring.

  1. On the Orion Web Console, select My Dashboards > Cloud.
  2. Locate the Getting Started: Monitor Cloud Instances and click Monitor My Cloud Instances.

    A page displays with a walk-through of steps.

  3. Click Get Started.

    A page displays to add an AWS account and configure cloud settings.

  4. Enter a name to display in the Orion Web Console for the account.
  5. Enter the AWS Access Key ID and Secret Address Key located in the AWS console.

  6. Optionally, enter a description to help identify the account.

    Use this description to keep track of the IAM user accounts added. The Orion display name and AWS account name can differ.

  7. Click Test Connection to verify the access keys to AWS.

    If issues occur, check the access keys and IAM user account in the AWS console.

  8. Click Next.

    A page opens to select instances for monitoring accessed with the AWS account IDs and Amazon APIs.

  9. Select instances and click Monitor to enable monitoring.

    Filter the list of instances to select and monitor cloud instances.

    All metrics poll using Amazon API calls, including CloudWatch. All monitored metrics count against the 1 million free requests provided by Amazon. Any requests beyond 1 million will incur additional costs. Other tools in your environment making CloudWatch API calls also count against your free requests limit.

  10. Click Save.

    The cloud instance displays in the cloud instance and infrastructure resources in the Cloud Summary page. You can manage the cloud instance as a node, assign templates, and monitor metrics in SAM.

 
Last modified
12:56, 14 Mar 2017

Tags

Classifications

Public