terraform-datadog-platform

what

• Update datadog monitors
• In the example. refactor the monitors into separate YAML files per category

why

• When monitor type = query alert, Datadog does not look into the event tags, so we can't use event.tags.cluster_name to detect the cluster and environment
• We need to aggregate the queries by all the parameters we want to use as variables in the alert messages

what

• Fixes 0.13 support
• Pins Terraform >= 0.12.26

why

• The minimum terraform was increased due to the required_providers syntax backwards compatibility.
• When running this module on 0.13, a terraform init results in the below error regardless of the fact that the correct required_providers syntax being used in the root module. I believe this is due to there never being a hashicorp/datadog provider during 0.12 as the datadog provider was just recently published as a community provider. I think this causes Terraform 0.13 to try to lookup the datadog provider as if it was previously published via hashicorp/, which blows up like below.

Error: Failed to install providers

Could not find required providers, but found possible alternatives:

  hashicorp/datadog -> datadog/datadog

If these suggestions look correct, upgrade your configuration with the
following command:

The following remote modules must also be upgraded for Terraform 0.13
compatibility:
- module.datadog_integration at
git::https://github.com/cloudposse/terraform-aws-datadog-integration.git?ref=tags/0.5.0

references

• See discussion in Slack: https://sweetops.slack.com/archives/CCT1E7JJY/p1603214212249300
• See the same fix / changes in terraform-aws-datadog-integration#15.

what

• Add Kubernetes monitors recommended by Datadog

why

• Some monitors recommended by Datadog were missing

references

• https://www.datadoghq.com/blog/datadog-recommended-monitors/

what

• Use YAM config for Datadog monitors
• Update to TF 0.12/0.13
• Update to context.tf
• Add example and tests

why

• Simplify configuration of Datadog monitors
• Standardization
• Keep the module up to date

related

• Closes #11

test

TestExamplesComplete 2020-09-30T20:59:49Z logger.go:66: Outputs:
TestExamplesComplete 2020-09-30T20:59:49Z logger.go:66: 
TestExamplesComplete 2020-09-30T20:59:49Z logger.go:66: datadog_monitor_names = [
TestExamplesComplete 2020-09-30T20:59:49Z logger.go:66:   "(RDS) Aurora Replica Lag Detected",
TestExamplesComplete 2020-09-30T20:59:49Z logger.go:66:   "(EC2) Failed Status Check",
TestExamplesComplete 2020-09-30T20:59:49Z logger.go:66:   "(EKS) ImagePullBackOff Error Detected",
TestExamplesComplete 2020-09-30T20:59:49Z logger.go:66:   "(EKS) High CPU Usage Detected",
TestExamplesComplete 2020-09-30T20:59:49Z logger.go:66:   "(EKS) High Disk Usage Detected",
TestExamplesComplete 2020-09-30T20:59:49Z logger.go:66:   "(EKS) High Filesystem Usage Detected",
TestExamplesComplete 2020-09-30T20:59:49Z logger.go:66:   "(EKS) High Memory Usage Detected",
TestExamplesComplete 2020-09-30T20:59:49Z logger.go:66:   "(EKS) High Network RX (receive) Errors",
TestExamplesComplete 2020-09-30T20:59:49Z logger.go:66:   "(EKS) High Network TX (send) Errors",
TestExamplesComplete 2020-09-30T20:59:49Z logger.go:66:   "(EKS) Node Not Ready",
TestExamplesComplete 2020-09-30T20:59:49Z logger.go:66:   "(EKS) Detected Unschedulable Node(s)",
TestExamplesComplete 2020-09-30T20:59:49Z logger.go:66:   "(EKS) Unavailable Replica(s) Detected",
TestExamplesComplete 2020-09-30T20:59:49Z logger.go:66: ]

what

• Add chatops.yml

why

• To run tests via GitHub comments

what

• Add GitHub actions

why

• To test and lint the module and example

what

• updated README.yaml file
• add tags and categories
• rebuild README.md file

why

• need to add categories and tags so we can pull them into the documentation

what

• Regenerate README.md

why

• Previous version of build-harness has some typos

what

• Add README.yaml

why

• Standardize README

Add CPU Usage, Memory Usage, and Swap Space modules

Datadog Monitors for Load Average