# DATABASES MONGODB DataDog monitors ## How to use this module ``` 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}" } ``` ## Purpose Creates DataDog monitors with the following checks: - MongoDB primary state - MongoDB secondary missing - MongoDB too much servers or wrong monitoring config - MongoDB replication lag ## Inputs | Name | Description | Type | Default | Required | |------|-------------|:----:|:-----:|:-----:| | environment | Architecture Environment | string | - | yes | | evaluation_delay | Delay in seconds for the metric evaluation | string | `15` | no | | 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_desired_servers_count | Number of servers that should be instanciated for this cluster | string | `3` | no | | mongodb_lag_critical | Critical replication lag in s | string | `5` | no | | mongodb_lag_warning | Warn replication lag in s | string | `2` | no | | mongodb_primary_aggregator | Monitor aggregator for MongoDB primary state [available values: min, max] | string | `max` | no | | mongodb_primary_message | Custom message for MongoDB primary monitor | string | `` | no | | mongodb_primary_silenced | Groups to mute for MongoDB primary state monitor | map | `` | no | | mongodb_primary_timeframe | Monitor timeframe for MongoDB wrong state for primary node [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_1m` | no | | mongodb_replication_aggregator | Monitor aggregator for MongoDB replication lag [available values: min, max, sum or avg] | string | `avg` | no | | mongodb_replication_message | Custom message for MongoDB replication monitor | string | `` | no | | mongodb_replication_silenced | Groups to mute for MongoDB replication lag monitor | map | `` | no | | mongodb_replication_timeframe | Monitor timeframe for MongoDB replication lag [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_1m` | no | | mongodb_secondary_aggregator | Monitor aggregator for MongoDB secondary state [available values: min, max] | string | `max` | no | | mongodb_secondary_message | Custom message for MongoDB secondary monitor | string | `` | no | | mongodb_secondary_silenced | Groups to mute for MongoDB secondary state monitor | map | `` | no | | mongodb_secondary_timeframe | Monitor timeframe for MongoDB wrong state for secondaries nodes [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_5m` | no | | mongodb_server_count_aggregator | Monitor aggregator for MongoDB server count [available values: min, max] | string | `min` | no | | mongodb_server_count_message | Custom message for MongoDB server count | string | `` | no | | mongodb_server_count_silenced | Groups to mute for MongoDB server count monitor | map | `` | no | | mongodb_server_count_timeframe | Monitor timeframe for MongoDB wrong server count [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_15m` | no | | new_host_delay | Delay in seconds before monitor new resource | string | `300` | no | ## Outputs | Name | Description | |------|-------------| | mongodb_primary_id | id for monitor mongodb_primary | | mongodb_replication_id | id for monitor mongodb_replication | | mongodb_secondary_id | id for monitor mongodb_secondary | | mongodb_server_count_id | id for monitor mongodb_server_count | ## Related documentation DataDog documentation: [https://docs.datadoghq.com/integrations/mongo/](https://docs.datadoghq.com/integrations/mongo/) MongoDB documentation: [https://docs.mongodb.com/manual/administration/monitoring/](https://docs.mongodb.com/manual/administration/monitoring/)