MON-259 regenerate all readme with new script

2018-07-17 15:37:57 +02:00 · 2018-07-17 15:37:57 +02:00 · cf688d9698
commit cf688d9698
parent eea3477acb
21 changed files with 346 additions and 430 deletions
--- a/cloud/aws/alb/README.md
+++ b/cloud/aws/alb/README.md
@ -1,11 +1,9 @@
-AWS ALB DataDog monitors
-==========================================
+# CLOUD AWS ALB DataDog monitors

-How to use this module
----------------------
+## How to use this module

 ```
-module "datadog-monitors-aws-alb" {
+module "datadog-monitors-cloud-aws-alb" {
  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//cloud/aws/alb?ref={revision}"

  environment = "${var.environment}"
@ -14,19 +12,18 @@ module "datadog-monitors-aws-alb" {

 ```

-Purpose
-------
+## Purpose
+
 Creates DataDog monitors with the following checks :

-* ALB no healthy hosts
-* ALB latency too high
-* ALB http code 5xx percent to high
-* ALB http code 4xx percent to high
-* ALB target http code 5xx percent to high
-* ALB target http code 4xx percent to high
+- ALB no healthy instances
+- ALB latency
+- ALB HTTP code 5xx
+- ALB HTTP code 4xx
+- ALB target HTTP code 5xx
+- ALB target HTTP code 4xx

