Creating AWS CloudWatch integrations
An AWS integration can provide CloudPak for AIOps metric, event, and topology data for the applications or infrastructure that you monitor.
To activate the integration, you must have an endpoint, an access key, and a secret key ready. You can select the metrics that you want to monitor by choosing the associated namespaces in the IBM Cloud Pak for AIOps console. The Metric anomaly detection AI algorithm analyzes the AWS CloudWatch data.
For more information about working with AWS CloudWatch integrations, see the following sections:
- Creating AWS CloudWatch integrations
- Enabling and disabling AWS CloudWatch integrations
- Editing AWS CloudWatch integrations
- Deleting AWS CloudWatch integrations
For more information about HTTP headers for the various credential types, see HTTP headers for credential types.
Creating AWS CloudWatch integrations
To create an AWS CloudWatch integration, complete the following steps:
-
Log in to IBM Cloud Pak for AIOps console.
-
Expand the navigation menu (four horizontal bars), then click Define > Integrations.
-
On the Integrations page, click Add integration.
-
From the list of available integrations, find and click the AWS CloudWatch tile.
Note: If you do not immediately see the integration that you want to create, you can filter the tiles by type of integration. Click the type of integration that you want in the Category section.
-
On the side-panel, review the instructions and select your required options from the following sections:
-
Select the data types that you need: Select the relevant checkbox for Metrics, Events, or Topology.
-
Specify whether you'd like to install the integration: Select between the Cluster running Cloud Pak for AIOps or Self-hosted with network visability to Dynatrace radio buttons.
-
Select Cloud Pak for AIOps integration: You can leave this at the default Use the integration recommended by Cloud Pak for AIOps, or deselect it, and change to just Metrics, Events, or Topology.
The below steps presuppose you select Metrics but if you do select Events then there will be a Collect event data page to complete, and if you select Topology then you will be brought to a New observer job page. The AWS observer reads services data from AWS through the AWS SDK and generates a topology. The AWS Observer supports multiple Amazon Web Services (AWS) services such as EC2 for its compute services. For more information, see Configuring an AWS observer job.
-
-
Then click Next.
You see an overview, further direction such as what you need to have ready and also what algorithms analyze Dynatrace data.
Figure. Configure AWS integration - get started -
Click Get Started.
-
On the Add integration page, define the general integration details:
-
Name: Type in the display name of your integration.
-
Description: Provide an optional description for the integration.
-
Endpoint: Enter an endpoint for the integration. For example
https://monitoring.us-east-1.amazonaws.com
.Figure. Add AWS integration -
Access Key: Enter an Access Key for the integration.
-
Secret Key: Enter a Secret Key for the integration. For getting access and secret keys, contact admin.
-
AWS CloudWatch region: Select a region from the available regions in AWS, for example, us-east-1.
-
Deployment options: Select one of the following options: Local or Remote.
The Local option deploys the integration in the same cluster where IBM Cloud Pak for AIOps is installed. Alternatively, the Remote option deploys it in your chosen location. If you select the remote option, you are provided with a bootstrap command after adding the integration to finish the deployment.
-
-
To verify the SSL/TLS configuration:
- Set the Verify the SSL/TLS certificate for the REST service toggle to on.
- Either enter a CA certificate used to verify the SSL/TLS integration to the REST service or click Fetch SSL certificate to fetch the certificate automatically.
-
Click Test connection. A message stating whether the test succeeded or failed is displayed.

