The AWS CloudWatch Metric Streams with Kinesis Data Firehose is not supported on the Datadog for Government site.
The AWS CloudWatch Metric Streams with Kinesis Data Firehose is not supported on the Datadog US3 site.
Using Amazon CloudWatch Metric Streams and Amazon Kinesis Data Firehose, you can get CloudWatch metrics into Datadog faster with a 2-3 minute latency. This is significantly faster than Datadog’s API polling approach, which provides updated metrics every 10 minutes.
Create these AWS resources in each AWS account and region for which you want to stream metrics:
Create a Kinesis Data Firehose delivery stream that delivers metrics to Datadog, along with an S3 Backup for any failed metrics delivery.
Create a CloudWatch Metric Stream linked to your delivery stream.
Optionally specify a limited set of namespaces to stream metrics.
Once you create these resources, Datadog immediately starts receiving the streamed metrics and displays them in the Datadog application with no additional configuration needed.
Note: Per-namespace defaults and account-level settings in the AWS Integration tile only apply to the API polling approach. Manage all rules for including and excluding namespaces in the streams using the CloudWatch Metric Streams configuration in your AWS accounts.
If you already receive metrics for a given CloudWatch namespace through the API polling method, Datadog automatically detects this and stops polling metrics for that namespace since you are now streaming them. This could lead to some differences in the specific metric names collected as noted in Supported Metrics.
If you later decide you don’t want to stream a metric and delete the stream or remove namespaces from it, Datadog automatically starts collecting those metrics using API polling again, according to your configuration settings in the AWS Integration tile.
Nearly all of the CloudWatch namespaces and metrics that Datadog supports via the API polling approach are also supported via Metric Streams. There are however a couple exceptions.
The following CloudWatch metrics are not currently supported:
Metrics for percentile statistics (p90, p95, p99, etc.). CloudWatch Metric Streams does not currently support the streaming of metrics for percentile statistics.
Metrics that have a timestamp of more than two hours old. Some examples of these include S3 daily storage metrics and some billing metrics.
There is no additional charge from Datadog to stream metrics.
AWS charges based on the number of metric updates on the CloudWatch Metric Stream and the data volume sent to the Kinesis Data Firehose. There is the potential to see an increased CloudWatch cost for the subset of metrics you are streaming, so Datadog recommends prioritizing using metric streams for the AWS services, regions, and accounts where you most need the lower latency. For more information, see Amazon’s pricing documentation.
EC2 or Lambda metrics in the stream could increase the number of billable hosts and Lambda invocations (if those hosts and functions aren’t already monitored with the AWS Integration or Datadog Agent in the case of EC2).
Regions: A comma separated list of the regions you wish to set up for metrics streaming. For a full list of supported regions, see the AWS documentation.
Fill in the optional parameters:
FilterMethod: Include or Exclude list of namespaces to include for metrics streaming.
First/Second/Third Namespace: Specify the namespaces you wish to include or exclude. Note: The namespace values have to precisely match the values in the namespace column in AWS’s documentation. For example, AWS/EC2.
Check the acknowledgment box that states, “I acknowledge that AWS CloudFormation might create IAM resources with custom names.”
Click Create Stack.
Once the stack has been successfully created, wait five minutes for Datadog to recognize this. Then go to Datadog’s AWS Integration tile to verify this is working by viewing the “CloudWatch Metric Streams” tab for the specified AWS account and noting the activated regions.
If you want to set up metric streams using the AWS Console, follow these steps for each AWS region.
Create a new Kinesis Data Firehose delivery stream with the following specifications:
For source, select “Direct PUT or other sources”
Select Third-party service provider: Datadog.
Select the metrics endpoint URL corresponding to your Datadog site: Datadog metrics - US or Datadog metrics - EU
Choose whether you want to stream all CloudWatch metrics, or choose specific namespaces with “Include” or “Exclude” lists.
Select the Firehose you created in Step 1 to use for sending the metrics to Datadog.
Create a new service role to put records in Kinesis Data Firehose.
Choose OpenTelemetry 0.7 as the output format.
Name your metric stream.
Click Create metric stream.
Once you see the Metric Stream resource has been successfully created, wait five minutes for Datadog to recognize this. Then go to the Datadog AWS Integration tile to see this is working by viewing the “CloudWatch Metric Streams” tab for the specified AWS account.
Note: If you’ve already enabled polling CloudWatch APIs, the transition to streaming could cause a brief (up to five minutes) period where the specific metrics you are streaming are double-counted in Datadog. This is because of the difference in timing between when Datadog’s crawlers are running and submitting your CloudWatch metrics, and when Datadog recognizes that you have started streaming those metrics and turn off the crawlers.