Overview

Deploy this integration to send your CloudWatch metrics to Logz.io.

This integration creates a Kinesis Data Firehose delivery stream that links to your CloudWatch metrics stream and then sends the metrics to your Logz.io account. It also creates a Lambda function that adds AWS namespaces to the metric stream, and a Lambda function that collects and ships the resources’ tags.

Setup

Before you begin, you’ll need:

  • An active account with Logz.io
Create a Kinesis Data Firehose delivery stream

To deploy this project, click the button that matches the region you wish to deploy your Stack to:

Region Deployment
us-east-1 Deploy to AWS
us-east-2 Deploy to AWS
us-west-1 Deploy to AWS
us-west-2 Deploy to AWS
eu-central-1 Deploy to AWS
eu-north-1 Deploy to AWS
eu-west-1 Deploy to AWS
eu-west-2 Deploy to AWS
eu-west-3 Deploy to AWS
sa-east-1 Deploy to AWS
ap-northeast-1 Deploy to AWS
ap-northeast-2 Deploy to AWS
ap-northeast-3 Deploy to AWS
ap-south-1 Deploy to AWS
ap-southeast-1 Deploy to AWS
ap-southeast-2 Deploy to AWS
ca-central-1 Deploy to AWS
Specify stack details

Specify the stack details as per the table below, check the checkboxes and select Create stack.

Parameter Description Required/Default
logzioListener The Logz.io listener URL for your region. (For more details, see the regions page. For example - https://listener.logz.io:8053 Required
logzioToken Your Logz.io metrics shipping token. Required
awsNamespaces Comma-separated list of the AWS namespaces you want to monitor. See this list of namespaces. If you want to automatically add all namespaces, use value all-namespaces. Required
logzioDestination Your Logz.io destination URL. Required
httpEndpointDestinationIntervalInSeconds The length of time, in seconds, that Kinesis Data Firehose buffers incoming data before delivering it to the destination. 60
httpEndpointDestinationSizeInMBs The size of the buffer, in MBs, that Kinesis Data Firehose uses for incoming data before delivering it to the destination. 5
Check Logz.io for your metrics

Give your data some time to get from your system to ours, then log in to your Logz.io Metrics account, and open the Logz.io Metrics tab.

The advanced configuration settings for this integration include:

Manual configuration with a Lambda function

Before you begin, you’ll need:

  • An active account with Logz.io
Create a Kinesis Data Firehose delivery stream
  1. Login to your AWS account and navigate to Amazon Kinesis > Delivery streams > Create delivery stream.

    Screen_1

  2. Choose Direct PUT as Source and HTTP Endpoint as Destination.

  3. Give the delivery stream a name.

  4. In the Destination settings section, enter the HTTP endpoint URL depending on your region.

Region URL
US-East-1 https://listener-aws-metrics-stream-us.logz.io/
EU-central-1 https://listener-aws-metrics-srteam-eu.logz.io/
  1. In the Access key section, enter your Logz.io metrics shipping token.

  2. For Content encoding, select Disabled.

  3. Set the Retry duration to 60 seconds.

  4. In the Buffer hints section, enter 5MB for buffer size, and 60 seconds for buffer interval.

  5. If required, in the Backup settings, select Failed data only and select an S3 bucket you would like to use for backup.

  6. Select Create delivery stream.

Create a CloudWatch metric stream
  1. Navigate to CloudWatch > Metric streams > Create a metric stream.

    Screen_2

  2. In the Metrics to be streamed section, select what namespaces you want to monitor (include/exclude or all namespaces).

  3. In the Configuration section, select an existing Firehose as the configuration option.

  4. In the Select your Kinesis Data section, select the Kinesis Data Firehose delivery stream created in the previous step.

  5. Select OpenTelemetry 0.7 as the output format.

  6. Give your metric stream a name.

  7. Select Create metric stream.

Check Logz.io for your metrics

Give your data some time to get from your system to ours, then log in to your Logz.io Metrics account, and open the Logz.io Metrics tab.