Merge branch 'MON-392_fix_readmes' into 'master'

Resolve MON-392 "Fix readmes"

Closes MON-392

See merge request claranet/pt-monitoring/projects/datadog/terraform/monitors!23

caas/kubernetes/ark/README.md

@@ -17,6 +17,7 @@ module "datadog-monitors-caas-kubernetes-ark" {
 Creates DataDog monitors with the following checks:
 
 - Ark backup failed
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |
@@ -41,14 +42,13 @@ Creates DataDog monitors with the following checks:
 |------|-------------|
 | ark\_schedules\_monitor\_id | id for monitor ark_schedules_monitor |
 
-Related documentation
+## Related documentation
----------------------
 
 DataDog blog: https://www.datadoghq.com/blog/monitor-prometheus-metrics
 Heptio Ark minimum release: https://github.com/heptio/ark/releases/tag/v0.9.0
 
-Ark annotations for Datadog
+## Ark annotations for Datadog
----------------------------
+
 ```
 apiVersion: apps/v1beta1
 kind: Deployment

caas/kubernetes/ingress/vts/README.md

@@ -18,6 +18,7 @@ Creates DataDog monitors with the following checks:
 
 - Nginx Ingress 4xx errors
 - Nginx Ingress 5xx errors
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |
@@ -54,16 +55,15 @@ Creates DataDog monitors with the following checks:
 | nginx\_ingress\_too\_many\_4xx\_id | id for monitor nginx_ingress_too_many_4xx |
 | nginx\_ingress\_too\_many\_5xx\_id | id for monitor nginx_ingress_too_many_5xx |
 
-Related documentation
+## Related documentation
----------------------
 
 DataDog blog: https://www.datadoghq.com/blog/monitor-prometheus-metrics
 https://github.com/kubernetes/ingress-nginx/pull/423/commits/1d38e3a38425f08de2f75fcae13896a3fec4d144
 
-Nginx Ingress Controller setup
+## Nginx Ingress Controller setup
-------------------------------
+
 This configuration and monitors only work for ingress controller version :
-- >= 0.10 because ingress is beta before that and metrics naming convention not stable
+- \>= 0.10 because ingress is beta before that and metrics naming convention not stable
 - <= 0.15 because ingress does not use VTS metrics since 0.16
 Enable the following flags in the Nginx Ingress Controller chart
 controller.stats.enabled=true,controller.metrics.enabled=true

cloud/aws/alb/README.md

@@ -22,6 +22,7 @@ Creates DataDog monitors with the following checks:
 - ALB latency
 - ALB target HTTP code 4xx
 - ALB target HTTP code 5xx
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/aws/apigateway/README.md

@@ -19,6 +19,7 @@ Creates DataDog monitors with the following checks:
 - API Gateway HTTP 4xx errors
 - API Gateway HTTP 5xx errors
 - API Gateway latency
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/aws/elasticache/common/README.md

@@ -22,6 +22,7 @@ Creates DataDog monitors with the following checks:
 - Elasticache free memory
 - Elasticache max connections reached
 - Elasticache swap
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |
@@ -88,8 +89,7 @@ Creates DataDog monitors with the following checks:
 | elasticache\_no\_connection\_id | id for monitor elasticache_no_connection |
 | elasticache\_swap\_id | id for monitor elasticache_swap |
 
-Related documentation
+## Related documentation
----------------------
 
 DataDog documentation: [https://docs.datadoghq.com/integrations/amazon_elasticache/](https://docs.datadoghq.com/integrations/amazon_elasticache/)
 

cloud/aws/elasticache/memcached/README.md

@@ -18,6 +18,7 @@ Creates DataDog monitors with the following checks:
 
 - Elasticache memcached cache hit ratio
 - Elasticache memcached CPU
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |
@@ -53,8 +54,7 @@ Creates DataDog monitors with the following checks:
 | memcached\_cpu\_high\_id | id for monitor memcached_cpu_high |
 | memcached\_get\_hits\_id | id for monitor memcached_get_hits |
 
-Related documentation
+## Related documentation
----------------------
 
 DataDog documentation:
 

cloud/aws/elasticache/redis/README.md

@@ -20,6 +20,7 @@ Creates DataDog monitors with the following checks:
 - Elasticache redis CPU
 - Elasticache redis is receiving no commands
 - Elasticache redis replication lag
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/aws/elasticsearch/README.md

@@ -8,6 +8,8 @@ module "datadog-monitors-cloud-aws-elasticsearch" {
 
   environment = "${var.environment}"
   message     = "${module.datadog-message-alerting.alerting-message}"
+
+  es_cluster_volume_size = 42
 }
 
 ```
@@ -19,6 +21,7 @@ Creates DataDog monitors with the following checks:
 - ElasticSearch cluster CPU high
 - ElasticSearch cluster free storage space
 - ElasticSearch cluster status is not green
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/aws/elb/README.md

@@ -22,6 +22,7 @@ Creates DataDog monitors with the following checks:
 - ELB backend 5xx errors too high
 - ELB healthy instances
 - ELB latency too high
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/aws/kinesis-firehose/README.md

@@ -17,6 +17,7 @@ module "datadog-monitors-cloud-aws-kinesis-firehose" {
 Creates DataDog monitors with the following checks:
 
 - Kinesis Firehose No incoming records
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/aws/rds/aurora/mysql/README.md

@@ -17,6 +17,7 @@ module "datadog-monitors-cloud-aws-rds-aurora-mysql" {
 Creates DataDog monitors with the following checks:
 
 - RDS Aurora Mysql replica lag
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/aws/rds/aurora/postgresql/README.md

@@ -17,6 +17,7 @@ module "datadog-monitors-cloud-aws-rds-aurora-postgresql" {
 Creates DataDog monitors with the following checks:
 
 - RDS Aurora PostgreSQL replica lag
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/aws/rds/common/README.md

@@ -19,6 +19,7 @@ Creates DataDog monitors with the following checks:
 - RDS instance CPU high
 - RDS instance free space
 - RDS replica lag
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/aws/vpn/README.md

@@ -17,6 +17,7 @@ module "datadog-monitors-cloud-aws-vpn" {
 Creates DataDog monitors with the following checks:
 
 - VPN tunnel down
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/azure/apimanagement/README.md

@@ -21,6 +21,7 @@ Creates DataDog monitors with the following checks:
 - API Management too many failed requests
 - API Management too many other requests
 - API Management too many unauthorized requests
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/azure/app-services/README.md

@@ -21,6 +21,7 @@ Creates DataDog monitors with the following checks:
 - App Services HTTP successful responses too low
 - App Services memory usage
 - App Services response time too high
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/azure/cosmosdb/README.md

@@ -20,6 +20,7 @@ Creates DataDog monitors with the following checks:
 - Cosmos DB 5xx requests rate is high
 - Cosmos DB is down
 - Cosmos DB max scaling reached for collection
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |
@@ -71,8 +72,7 @@ Creates DataDog monitors with the following checks:
 | cosmos\_db\_scaling\_id | id for monitor cosmos_db_scaling |
 | cosmos\_db\_status\_id | id for monitor cosmos_db_status |
 
-Related documentation
+## Related documentation
----------------------
 
 DataDog documentation : [https://docs.datadoghq.com/integrations/azure/](https://docs.datadoghq.com/integrations/azure/)  
 You must search `cosmosdb`, there is no integration for now.

cloud/azure/datalakestore/README.md

@@ -17,6 +17,7 @@ module "datadog-monitors-cloud-azure-datalakestore" {
 Creates DataDog monitors with the following checks:
 
 - Datalake Store is down
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |
@@ -41,8 +42,7 @@ Creates DataDog monitors with the following checks:
 |------|-------------|
 | datalakestore\_status\_id | id for monitor datalakestore_status |
 
-Related documentation
+## Related documentation
----------------------
 
 DataDog documentation : [https://docs.datadoghq.com/integrations/azure/](https://docs.datadoghq.com/integrations/azure/)  
 You must search `datalake`, there is no integration for now.

cloud/azure/eventhub/README.md

@@ -19,6 +19,7 @@ Creates DataDog monitors with the following checks:
 - Event Hub is down
 - Event Hub too many errors
 - Event Hub too many failed requests
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/azure/iothubs/README.md

@@ -30,6 +30,7 @@ Creates DataDog monitors with the following checks:
 - IOT Hub Too many list_jobs failure
 - IOT Hub Too many query_jobs failed
 - IOT Hub Total devices is wrong
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/azure/keyvault/README.md

@@ -19,6 +19,7 @@ Creates DataDog monitors with the following checks:
 - Key Vault API latency is high
 - Key Vault API result rate is low
 - Key Vault is down
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |
@@ -61,8 +62,7 @@ Creates DataDog monitors with the following checks:
 | keyvault\_api\_result\_id | id for monitor keyvault_api_result |
 | keyvault\_status\_id | id for monitor keyvault_status |
 
-Related documentation
+## Related documentation
----------------------
 
 DataDog documentation : [https://docs.datadoghq.com/integrations/azure/](https://docs.datadoghq.com/integrations/azure/)  
 You must search `keyvault`, there is no integration for now.

cloud/azure/mysql/README.md

@@ -21,6 +21,7 @@ Creates DataDog monitors with the following checks:
 - Mysql Server IO consumption
 - Mysql Server memory usage
 - Mysql Server storage
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |
@@ -80,8 +81,7 @@ Creates DataDog monitors with the following checks:
 | mysql\_memory\_usage\_id | id for monitor mysql_memory_usage |
 | mysql\_no\_connection\_id | id for monitor mysql_no_connection |
 
-Related documentation
+## Related documentation
----------------------
 
 DataDog documentation: [https://docs.datadoghq.com/integrations/azure/](https://docs.datadoghq.com/integrations/azure/)
 You have to search `mysql`

cloud/azure/postgresql/README.md

@@ -21,6 +21,7 @@ Creates DataDog monitors with the following checks:
 - Postgresql Server IO consumption
 - Postgresql Server memory usage
 - Postgresql Server storage
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |
@@ -80,8 +81,7 @@ Creates DataDog monitors with the following checks:
 | postgresql\_memory\_usage\_id | id for monitor postgresql_memory_usage |
 | postgresql\_no\_connection\_id | id for monitor postgresql_no_connection |
 
-Related documentation
+## Related documentation
----------------------
 
 DataDog documentation: [https://docs.datadoghq.com/integrations/azure/](https://docs.datadoghq.com/integrations/azure/)
 You have to search `mysql`

cloud/azure/redis/README.md

@@ -20,6 +20,7 @@ Creates DataDog monitors with the following checks:
 - Redis processor time too high
 - Redis server load too high
 - Redis too many evictedkeys
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/azure/serverfarms/README.md

@@ -19,6 +19,7 @@ Creates DataDog monitors with the following checks:
 - Serverfarm CPU percentage is too high
 - Serverfarm is down
 - Serverfarm memory percentage is too high
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/azure/servicebus/README.md

@@ -20,6 +20,7 @@ Creates DataDog monitors with the following checks:
 - Service Bus is down
 - Service Bus server errors rate is high
 - Service Bus user errors rate is high
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/azure/sql-database/README.md

@@ -21,6 +21,7 @@ Creates DataDog monitors with the following checks:
 - SQL Database DTU Consumption too high
 - SQL Database is down
 - SQL Database low free space
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/azure/storage/README.md

@@ -25,6 +25,7 @@ Creates DataDog monitors with the following checks:
 - Azure Storage too many server_other errors
 - Azure Storage too many throttling errors
 - Azure Storage too many timeout errors
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/azure/stream-analytics/README.md

@@ -21,6 +21,7 @@ Creates DataDog monitors with the following checks:
 - Stream Analytics too many conversion errors
 - Stream Analytics too many failed requests
 - Stream Analytics too many runtime errors
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/gcp/big-query/README.md

@@ -25,6 +25,7 @@ Creates DataDog monitors with the following checks:
 - GCP Big Query Table Count
 - GCP Big Query Uploaded Bytes Billed
 - GCP Big Query Uploaded Bytes
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/gcp/cloud-sql/common/README.md

@@ -22,6 +22,7 @@ Creates DataDog monitors with the following checks:
 - Cloud SQL Failover Unavailable
 - Cloud SQL Memory Utilization forecast
 - Cloud SQL Memory Utilization
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/gcp/cloud-sql/mysql/README.md

@@ -17,6 +17,7 @@ module "datadog-monitors-cloud-gcp-cloud-sql-mysql" {
 Creates DataDog monitors with the following checks:
 
 - Cloud SQL MySQL Replication Lag
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/gcp/lb/README.md

@@ -21,6 +21,7 @@ Creates DataDog monitors with the following checks:
 - GCP LB bucket backend latency
 - GCP LB Requests count increased abruptly
 - GCP LB service backend latency
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

cloud/gcp/pubsub/README.md

@@ -18,6 +18,7 @@ Creates DataDog monitors with the following checks:
 
 - GCP pubsub sending messages operations
 - GCP pubsub sending messages with result unavailable
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |
@@ -50,8 +51,7 @@ Creates DataDog monitors with the following checks:
 | sending\_operations\_count\_id | id for monitor sending_operations_count |
 | unavailable\_sending\_operations\_count\_id | id for monitor unavailable_sending_operations_count |
 
-Related documentation
+## Related documentation
-------------
 
 * [GCP Pub/Sub Metrics](https://cloud.google.com/monitoring/api/metrics_gcp#gcp-pubsub)
 * [Datadog GCP Pub/Sub integration](https://docs.datadoghq.com/integrations/google_cloud_pubsub/)

database/elasticsearch/README.md

@@ -38,6 +38,7 @@ Creates DataDog monitors with the following checks:
 - Elasticsearch JVM memory Old usage
 - Elasticsearch JVM memory Young usage
 - Elasticsearch number of current open HTTP connections anomaly detected
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

database/mongodb/README.md

@@ -20,6 +20,7 @@ Creates DataDog monitors with the following checks:
 - MongoDB replication lag
 - MongoDB secondary missing
 - MongoDB too much servers or wrong monitoring config
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

database/mysql/README.md

@@ -24,6 +24,7 @@ Creates DataDog monitors with the following checks:
 - Mysql server does not respond
 - Mysql Slow queries
 - Mysql threads changed abnormally
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |
@@ -123,7 +124,6 @@ Creates DataDog monitors with the following checks:
 | mysql\_slow\_id | id for monitor mysql_slow |
 | mysql\_threads\_anomaly\_id | id for monitor mysql_threads_anomaly |
 
-Related documentation
+## Related documentation
----------------------
 
 DataDog documentation: [https://docs.datadoghq.com/integrations/mysql/](https://docs.datadoghq.com/integrations/mysql/)

database/postgresql/README.md

@@ -19,6 +19,7 @@ Creates DataDog monitors with the following checks:
 - PostgreSQL Connections
 - PostgreSQL server does not respond
 - PostgreSQL too many locks
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |
@@ -61,7 +62,6 @@ Creates DataDog monitors with the following checks:
 | postgresql\_connection\_too\_high\_id | id for monitor postgresql_connection_too_high |
 | postgresql\_too\_many\_locks\_id | id for monitor postgresql_too_many_locks |
 
-Related documentation
+## Related documentation
----------------------
 
 DataDog documentation: [https://docs.datadoghq.com/integrations/postgres/](https://docs.datadoghq.com/integrations/postgres/)

database/redis/README.md

@@ -26,6 +26,7 @@ Creates DataDog monitors with the following checks:
 - Redis memory fragmented
 - Redis memory used
 - Redis rejected connections
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

middleware/apache/README.md

@@ -17,6 +17,7 @@ module "datadog-monitors-middleware-apache" {
 Creates DataDog monitors with the following checks:
 
 - Apache vhost status does not respond
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

middleware/nginx/README.md

@@ -18,6 +18,7 @@ Creates DataDog monitors with the following checks:
 
 - Nginx dropped connections
 - Nginx vhost status does not respond
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

middleware/php-fpm/README.md

@@ -18,6 +18,7 @@ Creates DataDog monitors with the following checks:
 
 - Php-fpm busy worker
 - Php-fpm ping url does not respond
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

scripts/02_update_readme.sh

@@ -90,6 +90,7 @@ EOF
         echo "- ${name/could reach/forecast}" >> README.md
     done
     IFS=$SAVEIFS
+    echo >> README.md
     # auto generate terraform docs (inputs and outputs)
     terraform-docs --with-aggregate-type-defaults md table ./ >> README.md
     # if README does not exist

system/generic/README.md

@@ -8,6 +8,8 @@ module "datadog-monitors-system-generic" {
 
   environment = "${var.environment}"
   message     = "${module.datadog-message-alerting.alerting-message}"
+
+  free_memory_message = "${module.datadog-message-alerting.alerting-message-bh-only}"
 }
 
 ```
@@ -22,6 +24,7 @@ Creates DataDog monitors with the following checks:
 - Free disk inodes
 - Free disk space
 - Free memory
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |

system/unreachable/README.md

@@ -17,6 +17,7 @@ module "datadog-monitors-system-unreachable" {
 Creates DataDog monitors with the following checks:
 
 - Host unreachable
+
 ## Inputs
 
 | Name | Description | Type | Default | Required |