MON-271 threshold adjustment for fragmentation ratio

This commit is contained in:
Quentin Manfroi 2018-08-13 10:05:30 +02:00
parent 3d44f7d144
commit 9a35aee91c
2 changed files with 4 additions and 4 deletions

View File

@ -73,8 +73,8 @@ Creates DataDog monitors with the following checks:
| latency_timeframe | Monitor timeframe for Redis latency [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_5m` | no |
| mem_frag_message | Custom message for Redis memory RAM fragmentation monitor | string | `` | no |
| mem_frag_silenced | Groups to mute for Redis memory RAM fragmentation monitor | map | `<map>` | no |
| mem_frag_threshold_critical | memory RAM fragmentation limit (critical threshold) | string | `130` | no |
| mem_frag_threshold_warning | memory RAM fragmentation limit (warning threshold) | string | `100` | no |
| mem_frag_threshold_critical | memory RAM fragmentation limit (critical threshold) | string | `150` | no |
| mem_frag_threshold_warning | memory RAM fragmentation limit (warning threshold) | string | `130` | no |
| mem_frag_time_aggregator | Monitor aggregator for Redis memory RAM fragmentation [available values: min, max or avg] | string | `min` | no |
| mem_frag_timeframe | Monitor timeframe for Redis memory RAM fragmentation [available values: `last_#m` (1, 5, 10, 15, or 30), `last_#h` (1, 2, or 4), or `last_1d`] | string | `last_5m` | no |
| mem_used_message | Custom message for Redis RAM memory used monitor | string | `` | no |

View File

@ -230,12 +230,12 @@ variable "mem_frag_timeframe" {
variable "mem_frag_threshold_critical" {
description = "memory RAM fragmentation limit (critical threshold)"
default = 130
default = 150
}
variable "mem_frag_threshold_warning" {
description = "memory RAM fragmentation limit (warning threshold)"
default = 100
default = 130
}
variable "rejected_con_silenced" {