Dynatrace AWS CloudWatch integration provides an easy and safe way to ingest AWS metrics.

Bobcres answers to all questions no matter the size, as part of our AWS support Service.

Let us take a look at Dynatrace AWS Cloudwatch integration in detail.

Integrate dynatrace aws cloudwatch Metric Streams

Dynatrace AWS CloudWatch integration is the most efficient way to ingest AWS metrics. All metrics distributed in a particular AWS locale are allowed to be broadcasted to the Dynatrace API. It uses Amazon CloudWatch Metric Streams via Kinesis Firehose. And, note that activeGate secure proxy is not necessary for this integration.

Requirements for Dynatrace Cloudwatch integration

The first step is to make an API token within the Dynatrace environment and allow the Ingest measurements consent. Decide the API URL for the required environment. Use the codes given below to determine the Dynatrace environment:

1. For Dynatrace SaaS: https://.live.dynatrace.com
2. For dynatrace Managed: https:///e/
3. For ActiveGate: https://:9999/e/

Metric Stream client configuration

CloudFormation permits a user to send a Metric Streams client. And, it uses only a single sending command to form a stack that groups numerous AWS assets. For each region the user wants to monitor, a separate client stack is required.

Deploy the Metric Streams client for a default region

Run the command below to retrieve the CloudFomration template and send it to the AWS account. Make sure to replace the values of user API URL and user API token.

DYNATRACE_ENV_URL= user_API_URL
DYNATRACE_API_KEY= user_API_token
STACK_NAME=dynatrace-aws-metric-streams-client
DELIVERY_ENDPOINT=https://aws.cloud.dynatrace.com/
REQUIRE_VALID_CERTIFICATE=true

wget -O dynatrace-aws-metric-streams-client.yaml https://dynatrace-aws-metric-streams-client.s3.amazonaws.com/dynatrace-aws-metric-streams-client.yaml && \
aws cloudformation deploy --capabilities CAPABILITY_NAMED_IAM --template-file ./dynatrace-aws-metric-streams-client.yaml --stack-name $STACK_NAME --parameter-overrides DynatraceEnvironmentUrl=$DYNATRACE_ENV_URL DynatraceApiKey=$DYNATRACE_API_KEY RequireValidCertificate=$REQUIRE_VALID_CERTIFICATE FirehoseHttpDeliveryEndpoint=$DELIVERY_ENDPOINT

Metric Streams client for other regions

The user can export other variables like AWS_DEFAULT_REGION and AWS_PROFILE. And, then restart the deployment procedure to modify the profile and the region.

If the user uses or relies on Cloudshell, then they can alter the region in the AWS console.

Metric streams Deployment confirmation

A user can make sure of the correct deployment of the Metric streams client by following the steps given below.

1. Firstly, go to CloudFormation from the AWS console
2. Then, select the stack from the CloudFormation deployment
3. After this, make sure of the successful completion of all of the events from the Events tab.
4. Then, the user must make sure that the Parameters hold the correct values

Restrict Metric streaming

A user can restrict the streaming on certain metrics using simple steps. They are:

1. Firstly, go to CloudFoundation in the AWS console
2. Then, choose the created stack from the CloudFormation deployment
3. After that, find the resources with the type AWS::CloudWatch::Metric Stream.(Make sure to note down the physical id)
4. Go to cloud watch. Choose Streams from the Metrics on cloudwatch.
5. Save the changes under Metrics to be streamed and save it.

View Metrics using dashboards

A user can use the predefined dashboards from the Github store in the Dynatrace web UI for data viewing. Use it after the deployment of the Metric streams client.

Follow the steps to upload predefined dashboards from GitHub.

1. Firstly, get upload_dashboards.py from the GitHub store as shown below

   curl -o upload_dashboards.py https://raw.githubusercontent.com/Dynatrace/snippets/master/product/dashboarding/upload_dashboards.p
2. Secondly, create a directory for ‘dashboards’ near ‘upload_dashbaords.py’
3. After that, add any dashboard definition JSON file from the Github store from GitHub to the dashboards directory
4. Finally, run the script given below. Make sure to replace the value of user_dynatrace_cluster version, user_API_token, and user_API_URL

python3 upload_dashboards.py --cluster-version --dynatrace-api-token --dynatrace-env-url user_API_URL

Below given is an example command to denote the command procedure.

python3 upload_dashboards.py --cluster-version user_dynatrace_cluster_version --dynatrace-api-token user_API_token --dynatrace-env-url_user_API_URL.

Uninstall the metrics stream client

If the user deployed the Metric Streams client with a CloudFormation template then:

1. Firstly, go to the CloudFormation in the AWS console
2. After that, select the created stack from CloudFormation deployment
3. Then, the user has to find the resource with the type, AWS::S3::Bucket
4. After that, select its link, in the s3 console eliminate all bucket objects

Note that, if AWS is used to deploy metric streams. Then deleting all of the created resources will uninstall the metric client.

[Need assistance with similar queries? We are here to help]

Conclusion

To conclude, the Dynatrace AWS CloudWatch integration is the safest and the most efficient way to ingest AWS metrics. And, CloudFormation allows the users to deploy Metric Stream Clients using a single deployment command.