From 8d27276ebaea027f8ff03da32326abac4f3cf6d9 Mon Sep 17 00:00:00 2001 From: Kevin Pecquet Date: Wed, 5 Jul 2017 11:26:17 +0200 Subject: [PATCH] README update --- README.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/README.md b/README.md index 2905d8e..61b554e 100644 --- a/README.md +++ b/README.md @@ -15,3 +15,28 @@ The easiest way to contribute on this repository is to add monitors file inside *Each monitors have to be disabled by default, so you have to manage this condition when you create your monitors. *If you override a basic monitor with a custom one, you have to use tag filters on you query. (Example dd_cpu_high, if you want to override default cpu monitors) + +### Module Declaration example ### + +``` +module "datadog-monitors" { + source = "git:ssh://git@bitbucket.org/morea/terraform.datadog.monitors.git" + + ho_escalation_group = "${var.ho_escalation_group}" + hno_escalation_group = "${var.hno_escalation_group}" + + #default monitors templates integrations examples + linux_basics = "${var.linux_basics}" + #nginx = "disabled" + #aws_rds_mysql = "disabled" + + #custom monitors template integrations examples + #cpu_custom = "enabled" #Will match the tag dd_cpu_high (NB: it will replace the basic cpu alert) + #cpu_custom_period = "60" + #cpu_custom_warning_threshold = "90" + #cpu_custom_warning_escalation_msg = ${var.ho_escalation_group} + #cpu_custom_alert_threshold = "95" + #cpu_custom_alert_escalation_msg = ${var.hno_escalation_group} +} + +```