DataDog Monitors

This repository is used to store all our monitors templates.

Here is the repository organization :

• cloud
  • aws
    • alb
    • apigateway
    • elasticsearch
    • elb
    • kinesis-firehose
    • rds
    • vpn
  • azure
    • apimanagement
    • app-services
    • eventhub
    • iothubs
    • redis
    • sql-database
    • storage
    • stream-analytics
• common
  • alerting-message
• databases
  • mongodb
• datadog-samples
• incubator
• middleware
  • apache
  • nginx
  • php-fpm
• system
  • generic

How to contribute ?

First, you may refresh your knowledge and look at the terminalogy

If you want to report an issue please be sure to follow this page : How to report an issue

It explains the different stages of a request, from the Backlog to the Merged.

If you want to contribute to any request, you must follow our best practices.

Important notes

• Each folder can be import as a feature on terraform, you must choose the one that you need.
• Each of these features contains the most commons monitors, but they probably not fulfill all your customer needs
• You still can create some DataDog monitors after importing a feature, it's even advisable to complete your needs
• You will find a complete README.md on each feature, explaining the feature's workaround
• The alerting-message module defines the alert channel and must be included in each configuration, you have to define it (Pager, Slack...)

The DataDog provider

Before importing some features, you must define the DataDog provider in your main.tf

provider "datadog" {
  api_key = "${var.datadog_api_key}"
  app_key = "${var.datadog_app_key}"
}

Both of the datadog_api_key and datadog_app_key are unique to the client.

Module Declaration example

A quick example to how import the monitors that you need :

module "datadog-monitors-feature" {
  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git/{monitors_feature_path}?ref={revision}"

  environment = "${var.environment}"
  message = "${module.datadog-message-alerting.alerting-message}"
}

{monitors_feature_path} could be defined as /cloud/aws/elb for example.