Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Server & Application Monitor (SAM) > SAM 6.6.1 Administrator Guide > Monitor cloud instances with Cloud Infrastructure Monitoring > Configure cloud monitoring settings

Configure cloud monitoring settings


Updated: 3-9-2017

After adding a cloud account to begin cloud monitoring, review and update cloud settings for your environment. Through the Cloud Infrastructure Monitoring Settings page, you can manage configuration settings and options to:

See Manage Cloud Accounts to modify existing accounts or remove accounts. For cloud instance management options including reboot and terminate, see Cloud instance management.

Access Cloud Infrastructure Monitoring Settings

You can access cloud accounts through Settings > All Settings > Product Specific Settings or using the Cloud Infrastructure Monitoring Settings link in the Cloud Summary page.

  1. In the Orion Web Console, select Settings > All Settings.
  2. In Product Specific Settings, select the Cloud Infrastructure Monitoring Settings link.

    A page displays with cloud configuration and system options.

Add cloud account

You can add AWS accounts using the AWS IAM account access IDs. If you need these IDs, access the AWS console and make note of the access information for the account:

  1. Log in to the AWS Console.
  2. Click Account > Security Credentials.
  3. Scroll down to Access Credentials.

Each account requires a set of permissions to poll data and management cloud instances.  recommends modifying these permissions before adding the account. For JSON permissions and instructions, see Learn more about Amazon EC2 credentials for cloud monitoring.

  1. Click Add Cloud Account.
    A page displays to add an AWS account and configure cloud settings.
  2. Enter a name to display in the Orion Web Console for the account.
  3. Enter the AWS Access Key ID and Secret Address Key located in the AWS console.
  4. 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.
  5. 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.
  6. Optional, modify the settings for the following features:
    • Automatic Monitoring: automatically adds instances for monitoring when launched for the account. This feature acts as a discovery job detecting new instances. These instances add for monitoring. To add as nodes, use the manage as node option per Instance Details page. The default is enabled.
    • CloudWatch Instance Polling: enables CloudWatch API polling for metrics through AWS into the Orion Platform. The default is enabled.
    • CloudWatch Instance Polling Frequency: sets the polling frequency for the instances associated with the account. The default is 5 minutes.
  7. Optionally, you can access and manage Orion alerts from the page.

    Depending on your account limitations, you may not have access to this option.

    To open the Alert Manager, click the link. You can modify, enable, and create alerts anytime through Alerts & Activity > Alerts and select Manage Alerts. For more information, see Alerts for cloud infrastructure monitoring.

  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.

    Filtering options include the state, region, availability zone, type, platform (or OS), and monitoring state (on/off). From the list of instances, select the Monitoring On option to on to monitor. The Do Not Monitor option disables monitoring for the selected instances.
    If an instance is shutdown or not accessible, an icon displays on the instance.

    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.
  11. Optionally, you can manage the instance as a node and monitor with Orion agents.

Retention Settings

Retention settings set the amount of days after to convert statistics into summarized values or to delete them from the database. The actions differ according to the type of data.

  1. On the Cloud Infrastructure Monitoring Settings page, click Retention Settings.
  2. Enter a value for the amount of days prior to taking action on data.

    • Detailed Statistics Retention summarized into hourly statistics after the configured period of time.
    • Hourly Statistics Retention summarized into daily statistics after the configured period of time.
    • Daily Statistics Retention deleted from the database after the configured period of time.
  3. Click Submit.

Cloud global thresholds

Set cloud global thresholds to identify the warning and critical values for monitored metrics. These thresholds affect polled data from Amazon for status and Orion alerts to trigger warning and critical actions.

  1. Click Edit Global Thresholds.
  2. Set the warning and critical values for the cloud-specific settings.

    These values affect the displayed status for listed metrics and triggered Orion alerts. Modify from the following metrics. For AWS accounts, all polled data displayed in the Orion Web Console pulls through CloudWatch APIs.

  • CPU Load (percentage) - default warning is 80%, critical 90%

  • Network Receive Rate (kB/seconds) - default warning is 50000 kB/s, critical 100000 kB/s

  • Network Transmit Rate (kB/second) - default warning is 50000 kB/s, critical 100000 kB/s

  • Network Usage Rate (kB/second) - default warning is 100000 kB/s, critical 200000 kB/s

  • Read IOPS (/second) - default warning is 50000 /s, critical 100000 /s

  • Write IOPS (/second) - default warning is 50000 /s, critical 100000 /s

  • Total IOPS (/second) - default warning is 50000 /s, critical 100000 /s

  • Disk Read (Bytes/second) - default warning is 700000 B/s, critical 900000 B/s

  • Disk Write (Bytes/second) - default warning is 700000 B/s, critical 900000 B/s

  1. Click Submit.
Last modified