🚀 Enhancements

what

• Added missing keys to var.datadog_monitors

  • Added new_group_delay as number
  • Added groupby_simple_monitor as bool
  • Added renotify_occurrences as number
  • Added renotify_statuses as set(string)
  • Added validate as bool

• Removal of new_host_delay in favor of new_group_delay but new_group_delay has to be set to 0 since none of the alerts in our catalogs are multi-monitor. See https://github.com/DataDog/terraform-provider-datadog/issues/1221#issuecomment-931006926. Apparently new_host_delay has zero effect for non multi monitor alerts.

  Error: error validating monitor from https://api.datadoghq.com/api/v1/monitor/validate: 400 Bad Request: {"errors": ["The new_group_delay option can only be used for multi-alert monitors"]}
  

why

• The lookups for the previously added keys will always return null unless the input var supports those same keys
• new_host_delay was not deprecated due to confusion in the docs. Safer to keep this as-is until we have more information.

references

• Previous PR https://github.com/cloudposse/terraform-datadog-platform/pull/51
• Clarify confusion between new_host_delay and new_group_delay
  • https://github.com/DataDog/terraform-provider-datadog/issues/1292
  • Multi alert examples https://docs.datadoghq.com/monitors/create/types/composite/#common-reporting-sources
• cc: @bateller

what

• Monitor inputs
  • Added new_group_delay (deprecated new_host_delay)
  • Added groupby_simple_monitor
  • Added renotify_occurrences
  • Added renotify_statuses
  • Added validate
• Bumped aws provider to 3.x
• Removed unused local provider

why

• Added additional monitor inputs

references

• Closes https://github.com/cloudposse/terraform-datadog-platform/issues/43
• https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/monitor

🚀 Enhancements

what

• Do not provision dd org settings
• default saml_enabled to false

why

• Prevent dd org settings from updating root org instead of updating child org
• Prevent datadog org creation from failing

references

N/A

what

• Adds Priority Level as an input to DD Monitor

why

• Allows monitors to have priority level

references

• https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/monitor

what

• Initial Take at Metric and Monitor Based SLO - via definition as yaml

why

• Datadog SLOs!

references

• https://docs.datadoghq.com/monitors/service_level_objectives/
• https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/service_level_objective

what

• Add child_organization module
• Add child_organization example and terratest

why

• Provision and manage multiple Datadog child-organizations from one parent-organization account
• Users can be added to the parent-organization and/or multiple child-organizations and switch between them from the user account settings menu
• The parent-organization can view the usage of individual child-organizations, allowing them to track trends in usage

notes

• The Multi-organization account feature is not enabled by default. Contact Datadog support to have it enabled.
• Free and Trial organizations cannot enable SAML
• We can only create Datadog child organizations with terraform, but cannot destroy them. When trying to destroy, the following error is thrown:

    Warning: Cannot delete organization. 
  
    Remove organization by contacting support (https://docs.datadoghq.com/help).
  

references

• https://docs.datadoghq.com/account_management/multi_organization
• https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/child_organization
• https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/organization_settings

what

• Update synthetic tests
• Add new Datadog monitors
• Fix k8s monitors

why

• Implement all features and attributes described in https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/synthetics_test
• New Datadog monitors to monitor RabbitMQ

related

• Closes #42

what

• Add catalog of Datadog roles
• Split into submodules
• Add roles and permissions submodules
• In the example, show how to create Datadog roles, assign permissions to the roles, and assign roles to monitors

why

• Catalog of Datadog roles in YAML to easily define and use Datadog roles
• Allow assigning roles with permissions to each Datadog monitor to restrict access
• Split into submodules to manage different Datadog resources (other resources will be added in the future)

references

• https://docs.datadoghq.com/account_management/rbac/?tab=datadogapplication
• https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/role
• https://registry.terraform.io/providers/DataDog/datadog/latest/docs/data-sources/permissions
• https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/monitor
• https://docs.datadoghq.com/account_management/rbac/permissions/
• https://docs.datadoghq.com/api/latest/monitors/
• https://github.com/hashicorp/cdktf-provider-datadog/blob/main/API.md

notes

• Creating and modifying custom roles is an opt-in Enterprise feature. Contact Datadog support to get it enabled for your account

🤖 Automatic Updates

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.

what

• Uses module.this.tags if datadog_monitor.tags is missing

why

• This will add all the context name, namespace, environment as tags to each synthetic and monitor if datadog_monitor.tags is not specified.

references

N/A

what

• Add k8s-daemonset-pod-down monitor in k8s catalog

why

• A monitor for DaemonSet pods being down is necessary. Usually, DaemonSets are for low-level system components, and a DaemonSet being down should definitely be visible.

references

• N./A

what

• Adds baseline redshift monitors

why

• Establish an out of box baseline set of monitors that can be used with Datadog integration

what

• Improve Kubernetes alert context by aggregating on cluster_name or cluster_name,kube_namespace where possible
• Add variables made available by these contexts to the alert message, such that alerted platforms can make use of additional data (e.g. OpsGenie)

why

• Kubernetes alerts with more information i.e. which cluster, namespace are more actionable

references

• N/A

what

• Remove deprecated Datadog Provider resources and upgrade to Datadog Terraform Provider 3.0.0
• Update README to reflect use Terraform registry as a module source, datadog_synthetics variable

why

• Datadog Terraform Provider 3.0.0 deprecated certain resources rendering this module unusable.

references

• Co-authored with changes from #30

what

• Adding baseline Amazon MQ Datadog standard monitors

why

• Establish an out of box baseline set of monitors that can be used with Datadog Amazon MQ integration

what

• Adding baseline RDS Datadog standard monitors for cpuutilization, database-connections, disk-queue-depth, freeable-memory, swap-usage

why

• Establish an out of box baseline set of monitors that can be used with Datadog standard integration

what

• Adding outputs for a list of the monitor IDs as a well as a list of the actual monitor objects.

why

• There are cases where you might want to have the IDs instead of the names or the objects in their entirety so you can reference their name and id. I have one such case where I want to know both the name and ID for creating an SLO from the monitor.

what

• Adds support for creating DataDog Synthetic Tests

why

• Synthetic Tests are very similar to monitors and they end up creating a monitor under the hood, so it's useful to create them via the same mechanism / module.

what

• Add k8s monitors (KubeAPI Down, HPA etc)
• Update k8s monitors
• Add host monitors

why

• Observability
• Fix monitors reporting NoData

what

• Add catalog of Datadog monitors

why

• The catalog is the one place to maintain our collection of Datadog monitors
• The monitors from the catalog will be used (remotely downloaded) in other modules (e.g. reference architectures)