Configure an AWS connector to pull metric data

Operational Intelligence provides the AWS CloudWatch connector definition which you can use to create a connector to pull metric data from Amazon Web Service (AWS). Operational Intelligence then analyses this data to provide statistical scores and detect anomalies.

Before you begin

Operational Intelligence plugin (com.snc.sa.metric) must be activated for the Operational Intelligence connectors to appear in the base system. In addition, the AWS connector requires an AWS Credentials credential that lets the instance access AWS accounts. You can use an existing credential, or create a new one.

Role required: evt_mgmt_admin

About this task

After you configure the AWS CloudWatch connector, you can run a test to ensure that the MID Server can authenticate itself to the AWS account and read data from the account.

Procedure

  1. Navigate to Event Management > Event Connectors (Pull) > Connector Instances.
  2. Click New.
  3. Fill out the Connector Instance form.
    Field Description
    Name A unique name for the connector instance record, such as the name of event source host.
    Description Any optional information that the administrator wants to use to identify this record.
    Connector definition Vendor and protocol used to gather metric data from the external source.

    Select AWS CloudWatch.

    Host IP Not used for this connector. Therefore enter any value such as 1.1.1.1, is valid.
    Metrics collection Designates collection of metric data for Operational Intelligence.

    This option appears only if the connector definition that is selected supports metric collection (such as SCOM) and if the Metrics collection option is selected.

    Metrics collection last run time The date and time of the most recent metric data collection. The value of this field is automatically populated.
    Last metrics collection status Status of the metric data collection activity. The value of this field is automatically populated.

    This option appears only if the connector definition that is selected supports metric collection (such as SCOM) and if the Metrics collection option is selected.

    Metrics collection schedule (seconds) The time, in seconds, to repeat the metric data collection scheduled job.

    This option appears only if the connector definition that is selected supports metric collection (such as SCOM) and when the Metrics collection option is selected.

    Credential A valid credential of the AWS Credentials type, to the AWS metric data source host. Click the Lookup using list icon to select a credential, or to create a new one.
    Last error message Last error message received by the connector. If the test connector fails, an error message appears in this field.
  4. In the MID Servers for Connectors related list, click Insert a new row and then select a MID Server to send metric data to.
  5. Right-click the form header and select Save.
    The Connector Instance Values related list appears.
  6. In the Connector Instance Values related list, for each name, double-click the Value column and enter values as follows:
    Name Value
    account_id The AWS account identification.
    max_fetch_interval_min Maximum time in minutes to go back to for retrieving data.

    Example value: 15

    offset_min Number of minutes to shift the time interval back by.

    Example value: 5

    period_sec The granularity in seconds of the returned data points.

    Example value: 60

    regions Regions (as they are defined in the AWS account), to get data from.
  7. Click Test connector to verify that the MID Server can communicate with the external server host.
    If the test fails, follow the instructions on the page to correct the problem and then run another test. The description of the reason for failure is shown in the MID Server log, according to the type of error, such as, Events, Metrics, or Bi-Directional.
  8. After a successful test, select the Active check box and then click Update.