-Inputs
------
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -67,8 +64,7 @@ Inputs
 | latency_timeframe | Monitor timeframe for ALB latency [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_5m` | no |
 | message | Message sent when a monitor is triggered | string | - | yes |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
@ -79,8 +75,7 @@ Outputs
 | ALB_latency_id | id for monitor ALB_latency |
 | ALB_no_healthy_instances_id | id for monitor ALB_no_healthy_instances |

-Related documentation
---------------------
+## Related documentation

 DataDog blog: [https://www.datadoghq.com/blog/monitor-application-load-balancer/](https://www.datadoghq.com/blog/monitor-application-load-balancer/)

--- a/cloud/aws/apigateway/README.md
+++ b/cloud/aws/apigateway/README.md
@ -1,11 +1,9 @@
-AWS API Gateway DataDog monitors
-==========================================
+# CLOUD AWS APIGATEWAY DataDog monitors

-How to use this module
----------------------
+## How to use this module

 ```
-module "datadog-monitors-aws-api-gateway" {
+module "datadog-monitors-cloud-aws-apigateway" {
  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//cloud/aws/apigateway?ref={revision}"

  environment = "${var.environment}"
@ -14,16 +12,15 @@ module "datadog-monitors-aws-api-gateway" {

 ```

-Purpose
-------
+## Purpose
+
 Creates DataDog monitors with the following checks :

-* API Gateway too much 5xx errors
-* API Gateway too much 4xx errors
-* API Gateway latency to high
+- API Gateway latency
+- API Gateway HTTP 5xx errors
+- API Gateway HTTP 4xx errors

-Inputs
------
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -49,8 +46,7 @@ Inputs
 | latency_timeframe | Monitor timeframe for API latency [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_5m` | no |
 | message | Message sent when a monitor is triggered | string | - | yes |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
@ -58,8 +54,7 @@ Outputs
 | API_http_4xx_errors_count_id | id for monitor API_http_4xx_errors_count |
 | API_http_5xx_errors_count_id | id for monitor API_http_5xx_errors_count |

-Related documentation
---------------------
+## Related documentation

 DataDog documentation: [https://docs.datadoghq.com/integrations/amazon_api_gateway/](https://docs.datadoghq.com/integrations/amazon_api_gateway/)

--- a/cloud/aws/elasticsearch/README.md
+++ b/cloud/aws/elasticsearch/README.md
@ -1,31 +1,26 @@
-AWS ElasticSearch Service DataDog monitors
-==========================================
+# CLOUD AWS ELASTICSEARCH DataDog monitors

-How to use this module
----------------------
+## How to use this module

 ```
-module "datadog-monitors-aws-elasticsearch" {
+module "datadog-monitors-cloud-aws-elasticsearch" {
  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//cloud/aws/elasticsearch?ref={revision}"

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

 ```

-Purpose
-------
+## Purpose
+
 Creates DataDog monitors with the following checks :

-* Cluster status not green
-* Free disk space low
-* CPU High
+- ElasticSearch cluster status is not green
+- ElasticSearch cluster free storage space
+- ElasticSearch cluster CPU high

-Inputs
------
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -51,8 +46,7 @@ Inputs
 | filter_tags_use_defaults | Use default filter tags convention | string | `true` | no |
 | message | Message sent when an alert is triggered | string | - | yes |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
@ -60,8 +54,7 @@ Outputs
 | es_cpu_90_15min_id | id for monitor es_cpu_90_15min |
 | es_free_space_low_id | id for monitor es_free_space_low |

-Related documentation
---------------------
+## Related documentation

 DataDog documentation: [https://docs.datadoghq.com/integrations/amazon_es/](https://docs.datadoghq.com/integrations/amazon_es/)

--- a/cloud/aws/elb/README.md
+++ b/cloud/aws/elb/README.md
@ -1,11 +1,9 @@
-AWS ELB DataDog monitors
-========================
+# CLOUD AWS ELB DataDog monitors

-How to use this module
----------------------
+## How to use this module

 ```
-module "datadog-monitors-aws-elb" {
+module "datadog-monitors-cloud-aws-elb" {
  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//cloud/aws/elb?ref={revision}"

  environment = "${var.environment}"
@ -14,19 +12,18 @@ module "datadog-monitors-aws-elb" {

 ```

-Purpose
-------
+## Purpose
+
 Creates DataDog monitors with the following checks :

-* ELB no healthy hosts
-* ELB latency too high
-* ELB http code 4xx percent to high
-* ELB http code 5xx percent to high
-* ELB backend http code 4xx percent to high
-* ELB backend http code 5xx percent to high
+- ELB no healthy instances
+- ELB 4xx errors too high
+- ELB 5xx errors too high
+- ELB backend 4xx errors too high
+- ELB backend 5xx errors too high
+- ELB latency too high

-Inputs
------
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -67,8 +64,7 @@ Inputs
 | filter_tags_use_defaults | Use default filter tags convention | string | `true` | no |
 | message | Message sent when an alert is triggered | string | - | yes |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
@ -79,7 +75,8 @@ Outputs
 | ELB_too_much_5xx_backend_id | id for monitor ELB_too_much_5xx_backend |
 | ELB_too_much_5xx_id | id for monitor ELB_too_much_5xx |

-Related documentation
---------------------
+## Related documentation

-DataDog documentation:
+DataDog blog: [https://www.datadoghq.com/blog/monitor-application-load-balancer/](https://www.datadoghq.com/blog/monitor-application-load-balancer/)
+
+AWS ELB metrics documentation: [https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-cloudwatch-metrics.html](https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-cloudwatch-metrics.html)
--- a/cloud/aws/kinesis-firehose/README.md
+++ b/cloud/aws/kinesis-firehose/README.md
@ -1,27 +1,24 @@
-AWS Kinesis Firehose DataDog monitors
-==========================================
+# CLOUD AWS KINESIS-FIREHOSE DataDog monitors

-How to use this module
----------------------
+## How to use this module

 ```
-module "datadog-monitors-aws-firehose" {
+module "datadog-monitors-cloud-aws-kinesis-firehose" {
  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//cloud/aws/kinesis-firehose?ref={revision}"

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

 ```

-Purpose
-------
+## Purpose
+
 Creates DataDog monitors with the following checks :

-* No incoming record
+- Kinesis Firehose No incoming records

-Inputs
------
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -34,15 +31,13 @@ Inputs
 | incoming_records_timeframe | Monitor timeframe for incoming records metrics evaluation [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_15m` | no |
 | message | Message sent when an alert is triggered | string | - | yes |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
 | firehose_incoming_records_id | id for monitor firehose_incoming_records |

-Related documentation
---------------------
+## Related documentation

 DataDog documentation: [https://docs.datadoghq.com/integrations/amazon_firehose/](https://docs.datadoghq.com/integrations/amazon_firehose/)

--- a/cloud/aws/rds/README.md
+++ b/cloud/aws/rds/README.md
@ -1,27 +1,25 @@
-AWS RDS Instance DataDog monitors
-=================================
+# CLOUD AWS RDS DataDog monitors

-How to use this module
----------------------
+## How to use this module

 ```
-module "datadog-monitors-aws-rds" {
+module "datadog-monitors-cloud-aws-rds" {
  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//cloud/aws/rds?ref={revision}"

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

-Purpose
-------
-Creates a DataDog monitors with the following checks :
+## Purpose

-* CPU High
-* Free disk space low
+Creates DataDog monitors with the following checks :

-Inputs
------
+- RDS instance CPU high
+- RDS instance free space
+
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -43,16 +41,14 @@ Inputs
 | filter_tags_use_defaults | Use default filter tags convention | string | `true` | no |
 | message | Message sent when an alert is triggered | string | - | yes |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
 | rds_cpu_90_15min_id | id for monitor rds_cpu_90_15min |
 | rds_free_space_low_id | id for monitor rds_free_space_low |

-Related documentation
---------------------
+## Related documentation

 DataDog documentation: [https://docs.datadoghq.com/integrations/amazon_rds/](https://docs.datadoghq.com/integrations/amazon_rds/)

--- a/cloud/aws/vpn/README.md
+++ b/cloud/aws/vpn/README.md
@ -1,26 +1,24 @@
-AWS VPN DataDog monitors
-===============================
+# CLOUD AWS VPN DataDog monitors

-How to use this module
----------------------
+## How to use this module

 ```
-module "vpn" {
-  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//cloud/aws/vpn?ref=MON-91-added-aws-vpn-state-check"
+module "datadog-monitors-cloud-aws-vpn" {
+  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//cloud/aws/vpn?ref={revision}"

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

-Purpose
-------
-Creates a DataDog monitors with the following checks :
+## Purpose

-* VPN status
+Creates DataDog monitors with the following checks :

-Inputs
------
+- VPN Down
+
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -34,17 +32,14 @@ Inputs
 | vpn_status_time_aggregator | Monitor aggregator for VPN status [available values: min, max or avg] | string | `max` | no |
 | vpn_status_timeframe | Monitor timeframe for VPN status [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_5m` | no |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
 | VPN_status_id | id for monitor VPN_status |

-Related documentation
---------------------
+## Related documentation

 DataDog documentation: [https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/vpn-metricscollected.html](https://docs.datadoghq.com/integrations/amazon_web_services/)

 AWS VPN metrics documentation: [https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/vpn-metricscollected.html](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/vpn-metricscollected.html)
-
--- a/cloud/azure/apimanagement/README.md
+++ b/cloud/azure/apimanagement/README.md
@ -1,29 +1,28 @@
-Azure API Management Datadog monitors
-=====================================
+# CLOUD AZURE APIMANAGEMENT DataDog monitors
+
+## How to use this module

-How to use this module
----------------------
 ```
-module "datadog-monitors-azure-apimanagement" {
+module "datadog-monitors-cloud-azure-apimanagement" {
  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//cloud/azure/apimanagement?ref={revision}"

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

-Purpose
-------
-Creates Datadog monitors with the following checks :
+## Purpose

-* Service status
-* Failed requests ratio
-* Other requests ratio
-* Unauthorized requests ratio
-* Successful requests ratio
+Creates DataDog monitors with the following checks :

-Inputs
------
+- API Management is down
+- API Management too many failed requests
+- API Management too many other requests
+- API Management too many unauthorized requests
+- API Management successful requests rate too low
+
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -57,8 +56,7 @@ Inputs
 | unauthorized_requests_threshold_warning | Warning regarding acceptable percent of unauthorized requests | string | `50` | no |
 | unauthorized_requests_timeframe | Monitor timeframe for API Management unauthorized requests [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_5m` | no |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
@ -68,7 +66,6 @@ Outputs
 | apimgt_successful_requests_id | id for monitor apimgt_successful_requests |
 | apimgt_unauthorized_requests_id | id for monitor apimgt_unauthorized_requests |

-Related documentation
---------------------
+## Related documentation

 Azure API Management metrics documentation: [https://docs.microsoft.com/en-us/azure/api-management/api-management-howto-use-azure-monitor](https://docs.microsoft.com/en-us/azure/api-management/api-management-howto-use-azure-monitor)
--- a/cloud/azure/app-services/README.md
+++ b/cloud/azure/app-services/README.md
@ -1,30 +1,28 @@
-Azure AppServices (Web, API, Functions) DataDog monitors
-========================================================
+# CLOUD AZURE APP-SERVICES DataDog monitors

-How to use this module
----------------------
+## How to use this module

 ```
-module "datadog-monitors-azure-app-services" {
+module "datadog-monitors-cloud-azure-app-services" {
  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//cloud/azure/app-services?ref={revision}"

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

-Purpose
-------
-Creates a DataDog monitors with the following checks :
+## Purpose

-* Response time
-* Memory usage count
-* HTTP 5xx requests
-* HTTP 4xx requests
-* HTTP 2xx requests
+Creates DataDog monitors with the following checks :

-Inputs
------
+- App Services response time too high
+- App Services memory usage
+- App Services HTTP 5xx errors too high
+- App Services HTTP 4xx errors too high
+- App Services HTTP successful responses too low
+
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -61,8 +59,7 @@ Inputs
 | response_time_time_aggregator | Monitor aggregator for App Services response time [available values: min, max or avg] | string | `min` | no |
 | response_time_timeframe | Monitor timeframe for App Services response time [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_5m` | no |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
@ -72,7 +69,6 @@ Outputs
 | appservices_memory_usage_count_id | id for monitor appservices_memory_usage_count |
 | appservices_response_time_id | id for monitor appservices_response_time |

-Related documentation
---------------------
+## Related documentation

 DataDog documentation: [https://docs.datadoghq.com/integrations/azure_app_services](https://docs.datadoghq.com/integrations/azure_app_services)
--- a/cloud/azure/eventhub/README.md
+++ b/cloud/azure/eventhub/README.md
@ -1,28 +1,26 @@
-Event Hub Datadog monitor
-=========================
+# CLOUD AZURE EVENTHUB DataDog monitors

-How to use this module
----------------------
+## How to use this module

 ```
-module "datadog-monitors-azure-eventhub" {
+module "datadog-monitors-cloud-azure-eventhub" {
  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//cloud/azure/eventhub?ref={revision}"

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

-Purpose
-------
-Creates a Datadog monitor with the following checks :
+## Purpose

-* Service status check
-* Failed request ratio
-* Erroneous requests ratio
+Creates DataDog monitors with the following checks :

-Inputs
------
+- Event Hub is down
+- Event Hub too many failed requests
+- Event Hub too many errors
+
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -46,8 +44,7 @@ Inputs
 | status_time_aggregator | Monitor aggregator for Event Hub status [available values: min, max or avg] | string | `max` | no |
 | status_timeframe | Monitor timeframe for Event Hub status [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_5m` | no |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
@ -55,8 +52,7 @@ Outputs
 | eventhub_failed_requests_id | id for monitor eventhub_failed_requests |
 | eventhub_status_id | id for monitor eventhub_status |

-Related documentation
---------------------
+## Related documentation

 Datadog documentation : [https://docs.datadoghq.com/integrations/azure_event_hub/](https://docs.datadoghq.com/integrations/azure_event_hub/)

--- a/cloud/azure/iothubs/README.md
+++ b/cloud/azure/iothubs/README.md
@ -1,40 +1,37 @@
-Azure IOT Hubs DataDog monitors
-===============================
+# CLOUD AZURE IOTHUBS DataDog monitors

-How to use this module
----------------------
+## How to use this module

 ```
-module "iothubs" {
-  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//cloud/azure/iothubs?ref=MON-80-azure-hub-iot-monitors"
+module "datadog-monitors-cloud-azure-iothubs" {
+  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//cloud/azure/iothubs?ref={revision}"

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

-Purpose
-------
-Creates a DataDog monitors with the following checks :
+## Purpose

-* Service status check
-* Jobs failed average check
-* Query Jobs failed average check
-* List Jobs failed average check
-* Total devices count check
-* C2D methods failed average check
-* C2D twin read failed average check
-* C2D twin update failed average check
-* D2C twin read failed average check
-* D2C twin update failed average check
-* D2C telemetry egress dropped count check
-* D2C telemetry egress orphaned count check
-* D2C telemetry egress invalid count check
-* D2C telemetry egress fallback count check
-* D2C telemetry ingress no sent count check
+Creates DataDog monitors with the following checks :

-Inputs
------
+- IOT Hub Too many jobs failed
+- IOT Hub Too many list_jobs failure
+- IOT Hub Too many query_jobs failed
+- IOT Hub is down
+- IOT Hub Total devices is wrong
+- IOT Hub Too many c2d methods failure
+- IOT Hub Too many c2d twin read failure
+- IOT Hub Too many c2d twin update failure
+- IOT Hub Too many d2c twin read failure
+- IOT Hub Too many d2c twin update failure
+- IOT Hub Too many d2c telemetry egress dropped
+- IOT Hub Too many d2c telemetry egress orphaned
+- IOT Hub Too many d2c telemetry egress invalid
+- IOT Hub Too many d2c telemetry ingress not sent
+
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -109,8 +106,7 @@ Inputs
 | total_devices_time_aggregator | Monitor aggregator for IoT Hub total devices [available values: min, max, sum or avg] | string | `min` | no |
 | total_devices_timeframe | Monitor timeframe for IoT Hub total devices [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_5m` | no |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
@ -129,8 +125,7 @@ Outputs
 | too_many_query_jobs_failed_id | id for monitor too_many_query_jobs_failed |
 | total_devices_id | id for monitor total_devices |

-Related documentation
---------------------
+## Related documentation

 DataDog documentation: [https://docs.datadoghq.com/integrations/azure_iot_hub](https://docs.datadoghq.com/integrations/azure_iot_hub)

--- a/cloud/azure/redis/README.md
+++ b/cloud/azure/redis/README.md
@ -1,29 +1,27 @@
-Azure Redis DataDog monitors
-============================
+# CLOUD AZURE REDIS DataDog monitors

-How to use this module
----------------------
+## How to use this module

 ```
-module "datadog-monitors-azure-redis" {
+module "datadog-monitors-cloud-azure-redis" {
  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//cloud/azure/redis?ref={revision}"

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

-Purpose
-------
-Creates a DataDog monitors with the following checks :
+## Purpose

-* Service status check
-* Evicted keys count check
-* Processor time (percent) threshold
-* Server CPU load threshold
+Creates DataDog monitors with the following checks :

-Inputs
------
+- Redis {{name}} is down
+- Redis too many evictedkeys
+- Redis processor time too high
+- Redis server load too high
+
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -55,8 +53,7 @@ Inputs
 | status_time_aggregator | Monitor aggregator for Redis status [available values: min, max or avg] | string | `max` | no |
 | status_timeframe | Monitor timeframe for Redis status [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_5m` | no |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
@ -65,8 +62,7 @@ Outputs
 | server_load_id | id for monitor server_load |
 | status_id | id for monitor status |

-Related documentation
---------------------
+## Related documentation

 DataDog documentation: [https://docs.datadoghq.com/integrations/azure_redis_cache/](https://docs.datadoghq.com/integrations/azure_redis_cache/)

--- a/cloud/azure/servicebus/README.md
+++ b/cloud/azure/servicebus/README.md
@ -1,26 +1,24 @@
-Service Bus Datadog monitor
-===========================
+# CLOUD AZURE SERVICEBUS DataDog monitors

-How to use this module
----------------------
+## How to use this module

 ```
-module "datadog-monitors-azure-servicebus" {
+module "datadog-monitors-cloud-azure-servicebus" {
  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//cloud/azure/servicebus?ref={revision}"

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

-Purpose
-------
-Creates a Datadog monitor with the following checks :
+## Purpose

-* Service status check
+Creates DataDog monitors with the following checks :

-Inputs
------
+- Service Bus is down
+
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -34,15 +32,13 @@ Inputs
 | status_time_aggregator | Monitor aggregator for Service Bus status [available values: min, max or avg] | string | `max` | no |
 | status_timeframe | Monitor timeframe for Service Bus status [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_15m` | no |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
 | servicebus_status_id | id for monitor servicebus_status |

-Related documentation
---------------------
+## Related documentation

 DataDog documentation : [https://docs.datadoghq.com/integrations/azure/](https://docs.datadoghq.com/integrations/azure/)  
 You must search `servicebus`, there is no integration for now.
--- a/cloud/azure/sql-database/README.md
+++ b/cloud/azure/sql-database/README.md
@ -1,29 +1,27 @@
-Azure SQL Database DataDog monitors
-===================================
+# CLOUD AZURE SQL-DATABASE DataDog monitors

-How to use this module
----------------------
+## How to use this module

 ```
-module "datadog-monitors-azure-storage" {
+module "datadog-monitors-cloud-azure-sql-database" {
  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//cloud/azure/sql-database?ref={revision}"

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

-Purpose
-------
-Creates a DataDog monitors with the following checks :
+## Purpose

-* CPU High
-* Free disk space low
-* DTU Consumption high
-* SQL deadlocks
+Creates DataDog monitors with the following checks :

-Inputs
------
+- SQL Database CPU too high
+- SQL Database low free space
+- SQL Database DTU Consumption too high
+- SQL Database Deadlocks too high
+
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -55,8 +53,7 @@ Inputs
 | filter_tags_use_defaults | Use default filter tags convention | string | `true` | no |
 | message | Message sent when an alert is triggered | string | - | yes |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
@ -65,8 +62,7 @@ Outputs
 | sql-database_dtu_consumption_high_id | id for monitor sql-database_dtu_consumption_high |
 | sql-database_free_space_low_id | id for monitor sql-database_free_space_low |

-Related documentation
---------------------
+## Related documentation

 DataDog documentation: [https://docs.datadoghq.com/integrations/azure_sql_database/](https://docs.datadoghq.com/integrations/azure_sql_database/)

--- a/cloud/azure/storage/README.md
+++ b/cloud/azure/storage/README.md
@ -1,34 +1,32 @@
-Azure Storage DataDog monitors
-==============================
+# CLOUD AZURE STORAGE DataDog monitors

-How to use this module
----------------------
+## How to use this module

 ```
-module "datadog-monitors-azure-storage" {
+module "datadog-monitors-cloud-azure-storage" {
  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//cloud/azure/storage?ref={revision}"

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

-Purpose
-------
-Creates a DataDog monitors with the following checks :
+## Purpose

-* Service availability
-* End to end latency
-* Minimum successful requests
-* Maximum timeout error requests
-* Maximum network error requests
-* Maximum throttling error requests
-* Maximum server other error requests
-* Maximum client other error requests
-* Maximum authorization error requests
+Creates DataDog monitors with the following checks :

-Inputs
------
+- Azure Storage is down
+- Azure Storage too few successful requests
+- Azure Storage too high end to end latency
+- Azure Storage too many timeout errors
+- Azure Storage too many network errors
+- Azure Storage too many throttling errors
+- Azure Storage too many server_other errors
+- Azure Storage too many client_other errors
+- Azure Storage too many authorization errors
+
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -92,8 +90,7 @@ Inputs
 | timeout_error_requests_time_aggregator | Monitor aggregator for Storage timeout [available values: min, max or avg] | string | `min` | no |
 | timeout_error_requests_timeframe | Monitor timeframe for Storage timeout [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_5m` | no |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
@ -107,8 +104,7 @@ Outputs
 | throttling_error_requests_id | id for monitor throttling_error_requests |
 | timeout_error_requests_id | id for monitor timeout_error_requests |

-Related documentation
---------------------
+## Related documentation

 DataDog documentation: [https://docs.datadoghq.com/integrations/azure_storage/](https://docs.datadoghq.com/integrations/azure_storage/)

--- a/cloud/azure/stream-analytics/README.md
+++ b/cloud/azure/stream-analytics/README.md
@ -1,20 +1,28 @@
-Azure Stream Analytics DataDog monitors
-=======================================
+# CLOUD AZURE STREAM-ANALYTICS DataDog monitors

-How to use this module
----------------------
+## How to use this module

 ```
-module "datadog-monitors-azure-redis" {
+module "datadog-monitors-cloud-azure-stream-analytics" {
  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//cloud/azure/stream-analytics?ref={revision}"

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

-Inputs
------
+## Purpose
+
+Creates DataDog monitors with the following checks :
+
+- Stream Analytics is down
+- Stream Analytics streaming units utilization too high
+- Stream Analytics too many failed requests
+- Stream Analytics too many conversion errors
+- Stream Analytics too many runtime errors
+
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -51,8 +59,7 @@ Inputs
 | su_utilization_time_aggregator | Monitor aggregator for Stream Analytics utilization [available values: min, max or avg] | string | `min` | no |
 | su_utilization_timeframe | Monitor timeframe for Stream Analytics utilization [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_5m` | no |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
@ -62,7 +69,6 @@ Outputs
 | status_id | id for monitor status |
 | su_utilization_id | id for monitor su_utilization |

-Related documentation
---------------------
+## Related documentation

 DataDog documentation: [https://docs.datadoghq.com/integrations/azure/](https://docs.datadoghq.com/integrations/azure/)
--- a/databases/mongodb/README.md
+++ b/databases/mongodb/README.md
@ -1,12 +1,50 @@
-AWS MongoDB Service DataDog monitors
-==========================================
+# DATABASES MONGODB DataDog monitors

-Link to integration documentation :
+## How to use this module

-[https://docs.datadoghq.com/integrations/mongo/](https://docs.datadoghq.com/integrations/mongo/)
+```
+module "datadog-monitors-databases-mongodb" {
+  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//databases/mongodb?ref={revision}"

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

-**Prepare your ReplicaSet** :
+```
+
+## Purpose
+
+Creates DataDog monitors with the following checks :
+
+- Member down in the replica set
+
+## Inputs
+
+| Name | Description | Type | Default | Required |
+|------|-------------|:----:|:-----:|:-----:|
+| delay | Delay in seconds for the metric evaluation | string | `15` | no |
+| environment | Architecture Environment | string | - | yes |
+| filter_tags_custom | Tags used for custom filtering when filter_tags_use_defaults is false | string | `*` | no |
+| filter_tags_use_defaults | Use default filter tags convention | string | `true` | no |
+| message | Message sent when an alert is triggered | string | - | yes |
+| mongodb_replicaset_message | Custom message for Mongodb replicaset monitor | string | `` | no |
+| mongodb_replicaset_silenced | Groups to mute for Mongodb replicaset monitor | map | `<map>` | no |
+| mongodb_replicaset_time_aggregator | Monitor aggregator for Mongodb replicaset [available values: min, max or avg] | string | `max` | no |
+| mongodb_replicaset_timeframe | Monitor timeframe for Mongodb replicaset [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_5m` | no |
+
+## Outputs
+
+| Name | Description |
+|------|-------------|
+| mongodb_replicaset_state_id | id for monitor mongodb_replicaset_state |
+
+## Related documentation
+
+DataDog documentation: [https://docs.datadoghq.com/integrations/mongo/](https://docs.datadoghq.com/integrations/mongo/)
+
+## Custom settings
+
+### Prepare your ReplicaSet

 Add a user to your ReplicaSet (on the primary instance)

@ -17,7 +55,7 @@ db.auth("admin", "admin-password") ## This is optional is you don't have any adm
 db.createUser({"user":"datadog", "pwd": "{{PASSWORD}}", "roles" : [ {role: 'read', db: 'admin' }, {role: 'clusterMonitor', db: 'admin'}, {role: 'read', db: 'local' }]})
 ```

-**Configure your Datadog agent**
+### Configure your Datadog agent

 Add this file conf.d/mongo.yaml

@ -36,7 +74,7 @@ instances:
              - mytag2
 ```

-**Monitor ReplicaSet Health**
+### Monitor ReplicaSet Health

 Name: [environment] Replica Set heath for {{ replset_name }}

@ -49,49 +87,3 @@ Metrics are :

 This monitor will trigger an alert for each ReplicaSet.

-
-How to use this module
----------------------
-
-```
-module "datadog-monitors-aws-mongodb" {
-  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//databases/mongodb?ref={revision}"
-
-  message     = "${module.datadog-message-alerting.alerting-message}"
-  environment = "${var.environment}"
-
-}
-```
-
-Purpose
-------
-
-Creates a DataDog monitors with the following checks : 
-* Mongodb ReplicaSet status
-
-Inputs
------
-
-| Name | Description | Type | Default | Required |
-|------|-------------|:----:|:-----:|:-----:|
-| delay | Delay in seconds for the metric evaluation | string | `15` | no |
-| environment | Architecture Environment | string | - | yes |
-| filter_tags_custom | Tags used for custom filtering when filter_tags_use_defaults is false | string | `*` | no |
-| filter_tags_use_defaults | Use default filter tags convention | string | `true` | no |
-| message | Message sent when an alert is triggered | string | - | yes |
-| mongodb_replicaset_message | Custom message for Mongodb replicaset monitor | string | `` | no |
-| mongodb_replicaset_silenced | Groups to mute for Mongodb replicaset monitor | map | `<map>` | no |
-| mongodb_replicaset_time_aggregator | Monitor aggregator for Mongodb replicaset [available values: min, max or avg] | string | `max` | no |
-| mongodb_replicaset_timeframe | Monitor timeframe for Mongodb replicaset [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_5m` | no |
-
-Outputs
-------
-
-| Name | Description |
-|------|-------------|
-| mongodb_replicaset_state_id | id for monitor mongodb_replicaset_state |
-
-Related documentation
---------------------
-
-DataDog documentation:
--- a/middleware/apache/README.md
+++ b/middleware/apache/README.md
@ -1,26 +1,24 @@
-Apache Middleware DataDog monitors
-==================================
+# MIDDLEWARE APACHE DataDog monitors

-How to use this module
----------------------
+## How to use this module

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

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

-Purpose
-------
-Creates a DataDog monitors with the following checks :
+## Purpose

-* Apache connect
+Creates DataDog monitors with the following checks :

-Inputs
------
+- Can't connect to apache vhost status
+
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -32,14 +30,12 @@ Inputs
 | filter_tags_use_defaults | Use default filter tags convention | string | `true` | no |
 | message | Message sent when an alert is triggered | string | - | yes |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
 | datadog_apache_process_id | id for monitor datadog_apache_process |

-Related documentation
---------------------
+## Related documentation

-DataDog documentation:
+DataDog documentation: [https://docs.datadoghq.com/integrations/apache/](https://docs.datadoghq.com/integrations/apache/)
--- a/middleware/nginx/README.md
+++ b/middleware/nginx/README.md
@ -1,26 +1,24 @@
-Nginx Middleware DataDog monitors
-=================================
+# MIDDLEWARE NGINX DataDog monitors

-How to use this module
----------------------
+## How to use this module

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

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

-Purpose
-------
-Creates a DataDog monitors with the following checks :
+## Purpose

-* Nginx connect
+Creates DataDog monitors with the following checks :

-Inputs
------
+- Can't connect to nginx vhost status
+
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -32,14 +30,12 @@ Inputs
 | nginx_connect_message | Custom message for Nginx process monitor | string | `` | no |
 | nginx_connect_silenced | Groups to mute for Nginx process monitor | map | `<map>` | no |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
 | datadog_nginx_process_id | id for monitor datadog_nginx_process |

-Related documentation
---------------------
+## Related documentation

-DataDog documentation:
+DataDog documentation: [https://docs.datadoghq.com/integrations/nginx/](https://docs.datadoghq.com/integrations/nginx/)
--- a/middleware/php-fpm/README.md
+++ b/middleware/php-fpm/README.md
@ -1,27 +1,25 @@
-PHP FPM Middleware DataDog monitors
-===================================
+# MIDDLEWARE PHP-FPM DataDog monitors

-How to use this module
----------------------
+## How to use this module

 ```
-module "datadog-monitors-php-fpm-middleware" {
+module "datadog-monitors-middleware-php-fpm" {
  source = "git::ssh://git@bitbucket.org/morea/terraform.feature.datadog.git//middleware/php-fpm?ref={revision}"

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

-Purpose
-------
-Creates a DataDog monitors with the following checks :
+## Purpose

-* PHP FPM connect
-* PHP FPM load
+Creates DataDog monitors with the following checks :

-Inputs
------
+- php_fpm busy worker
+- Can't connect to php-fpm
+
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -39,15 +37,13 @@ Inputs
 | php_fpm_connect_message | Custom message for PHP FPM process monitor | string | `` | no |
 | php_fpm_connect_silenced | Groups to mute for PHP FPM process monitor | map | `<map>` | no |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
 | datadog_fpm_process_id | id for monitor datadog_fpm_process |
 | datadog_php_fpm_connect_idle_id | id for monitor datadog_php_fpm_connect_idle |

-Related documentation
---------------------
+## Related documentation

-DataDog documentation:
+DataDog documentation: [https://docs.datadoghq.com/integrations/php_fpm/](https://docs.datadoghq.com/integrations/php_fpm/)
--- a/system/generic/README.md
+++ b/system/generic/README.md
@ -1,30 +1,28 @@
-System Generic DataDog monitors
-===============================
+# SYSTEM GENERIC DataDog monitors

-How to use this module
----------------------
+## How to use this module

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

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

-Purpose
-------
-Creates a DataDog monitors with the following checks :
+## Purpose

-* CPU usage
-* CPU load ratio
-* Free memory
-* Free disk inodes
-* Free disk space
+Creates DataDog monitors with the following checks :

-Inputs
------
+- CPU usage
+- CPU load 5
+- Free disk space
+- Free disk inodes
+- Free memory
+
+## Inputs

 | Name | Description | Type | Default | Required |
 |------|-------------|:----:|:-----:|:-----:|
@ -64,8 +62,7 @@ Inputs
 | free_memory_timeframe | Monitor timeframe for Free memory [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_5m` | no |
 | message | Message sent when an alert is triggered | string | - | yes |

-Outputs
-------
+## Outputs

 | Name | Description |
 |------|-------------|
@ -75,7 +72,6 @@ Outputs
 | datadog_free_memory_id | id for monitor datadog_free_memory |
 | datadog_load_too_high_id | id for monitor datadog_load_too_high |

-Related documentation
---------------------
+## Related documentation

 DataDog documentation: