Skip to main content

AWS metrics from CloudWatch

Overview​

AWS Metrics from CloudWatch integration will poll all your metrics from specified AWS account every 10 minutes, with one exception so far which is S3 metrics that are avaliable on CloudWatch side daily. Tags and metric definitions are pulled every 5 minutes. As a prerequisite, you need to first prepare an AWS IAM policy and role with this CloudFormation template

For more information about this integration, click here.

How to use with Terraform​

To deploy this integration using Terraform, you can use the coralogix_integration resource provided by the Coralogix Terraform provider. Below is an example configuration:

resource "coralogix_integration" "aws-metrics-collector" {
integration_key = "aws-metrics-collector"
version = "1.0.0"

parameters = {
IntegrationName = "cx-aws-cw-metrics"
AwsRoleArn = "arn:aws:iam::012345678901:role/access-cloudwatch-metrics"
AwsRegions = [ "eu-west-1" ]
ApplicationName = "<ApplicationName>"
SubsystemName = "<SubsystemName>"
MetricNamespaces = [ "value1", "value2" ]
Statistics = [ "Maximum", "Minimum", "SampleCount", "Sum", "Average" ]
WithAggregations = false
EnrichWithTags = true
DiscoverNamespaces = false
IncludeLinkedAccounts = false
}
}

Replace the placeholder values with your actual configuration parameters. Refer to the parameter table below for required fields and their descriptions.

Revisions​

Resource tags are now attached to metrics in AWS/AutoScaling, AWS/EC2Spot, AWS/Kafka, AWS/KafkaConnect, AWS/PrivateLinkEndpoints and AWS/PrivateLinkServices. DynamoDB and Kinesis sub-resources no longer overwrite their parent's tags, and regional and global WAFV2 web ACLs sharing a name no longer share tags.

Upgrade impact: metrics in these namespaces gain new labels, so existing series end and new ones begin. If ResourceTagsFilter is set, it now applies to these namespaces. No new AWS permissions are required.

Parameters are the same as in 0.11.1.

Last updated on
Was this page helpful?