-
Notifications
You must be signed in to change notification settings - Fork 1
/
no_active_controllers-variables.tf
55 lines (44 loc) · 1.52 KB
/
no_active_controllers-variables.tf
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
variable "no_active_controllers_enabled" {
type = bool
default = true
}
variable "no_active_controllers_warning" {
type = number
default = 0
}
variable "no_active_controllers_critical" {
type = number
default = 1
}
variable "no_active_controllers_evaluation_period" {
type = string
default = "last_5m"
}
variable "no_active_controllers_note" {
type = string
default = ""
}
variable "no_active_controllers_docs" {
type = string
default = <<EOFF
The first node to boot in a Kafka cluster automatically becomes the controller, and there can be only one. The controller in a Kafka cluster is responsible for maintaining the list of partition leaders, and coordinating leadership transitions (in the event a partition leader becomes unavailable). If it becomes necessary to replace the controller, ZooKeeper chooses a new controller randomly from the pool of brokers. The sum of ActiveControllerCount across all of your brokers should always equal one, and you should alert on any other value that lasts for longer than one second.
https://www.datadoghq.com/blog/monitoring-kafka-performance-metrics/
EOFF
}
variable "no_active_controllers_filter_override" {
type = string
default = ""
}
variable "no_active_controllers_alerting_enabled" {
type = bool
default = true
}
variable "no_active_controllers_require_full_window" {
type = bool
default = true
}
variable "no_active_controllers_priority" {
description = "Number from 1 (high) to 5 (low)."
type = number
default = 2
}