-
Click Next.
-
On the Configure Proxy (Optional) page complete the following fields:
-
Connect to AWS CloudWatch via a proxy server: Set the toggle button to on.
-
URL of HTTP proxy server: Enter a URL for the HTTP proxy server.
-
Port number of proxy server: Enter a port. The default is 8080.
Note: Only unauthenticated HTTP proxy is supported.
-
-
Click Next.
-
Enter the following Collect metric data information. It defines how you want to collect metric data.
-
Enable data collection: Set the toggle button to on.
Note: If you disable data flow, a new integration is created, but metrics are not collected.
-
Namespace: Select one or more namespaces from the list to see its associated metrics in the filter table. By default, all metrics are selected in the table. You can search and select or remove metrics from it.
-
Aggregation interval (minutes): Enter a value in minutes. This value is the frequency at which data is collected. The default value is 5 minutes.
-
Select live or historical data collection
Note: If you choose to collect only live data, you cannot collect historical data after the live data collection starts. However, if you collect historical data, you can continue live data collection afterwards.
-
Live data collection: To collect live data, complete the following steps:
- Only collect live data once the integration is established: Select the checkbox.
- Scheduler run time (minutes): Enter a value in minutes. The value represents the frequency at which live scheduler runs. For example, if you set the value to 10 minutes, the live scheduler runs every 10 minutes. The default value is 5 minutes.
-
Historical data collection: To collect historical data, complete the following steps:
-
Start date and time: Select the start date from the calendar and enter the time in the 'hh:mm' format (hours and minutes).
Note: The start date must not exceed 31 days from the present as the maximum time period for historical data collection is 31 days. The recommended time period is two weeks.
-
Time zone: Select your time zone from the dropdown list.
-
End date and time: Select a date from the calendar. Also, enter the time in the hh:mm format (hours and minutes). If you want to the end date, click Remove end date.
Note: If you do not set an end date, IBM Cloud Pak for AIOps collects historical data from the specified start date and continues with live data collection. You cannot collect historical data after the live data collection starts.
-
Scheduler run time (minutes): Enter a value in minutes. The value represents the frequency at which live scheduler runs. The default value is 5 minutes.
Note: Scheduler run time is only applicable to live mode. You must configure the scheduler run time only if you do not add an end date as the integration will continue to run in live mode after historical mode.
-
-
-
-
Click Done.
For more information about performance considerations for metric data collection, see Performance considerations for metric data collection.
Enabling and disabling AWS CloudWatch integrations
If you didn't enable your data collection during creation, you can enable your integration afterward. You can also disable a previously enabled integration the same way. To enable or disable a created integration, complete the following steps:
-
Log in to IBM Cloud Pak for AIOps console.
-
Expand the navigation menu (four horizontal bars), then click Define > Integrations.
-
On the Manage integrations tab of the Integrations page, click the AWS CloudWatch integration type.
-
Click the integration that you want to enable or disable.
-
Go to the Collect metric data section. Set Enable data collection to On or Off to enable or disable data collection. Disabling data collection for an integration does not delete the integration.
You enabled or disabled your integration. For more information about deleting a integration, see Deleting AWS CloudWatch integrations.
Editing AWS CloudWatch integrations
After you create your integration, you can edit it. To edit a integration, complete the following steps:
-
Log in to IBM Cloud Pak for AIOps console.
-
Expand the navigation menu (four horizontal bars), then click Define > Integrations.
-
Click the AWS CloudWatch integration type on the Manage integrations tab of the Integrations page.
-
On the AWS CloudWatch integrations page, click the name of the integration that you want to edit. Alternatively, you can click the options menu (three vertical dots) for the integration and click Edit. The integration configuration opens.
-
Edit your integration as required. Click Save when you are done editing.
Deleting AWS CloudWatch integrations
If you no longer need your AWS CloudWatch integration and want to not only disable it, but delete it entirely, you can delete the integration from the console.
To delete a integration, complete the following steps:
-
Log in to IBM Cloud Pak for AIOps console.
-
Expand the navigation menu (four horizontal bars), then click Define > Integrations.
-
Click the AWS CloudWatch integration type on the Manage integrations tab of the Integrations page.
-
On the AWS CloudWatch integrations page, click the options menu (three vertical dots) for the integration that you want to delete and click Delete.
-
Enter the name of the integration to confirm that you want to delete your integration. Then, click Delete.
Your integration is deleted.