Home > Cloud Cruiser 4 > Collecting, transforming, and publishing > Amazon CloudWatch

Amazon CloudWatch

Amazon CloudWatch monitors and provides metrics for your Amazon Web Services (AWS) resources and the applications you run on AWS. For example, you can monitor the CPU usage and disk reads and writes of your Amazon EC2 instances and then use this data to determine whether you should launch additional instances to handle increased load.

In your Cloud Cruiser collection you can define metrics, namespaces, and statistics from Amazon CloudWatch. A metric is a variable that you want to monitor, such as CPUUtilization or Latency. Each metric is contained within a namespace, and is unique within that namespace. For example, if you define the same metric in two different namespaces, they are treated as independent metrics. For each metric you want to collect, specify a statistic that defines the type of aggregation done for that metric, such as Sum or Average. Cloud Cruiser collects each independent metric as a measure.

For more information, see Amazon CloudWatch concepts in the Amazon CloudWatch documentation.

Amazon CloudWatch provides data only for the most recent 2 weeks. If you try to collect data more than 2 weeks old, Cloud Cruiser collects data only up to the last valid 24 hour period within the most recent 2 weeks. If you try to collect a single day's data that is exactly 2 weeks old, Cloud Cruiser produces an error for an invalid time period because the Start Date and End Date of your job are treated by Amazon CloudWatch as the same date.

Before you begin

While Cloud Cruiser includes an AWS schema that enables you to map collected AWS usage data to the Cloud Cruiser database, the AWS usage schema might not suit the specific data you collect from Amazon CloudWatch. Consider creating a separate schema for Amazon CloudWatch data. For more information, see Managing schemas.

Configuring Cloud Cruiser to collect, transform, and publish Amazon CloudWatch data

To collect, transform, and publish Amazon CloudWatch data

  1. Create an Amazon CloudWatch data source.
    1. Navigate to Data > Setup > Sources.
    2. Right-click Amazon Web Services and select Add data source.
    3. In the Name field, enter a name for your data source.
    4. In the Access Key Id field, enter the access key ID for an AWS user who has access to billing information.
    5. In the Secret Key field, enter the secret key for this user.
    6. Click Save.
  2. Create a workbook, as described in Creating workbooks.
  3. Create an Amazon CloudWatch collection, as described in Creating collections.
    • In the Data Source field, select the data source you created earlier in this procedure.
    • In the AWS Collection properties section, set the Sampling Period field to collect data either Hourly or Daily.
  4. Specify the Amazon CloudWatch namespaces and metrics you want to collect:
    1. In the Amazon CloudWatch Collection dialog box, click Advanced.
      The Advanced Configuration dialog box opens.
    2. Click the CloudWatch Profiles tab.
      cloudWatchProperties.jpg
    3. In the upper pane, modify the collection to include the CloudWatch namespaces, metrics, and statistics you want to collect. By default, the Amazon CloudWatch collection includes the AWS/EC2 namespace, with the CPUUtilization, NetworkIn, NetworkOut, DiskReadOps, and DiskWriteOps metrics. For more information about CloudWatch namespaces and metrics, see Amazon CloudWatch Namespaces, Dimensions, and Metrics Reference in the Amazon CloudWatch documentation.
    4. Click OK.
  5. Create any required data-transformation workflow, as described in Working with flows.
  6. Configure your workbook to publish the transformed data, as described in Publishing data to a schema.
  7. Test your workbook to ensure it collects, transforms, and publishes your data correctly.
    1. In the Workbook ribbon, click Run.
      The Run Workbook dialog box opens.
    2. In the Select Date field, enter the current date.
    3. Select all of the collections and flows, and then click Run.
    4. After the run finishes, click View Log at the bottom left of the dialog box to open the Monitoring window, where you can view the log for any specific collection or flow.
    5. If your workbook test run did not complete successfully, or if it did not provide the data you need, edit the workbook and then run another test.
  8. When you are done editing your workbook delete any data loads from your test runs.
    1. Navigate to Data > Processing > Published Loads.
    2. Select one or more entry rows and click Delete Load(s) at the top of the page.
    3. Click Yes to confirm the deletion.
  9. Schedule regular collection for this workbook, starting when the next day's complete data is available, as described in Scheduling jobs to run.
  10. Collect and publish past data for this workbook to ensure that Cloud Cruiser has all available prior data, as described in Run a workbook for a range of dates.

Dimensions and Measures collected from Amazon CloudWatch

Cloud Cruiser collects all of the dimensions available for the Amazon CloudWatch namespaces configured in your collection. Additionally, Cloud Cruiser collects measures for any metrics configured in your collection. Each measure is named in Cloud Cruiser using the following convention: <namespace>.<metric>.<statistic>.<unit>. For example, AWS/EC2.CPUUtilization.Average.Percent.

For more information about the dimensions and measures available from Amazon CloudWatch, see Amazon CloudWatch Namespaces, Dimensions, and Metrics Reference in the Amazon CloudWatch documentation.

Last modified

Tags

Classifications

This page has no classifications.
© Copyright 2018 Hewlett Packard Enterprise Development LP